WO2013034953A1

WO2013034953A1 - Locating system and method for taxi drivers and passengers

Info

Publication number: WO2013034953A1
Application number: PCT/IB2011/053883
Authority: WO
Inventors: Anthony Koh BENG KIOK; Kim MOON SOO
Original assignee: Mobile Credit Payment Pte Ltd
Priority date: 2011-09-06
Filing date: 2011-09-06
Publication date: 2013-03-14
Also published as: PH12014500495A1; CN103959355A; AU2012304946A1; WO2013036199A1

Abstract

A Location-Based Service (LBS) is a mobile computing application that provides services to users based on their geographical location. The present invention relates to a system and method for a peer-to-peer (passenger-to-taxi driver or Taxi driver-to-passenger) locating system in the taxi transportation sector and uses a LBS for real-time, interactive 'taxi-hailing' and 'Passenger- Locating'. The LBS uses functionality such as 'find the nearby taxis' and 'tell me if the taxi is hired or booked within my vicinity.' The present invention relates to a system and method in the taxi transportation sector addressing these issues, namely, passengers in need of a taxi 'hail- a-cab', taxi drivers searching for potential passengers 'locate-a-passenger' and the inefficiency of the call centers system operate by taxi companies.

Description

LOCATING SYSTEM AND METHOD FOR TAXI DRIVERS AND PASSENGERS

[0001] The present invention relates to a locating system and method between taxi drivers and passengers. A system and method for a peer-to-peer (passenger-to-taxi driver or Taxi driver-to-passenger) locating system in the taxi transportation sector generally and more particularly to a method and system for a taxi passenger to hail a taxi in real-time and interactive manner using a location-based service enabled mobile device and similarly, for a taxi driver to locate potential taxi passengers in a locality or vicinity and subsequently, transacting payment.

[0002] Location-based Services are well-known to the practitioners in the field. The present invention relates to a locating system and method between taxi drivers and passengers. A system and method for a peer-to-peer transaction system generally.

[0003] Traditionally, a taxi passenger has to wait at the taxi stand or along the roadside to wait for the arrival of the taxi. The taxi passenger is unsure the duration of the wait before the arrival of a taxi. Similarly, a taxi driver usually drives around to locate a potential taxi passenger. This results in a waste of time and resources trying to locate a taxi passenger.

[0004] Conventional method to solving this problem is to setup a call center administering the calls for taxi booking. A taxi passenger may call the taxi booking hotline to book for a taxi. As technology advances, more types of platforms such as sms, emails and web booking are supported by the call centers. That is, a taxi passenger may book for a taxi through these available methods provided by the call center. The call center is usually manned by the taxi company. As there are many taxi companies in the market and each taxi company has a different taxi fleet size in the market. This result in many call centers with different hotline numbers available in the market. Hence, passengers need to remember the various taxi booking hotline number available in the market. Taxi companies with a bigger fleet tend to dominate the market and their call center's hotline usually is more popular than the smaller taxi companies. During peak hours, the more popular call center will be jammed with calls. The call center becomes a bottleneck for processing calls for taxi booking while other taxi drivers from less popular call centers are on the road roaming around aimlessly looking around for potential passengers. This results in an unfair competition among taxis companies.

[0005] As a call center is costly to maintain, a taxi company with a small taxi fleet size faces problems operating a call center. Hence, in order to cover the cost of operating the call centers, the cost is passed backed to the Passenger via taxi booking fee which currently a source of income to the taxi company and the taxi driver.

[0006] Taxi booking via phone calls or sms to the taxi booking call center are well known in the art. Generally, booking of a taxi is done through calling a designated taxi hotline number which routes to the taxi call center managed by the taxi company. In the context of Singapore, there is a booking fee levied on the taxi passenger for using this service while an impromptu taxi hailing is free.

[0007] Earlier method of solving this problem includes a Location-Based Service that resides in smart mobile device or smartphone such as iPhones, android-enabled phones, that assists taxi passenger to book for a taxi. This method, nevertheless, is an extension of the service provided by the call center where the mobile application is integrated to the call center system or conduct an autodial to the call center booking system. This system inherits the problem of the call center as the bottleneck where its efficiency depends greatly on the processing capability.

