WO2018217161A1 - Systèmes et procédés de gestion de services de navette et de dérivation de services et d'itinéraires de service de navette - Google Patents

Systèmes et procédés de gestion de services de navette et de dérivation de services et d'itinéraires de service de navette Download PDF

Info

Publication number
WO2018217161A1
WO2018217161A1 PCT/SG2017/050271 SG2017050271W WO2018217161A1 WO 2018217161 A1 WO2018217161 A1 WO 2018217161A1 SG 2017050271 W SG2017050271 W SG 2017050271W WO 2018217161 A1 WO2018217161 A1 WO 2018217161A1
Authority
WO
WIPO (PCT)
Prior art keywords
shuttle service
shuttle
candidate
service
route
Prior art date
Application number
PCT/SG2017/050271
Other languages
English (en)
Inventor
Abdullah Shamil Hashim AL-DUJAILI
Kong-Wei Lye
Muchen TANG
Liuqin YANG
Original Assignee
Grabtaxi Holdings Pte. Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Grabtaxi Holdings Pte. Ltd. filed Critical Grabtaxi Holdings Pte. Ltd.
Priority to KR1020197038246A priority Critical patent/KR102390269B1/ko
Priority to PCT/SG2017/050271 priority patent/WO2018217161A1/fr
Priority to CN201780092576.7A priority patent/CN110832535A/zh
Priority to JP2019565309A priority patent/JP6956810B2/ja
Publication of WO2018217161A1 publication Critical patent/WO2018217161A1/fr
Priority to PH12019502670A priority patent/PH12019502670A1/en

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/04—Forecasting or optimisation specially adapted for administrative or management purposes, e.g. linear programming or "cutting stock problem"
    • G06Q10/047—Optimisation of routes or paths, e.g. travelling salesman problem
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063—Operations research, analysis or management
    • G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
    • G06Q10/06312—Adjustment or analysis of established resource schedule, e.g. resource or task levelling, or dynamic rescheduling
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063—Operations research, analysis or management
    • G06Q10/0633—Workflow analysis
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/40—Business processes related to the transportation industry