[0008] For call center method of booking, the usual practice is the passenger communicates with the staff of the call center and the staff of the call center communicates with the taxi driver. There is usually no direct contact between the passenger and the driver. Upon confirmation of booking, the taxi vehicle number and estimate time of arrival is then sent to the passenger. Other details of the taxi are not made known to the passenger and the passenger is not free to choose the choice of the taxi.

[0009] Depending on location of the taxi that responds to the call center for the passenger job request, it may not be the nearest taxi to the passenger available at the instant.

[0010] For the foregoing reasons, there is a need for a real-time, location-based and peer-to-peer interactive method and system between the taxi passenger and the taxi driver, particularly for the passenger to hail for a taxi and the taxi driver to locate the taxi passenger, that overcomes the limitations of the prior art and provides mobility and convenience to the taxi passenger and taxi drivers.

[0011] The Present invention such enhanced system and method capabilities and addresses , in new and innovative ways, various of the (not insubstantial) challenges that are associated with the same.

Summary

[0012] A method is provided for a taxi passenger to 'hail-a-taxi' real-time using a smartphone via a Location-Based Service (LBS) enabled smartphone by locating the taxi s in the vicinity. Using the LBS, the taxi passenger is able to locate visually the numbers of taxis available in the vicinity. The passenger is further able to access the application server via the internet, information on trips, retrieve and check past traveling records, payment records and receipts.

[0013] A method is provided for a taxi driver to 'locate-a-taxi passenger' real-time using a smartphone via a Location-Based Service (LBS) by locating the passenger in the vicinity. It is, therefore, an object of the present invention to provide a real-time, interactive and location-based 'locate-a-passenger' system. The taxi driver is further able to access the application server via the internet, information on trips, retrieve and check past traveling records, payment records on taxi fares and receipts.

[0014] A system is provided for the LBS mobile application in the passenger smartphone communicating with LBS mobile application of taxi driver via the server application for the passenger to hail a taxi real-time. Using the LBS mobile application, taxi passengers are able to 'hail-a-taxi' of their choice by locating visually the numbers of taxis available in the vicinity, send a job request, track the movement of the taxi and transacting payments.

[0015] A system is provided for the LBS mobile application in the taxi driver's smartphone communicating with LBS mobile application in the Passenger's smartphone via the Application Server for the Taxi driver to locate its potential passenger in real-time. Using the LBS mobile application, taxi drivers are able to 'locate-a-passenger' of their choice by locating visually the numbers of taxis available in the vicinity, send them a service request, allow tracking of the taxi movement and transacting payments.

[0016] There is thus provided in accordance with a preferred embodiment of the present invention of a real-time, interactive taxi locating system comprises of a location-based service enabled mobile device, an Application Server. Further, in a preferred embodiment, the location-based service enabled mobile device is installed with a LBS mobile application that communicates with the Application Server.

[0017] The features, functions, and advantages that have been discussed can be achieved independently in various embodiments of the present invention or may be combined in yet other embodiments further details of which can be seen with reference to the following descriptions and drawings.

Description of Drawings

[0018] The present invention will be understood and appreciated more fully from the following detailed description, taken in conjunction with the drawings in which;

[0019] FIG. 1 illustrates one overview of a passenger -to-driver services employed in one embodiment of the present invention;

[0020] FIG.2 illustrates a typical network architecture employed in second embodiment of the present invention;

[0021] FIG.3 illustrates a typical passenger-to-driver services process employed in third embodiment of the present invention;

[0022] FIG.4 illustrates a typical passenger-to-driver transaction flowchart employed in fourth embodiment of the present invention;

[0023] FIG.5 is a diagram illustrating a graphical user interface (GUI) for hailing a taxi in the fifth embodiment of the present invention;

[0024] FIG. 6 illustrates a typical logical process flowchart employed in sixth embodiment of the present invention;

[0025] FIG. 7 illustrates a typical block module architecture of an application server employed in seventh embodiment of the present invention;

[0026] FIG. 8 illustrates a typical block module architecture of a mobile LBS application employed in eighth embodiment of the present invention;

BEST MODE

Illustration of the Preferred Embodiment of the Invention

[0027] Describe below is the best mode of the present invention a system and method for a taxi passenger to hail for a taxi and similarly, for a taxi driver to locate its potential passenger. Throughout the description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, to one skilled in the art that the present invention may be practiced without some of these specific details.

Overview of a Passenger -to-Driver services

[0028] FIG 1 illustrates the overview of the passenger-to-taxi driver client services of one preferred embodiment of the present invention. The passenger-to-driver client services is a peer-to-peer location-based services FIG 1where the user (passenger or taxi driver) has full control over his location information.

Network Architecture Diagram

[0029] A preferred embodiment of the present invention is broadly illustrated in network architecture diagram of FIG. 2 which illustrates a typical network architecture. FIG. 2 also illustrates the typical transaction process of the LBS Mobile Application 180 and the Application Server 130.

[0030] With continuing reference to FIG 2, where a preferred embodiment of the Typical Network Architecture Diagram is illustrated, comprises a Payment Solution Server 120,

Application Server

130, a passenger mobile device with a LBS mobile application 110, a taxi driver mobile device with a LBS mobile application 150, local fixed and mobile carrier 210, Network 220, GPS Satellite 230 and wireless carrier.

Typical Passenger-to-Driver Services Process

[0031] FIG.3 illustrates a typical passenger-to-driver services process in third embodiment of the present invention. The User, namely the passenger or the taxi driver, downloads the relevant LBS Mobile Application depending on the types of mobile device the user possessed. The most commonly used smartphones in current times are Apple's iphones, Google's android phones and Blackberry's smartphones 300. The user then registers via its smartphone as a Passenger 310 or Taxi Driver 350. Thereafter, upon running the application, the location status of the passenger is set to 'ON' 311, a registered passenger may use the LBS mobile application to search and display for taxis available 312 within the radar range specified. The passenger may also view the taxi drivers' details 313 which consists information such as company details, vehicle details and the other details such as rating, comments etc. The graphical representation of the taxis vehicles will be displayed on the passenger's mobile device. Upon reviewing the taxi details, the passenger is free to choose the taxi he preferred and send a request to the taxi driver 314. The job request consists of the Passenger current location and his desired destination. The Taxi driver may choose to reject or accept the job request received. If the taxi driver rejects the job request, the passenger will then have to choose his next choice. Once the taxi driver accepts the job request 315, the Passenger's Location status will be turned 'OFF' 316 and the passenger will receive a confirmation message through SMS or the LBS Mobile Application 317. Both the Passenger and the taxi driver will then be disappeared (turn offline) from the available user list. But the passenger is able to track the movement of the 'hailed' taxi real-time visually via the maps and routing modules of the LBS Application on his mobile device 318. When the passenger boards the taxi, the passenger will receive an service fee payment acknowledgement request 320. When the Passenger acknowledges, the services process completes 321

[0032] Similarly, the Taxi driver may play an active role is searching for his potential passengers in the vicinity using his mobile device through the LBS Mobile Application. As a user, the taxi driver is required to register his role as a taxi driver 350. Upon running the application 351, as a registered taxi driver, he may play and active role in searching for potential passengers 352 and need not wait for passengers to sent him job request. The Taxi Driver may view the passenger's details 353 displayed in the profile before sending the passenger offering his service request 354. The Passenger may choose to reject the service request or accept the offer 355. Once the Passenger accepts the service request, the Taxi Driver location status will be turn 'OFF' 356 and he will receive a confirmation message through SMS or the LBS Mobile Application 357. Both the Passenger and the taxi driver will then be disappeared (turn offline) from the available user list. However, the taxi driver is still able to view the location of the passenger 358 till he reach is location to pick him up unless a cancellation request is received. When the taxi driver picks up the passenger 359, he will send out a 'picked up' message and request service payment acknowledgement 360 to the passenger requesting for acknowledgement. Upon receiving the acknowledgement, the service process completes 361.

Typical Passenger-to-Driver Transaction Flowchart

[0033] By way of further explanation, the flowchart of FIG. 4 illustrates a typical passenger-to-driver transaction flow in accordance with the current example system. This example on transaction flow is shown from the perspective of a passenger hailing a cab or taxi using his mobile device. First, the passenger requests for displaying all available taxis nearby 401. The request is send from the LBS Mobile Application in the passenger smartphone 110 to the application server 130 which then request the location information from the LBS Mobile Application of the taxi driver 150, the location of the taxi was then returned to the application server 403 and determined before being displayed in the passenger's mobile device 404.