Definitions

  • the present disclosure relates generally to managing transportation-related services, and more specifically, to methods, systems, and devices for managing shuttle-related services, including the derivation of shuttle service routes.
  • Present example embodiments relate generally to and/or comprise systems, subsystems, processors, devices, logic, and methods for addressing conventional problems, including those described above and in the present disclosure, and more specifically, example embodiments relate to systems, subsystems, processors, devices, logic, and methods of managing shuttle-related services and deriving of shuttle service routes.
  • a method of managing a shuttle service may include searching a database of historic transport -related requests to identify a plurality of historic non-shuttle service requests.
  • Each historic non-shuttle service request may include a start time and a route. The route may be defined by at least an origin location and a destination location.
  • the method may also include selecting a plurality of historic non-shuttle service requests.
  • One or more of the selected historic non-shuttle service requests may include at least a portion of its route in common with one or more other selected historic non-shuttle service requests.
  • the method may also include deriving a candidate shuttle service route for use in providing a shuttle service.
  • the candidate shuttle service route may be derived based on one or more of the selected historic non- shuttle service requests.
  • a method of managing a shuttle service may include searching a database of historic transport -related requests to identify a plurality of historic non-shuttle service requests.
  • Each historic non-shuttle service request may include a start time and a route defined by at least an origin location and a destination location.
  • the method may also include selecting one or more of the historic non-shuttle service requests.
  • the method may also include selecting one or more candidate service providers available to service one or more of the selected historic non-shuttle service requests.
  • the method may also include deriving one or more candidate shuttle service routes, the one or more candidate shuttle service routes derived based on one or more of the selected historic non-shuttle service requests.
  • the method may also include selecting one or more of the candidate shuttle service routes for use in providing a shuttle service.
  • the selected one or more candidate shuttle service routes may be selected based on one or more of the selected candidate service providers.
  • a method of managing a shuttle service may include searching a database of historic transport -related requests to identify a plurality of historic non-shuttle service requests.
  • Each historic non-shuttle service request may include a start time and a route defined by at least an origin location and a destination location.
  • the method may also include selecting one or more potential users for a shuttle service. One or more of the selected potential users may be identified as a price-sensitive user.
  • the method may also include selecting one or more of the historic non-shuttle service requests.
  • One or more of the selected historic non-shuttle service requests may be a request previously sent by one of the selected potential users.
  • one or more of the selected historic non-shuttle service requests may be a request that was not allocated, not matched, and/or cancelled.
  • the method may also include deriving a candidate shuttle service route for use in providing the shuttle service, the candidate shuttle service route derived based on one or more of the selected historic non-shuttle service requests.
  • a method of managing a shuttle service may include searching a database of historic transport-related requests to identify a plurality of historic non-shuttle service requests received from a plurality of users.
  • Each historic non-shuttle service request may include a start time and a route defined by at least an origin location and a destination location.
  • the method may also include performing an analysis to identify one or more price- sensitive users.
  • the method may also include selecting one or more potential users for a shuttle service. At least one of the selected potential users may be identified as a price-sensitive user.
  • the method may also include selecting one or more of the historic non-shuttle service requests when the historic non-shuttle service request is a request previously sent by one or more of the selected potential users.
  • the method may include selecting one or more of the historic non-shuttle service requests when the historic non-shuttle service request is a request that was not allocated, not matched, and/or cancelled.
  • the method may include selecting one or more of the historic non-shuttle service requests when the historic non-shuttle service request has at least a portion of its route in common with one or more other selected historic non-shuttle service requests.
  • the method may also include selecting one or more candidate service providers available to service one or more of the selected historic non- shuttle service requests.
  • the method may also include deriving one or more candidate shuttle service routes.
  • the one or more candidate shuttle service routes may be derived based on one or more of the selected historic non-shuttle service requests.
  • the method may also include selecting one of the candidate shuttle service routes for use in providing the shuttle service.
  • the selected candidate shuttle service route may be selected based on one or more of the selected candidate service providers.
  • Figure 1 is an illustration of an example embodiment of a system for managing a shuttle service
  • Figure 2 is an illustration of an example embodiment of a processor for managing a shuttle service
  • Figure 3 is an illustration of an example embodiment of a method for managing a shuttle service
  • Figure 4 is an illustration of another example embodiment of a method for managing a shuttle service.
  • Figure 5 is an illustration of another example embodiment of a method for managing a shuttle service.
  • the term “in” may include “in” and “on,” and the terms “a,” “an,” and “the” may include singular and plural references.
  • the term “by” may also mean “from,” depending on the context.
  • the term “if” may also mean “when” or “upon,” depending on the context.
  • the words “and/or” may refer to and encompass any and all possible combinations of one or more of the associated listed items.
  • service providers may include, but are not limited to, traditional and/or online merchants (e.g., retailers, department stores, e-commerce websites, etc.), providers of specialty products and/or services (e.g., transport-related services such as public transportation, private car hires, limousine services, shuttles, taxis, motorcycle taxis, ride- sharing, delivery, etc.), intermediaries, resellers, brokers, those who provide platforms/services for comparative shopping and/or reviews, etc. (hereinafter a "service provider").
  • traditional and/or online merchants e.g., retailers, department stores, e-commerce websites, etc.
  • providers of specialty products and/or services e.g., transport-related services such as public transportation, private car hires, limousine services, shuttles, taxis, motorcycle taxis, ride- sharing, delivery, etc.
  • intermediaries e.g., resellers, brokers, those who provide platforms/services for comparative shopping and/or reviews, etc.
  • Technological products and solutions offered by such service providers continue to empower users to interact and/or transact, including purchase, reserve, book, add-to-cart, leave a deposit or partial payment, save, cancel, and/or share, such products and/or services with more ease, effectiveness, and/or efficiency.
  • transport-related services such as public transportation (trains, buses, etc.), taxis (cars, vans, motorcycles, and other types of vehicles), private car hires, limousine services, shuttles, ride-sharing, delivery, etc., and other types of services, to be searched for, priced, compared, reserved, and/or booked (and/or cancelled) directly and with ease from a computing device (e.g., a desktop computer, laptop computer/ultrabook, mobile device, and/or wearable device) via a website or application (e.g., mobile application, widget, etc.).
  • a computing device e.g., a desktop computer, laptop computer/ultrabook, mobile device, and/or wearable device
  • a website or application e.g., mobile application, widget, etc.
  • a shuttle service may be provided to meet demands or needs of those who need to travel from their hotel to a convention center for a particular conference or show, and such shuttle services will generally be provided and/or arranged by the hotel, the convention center, the organizer of the conference or show, and/or a shuttle service provider engaged, hired, or requested by one of these.
  • a shuttle service may be provided or arranged by a company to meet demands or needs of their employees who need to travel from one office location of the company to another office location of the company.
  • shuttle service routes will generally include a fixed starting location for the shuttle service (which may be an already established bus stop, entrance to a building, or landmark location), a fixed ending location for the shuttle service (which may be another already established bus stop, entrance to a building, or landmark location), and a starting time for the shuttle service.
  • Present example embodiments relate generally to and/or comprise systems, subsystems, processors, devices, logic, and methods for addressing conventional problems, including those described above and in the present disclosure, and more specifically, example embodiments relate to systems, subsystems, processors, devices, logic, and methods of managing shuttle and/or shuttle- related services.
  • example embodiments may be described in the present disclosure as pertaining to and/or for use with passenger-based shuttle and/or shuttle -related services on buses, min buses, and/or other larger multi-passenger vehicles, it is to be understood that example embodiments may also be applicable to and/or for use in delivery and/or transporting parcels, items, documents, etc. and in other environments, surroundings, situations, circumstances, and/or applications without departing from the teachings of the present disclosure.
  • Example embodiments of a system for managing shuttle services e.g., system 100.
  • FIGURE 1 an example embodiment of a system (e.g., system 100) for managing shuttle or shuttle-related services is illustrated in FIGURE 1.
  • the system may include one or more processors (e.g., processor 150).
  • processors e.g., processor 150
  • a reference to a processor may also refer to, apply to, and/or include a computing device, server, cloud-based computing, or the like, and/or functionality of a processor, computing device, server, cloud-based computing, or the like.
  • the system 100 may also include one or more databases (e.g., database 140, 140a, 140b, 140c, 140d).
  • the system 100 may also include one or more user computing devices (e.g., user computing device 110).
  • the system 100 may also include one or more shuttle or service provider computing devices (e.g., shuttle or service provider computing device 120).
  • the one or more processors 150, databases 140, 140a-d, user computing devices 110, and/or shuttle computing devices 120 may be in communication with one another via one or more networks (e.g., network, 130), such as the Internet, World Wide Web, one or more private networks, or the like.
  • networks e.g., network, 130
  • an example embodiment of a shuttle service and/or shuttle -related service (hereinafter “shuttle service”) manageable or managed by the processor 150 may include, among other things, multi-passenger, multi-user, and/or multi-parcel transport-related services.
  • the shuttle service may be provided by a multi-passenger, multi-user, and/or multi-parcel vehicle (hereinafter “shuttle", “service provider”, or “shuttle service provider”) capable of being simultaneously booked by and/or providing services to more than one user at a time (e.g., providing services to more than one paid user for each driven route).
  • the shuttle or service provider may include a car, sport utility vehicle (SUV), minivan, van, mini bus, bus, coach, non-land vehicle (e.g., boats, vehicles capable of traveling in or on water, vehicles capable of traveling in the air, airplanes, etc.), autonomous and semi-autonomous versions of one or more of the aforementioned example vehicles, and/or other multi-passenger vehicle.
  • the shuttle service may include, among other things, a route, one or more stops along the route, a timing component, a cost component, and/or a fare or fee component.
  • the shuttle service may be provided on a fixed, semi-fixed, and/or variable route.
  • Each route may be predetermined and/or dynamically derived (e.g., derived on- demand) based on one or more considerations and/or criterion.
  • Each route may also be adjusted or changed during the servicing of the route, such as in situations where heavy traffic, construction, and/or an accident are encountered, when a new user has just booked on the shuttle during the servicing of the route, when a booked user did not make it on time to board the shuttle (e.g., exceeded the wait time, cancelled, etc.), etc.
  • each route may include an origin location and destination location.
  • the shuttle service may include one or more stops along the overall route, and such stops may also be predetermined and/or dynamically derived based on one or more considerations and/or criterion.
  • the shuttle service may include an origin location (or initial location, starting location, first location, etc., hereinafter "origin location”).
  • Each origin location may be a single point (e.g., point on a map, latitude/longitude coordinates, GPS coordinates, etc.), landmark, address, location name, intersection, area/region, etc.
  • the shuttle service may also include a destination location (or final location, ending location, last location, etc., hereinafter "destination location").
  • Each destination location may be a single point (e.g., point on a map, latitude/longitude coordinates, GPS coordinates, etc.), landmark, address, and/or area/region.
  • the shuttle service may also include one or more pickup location or stops for picking up or allowing passengers or parcels to be picked up or boarded (hereinafter "pickup location” or "pick-up location”).
  • pick-up location may be a single point (e.g., point on a map, latitude/longitude coordinates, GPS coordinates, etc.), landmark, address, and/or area/region.
  • the shuttle service may also include one or more drop-off locations or stops for dropping off or allowing passengers or parcels to be dropped off or disembarked (hereinafter "drop off location” or “drop-off location”).
  • Each drop-off location may be a single point (e.g., point on a map, latitude/longitude coordinates, GPS coordinates, etc.), landmark, address, and/or area/region.
  • Each stop may also be adjusted or changed during the servicing of the route, such as in situations where heavy traffic, construction, and/or an accident are encountered, when a new user has just booked on the shuttle during the servicing of the route, when a booked user did not make it on time to board the shuttle (e.g., exceeded the wait time, cancelled, etc.), etc.
  • each route may include an origin location and destination location. It is to be understood in the present disclosure that a pick-up location may be the same location as a drop-off location (e.g., the location may pick up one user and drop off another user). Furthermore, a pick-up location may also be the same location as the origin location, and a drop-off location may also be the same location as the destination location.
  • the shuttle service may include a start time or time period (or initial time, origin time, etc., hereinafter “start time” or “starting time”), which may be a date, day, time, time period, and/or estimated time or time period when the shuttle or shuttle service will or is expected to commence at, arrives at, and/or depart from the origin location and/or when the shuttle services commences its overall route.
  • start time or initial time, origin time, etc., hereinafter “start time” or “starting time”
  • start time may be a date, day, time, time period, and/or estimated time or time period when the shuttle or shuttle service will or is expected to commence at, arrives at, and/or depart from the origin location and/or when the shuttle services commences its overall route.
  • the shuttle service may also include an end time or time period (or final time, destination time, etc., hereinafter "end time” or “ending time”), which may be a date, day, time, time period, and/or estimated time or time period when the shuttle or shuttle service arrives at or is expected to arrive at the destination location and/or when the shuttle service completes its overall route.
  • the shuttle service may also include one or more pick-up times, which may be a date, day, time, time period, and/or estimated time or time period when the shuttle or shuttle service arrives at or is expected to arrive at a pick-up location.
  • the shuttle service may also include one or more drop-off times, which may be a day, date, time, time period, and/or estimated time or time period when the shuttle or shuttle service arrives at or is expected to arrive at a drop-off location.
  • the shuttle service may determine a cost associated with providing the shuttle service for each route.
  • the cost may be set as a fixed cost amount and/or variable amount (e.g., based on distance, number of stops, day of the week, time of the day, discounted amount, promotional amount, etc.).
  • the cost may include the cost that may be incurred by each shuttle service provider to service each route.
  • Such costs may take into consideration, among other things, costs associated with fuel, vehicle depreciation, opportunity cost, tolls and/or other additional costs to operate and/or maintain the vehicle, idle and/or wait times, costs to travel to the origin location of the route, commissions and/or fees to pay to others (e.g., owner, employer, higher-level service provider, platform provider, etc.), traffic considerations, overtime, holidays, etc.
  • the shuttle service may (or may not) require payment and/or require its passengers or users to pay a fixed or flat amount and/or variable amount (e.g., based on distance, number of stops, day of the week, time of the day, discounted amount, promotional amount, etc.).
  • the fares and/or fees may be determined based on one or more factors or considerations, such as the number of potential users to be serviced by each shuttle for each route, availability and/or location of each shuttle, capacity of each shuttle, costs for each service provider (as described above and in the present disclosure), fees for other types of services, current market rates, competitor's fees, etc.
  • a shuttle service may be a multiple passenger or user shuttle service provided by a shuttle (e.g., bus or mini bus) capable of serving 7 users or passengers that travels along a predetermined or dynamically determined overall route in Singapore between an origin location set as 6 Shenton Way and a destination location set as Marina Bay Financial Centre having a start time at the origin location of 2 pm today and having two pickup locations and/or one drop off location along the route.
  • a shuttle e.g., bus or mini bus
  • non-shuttle service may include those transport- related services that are not or may not be considered as a shuttle service.
  • the non-shuttle service may be provided by a vehicle (hereinafter “non-shuttle service provider") capable of being singly booked by and/or providing services to one user at a time (e.g., providing services to one paid user for each route, but such service may include accompanying passengers).
  • the non-shuttle service provider may include a car, sport utility vehicle (SUV), minivan, van, non-land vehicle (e.g., boats, vehicles capable of traveling in or on water, vehicles capable of traveling in the air, airplanes, etc.), autonomous and semi- autonomous versions of one or more of the aforementioned example vehicles, and/or other vehicle.
  • each non-shuttle service may include those provided by a standard or traditional taxi service, a private car service (e.g., GrabCar service provided by Grab), a limousine service, etc.
  • Example embodiments of the system may include or not include one or more of the elements described above and in the present disclosure, may include additional elements, may include equivalent elements, may be formed and/or used in different sequences, actions, combinations, and/or configurations, and/or one or more of the elements (and/or elements of elements) may be combinable into a single element or divided into two or more elements. Communication using technologies other than the Internet are also contemplated in example embodiments without departing from the teachings of the present disclosure. These systems 100, and elements and functionalities thereof, will now be further explained with reference to the accompanying figures.
  • User computing device e.g., user computing device 110.
  • the system 100 may include one or more computing devices 110 for use by users (e.g., those who send shuttle service requests and/or non-shuttle service requests).
  • User computing devices 110 may be any device, computing device, mobile computing device, processor, controller, or the like, configurable or configured to perform a processing of information, wired and/or wireless communications, and/or any of the other actions and/or processes described above and in the present disclosure.
  • the user computing device 110 may be configurable to perform wireless communications through 3G networks, 4G networks, 4G LTE networks, or the like, such as via a SIM card installed in the user computing device 110, or the like.
  • the user computing device 110 may be configurable to perform wireless communications via WLANs, such as Wi-Fi networks and Li-Fi networks, and/or via other forms, such as Bluetooth, NFC, and other forms of wireless signals.
  • WLANs such as Wi-Fi networks and Li-Fi networks
  • other forms such as Bluetooth, NFC, and other forms of wireless signals.
  • One or more of the aforementioned communications may be between example embodiments of the user computing device 110, one or more processors 150, one or more shuttle computing devices 120, one or more databases 140, 140a- d, and/or one or more networks 130.
  • the user computing device 110 may be configured (e.g., via an application or mobile application installed on the user computing device, via a web browser, etc.) to communicate, wirelessly or via wires, with the processor 150 and such communications may include sending shuttle service requests and/or non-shuttle service requests, viewing available shuttle service routes, receiving notifications of new and/or existing shuttle service routes, booking a shuttle service and/or non-shuttle service, etc.
  • the user computing device 110 described above and in the present disclosure may be directed to and/or include mobile computing devices, smart phones, mobile phones, PDAs phablets, tablets, portable computers, laptops, notebooks, ultrabooks, readers, electrical devices, media players, specialized devices (e.g., a dedicated or specialized device to communicate with and/or operate in the system 100, or parts thereof), a plurality of computing devices interacting together in part or in whole, and other specialized computing devices and industry-specific computing devices.
  • the user computing device 110 described herein may also be directed to and/or include wearable computing devices, including watches (such as the Apple Watch), glasses, etc.
  • the user computing device 110 may also be directed to and/or include a virtual machine, computer, node, instance, host, or machine in a networked computing environment.
  • a virtual machine computer, node, instance, host, or machine in a networked computing environment.
  • Such networked environment, and/or cloud may be a collection of machines connected by communication channels that facilitate communications between machines and allow for machines to share resources.
  • Such resources may encompass any types of resources for running instances including hardware (such as servers, clients, mainframe computers, networks, network storage, data sources, memory, central processing unit time, scientific instruments, and other computing devices), as well as software, software licenses, available network services, and other non-hardware resources, or a combination thereof.
  • Shuttle computing device e.g., shuttle computing device 120.
  • the system 100 may include one or more computing devices 120 for use by shuttles (i.e., those who provide shuttle services).
  • Shuttle computing devices 120 may be any device, computing device, mobile computing device, processor, controller, or the like, configurable or configured to perform a processing of information, wired and/or wireless communications, and/or any of the other actions and/or processes described above and in the present disclosure.
  • the shuttle computing device 120 may be configurable to perform wireless communications through 3G networks, 4G networks, 4G LTE networks, or the like, such as via a SIM card installed in the service provider computing device 120, or the like, and may also be configurable or capable of performing vehicle-to-vehicle communications.
  • the shuttle computing device 120 may be configurable to perform wireless communications via WLANs, such as Wi-Fi networks and Li-Fi networks, and/or via other forms, such as Bluetooth, NFC, and other forms of wireless signals.
  • WLANs such as Wi-Fi networks and Li-Fi networks
  • other forms such as Bluetooth, NFC, and other forms of wireless signals.
  • One or more of the aforementioned communications may be between example embodiments of the shuttle computing device 120, one or more processors 150, one or more user computing devices 110, one or more databases 140, 140a-d, and/or one or more networks 130.
  • the shuttle computing device 120 may be configured (e.g., via an application or mobile application installed on the shuttle computing device, via a web browser, etc.) to communicate, wirelessly or via wires, with the processor 150 and such communications may include receiving shuttle services and shuttle service routes that are available or need to be serviced, viewing available shuttle service routes, receiving notifications of new and/or existing shuttle service routes, accepting to service a shuttle service or shuttle service route, etc.
  • the shuttle computing device 120 described above and in the present disclosure may be directed to and/or include mobile computing devices, smart phones, mobile phones, PDAs phablets, tablets, portable computers, laptops, notebooks, ultrabooks, readers, electrical devices, media players, specialized devices (e.g., a dedicated or specialized device to communicate with and/or operate in the system 100, or parts thereof), a plurality of computing devices interacting together in part or in whole, and other specialized computing devices and industry-specific computing devices.
  • the shuttle computing device 120 may also be a part of or be integrated with shuttles, including those shuttles that are autonomous vehicles, semi -autonomous vehicles, and non-autonomous vehicles.
  • the shuttle computing device 120 described herein may also be directed to and/or include wearable computing devices, including watches (such as the Apple Watch), glasses, etc.
  • the shuttle computing device 120 may also be directed to and/or include a virtual machine, computer, node, instance, host, or machine in a networked computing environment.
  • Such networked environment, and/or cloud may be a collection of machines connected by communication channels that facilitate communications between machines and allow for machines to share resources.
  • Such resources may encompass any types of resources for running instances including hardware (such as servers, clients, mainframe computers, networks, network storage, data sources, memory, central processing unit time, scientific instruments, and other computing devices), as well as software, software licenses, available network services, and other non-hardware resources, or a combination thereof.
  • the shuttle computing device 120 and the user computing device 110 may be any computing device operable to perform information processing and wireless communications, and the shuttle computing device 120 and the user computing device 110 may be a similar or the same type of computing device.
  • Processor e.g., processor 150
  • the system 100 may include one or more processors (e.g., processor 150).
  • An example embodiment of the processor 150 may include one or more functionalities of one or more non-shuttle service request identifiers (e.g., non-shuttle service request identifier 151), one or more non-shuttle service request selectors (e.g., non-shuttle service request selector 152), one or more candidate service route generators (e.g., candidate service route generator 153), one or more candidate shuttle service route selectors (e.g., candidate shuttle service route selector 156), one or more potential user selectors (e.g., potential user selector 154), one or more candidate service provider selectors (e.g., candidate service provider selector 155), one or more shuttle service route managers (e.g., shuttle service route manager 157), one or more shuttle-side notification and dispatch controllers (e.g., shuttle-side notification and dispatch controller 158), and/or one or more user-side
  • the processor 150 may also be configurable or configured to perform one or more operations, functions/functionalities, and/or processes of the non-shuttle service request identifier 151, non-shuttle service request selector 152, candidate service route generator 153, potential user selector 154, candidate service provider selector 155, candidate shuttle service route selector 156, shuttle service route manager 157, shuttle-side notification and dispatch controller 158, and/or user-side notification and booking controller 159.
  • the processor 150 may be any processor, server, device, computing device, server, controller, microprocessor, microcontroller, microchip, semiconductor device, virtual machine, or the like, configurable or configured to perform, among other things, a processing of information, voice and/or data communications, and/or other actions described above and in the present disclosure.
  • such a network and/or cloud may be a collection of devices connected by communication channels that facilitate communications between devices and allow for devices to share resources.
  • resources may encompass any types of resources for running instances including hardware (such as servers, clients, mainframe computers, networks, network storage, data sources, memory, central processing unit time, scientific instruments, and other computing devices), as well as software, software licenses, available network services, and other non-hardware resources, or a combination thereof.
  • a network or cloud may include, but is not limited to, computing grid systems, peer to peer systems, mesh-type systems, distributed computing environments, cloud computing environment, etc.
  • Such network or cloud may include hardware and/or software infrastructures configured to form a virtual organization comprised of multiple resources which may be in geographically disperse locations.
  • Network may also refer to a communication medium between processes on the same device.
  • a network element, node, or server may be a device deployed to execute a program operating as a socket listener and may include software instances.
  • Example embodiments of the processor 150 may include or not include one or more of the elements and/or functionalities described above and in the present disclosure, may include additional elements and/or functionalities, may be formed and/or used in different sequences, actions, combinations, and/or configurations, and/or one or more of the elements and/or functionalities (and/or elements of elements and/or functionalities of elements) may be combinable into a single element, single functionality and/or process, divided into two or more elements, and/or divided into two or more functionalities and/or processes.
  • the processor 150, and elements and functionalities thereof, will now be further explained with reference to the accompanying figures.
  • Non-shuttle service request identifier e.g., non-shuttle service request identifier 151).
  • the processor 150 may include (and/or be configurable or configured to perform one or more functionalities of) one or more non-shuttle service request identifiers (e.g., non-shuttle service request identifier 151).
  • the non-shuttle service request identifier 151 may be configurable or configured to search a database (e.g., a database of historic transport -related requests 140a, database of historic non-shuttle service requests 140b, database of historic shuttle service requests 140c, and/or database of users 140d) to identify one or more historic non-shuttle service requests.
  • non-shuttle service request identifier 151 may be configurable or configured to receive historic shuttle service requests and/or non-shuttle service requests (e.g., from the processor 150, an element of the processor 150, one or more databases 140a-d, etc.) and identify one or more historic non-shuttle service requests.
  • Such searching, receiving, and/or identifying may be performed continuously (e.g., whenever a non-shuttle service request has been received by the system 100), intermittently (e.g., whenever a predetermined number of non-shuttle service requests have been received by the system 100), periodically (e.g., once per hour, once per day, once per week, once per month, etc.), and/or scheduled based on other considerations (e.g., whenever a predetermined number of price-sensitive users have been identified, whenever a predetermined number of unallocated, unmatched, and/or cancelled service requests for non-shuttle services reaches a predetermined number, whenever a demand for shuttle services reaches a predetermined number, whenever a supply for shuttle services reaches a predetermined number, etc.).
  • the identified historic non-shuttle service requests may include a service request that was successfully matched to a service provider, a service request that was successfully booked and completed, a service request that was unsuccessfully matched to a service provider, a service request that was unallocated, a service request that was abandoned, a service request that was cancelled by the user, and/or a service request that was cancelled by the service provider.
  • Each identified historic non-shuttle service request may include a start time (e.g., time the request was initiated on the user computing device 1 10, time the request was sent by the user computing device 110, time the request was received by the processor 150, time the request was processed by the processor 150 (e.g., request matched to a service provider, request booked, request not matched to a service provider, request not allocated, request cancelled, request abandoned, etc.), time the non-shuttle service commenced, etc.).
  • Each identified historic non-shuttle service request may also include an origin location (e.g., initial location, starting location, desired location, pick-up location, etc.).
  • Each identified historic non-shuttle service request may also include a destination location (e.g., final location, ending location, drop-off location, etc.).
  • Each identified historic non- shuttle service request may also include one or more routes, which may be defined by at least the origin and destination locations.
  • each identified historic non-shuttle service request may include the best or most optimal route based on the above-mentioned start time, and may also include other optional, alternative, or less optimal routes.
  • the non-shuttle service request identifier 151 may be configurable or configured to search for, receive, and/or identify historic non-shuttle service requests based on one or more considerations and/or criterion, such as by geographical region, time or period of time (e.g., years, months, weeks, days, hours, minutes, seconds, etc.), type of service requested (e.g., taxi, private car, public transportation, limousine, ride share, delivery, etc.), location (e.g., initial location, origin location, starting location, desired location, pick-up location, destination location, etc.), route, user-specific criterion (which may be performed by the potential user selector 154), availability and/or location of shuttles (which may be performed by the candidate service provider selector 155), etc.
  • considerations and/or criterion such as by geographical region, time or period of time (e.g., years, months, weeks, days, hours, minutes, seconds, etc.), type of service requested (e.g., taxi, private car, public transportation,
  • the non-shuttle service request identifier 151 may be configurable to identify historic non-shuttle service requests based on country, region, province, state, city, county, district, specific area (e.g., within certain city blocks, on certain roads, within a geometric shape drawn on a map, etc.), etc.
  • the non- shuttle service request identifier 151 may be configurable to identify historic non-shuttle service requests based on year, month, week, day, specific hour(s) and/or minutes, peak hours, rush hours, etc.
  • the non-shuttle service request identifier 151 may be configurable to identify historic non-shuttle service requests based on whether the user of the request is a price-sensitive user, history of unallocated requests, history of unmatched requests, history of cancelled requests, history of abandoned requests, whether the user of the request is a frequent user of lower cost services such as shuttle, ride share, etc.
  • the non- shuttle service request identifier 151 may be configurable to identify historic non -shuttle service requests that have similar, the same, and/or overlapping routes (and such routes may include the best or most optimal route, secondary routes, etc.).
  • the non-shuttle service request identifier 151 may be configurable to identify historic non- shuttle service requests based on whether a location associated with the request (e.g., the origin location and/or destination location) is or will be near to a location of an available or to-be-available shuttle.
  • the non-shuttle service request identifier 151 may be configurable to identify non-shuttle requests from price-sensitive users (and/or users having a history of unallocated, unmatched, cancelled, and/or abandoned requests) having an origin location in one or more predetermined or dynamically generated areas of the central business district (CBD) of a city, a destination location in one or more predetermined or dynamically generated areas of the CBD of the city, and a starting time during morning rush hour (e.g., between 8-815am).
  • CBD central business district
  • the non-shuttle service request identifier 151 may also be configurable to identify historic non-shuttle service requests from price-sensitive users (and/or users having a history of unallocated, unmatched, cancelled, and/or abandoned requests) having origin locations in other (e.g., adjacent) predetermined or dynamically generated areas of the CBD of that city, destination locations in other (e.g., adjacent) predetermined or dynamically generated areas of the CBD of that city, and/or for the same and/or different starting times.
  • the one or more criterion and/or parameters including geographical region, starting time, time or period of time, origin location, destination location, user-specific criterion, availability and/or location of shuttles, etc., used by the non-shuttle service request identifier 151 may be any criterion and/or parameter thereof (e.g., any amount, duration, type, etc.) without departing from the teachings of the present disclosure.
  • Non-shuttle service request selector e.g., non-shuttle service request selector 152).
  • the processor 150 may include (and/or be configurable or configured to perform one or more functionalities of) one or more non-shuttle service request selectors (e.g., non-shuttle service request identifier 152).
  • the non-shuttle service request selector 152 may be configurable or configured to select one or more historic non-shuttle service requests. The selection may be performed from among the historic non-shuttle service requests identified by the non-shuttle service request identifier 151.
  • the non-shuttle service request selector 152 may be configurable or configured to receive previously selected (or not previously selected) historic shuttle and/or non-shuttle service requests (e.g., from the processor 150, an element of the processor 150, one or more databases 140a-d, etc.).
  • the selecting and/or receiving by the non-shuttle service request selector 152 may be performed continuously (e.g., whenever a non-shuttle service request has been identified), intermittently (e.g., whenever a predetermined number of non-shuttle service requests have been identified), periodically (e.g., once per hour, once per day, once per week, once per month, etc.), and/or scheduled based on other considerations (e.g., whenever a predetermined number of price-sensitive users have been selected, whenever a predetermined number of unallocated, unmatched, and/or cancelled service requests for non-shuttle services reaches a predetermined number, whenever a demand for shuttle services reaches a predetermined number, whenever a supply for shuttle services reaches a predetermined number, etc.).
  • the selected historic non-shuttle service requests may include a service request that was successfully matched to a service provider, a service request that was successfully booked and completed, a service request that was unsuccessfully matched to a service provider, a service request that was unallocated, a service request that was abandoned, a service request that was cancelled by the user, and/or a service request that was cancelled by the service provider.
  • Each selected historic non-shuttle service request may include a start time (e.g., time the request was initiated on the user computing device 110, time the request was sent by the user computing device 110, time the request was received by the processor 150, time the request was processed by the processor 150 (e.g., request matched to a service provider, request booked, request not matched to a service provider, request not allocated, request cancelled, request abandoned, etc.), time the non-shuttle service commenced, etc.).
  • Each selected historic non-shuttle service request may also include an origin location (e.g., initial location, starting location, desired location, pick-up location, etc.).
  • Each selected historic non-shuttle service request may also include a destination location (e.g., final location, ending location, drop-off location, etc.).
  • Each selected historic non- shuttle service request may also include one or more routes, which may be defined by at least the origin location and the destination location.
  • each selected historic non-shuttle service request may include the best or most optimal route based on the above-mentioned start time, as well as other optional, alternative, or less optimal routes.
  • the non-shuttle service request selector 152 may be configurable or configured to select and/or receive historic non-shuttle service requests based on one or more criterion and/or conditions, such as by geographical region, time or period of time (e.g., years, months, weeks, days, hours, minutes, seconds, etc.), type of service requested (e.g., taxi, private car, public transportation, limousine, ride share, delivery, etc.), location (e.g., initial location, origin location, starting location, desired location, pick-up location, destination location, etc.), user- specific criterion (which may be performed by the potential user selector 154), availability and/or location of shuttles (which may be performed by the candidate service provider selector 155), etc.
  • time or period of time e.g., years, months, weeks, days, hours, minutes, seconds, etc.
  • type of service requested e.g., taxi, private car, public transportation, limousine, ride share, delivery, etc.
  • location e.g., initial location, origin
  • the non-shuttle service request selector 152 may also perform the selecting through a cooperation with one or more other elements of the system 100, such as with the potential user selector 154, the candidate service provider selector 155, databases 140, 140a-d, etc.
  • the non-shuttle service request selector 152 may be configurable to select historic non- shuttle service requests based on country, region, province, state, city, county, district, specific area (e.g., within certain city blocks, on certain roads, within a geometric shape drawn on a map, etc.), etc.
  • the non-shuttle service request selector 152 may be configurable to select historic non-shuttle service requests based on year, month, week, day, specific hour(s) and/or minutes, peak hours, rush hours, etc. In respect to user-specific criterion, the non-shuttle service request selector 152 may be configurable to select historic non-shuttle service requests through a cooperation with the potential user selector 154, which may assist in identifying and/or selecting historic non-shuttle service requests based on whether the user of the request is a price-sensitive user, history of unallocated requests, history of unmatched requests, history of cancelled requests, history of abandoned requests, whether the user of the request is a frequent user of lower cost services such as shuttle, ride share, etc.
  • the non-shuttle service request selector 152 may be configurable to select historic non-shuttle service requests based on whether the one or more routes associated with the requests have similar, the same, and/or overlapping routes or portions of routes. Such one or more routes may include, among other routes, the best or most optimal route, secondary routes, etc. In respect to availability and/or location of shuttles, the non- shuttle service request selector 152 may be configurable to select historic non-shuttle service requests based on whether a location associated with the request (e.g., origin location and/or destination location) is or will be near to a location of an available or to-be-available shuttle.
  • a location associated with the request e.g., origin location and/or destination location
  • the one or more criterion and/or parameters including geographical region, starting time, time or period of time, origin location, destination location, user- specific criterion, availability and/or location of shuttles, etc., used by the non-shuttle service request selector 152 may be any criterion and/or parameter thereof (e.g., any amount, duration, type, etc.) without departing from the teachings of the present disclosure.
  • the non-shuttle service request selector 152 may be configurable to select one or more historic non-shuttle service requests having at least a portion of one or more of its routes in common with one or more other selected and/or identified historic non- shuttle service requests.
  • the potential user selector 154 may first identify and/or select one or more potential users for the shuttle service.
  • the one or more potential users may be users that have been identified as being price-sensitive users.
  • the one or more potential users may also be users that have been identified as having a history of unallocated, unmatched, cancelled, and/or abandoned requests.
  • the non-shuttle service request selector 152 may then be configurable to select one or more historic non- shuttle service requests that have been identified and/or selected by the potential user selector 154 as being a request previously sent by one or more of the selected potential users.
  • the non-shuttle service request selector 152 may be configurable to select one or more historic non-shuttle service requests that have been identified and/or selected as being a request that was not allocated, not matched, cancelled, and/or abandoned.
  • the non-shuttle service request selector 152 and the non- shuttle service request identifier 151 may be combined and/or integrated into a single or unitary element and/or process, in which case such a unified element or process may be configurable or configured to perform the searching, receiving, identifying, and/or selecting operations described above and in the present disclosure.
  • Candidate service route generator (e.g., candidate service route generator 153).
  • the processor 150 may include (and/or be configurable or configured to perform one or more functionalities of) of one or more candidate service route generators (e.g., candidate service route generator 153).
  • the candidate service route generator 153 may be configurable or configured to derive, generate, and/or dynamically derive and/or generate (hereinafter "derive") one or more candidate shuttle service routes.
  • the deriving of the one or more candidate shuttle service routes may be based on one or more of the historic non-shuttle service requests selected by the non-shuttle service request selector 152.
  • the non-shuttle service request selector 152 may be configurable or configured to select, modify, and/or adjust candidate shuttle service routes that were previously derived (or not previously derived) by the candidate service route generator 153.
  • the deriving and/or selecting by the candidate service route generator 153 may be dynamically performed in a continuous manner (e.g., whenever a non-shuttle service request has been selected), intermittent manner (e.g., whenever a predetermined number of non-shuttle service requests have been selected), periodical manner (e.g., once per hour, once per day, once per week, once per month, etc.), and/or scheduled manner based on other considerations (e.g., whenever a predetermined number of price-sensitive users have been selected, whenever a predetermined number of unallocated, unmatched, and/or cancelled service requests for non-shuttle services reaches a predetermined number, whenever a demand for shuttle services reaches a predetermined number, whenever a supply for shuttle services reaches a predetermined number, etc.).
  • a continuous manner e.g., whenever a non-shuttle service request has been selected
  • intermittent manner e.g., whenever a predetermined number of non-shuttle service requests have been selected
  • periodical manner
  • the candidate shuttle service routes may be derived for potential users that have been identified as being price-sensitive users, potential users that have previously booked a shuttle service, potential users that have not previously booked a shuttle service, potential users that have a history of unsuccessful matches to a service provider, potential users that have a history of unallocated service requests, potential users that have a history of abandoned requests, potential users that have a history of cancelling service requests, and/or potential users that have a history of having their service requests being cancelled by a service provider.
  • the candidate service route generator 153 may derive an origin location (e.g., initial location, starting location, desired location, pick-up location, etc.) for each candidate shuttle service route.
  • the origin location may be the location where the candidate shuttle service route will start from.
  • the candidate service route generator 153 may also derive a start time for each candidate shuttle service route. The start time may be the time when the candidate shuttle service route will start from, arrive at, and/or depart from the origin location of the candidate shuttle service route.
  • the candidate service route generator 153 may also derive a destination location (e.g., final location, ending location, drop-off location, etc.) for each candidate shuttle service route. The destination location may be the location where the candidate shuttle service route will end.
  • the candidate service route generator 153 may also derive one or more pick-up locations for each candidate shuttle service route.
  • the candidate service route generator 153 may also derive one or more drop-off locations for each candidate shuttle service route.
  • the candidate service route generator 153 may be configurable or configured to derive the candidate shuttle service route, the origin location of the candidate shuttle service route, the start time of the candidate shuttle service route, and the destination location of the candidate shuttle service route based on one or more criterion and/or conditions, such as by geographical region, time or period of time (e.g., start times of the selected historic non-shuttle service requests, ending times of the selected historic non-shuttle service requests etc.), location (e.g., origin locations of the selected historic non-shuttle service requests, destination locations of the selected historic non-shuttle service requests, etc.), routes (e.g., routes of the selected historic non-shuttle service requests), user-specific criterion (which may be performed by the potential user selector 154), availability and/or location of shuttles (which may be performed by the candidate service provider selector 155), etc.
  • time or period of time e.g., start times of the selected historic non-shuttle service requests, ending times of the selected historic non-shuttle service requests etc.
  • the candidate service route generator 153 may also perform the deriving through a cooperation with one or more other elements of the system 100, such as with the potential user selector 154, the candidate service provider selector 155, databases 140, 140a-d, etc.
  • the candidate service route generator 153 may be configurable to derive candidate shuttle service routes for each country, region, province, state, city, county, district, specific area (e.g., within certain city blocks, on certain roads, within a geometric shape drawn on a map, etc.), etc., the granularity of which may be based on supply, demand, date, day, time, holidays or special events, etc.
  • the candidate service route generator 153 may be configurable to derive candidate shuttle service routes for each year, month, week, day, specific hour(s) and/or minutes, peak hours, rush hours, etc.
  • the candidate service route generator 153 may be configurable to derive the candidate shuttle service routes through a cooperation with the potential user selector 154, which may consider and/or target certain users or types of users (e.g., price-sensitive user, users that are frequent users of low cost services, and/or users with a history of unallocated requests, unmatched requests, cancelled requests, abandoned requests, etc.).
  • the candidate service route generator 153 may be configurable to derive candidate shuttle service routes based on a number or frequency of selected historic non-shuttle service routes having similar, the same, and/or overlapping routes or portions of routes. In respect to availability and/or location of shuttles, the candidate service route generator 153 may be configurable to derive candidate shuttle service routes based on whether a potential service provider of the shuttle service is or will be available and has or will have a location near to an origin location of candidate shuttle service route.
  • the one or more criterion and/or parameters including geographical region, starting time, time or period of time, origin location, destination location, route, user-specific criterion, availability and/or location of shuttles, etc., used by the candidate service route generator 153 may be any criterion and/or parameter thereof (e.g., any amount, duration, type, etc.) without departing from the teachings of the present disclosure.
  • Potential user selector e.g., potential user selector 154.
  • the processor 150 may include (and/or be configurable or configured to perform one or more functionalities of) one or more potential user selectors (e.g., potential user selector 154).
  • the potential user selector 154 may be configurable or configured to perform an analysis, identification, and/or selection of potential users of a shuttle service.
  • the analysis, identification, and/or selection of the potential users of the shuttle service may be based on, among other things, user information and/or settings, user priority level, user loyalty level, user payment history (form of payment and amounts), user booking history (e.g., history of booking low cost services, history of booking shuttle services, history of being price- sensitive, history of unallocated service requests, history of unmatched service requests, history of cancelled service requests, history of abandoned service requests, etc.), one or more of the historic non-shuttle service requests stored in a database 140, 140a-d, one or more of the identified and/or selected historic non-shuttle service requests, etc.
  • the potential user selector 154 may be configurable or configured to select and/or drop potential users that were previously selected (or not previously selected) by the potential user selector 154.
  • the analysis, identification, and/or selection by the potential user selector 154 may be dynamically or non-dynamically performed for some or all users in a continuous manner, intermittent manner, periodical manner (e.g., once per hour, once per day, once per week, once per month, etc.), and/or scheduled manner based on one or more other considerations (e.g., for new users, new regions serviced, change in user activity level, change in services used by users, etc.).
  • Candidate service provider selector (e.g., candidate service provider selector 155).
  • the processor 150 may include (and/or be configurable or configured to perform one or more functionalities of) one or more candidate service provider selectors (e.g., candidate service provider selector 155).
  • the candidate service provider selector 155 may be configurable or configured to perform an analysis, identification, and/or selection of candidate shuttles (or candidate service providers) for providing a shuttle service.
  • the analysis, identification, and/or selection of the candidate shuttles for providing the shuttle service may be based on, among other things, availability of the candidate shuttle, existing schedule for servicing shuttle routes, current servicing of a shuttle route, current location of the candidate shuttle, expected/projected/predicted/estimated location of the candidate shuttle, etc.
  • the candidate service provider selector 155 may be configurable or configured to select and/or drop candidate shuttles that were previously selected (or not previously selected) by the candidate service provider selector 155.
  • the analysis, identification, and/or selection by the candidate service provider selector 155 may be dynamically or non-dynamically performed for some or all shuttle service providers in a continuous manner, intermittent manner, periodical manner (e.g., once per hour, once per day, once per week, once per month, etc.), and/or scheduled manner based on one or more other considerations (e.g., for shuttle service providers based on activity level, new regions serviced, etc.).
  • Candidate shuttle service route selector (e.g., candidate shuttle service route selector 156).
  • the processor 150 may include (and/or be configurable or configured to perform one or more functionalities of) one or more candidate shuttle service route selectors (e.g., candidate shuttle service route selector 156).
  • the candidate shuttle service route selector 156 may be configurable or configured to select one or more of the derived candidate shuttle service routes (as derived by the candidate shuttle service route generator 153) to provide a shuttle service.
  • the candidate shuttle service route selector 156 may be configurable or configured to select, modify, and/or adjust candidate shuttle service routes that were previously selected (or not previously selected) by the candidate shuttle service route selector 156.
  • the candidate shuttle service route selector 156 and/or one or more other elements of the processor 150 may be configurable or configured to first perform a projection, estimation, and/or prediction of the number of potential users of one or more of the candidate shuttle service routes.
  • the candidate shuttle service route selector 156 and/or one or more other elements of the processor 150 may also be configurable or configured to perform a projection, estimation, and/or prediction of the availability and/or locations of potential shuttle service providers that may be able to service one or more of the candidate shuttle service routes, and/or the number of required shuttle service providers that may be needed to service each candidate shuttle service route based on, among other things, the projected, estimated, and/or predicted number of potential users.
  • the candidate shuttle service route selector 156 and/or one or more other elements of the processor 150 may also be configurable or configured to perform an analysis and/or derivation of, among other things, the costs that would be incurred by each shuttle service provider to service each candidate shuttle service route. Such costs may take into consideration, among other things, the fuel cost, vehicle depreciation cost, opportunity cost, tolls and/or other additional fees, idle and/or wait times, costs to travel to the origin location of the candidate shuttle service route, commissions and/or fees to pay to others (e.g., owner, employer, platform provider, etc.), traffic considerations, etc.
  • the candidate shuttle service route selector 156 and/or one or more other elements of the processor 150 may also be configurable or configured to perform an analysis and/or derivation of the fees or fares to charge users of the shuttle service.
  • Such fees may be a flat fee or variable fee based on distance, number of stops, date, day, time, holidays, traffic, etc.
  • various factors may be taken into consideration, including number of potential users, availability and location of potential shuttle service providers, costs for the shuttle service providers, fees for other services, current market fees, competitor fees, etc. may also be taken into consideration.
  • the candidate shuttle service route selector 156 may be configurable or configured to select, modify, and/or adjust potential user, potential shuttle service provider, cost, fee, revenue, and/or profit information that were previously analyzed, derived, projected, predicted, and/or estimated (each as applicable) (or not previously analyzed, derived, projected, predicted, and/or estimated, each as applicable) by the candidate shuttle service route selector 156.
  • the candidate shuttle service route selector 156 may then be configurable or configured to select one or more of the derived candidate shuttle service routes to provide a shuttle service based on one or more of the potential users, potential shuttle service providers, cost, fee, revenue, and/or profit considerations described above and in the present disclosure.
  • the selecting of the one or more derived candidate shuttle service routes by the candidate shuttle service route selector 156 may be dynamically performed in a continuous manner (e.g., whenever a candidate shuttle service route has been derived), intermittent manner (e.g., whenever a predetermined number of candidate shuttle service routes have been derived), periodical manner (e.g., once per hour, once per day, once per week, once per month, etc.), and/or scheduled manner based on other considerations (e.g., whenever a predetermined number of price-sensitive users have been selected, whenever a predetermined number of unallocated, unmatched, and/or cancelled service requests for non-shuttle services reaches a predetermined number, whenever a demand for shuttle services reaches a predetermined number, whenever a supply for shuttle services reaches a predetermined number, etc.).
  • a continuous manner e.g., whenever a candidate shuttle service route has been derived
  • intermittent manner e.g., whenever a predetermined number of candidate shuttle service routes have been derived
  • the candidate shuttle service routes may be selected for potential users that have been identified as being price-sensitive users, potential users that previously booked a shuttle service, potential users that have not previously booked a shuttle service, potential users that have a history of unsuccessful matches to a service provider, potential users that have a history of unallocated service requests, potential users that have a history of abandoned requests, potential users that have a history of cancelling service requests, and/or potential users that have a history of having their service requests being cancelled by a service provider.
  • Each selected candidate shuttle service route may have an origin location (e.g., initial location, starting location, desired location, pick-up location, etc.). The origin location may be the location where the selected candidate shuttle service route will start from. Each selected candidate shuttle service route may also have a start time. The start time may be the time scheduled for the selected candidate shuttle service route to start from, arrive at, and/or depart from the origin location of the selected candidate shuttle service route. Each selected candidate shuttle service route may also have a destination location (e.g., final location, ending location, drop-off location, etc.). The destination location may be the location where the selected candidate shuttle service route will end. Each selected candidate shuttle service route may also have one or more pick-up locations and/or one or more drop-off locations. In selecting the candidate shuttle service route, the candidate shuttle service route selector 156 may select those candidate shuttle service routes having fewer drop -off and/or pick-up locations.
  • the candidate shuttle service route selector 156 may be configurable or configured to select the candidate shuttle service route based on one or more other criterion, such as by geographical region, time or period of time (e.g., closest match and/or most number of matches of start times and ending times to those of the selected historic non-shuttle service requests, etc.), location (e.g., closest match and/or most number of matches of origin locations and destination locations to those of the selected historic non-shuttle service requests, etc.), routes (e.g., closest match and/or most number of matches of routes to those of the selected historic non-shuttle service requests), user-specific criterion (e.g., closest match and/or most number of matches of locations, start times, and/or routes to those of price-sensitive users and/or those of unallocated, unmatched, cancelled, and/or abandoned service requests), availability and/or location of shuttles (e.g., closest match and/or most number of matches of origin location, destination location, and/or start
  • the candidate shuttle service route selector 156 may also perform the selecting through a cooperation with one or more other elements of the system 100, such as with the potential user selector 154, the candidate service provider selector 155, databases 140, 140a-d, etc.
  • the candidate shuttle service route selector 156 may be configurable to select candidate shuttle service routes for each country, region, province, state, city, county, district, specific area (e.g., within certain city blocks, on certain roads, within a geometric shape drawn on a map, etc.), etc., the granularity of which may be based on supply, demand, date, day, time, holidays or special events, etc.
  • the candidate shuttle service route selector 156 may be configurable to select candidate shuttle service routes for each year, month, week, day, specific hour(s) and/or minutes, peak hours, rush hours, etc.
  • the candidate shuttle service route selector 156 may be configurable to select the candidate shuttle service routes through a cooperation with the potential user selector 154, which may consider and/or target certain users or types of users (e.g., price-sensitive user, users that are frequent users of low cost services, and/or users with a history of unallocated requests, unmatched requests, cancelled requests, abandoned requests, etc.).
  • the candidate shuttle service route selector 156 may be configurable to select candidate shuttle service routes based on a number or frequency of selected historic non-shuttle service routes having similar, the same, and/or overlapping routes or portions of routes. In respect to availability and/or location of shuttles, the candidate shuttle service route selector 156 may be configurable to select candidate shuttle service routes based on whether an available or to-be-available potential shuttle or service provider of the shuttle service has or will have a location near to an origin location of candidate shuttle service route.
  • the one or more criterion and/or parameters, including geographical region, starting time, time or period of time, origin location, destination location, route, user-specific criterion, availability and/or location of shuttles, etc., used by the candidate shuttle service route selector 156 may be any criterion and/or parameter thereof (e.g., any amount, duration, type, etc.) without departing from the teachings of the present disclosure.
  • Shuttle service route manager e.g., shuttle service route manager 157).
  • the processor 150 may include (and/or be configurable or configured to perform one or more functionalities of) of one or more shuttle service route managers (e.g., shuttle service route manager 157).
  • the shuttle service route manager 157 may be configurable or configured to manage the shuttle service routes selected by the candidate shuttle service route selector 156. In doing so, the shuttle service route manager 157 may be configurable to enable users to view and/or book on one or more of the selected shuttle service routes.
  • the shuttle service route manager 157 may also be configurable to enable shuttle service providers to confirm servicing of one or more of the selected shuttle service routes.
  • the shuttle service route manager 157 may also cooperate with the shuttle-side notification and dispatch controller 158 and/or the user-side notification and booking controller 159 to manage the selected shuttle service routes.
  • Shuttle-side notification and dispatch controller e.g., shuttle-side notification and dispatch controller 158.
  • the processor 150 may include (and/or be configurable or configured to perform one or more functionalities of) of one or more shuttle-side notification and dispatch controllers (e.g., shuttle-side notification and dispatch controller 158).
  • the shuttle-side notification and dispatch controller 158 may be configurable or configured to provide notifications to shuttle service providers of selected shuttle service routes.
  • Notifications provided by the shuttle-side notification and dispatch controller 158 may be provided to all shuttle service providers registered and/or located (or projected, predicted, or estimated to be located) within a geographical region covering the origin location and/or destination location of the selected shuttle service route, within a predetermined distance (and/or travel time) of the origin location and/or destination location of the selected shuttle service route, and/or to certain shuttle service providers based on one or more considerations.
  • the notifications may be provided to those shuttle service providers that are available or will be available to service the selected shuttle service route at the starting time of the selected shuttle service route.
  • the notifications may be provided to those shuttle service providers that have vehicle capacity to service the projected, predicted, or estimated number of potential users.
  • the notifications may be provided to those shuttle service providers that have previously provided shuttle services.
  • the shuttle-side notification and dispatch controller 158 may also be configurable to accept commitments from shuttle service providers who accept, confirm, and/or agree to service the selected shuttle service route, and dispatch the shuttle service provider(s) (including providing information on one or more of the following: starting time, origin location, destination location, pick-up location(s), drop-off location(s), fees to be charged or collected for each user, predicted, projected, or estimated number of users, etc.).
  • User-side notification and booking controller e.g., user-side notification and booking controller 159.
  • the processor 150 may include (and/or be configurable or configured to perform one or more functionalities of) of one or more user-side notification and booking controllers (e.g., user-side notification and booking controller 159).
  • the user-side notification and booking controller 159 may be configurable or configured to provide notifications to potential users of selected shuttle service routes.
  • Notifications provided by the user-side notification and booking controller 159 may be provided to all users registered and/or located (or projected, predicted, or expected to be located) within a geographical region covering the origin location and/or destination location of the selected shuttle service route, within a predetermined distance (and/or travel time) of the origin location and/or destination location of the selected shuttle service route, and/or to certain users based on one or more considerations.
  • the notifications may be provided to those users who are projected, predicted, and/or expected to require transport-related services at the starting time of the selected shuttle service route, from the origin location and/or one of the pick-up locations along the route, to the destination location and/or one of the drop-off locations along the route, etc.
  • the notifications may be provided to those users who have been identified as being a potential user.
  • the notifications may be provided to those users who have previously booked shuttle services.
  • the user-side notification and booking controller 159 may also be configurable to accept bookings from users, and/or provide confirmed details on the selected shuttle service route including one or more of the following: starting time, origin location, destination location, pick-up location(s), drop-off location(s), fees to be charged or collected for each user, details of the shuttle service provider (e.g., make and model of the vehicle, license plate, color, name of driver, etc.), predicted, projected, or estimated number of total users, etc.).
  • details of the shuttle service provider e.g., make and model of the vehicle, license plate, color, name of driver, etc.
  • Method of managing a shuttle service based on routes e.g., method 300.
  • an example embodiment of a method (e.g., method 300) of managing a shuttle service may be based on, among other things, origin locations, destination locations, routes, starting times, and/or ending times of historic non-shuttle service requests.
  • the method 300 may include searching a database of historic transport-related requests to identify a plurality of historic non-shuttle service requests (e.g., action 302).
  • Each historic non-shuttle service request may include a start time and a route.
  • the route may be defined by at least an origin location and a destination location.
  • the method 300 may also include selecting a plurality of historic non-shuttle service requests (e.g., action 304).
  • One or more of the selected historic non-shuttle service requests may include at least a portion of its route in common with (or overlapping) at least a portion of one or more other selected historic non-shuttle service requests.
  • the selecting may be based on those historic non-shuttle service requests having start times within a first threshold time period (e.g., 5, 10, 15, 20, or 30 minute periods, etc.).
  • the selecting may also be based on those historic non- shuttle service requests having origin locations located within a first threshold area (e.g., 5, 10, 20, 30, 50, 100 meter radius, same street, same intersection, same building or complex, customized area, etc.).
  • the selecting may also be based on those historic non-shuttle service requests having destination locations located within a second threshold area (e.g., 5, 10, 20, 30, 50, 100 meter radius, same street, same intersection, same building or complex, customized area, etc.).
  • the selecting may also include selecting historic non-shuttle service requests that were not allocated, not matched, cancelled, and/or abandoned.
  • One or more of the selected historic non-shuttle service requests may also include requests for taxi service, private car service, and/or ride share service.
  • each historic non-shuttle service request may be a transport- related request that is not a request for shuttle service.
  • the method 300 may further include performing an analysis to identify one or more users who may be price-sensitive.
  • the method 300 may then include selecting one or more potential users for the shuttle service, at least one of the selected potential users being a user identified as being price-sensitive.
  • the selecting of the one or more historic non-shuttle service requests may include selecting one or more historic non-shuttle service requests previously sent by one or more of the selected potential users.
  • the method 300 may also include deriving a candidate shuttle service route for use in providing a shuttle service (e.g., action 306).
  • the candidate shuttle service route may be derived based on one or more of the selected historic non-shuttle service requests.
  • the deriving of the candidate shuttle service route may be based on at least the start time, route, origin location, and/or destination location of one or more of the selected historic non- shuttle service requests.
  • the method 300 may further include deriving one or more drop off and/or one or more pickup locations between the origin location for the candidate shuttle service route and destination location for the candidate shuttle service route.
  • the one or more drop off and/or one or more pickup locations may be derived based on the start time, origin location, and/or destination location of one or more of the selected historic non-shuttle service requests.
  • the method may further include refining, adjusting, and/or changing the candidate service route so as to minimize a quantity of pickups and/or drop offs along the candidate service route.
  • the refining, adjusting, and/or changing of the candidate service route may also be based on one or more considerations and/or criterion described above and in the present disclosure.
  • the refining, adjusting, and/or changing of the candidate service route may pertain to the start time and/or end time for the candidate shuttle service route, the origin location for the candidate shuttle service route, the destination location for the candidate shuttle service route, the pick-up location(s), the drop-off location(s), the costs, the fees or fares, etc.
  • the database of historic transport-related requests may also include a plurality of historic shuttle service requests, in which case, the deriving of the candidate shuttle service route may be further based on one or more of the historic shuttle service requests.
  • the method 300 may also include deriving a start time for the candidate shuttle service route, an origin location for the candidate shuttle service route, and a destination location for the candidate shuttle service route.
  • the start time for the candidate shuttle service route, the origin location for the candidate shuttle service route, and the destination location for the candidate shuttle service route may be derived based on the start time, origin location, and/or destination location of one or more of the selected historic non-shuttle service requests.
  • the method 300 may also include selecting one or more potential users for the shuttle service and communicating to one or more of the selected potential users. Such communicating may include providing information pertaining to the candidate shuttle service route and/or an opportunity to receive shuttle service on the candidate shuttle service route.
  • the method 300 may also include performing a service provider matching process to match a service provider with the candidate shuttle service route.
  • the service provider matching process may be based on minimizing a travel distance and/or travel time by the matched service provider between servicing a prior candidate shuttle service route and servicing the candidate service route.
  • the service provider matching process may be based on minimizing a travel distance and/or travel time by the matched service provider between servicing the candidate service route and a next candidate shuttle service route.
  • Method of managing a shuttle service based on available and/or nearby shuttles e.g., method 400.
  • an example embodiment of a method (e.g., method 400) of managing a shuttle service may be based on, among other things, available and/or nearby shuttles or shuttle service providers.
  • the method 400 may include searching a database of historic transport -related requests to identify a plurality of historic non-shuttle service requests (e.g., action 402).
  • Each historic non-shuttle service request may include a start time and a route defined by at least an origin location and a destination location.
  • the method 400 may also include selecting one or more of the historic non-shuttle service requests (e.g., action 404). Each selected historic non-shuttle service request may include at least a portion of its route in common with one or more other selected historic non-shuttle service requests.
  • the selecting of the one or more historic non-shuttle service requests may be based on those historic non-shuttle service requests having start times within a first threshold time period. Alternatively or in addition, the selecting of the one or more historic non-shuttle service requests may be based on those historic non-shuttle service requests having origin locations located within a first threshold area. Alternatively or in addition, the selecting of the one or more historic non- shuttle service requests may be based on those historic non-shuttle service requests having destination locations located within a second threshold area.
  • the selecting of the historic non-shuttle service requests may include selecting historic non-shuttle service requests that were not allocated, not matched, cancelled, and/or abandoned. Furthermore, one or more of the selected historic non-shuttle service requests may include requests for taxi service, private car service, and/or ride share service. Each historic non-shuttle service request may be a transport-related request that is not a request for shuttle service. [00108]
  • the method 400 may also include performing an analysis to identify one or more users who may be price-sensitive. The method 400 may then include selecting one or more potential users for the shuttle service. At least one of the selected potential users may be a user identified as being price-sensitive. The selecting of the one or more historic non-shuttle service requests may include selecting one or more historic non-shuttle service requests previously sent by one or more of the selected potential users.
  • the method 400 may also include selecting one or more candidate service providers available to service one or more of the selected historic non-shuttle service requests (e.g., action 406).
  • the selecting of the candidate service providers may be based on minimizing a travel distance and/or travel time by the candidate service providers between servicing a prior candidate shuttle service route and servicing the candidate service route.
  • the selecting of the candidate service providers may be based on minimizing a travel distance and/or travel time by the candidate service providers between servicing the candidate service route and a next candidate shuttle service route.
  • the method 400 may also include deriving one or more candidate shuttle service routes (e.g., action 408).
  • the one or more candidate shuttle service routes may be derived based on one or more of the selected historic non-shuttle service requests.
  • the deriving of the candidate shuttle service route may be based on at least the start time, route, origin location, and/or destination location of one or more of the selected historic non-shuttle service requests.
  • the method 400 may also include deriving a start time for the candidate shuttle service route, an origin location for the candidate shuttle service route, and a destination location for the candidate shuttle service route.
  • the start time for the candidate shuttle service route, the origin location for the candidate shuttle service route, and the destination location for the candidate shuttle service route may be derived based on the start time, origin location, and/or destination location of one or more of the selected historic non-shuttle service requests.
  • the method 400 may also include deriving one or more drop off and/or one or more pickup locations between the origin location for the candidate shuttle service route and destination location for the candidate shuttle service route.
  • the one or more drop off and/or one or more pickup locations may be derived based on the start time, origin location, and/or destination location of one or more of the selected historic non-shuttle service requests.
  • the method 400 may further include refining, adjusting, and/or changing the candidate service route so as to minimize a quantity of pickups and/or drop offs along the candidate service route.
  • the refining, adjusting, and/or changing of the candidate service route may also be based on one or more considerations and/or criterion described above and in the present disclosure.
  • the refining, adjusting, and/or changing of the candidate service route may pertain to the start time and/or end time for the candidate shuttle service route, the origin location for the candidate shuttle service route, the destination location for the candidate shuttle service route, the pick-up location(s), the drop-off location(s), the costs, the fees or fares, etc.
  • the database of historic transport-related requests may also include a plurality of historic shuttle service requests, in which case, the deriving of the candidate shuttle service route may be further based on one or more of the historic shuttle service requests.
  • the method 400 may also include selecting one or more of the candidate shuttle service routes for use in providing a shuttle service (e.g., action 410).
  • the selected one or more candidate shuttle service routes may be selected based on one or more of the selected candidate service providers.
  • the method 400 may further include selecting one or more potential users for the shuttle service, and communicating to one or more of the selected potential users.
  • the communicating may include providing information pertaining to the candidate shuttle service route and/or an opportunity to receive shuttle service on the candidate shuttle service route.
  • Method of managing a shuttle service based on potential users and/or previously unallocated, unmatched, and/or cancelled requests e.g., method 500.
  • an example embodiment of a method (e.g., method 500) of managing a shuttle service may be based on, among other things, potential users and/or previously unallocated, unmatched, cancelled, and/or abandoned requests.
  • the method 500 may include searching a database of historic transport-related requests to identify a plurality of historic non-shuttle service requests (e.g., action 502).
  • Each historic non-shuttle service request may include a start time and a route defined by at least an origin location and a destination location.
  • the method 500 may also include selecting one or more potential users for a shuttle service (e.g., action 504).
  • One or more of the selected potential users may be identified as a price- sensitive user.
  • the method 500 may also include selecting one or more of the historic non-shuttle service requests (e.g., action 506).
  • One or more of the selected historic non-shuttle service requests may be a request previously sent by one of the selected potential users.
  • one or more of the selected historic non-shuttle service requests may be a request that was not allocated, not matched, cancelled, and/or abandoned.
  • Each selected historic non-shuttle service request may include at least a portion of its route in common with one or more other selected historic non-shuttle service requests.
  • the selecting of the one or more historic non-shuttle service requests may be based on those historic non-shuttle service requests having start times within a first threshold time period.
  • the selecting of the one or more historic non- shuttle service requests may be based on those historic non-shuttle service requests having origin locations located within a first threshold area.
  • the selecting of the one or more historic non-shuttle service requests may be based on those historic non-shuttle service requests having destination locations located within a second threshold area.
  • One or more of the selected historic non-shuttle service requests may include requests for taxi service, private car service, and/or ride share service.
  • each historic non-shuttle service request may be a transport-related request that is not a request for shuttle service.
  • the method 500 may also include deriving a candidate shuttle service route for use in providing the shuttle service (e.g., action 508).
  • the candidate shuttle service route may be derived based on one or more of the selected historic non-shuttle service requests.
  • the deriving of the candidate shuttle service route may be based on at least the start time, route, origin location, and/or destination location of one or more of the selected historic non-shuttle service requests.
  • the method 500 may also include deriving a start time for the candidate shuttle service route, an origin location for the candidate shuttle service route, and a destination location for the candidate shuttle service route.
  • the start time for the candidate shuttle service route, the origin location for the candidate shuttle service route, and the destination location for the candidate shuttle service route may be derived based on the start time, origin location, and/or destination location of one or more of the selected historic non-shuttle service requests.
  • the method 500 may also include deriving one or more drop off and/or one or more pickup locations between the origin location for the candidate shuttle service route and destination location for the candidate shuttle service route.
  • the one or more drop off and/or one or more pickup locations may be derived based on the start time, origin location, and/or destination location of one or more of the selected historic non-shuttle service requests.
  • the database of historic transport-related requests may also include a plurality of historic shuttle service requests, in which case, the deriving of the candidate shuttle service route may be further based on one or more of the historic shuttle service requests.
  • the method 500 may further include performing an analysis to identify one or more users who may be price-sensitive.
  • the method 500 may then include selecting one or more potential users for the shuttle service. At least one of the selected potential users may be a user identified as being price-sensitive.
  • the selecting of the one or more historic non- shuttle service requests may include selecting one or more historic non-shuttle service requests previously sent by one or more of the selected potential users.
  • the method 500 may further include communicating to one or more of the selected potential users.
  • the communicating may include providing information pertaining to the candidate shuttle service route and/or an opportunity to receive shuttle service on the candidate shuttle service route.
  • the method 500 may further include performing a service provider matching process to match a service provider with the candidate shuttle service route.
  • the service provider matching process may be based on minimizing a travel distance and/or travel time by the matched service provider between servicing a prior candidate shuttle service route and servicing the candidate service route.
  • the service provider matching process may also be based on minimizing a travel distance and/or travel time by the matched service provider between servicing the candidate service route and a next candidate shuttle service route.
  • Example embodiments of the method of managing shuttle services 300, 400, and/or 500, as described above and in the present disclosure may include or not include one or more of the actions and/or functionalities described above and in the present disclosure, may include additional actions and/or functionalities, may be performed and/or used in different sequences, combinations, and/or configurations, and/or one or more of the actions and/or functionalities may be combinable into a single action and/or functionality and/or divided into two or more actions and/or functionalities.
  • a processor, device, computing device, telephone, phone, server, gateway server, communication gateway server, and/or controller may be any processor, computing device, and/or communication device, and may include a virtual machine, computer, node, instance, host, or machine in a networked computing environment.
  • a network or cloud may be or include a collection of machines connected by communication channels that facilitate communications between machines and allow for machines to share resources. Network may also refer to a communication medium between processes on the same machine.
  • a network element, node, or server may be a machine deployed to execute a program operating as a socket listener and may include software instances.
  • Database may comprise any collection and/or arrangement of volatile and/or non-volatile components suitable for storing data.
  • memory may comprise random access memory (RAM) devices, read-only memory (ROM) devices, magnetic storage devices, optical storage devices, solid state devices, and/or any other suitable data storage devices.
  • database may represent, in part, computer -readable storage media on which computer instructions and/or logic are encoded.
  • Database may represent any number of memory components within, local to, and/or accessible by a processor and/or computing device.
  • Words of comparison, measurement, and timing such as “at the time,” “equivalent,” “during,” “complete,” and the like should be understood to mean “substantially at the time,” “substantially equivalent,” “substantially during,” “substantially complete,” etc., where “substantially” means that such comparisons, measurements, and timings are practicable to accomplish the implicitly or expressly stated desired result.

Landscapes

  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Engineering & Computer Science (AREA)
  • Economics (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Tourism & Hospitality (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Physics & Mathematics (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Game Theory and Decision Science (AREA)
  • Development Economics (AREA)
  • Educational Administration (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Primary Health Care (AREA)
  • Traffic Control Systems (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Navigation (AREA)

Abstract

L'invention se rapporte de manière générale, dans des modes de réalisation donnés à titre d'exemple, à des procédés de gestion de services de navette. Le procédé peut comprendre la recherche d'une base de données de requêtes historiques liées au transport pour identifier une pluralité de requêtes historiques de service non-navette. Chaque requête historique de service non-navette peut comprendre une heure de début et un itinéraire. L'itinéraire peut être défini par au moins un emplacement d'origine et un emplacement de destination. Le procédé peut également consister à sélectionner une pluralité de requêtes historiques de service non-navette. Une ou plusieurs des requêtes historiques de service non-navette sélectionnées peuvent comprendre au moins une partie de leur itinéraire en commun avec une ou plusieurs autres requêtes historiques de service non-navette sélectionnées. Le procédé peut également consister à dériver un itinéraire de service de navette candidat à utiliser pour offrir un service de navette. L'itinéraire de service de navette candidat peut être dérivé sur la base d'une ou de plusieurs requêtes historiques de service non-navette sélectionnées.
PCT/SG2017/050271 2017-05-26 2017-05-26 Systèmes et procédés de gestion de services de navette et de dérivation de services et d'itinéraires de service de navette WO2018217161A1 (fr)

Priority Applications (5)

Application Number Priority Date Filing Date Title
KR1020197038246A KR102390269B1 (ko) 2017-05-26 2017-05-26 셔틀 서비스 관리 및 셔틀 서비스 루트 및 서비스 도출을 위한 시스템 및 방법
PCT/SG2017/050271 WO2018217161A1 (fr) 2017-05-26 2017-05-26 Systèmes et procédés de gestion de services de navette et de dérivation de services et d'itinéraires de service de navette
CN201780092576.7A CN110832535A (zh) 2017-05-26 2017-05-26 管理班车服务和推导班车服务路线和服务的系统和方法
JP2019565309A JP6956810B2 (ja) 2017-05-26 2017-05-26 シャトルサービスを管理する方法
PH12019502670A PH12019502670A1 (en) 2017-05-26 2019-11-26 Systems and methods for managing shuttle services and deriving of shuttle service routes and services

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/SG2017/050271 WO2018217161A1 (fr) 2017-05-26 2017-05-26 Systèmes et procédés de gestion de services de navette et de dérivation de services et d'itinéraires de service de navette

Publications (1)

Publication Number Publication Date
WO2018217161A1 true WO2018217161A1 (fr) 2018-11-29

Family

ID=64396917

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SG2017/050271 WO2018217161A1 (fr) 2017-05-26 2017-05-26 Systèmes et procédés de gestion de services de navette et de dérivation de services et d'itinéraires de service de navette

Country Status (5)

Country Link
JP (1) JP6956810B2 (fr)
KR (1) KR102390269B1 (fr)
CN (1) CN110832535A (fr)
PH (1) PH12019502670A1 (fr)
WO (1) WO2018217161A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110175691A (zh) * 2019-04-09 2019-08-27 阿里巴巴集团控股有限公司 规划区域交通运营线路的方法、装置和电子设备
WO2020220188A1 (fr) * 2019-04-29 2020-11-05 Grabtaxi Holdings Pte. Ltd. Appareil serveur de communication, procédés et systèmes de communication permettant la recommandation d'un ou plusieurs points d'intérêt pour un service lié au transport à un utilisateur
WO2020231324A1 (fr) * 2019-05-16 2020-11-19 Grabtaxi Holdings Pte. Ltd. Appareil serveur de communications et procédé de déduction d'un modificateur quantique pour un service lié au transport
JPWO2019145747A1 (ja) * 2018-01-25 2021-02-12 日産自動車株式会社 車両管理方法及び車両管理装置
US11621921B2 (en) * 2017-06-14 2023-04-04 Beijing Didi Infinity Technology And Development Co., Ltd. Systems and methods for transport capacity scheduling

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112418465B (zh) * 2020-11-05 2021-06-15 盐城工业职业技术学院 一种轨道式校车系统
CN114049757B (zh) * 2021-08-27 2023-03-21 北京中交兴路信息科技有限公司 班车到站时间预估方法、装置、计算机设备和存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070143012A1 (en) * 2005-12-20 2007-06-21 Trapeze Software Inc. System and method of optimizing a fixed-route transit network
US20080059273A1 (en) * 2006-02-21 2008-03-06 Dynamic Intelligence Inc. Strategic planning
US20100299177A1 (en) * 2009-05-22 2010-11-25 Disney Enterprises, Inc. Dynamic bus dispatching and labor assignment system
US20130024249A1 (en) * 2010-04-08 2013-01-24 Zeev El Asher Adin Zohar Public transport optimization
US9562785B1 (en) * 2015-07-20 2017-02-07 Via Transportation, Inc. Continuously updatable computer-generated routes with continuously configurable virtual bus stops for passenger ride-sharing of a fleet of ride-sharing vehicles and computer transportation systems and computer-implemented methods for use thereof

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002140399A (ja) * 2000-11-02 2002-05-17 Nippon Telegr & Teleph Corp <Ntt> 自動車乗合支援方法及びシステム
JP2002286486A (ja) * 2001-03-28 2002-10-03 Casio Comput Co Ltd 車両用走行ルート情報提供方法及びその支援システム
US20030040944A1 (en) * 2001-08-22 2003-02-27 Hileman Ryan M. On-demand transportation system
JP2004199179A (ja) * 2002-12-16 2004-07-15 Toshihiro Hosokawa デマンドバス運行管理システムおよび方法
KR20110132765A (ko) * 2010-06-03 2011-12-09 아주대학교산학협력단 카풀 서비스를 제공하는 방법, 서버 및 그 시스템
KR20130040430A (ko) * 2011-10-14 2013-04-24 (주)스마트비아 카풀 운영 장치 및 방법
JP2013186541A (ja) * 2012-03-06 2013-09-19 Nissan Motor Co Ltd オンデマンド車両の運行システム及びオンデマンド車両の運行計画設定方法
KR20130111801A (ko) * 2012-04-02 2013-10-11 한국전자통신연구원 다수의 경유지에 대한 경로 설정 방법
KR101586815B1 (ko) * 2014-01-29 2016-01-20 (주)휴빌론 통신형 내비게이션을 이용한 카풀 서비스 제공방법 및 시스템
CN105976038A (zh) * 2016-05-03 2016-09-28 易通创新科技（大连）有限公司 一种基于用户需求的定制班车系统
KR101681293B1 (ko) * 2016-06-13 2016-12-12 주식회사 더불어 교통수단 동승 서비스 제공 시스템

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070143012A1 (en) * 2005-12-20 2007-06-21 Trapeze Software Inc. System and method of optimizing a fixed-route transit network
US20080059273A1 (en) * 2006-02-21 2008-03-06 Dynamic Intelligence Inc. Strategic planning
US20100299177A1 (en) * 2009-05-22 2010-11-25 Disney Enterprises, Inc. Dynamic bus dispatching and labor assignment system
US20130024249A1 (en) * 2010-04-08 2013-01-24 Zeev El Asher Adin Zohar Public transport optimization
US9562785B1 (en) * 2015-07-20 2017-02-07 Via Transportation, Inc. Continuously updatable computer-generated routes with continuously configurable virtual bus stops for passenger ride-sharing of a fleet of ride-sharing vehicles and computer transportation systems and computer-implemented methods for use thereof

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"An Affordable Shuttle Service for Commuters", GRAB LAUNCHES GRABSHUTTLE, 2 March 2017 (2017-03-02), Retrieved from the Internet <URL:https://www.grab.com/sg/press/others/grab-launches-grabshuttle-affordable-shuttle-service-commuters> [retrieved on 20170817] *
LYFT SHUTTLE IS A BUS SERVICE FOR COMMUTERS WITH FIXED ROUTES AND FARES, 30 March 2017 (2017-03-30), Retrieved from the Internet <URL:https://www.aivanet.com/2017/03/lyft-shuttle-is-a-bus-service-for-commuters-with-fixed-routes-and-fares> [retrieved on 20170817] *

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11621921B2 (en) * 2017-06-14 2023-04-04 Beijing Didi Infinity Technology And Development Co., Ltd. Systems and methods for transport capacity scheduling
JPWO2019145747A1 (ja) * 2018-01-25 2021-02-12 日産自動車株式会社 車両管理方法及び車両管理装置
CN110175691A (zh) * 2019-04-09 2019-08-27 阿里巴巴集团控股有限公司 规划区域交通运营线路的方法、装置和电子设备
CN110175691B (zh) * 2019-04-09 2023-06-02 创新先进技术有限公司 规划区域交通运营线路的方法、装置和电子设备
WO2020220188A1 (fr) * 2019-04-29 2020-11-05 Grabtaxi Holdings Pte. Ltd. Appareil serveur de communication, procédés et systèmes de communication permettant la recommandation d'un ou plusieurs points d'intérêt pour un service lié au transport à un utilisateur
WO2020231324A1 (fr) * 2019-05-16 2020-11-19 Grabtaxi Holdings Pte. Ltd. Appareil serveur de communications et procédé de déduction d'un modificateur quantique pour un service lié au transport
JP2022532904A (ja) * 2019-05-16 2022-07-20 グラブタクシー ホールディングス プライベート リミテッド 輸送関連サービスのための量子修飾子を得るための通信サーバ装置および方法
JP7303333B2 (ja) 2019-05-16 2023-07-04 グラブタクシー ホールディングス プライベート リミテッド 輸送関連サービスのための量子修飾子を得るための通信サーバ装置および方法

Also Published As

Publication number Publication date
KR102390269B1 (ko) 2022-04-25
JP2020522064A (ja) 2020-07-27
CN110832535A (zh) 2020-02-21
KR20200013243A (ko) 2020-02-06
JP6956810B2 (ja) 2021-11-02
PH12019502670A1 (en) 2020-06-08

Similar Documents

Publication Publication Date Title
US20210319380A1 (en) System and method for facilitating a transport service for drivers and users of a geographic region
US11416795B2 (en) Systems and methods for vehicle resource management
KR102390269B1 (ko) 셔틀 서비스 관리 및 셔틀 서비스 루트 및 서비스 도출을 위한 시스템 및 방법
US11386359B2 (en) Systems and methods for managing a vehicle sharing facility
US9805431B2 (en) Systems and methods for allocating networked vehicle resources in priority environments
US9857190B2 (en) System for generating travel route to be serviced by primary transportation service and secondary transportation service
JP2022106777A (ja) ライドシェアリング（相乗り）を管理するためのシステムと方法
US11392861B2 (en) Systems and methods for managing a vehicle sharing facility
US20170169366A1 (en) Systems and Methods for Adjusting Ride-Sharing Schedules and Routes
US20150254581A1 (en) Rideshare system and method to facilitate instant carpooling
US20130246301A1 (en) Providing user feedback for transport services through use of mobile devices
WO2018208226A1 (fr) Attribution optimale de fournisseurs de services et de demandeurs de services groupés de manière dynamique
US20150032485A1 (en) Digital method For Providing Transportation Services
US20180075566A1 (en) System and method of calculating a price for a vehicle journey
WO2020230149A1 (fr) Procédé et système pour des options de transport et de voyage multi-destinations multimodales en temps réel
AU2015202596B2 (en) System and method for arranging transport amongst parties through use of mobile devices

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17911320

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019565309

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20197038246

Country of ref document: KR

Kind code of ref document: A

122 Ep: pct application non-entry in european phase

Ref document number: 17911320

Country of ref document: EP

Kind code of ref document: A1