[0034] Next, the Passenger requests the service of the taxi of his choice from his smartphone and sent the taxi driver a job request 405. The taxi driver acceptance was returned as a confirmation to the passenger mobile device and his location status turns 'OFF' 406. Upon picking the passenger up, the driver initiates a service fee request to the passenger through the application server 407. The passenger receives the service fee acknowledgement request on his mobile device 408. Upon boarding the taxi, the passenger acknowledges that the taxi has arrives and service completes 409. The application server will initiate a payment request to the payment solution server to charge the service fee to the passenger's credit cards 410. The service fee will be paid to the driver to complete the transaction process 411.

Typical LBS Mobile Application

[0035] FIG. 5 illustrates a typical scenario for 'Hail-A-Cab' LBS mobile application graphical user interface (GUI) process for user registered as passenger. For example, a passenger may begin the process of hailing a cab by activating the mobile application in his smart mobile device. Assumption is made that the user is a registered passenger and wanting to catch a taxi to a desired destination.

[0036] The passenger starts the LBS Mobile Application called 'Hail-A-Cab' and his status is set to online, that is visible to taxi drivers searching for passengers. The Passenger enters his trip information and search for available taxis in the vicinity as in 511. Available taxis are represented by symbols, graphical Icons or any other representations deem fit on its current location on the map applications. The passenger is also able to view details of the taxis represented by graphical icons. The graphical Icons shall have properties and attributes such as colors, numbers etc to represent types of taxis, the number of taxis at that locations.

[0037] Taxi details can be viewed as in 512 showing registered taxi drivers details comprises of the type of taxis, taxi company, registered vehicle number, taxi fare, payment types available, language spoken and other relevant information such as user ratings and comments.

[0038] Prior to sending a job request, the Passenger is able to enter trip information, type of payments and other preferences as in 513. A confirmation screen as shown is will be display in 514 before sending the job request to the taxi driver for his acceptance. The passenger sent the job request to the taxi driver and once the taxi driver accept the job request, a confirmation message will be received as in 515. The confirmation message will display a message indicating the booking is confirmed and the estimated time of arrival. The passenger may proceed to track the location of the taxi visually via the mobile application as in 516.

Typical Logical Process Flowchart

[0039] FIG. 6 illustrates a typical logical process flowchart employed in the sixth embodiment of the present invention. The logical process flowchart illustrates the both the 'hail-a-cab' and the 'locate-a-passenger' logical process flow.

[0040] The user downloads the application and register as either passenger 602 or taxi driver 603 . The passenger will need to enter his profiles, preferred payment methods including credit cards information for payment of service fees or taxi fares, emergency contacts etc. The taxi driver will enter the taxi driver details, bank account information for receipt of service fee and taxi fares and emergency contact in event of emergency, the application will dial to emergency number specify. The user will need to accept the term and conditions including the privacy settings to allow tracking of its location 605 .

[0041] When the user accepting the privacy setting, the location status is turn 'ON' 608 when the application runs. This allows the passenger to 'hail-a-cab' and the taxi driver to 'locate-a-passenger' service 609 . The passenger and the taxi driver will then be able to send Job or Service request. If acknowledgement is received, the location status will be 'OFF' 612 else the user will need to resent or repeat the process 610 .

[0042] The passenger is still able to track the taxi location till it arrives to pick up the passenger. 613. If passenger activates the cancel request after acknowledgement is received before the taxi turn up 614, a notification message will be sent to the driver 615 . The application server will also be informed and the number of cancel trips per user is logged for rating purposes. In the event the taxi driver defaulted in picking up the passenger or the passenger defaults the taxi driver 617 , this information is sent to the application server and logged for rating the user accordingly. The passenger or the taxi driver may repeat the 'hail-a-cab' or 'locate-a-passenger' process respectively 616.

[0043]In 618 , the driver arrives to pick up the passenger as promised. The taxi driver will then send a service fee payment request for the passenger to acknowledge 620. Both the users will be notified of the successful transactions by the payment solutions server 621.

Typical Block Module Architecture of an Application Server

[0044] FIG. 7 illustrates a typical block module architecture of an application server 130 employed in seventh embodiment of the present invention. The Application Server 130 consists of various modules that communicate with the Passenger or the Taxi Driver Mobile application 180. The functionalities of each module are described as follows:

[0045] Mobile-server integration module 31 handles client-server communications between the Passenger Mobile Application 180 and the Application Logic Module 32. It processes functions provided by the Application logic module in a secure manner to the mobile application.

[0046] The Application Logic Module 31 contains the business logic for the user interface of the application such as for hailing for a cab, searching or displaying available taxis within specific range, viewing real-time running information on taxis, and updating a user' s location when boarding the taxi .

[0047] The Database Module 33 is responsible for storing application specific information such as such as user trips and estimated arrival/departure times.

[0048] The Notification Service module 34 is responsible for sending notifications to passengers when a booking is confirmed or when the taxis are approaching their destination. This could be triggered on a regular basis (e.g., once a minute), or via an update notification on tracked passengers or taxis from the Location service.

[0049] The SMS Service module 35 is responsible for sending notifications to passengers when a booking is confirmed or when payment is made via payment solutions server 20 .

[0050] The Real-time Running Processor 36 module requests real-time updates on the taxi locations and estimated arrival/departure times if available, and updates relevant data points accordingly. This could be triggered to run on a regular basis (e.g., once a minute). Updates are pushed to it from the taxi mobile application.

[0051] The User Management Module 37 allows the users (passengers, taxi drivers) to register, view transactions records, update details and settings etc. The profile of the passengers and the taxi details driven by the taxi drivers are recorded. The User Management is accessible by the user via the internet. It provides a backend administration page that administers users profile, settings, properties and attributes settings.

[0052] The Transaction Management Module 38 keeps transaction records such as number of trips, the amounts, trips details, methods of payments etc. The Transaction Management is accessible by the user via the internet. The user may retrieves, view and print past transaction history, trips history, receipts and statement of accounts.

[0053]The Payment Module 39 allows the passengers to select the methods of payments. This module integrates to various payment platforms available such as mobile payment, credit card or detail card payment gateways.

[0054] The Location Service and Location Update Service Module 40 are responsible for accessing and storing location trace information about passengers and the taxis. Ideally, this would implement the OpenLS Tracking specification, as other modules in this system can make use of location update and notification features. It is expected that a commercial product could be used to provide the functionality of these modules. These modules could also be reusable between LBSs

[0055] Furthermore, This module updates the location of taxis, calculates estimated time of arrival/departure at interchange points, and determines taxis location and estimated time of arrival. It can also clean up specific user information, such as mobile phone identifiers, once a user has completed a trip. Since this is a data-intensive process, a production rules engine such as JBoss Drools or IBM iLog could be considered for the implementation. This could be triggered on a regular basis (e.g., once a minute) or via an update notification on vehicle movements from the Location service.

Typical Block Module Architecture of a Mobile LBS Application

[0056] FIG. 8 illustrates a typical block module architecture of a Mobile LBS application employed in eighth embodiment of the present invention. The Passenger or the Taxi Driver Mobile application 180 is a Mobile LBS application that runs on the user's smartphone. It consists of a user interface and various modules such as one for searching for available taxis or passengers, entering trip information, a module for managing location and movement information, a client-server communications module, and a push notification handler etc.

[0057] The Application module 81 consists of a user interface and it communicates between the Application Server 130 and its various modules such as Messaging module 82, Maps and routing module 83, location module 84, privacy module 85, content module 86 and billing module 87.

[0058] The application module also communicates with the various functionality features such as SMS, MMS, LBS and Payment 88 provided by the Mobile Operator 90 through Gateway connectors 89 services.

[0059] The module on the user mobile terminal such as the Messaging Module 82 is for the instant messaging service, and the Location Module 84 is a LBS- client component for the location information provisioning. The location information requests are signaled via specially encoded instant messages between the clients on the participating mobile devices. A GPS positioning device at the mobile terminal is used for sending the raw location coordinates (Longitude-Latitude-Altitude) to the requesting peer. Using this location information, a map or street address can be obtained from an external Map server of the positioned peer (e.g. Google Maps) via GPRS. The interface between LBS client and an application service provider uses standardized HTTP or SIP based communication.

[0060] A positioning request between two mobile peers (passenger and taxi drivers) is carried out as follows : A mobile peer (Passenger) registered with the location-based service can request the position of another fellow registered peer (Taxi Driver) from his Messaging Menu.

[0061] Depending on Taxi Driver's privacy setting (handled by the Privacy Module 85), a message pop-up will be displayed on Taxi Driver's display showing Passenger's request. If the Taxi Driver's privacy setting is set to 'accept allowed' for User B, no message will appear in this case. If the request of Passenger is granted by the Taxi Driver, GPS coordinates will be converted to a special Message format and transmitted to the Passenger. Once the required position coordinates are received by Passenger, a Map showing Taxi Driver's location (handled by Maps and Routing Module 83) can be received from the online map server.

[0062] Alternatively, the Passenger can calculate the distance to the remote peer Taxi Driver using the location information from his own GPS device. Using this principle, it would be possible to find nearby taxis, triggering an instant message if registered taxi drivers comes into range. This could be realized by performing periodic location requests to registered peers

[0063] The location request between two peers (Passengers and Taxi Drivers) is only possible if both peers are online. Hence it is necessary to know the presence status (online/offline) of the peer before sending any location requests.

[0064]The Billing Module 87 handles the payment services such as service charge or taxi fare.

[0065] It is appreciated that the most preferred implementation of Locating System and method for Taxi Drivers and Passengers is available from Mobile Credit Payment Pte Ltd. Of course, it is appreciated that implementations of the preferred embodiments of the Invention may vary in accordance with the broad description given previously.

[0066] It is further appreciated that the backend network applications (FIG. 2) may vary substantially in different implementations of the present invention. It is appreciated that the embodiments of the present invention, for the very first time, provide a system and method for commuter-to-taxi driver locating system.

[0067] While embodiments of the invention have been illustrated and described, it is not intended that these embodiments illustrate and describe all possible forms of the invention. Rather, the words used in the specification are words of description rather than limitation, and it is understood that various changes may be made without departing from the spirit and scope of the invention.

INDUSTRIAL APPLICABILITY

[0068] The foregoing describes one preferred form of the system of the invention which illustrates the principle of the invention and is not intended to be limiting, and alterations and modifications as will be apparent to those skilled in the art are intended to be incorporated within the scope hereof as defined in the following claims.

What is claimed is:

Claims

1. A system for a peer-to-peer (passenger-to-taxi driver or Taxi driver-to-passenger) locating system in the taxi transportation sector comprising:

An application server that communicates with the Passenger Mobile LBS application and the Taxi Driver Mobile LBS application, integrates to the payment solution server and provide user access via internet for administration purposes such as registration, edit of user profiles and settings, view and retrieval of transactional records on number of trips, receipts and statement of accounts;

A Passenger Mobile LBS application that runs in the Passenger mobile device, communicates with the application server, and enables the passenger to 'hail-a-taxi';

A taxi Mobile LBS application that runs in the taxi driver mobile device, communicates with the application server, and enables the taxi driver to 'locate-a-passenger';

A payment solution server integrated to the application server with various platforms of payment services;

2. A system as in claim 1 wherein the application server comprises:

A Mobile-server integration module that is responsible for handling client-server communications between the Passenger Mobile Application and the Application Logic Module. It processes functions provided by the Application logic module in a secure manner to the mobile application; and

An Application Logic Module which contains the business logic for the user interface of the application, searching or displaying available taxis within specific range, viewing real-time running information on taxis, and updating a user' s location when boarding the taxi ; and

A Database Module that is responsible for storing application specific information and data store such as such as user trips and estimated arrival/departure times; and

A Notification Service module that is responsible for sending notifications to passengers when a booking is confirmed or when the taxis are approaching their destination. The notification is triggered on a regular basis or via an update notification on tracked passengers or taxis from the Location service; and

A Real-time Running Processor module that is responsible for requesting real-time updates on the taxi locations and estimated arrival/departure times if available, and updates relevant data points accordingly, triggering on a regular basis. Updates are pushed to it from the taxi mobile application; and

A SMS Service module that is responsible for sending notifications to passengers when a booking is confirmed or when payment is made via payment solutions server.

3. A system as in claim 2 wherein the application server further comprises:

A User Management Module accessible by the user via the internet that allows the users to register, view transactions records, update details and settings etc. It administers users profile, settings, properties and attributes settings; and

The Transaction Management Module that administer transaction records such as number of trips, the amounts, trips details, methods of payments etc, and is accessible by the user via the internet. The user may retrieves, view and print past transaction history, trips history, receipts and statement of accounts; and

A Payment M Module that is responsible for the passengers to select the methods of payments. This module integrates to various payment platforms available such as mobile payment, credit card or detail card payment gateways.

4. A system as in claim 1 wherein the Payment Solution Server comprises:

Payments of taxi fares or admin charges using online credit card or debit card facilities through the LBS application and authenticated via mobile SMS and billing through the banks; and

Payments of taxi fares or admin charges using mobile payments and billing through the telephone companies; and

Payments of taxi fares or admin charges using online credit card, debit card facilities or mobile payments and billing through third party payment service provider.

5. A system as in claim 1 wherein theMobile LBS applicationcomprises:

An application module that consists of a user interface and communicates between the Application Server and various modules such as Messaging module, Maps and routing module, location module, privacy module, content module and billing module.

6. A system as in claim 4 wherein theMobile LBS application further comprises:

The application module also communicates with the various functionality features such as SMS, MMS, LBS and Payment provided by the Mobile Operator through Gateway connectors services.

7. A system as in claim 4 wherein theMobile LBS application further comprises:

A Messaging Module for the instant messaging service provisioning and purposes; and

A Location Module for the location information provisioning and purposes;

A Map and routing module for showing the user location and receiving map information from the online map server; and

A privacy module responsible for handling user's privacy settings; and

A content module responsible for processing and displaying application content; and

A billing module responsible for handling user selected payment methods.

8. A method for passenger-to-taxi driver locating system comprising:

A mobile LBS application in passenger mobile device communicating with the LBS application in the taxi driver mobile device via an application server; and

Locating and searching for the taxis within the vicinity of the passenger and viewing the graphical representation of the taxis in the mobile device; and

Viewing the taxi details in the mobile device; and

Setting the privacy settings to 'online' and enter trip information; and

Sending a job request the taxi driver; and

Receiving booking confirmation via messaging or SMS after Taxi driver accept the job request; and

Contact the taxi driver via messaging, sms or mobile; and

Track the location of the booked taxi real-time on the mobile device; and

Taxi fare and /or administrative charges Payment through mobile device.

9. A method for taxi driver-to-passenger locating system comprising:

A mobile LBS application in driver mobile device communicating with the LBS application in the passenger mobile device via an application server.

Locating and searching for the passengers within the vicinity of the taxis and viewing the graphical representation of the Passenger in the mobile device; and

Viewing the Passenger profile in the mobile device; and

Setting the privacy settings to 'online' and enter taxi vehicle details, taxi fare charges, vehicle registration number, contact details; and

Sending a service request the passenger; and

Contact the passenger's via messaging, sms or mobile; and

View the location of the Passenger real-time on the mobile device; and

Received Taxi fare and /or administrative charges Payment confirmation through mobile device.

10. A method as in claim 8 for passenger-to-taxi driver locating system further comprises:

Accessing the application server via the internet for user registration, administer user profile, access information on trips, retrieve and check past traveling records, payment records and receipts.

11. A method as in claim 9 for taxi driver-to-passenger locating system further comprises:

Accessing the application server via the internet for user registration, administer user profile, accessing information on trips, retrieve and check past traveling records, payment records on taxi fares and receipts.

12. A method for taxi drivers and passengers locating system, comprising of the steps of:

The user, being the passenger or taxi driver, downloads the LBS client application to the user's mobile device;

The user registers as either passenger or taxi driver, entering information such as profile, preferences, payment methods, bank accounts, emergency contact number and taxi vehicle details into the system;

The user shall agree to the terms and conditions of using the software, including accepting the privacy settings of allowing their locations to be tracked and monitored;

The user's location status is 'ON' when the application runs. The user is able to search and display the other users in the vicinity via the mobile device. For example, a passenger is able to search and display locations of the taxis while the taxi driver is able to search and display locations of the passengers;

The user is able to send a job or service request to the other user; and the other user is free to choose to accept the acknowledgement or reject the request; and

In the event of any cancellation, both the user and the application server are being notified and the user shall repeat the process again;

Upon acknowledgement by the other user, the user's location status is 'OFF' and the user is able to track the location of the other user whom accepted his job request. If the user is a passenger, he will board the taxi (the other user) upon the arrival of the taxi;

The taxi driver will send a service fee payment request for the passenger to acknowledge; and upon receiving acknowledgement, the payment solution server will send both users a notification on successful transaction.