KR102390269B1 - System and method for shuttle service management and shuttle service route and service derivation - Google Patents

Abstract

Exemplary embodiments relate generally to a method of administering a shuttle service. The method may include searching a database of historical transportation-related requests to identify a plurality of historical non-shuttle service requests. Each past non-shuttle service request may include a start time and route. A route may be defined by at least an original location and an arrival location. The method may also include selecting a plurality of past non-shuttle service requests. The one or more selected past non-shuttle service requests may include at least a portion of a route common to one or more other selected past non-shuttle service requests. The method may also include deriving a candidate shuttle service route for use in providing the shuttle service. A candidate shuttle service route may be derived based on one or more selected past non-shuttle service requests.

Description

System and method for shuttle service management and shuttle service route and service derivation

FIELD OF THE INVENTION The present invention relates generally to managing transport-related services, and more particularly to methods, systems and apparatus for managing shuttle-related services, including derivation of shuttle service routes.

Technological developments in computing technology and communications continue to empower suppliers to create and deliver new and improved offerings for products and services. Online services made available by these developments include, but are not limited to, information retrieval, purchasing, reserving, booking, add to cart, deposit, partial payment, storage and/or sharing of products and/or services; , but is not limited thereto. Currently, users are increasingly able to conduct online transactions more easily, efficiently and effectively for products and/or services that have traditionally been done in other ways.

It is recognized that, despite recent advances in computing technology, including systems, apparatus, software, methods and communications, difficulties or problems are often encountered when managing transportation-related services, including shuttle services, in the present disclosure.

The present exemplary embodiments relate generally to and/or include systems, subsystems, processors, apparatus, logic and methods for solving the problems of the prior art, including those described above and in this disclosure, and more particularly In general, exemplary embodiments relate to systems, subsystems, processors, apparatus, logic and methods for managing shuttle-related services and deriving shuttle service routes.

In an exemplary embodiment, a method for managing a shuttle service is described. The method may include searching a database of historical transportation-related requests to identify a plurality of historical non-shuttle service requests. Each past non-shuttle service request may include a start time and route. A route may be defined by at least an original location and an arrival location. The method may also include selecting a plurality of past non-shuttle service requests. The one or more selected past non-shuttle service requests may include at least a portion of a route common to one or more other selected past non-shuttle service requests. The method may also include deriving a candidate shuttle service route for use in providing a shuttle service. A candidate shuttle service route may be derived based on one or more selected past non-shuttle service requests.

In another exemplary embodiment, a method for managing a shuttle service is described. The method may include searching a database of past transportation-related requests to identify a plurality of past non-shuttle service requests. Each past non-shuttle service request may include a start time and a route defined by at least an original location and an arrival location. The method may also include selecting one or more past non-shuttle service requests. The method may also include selecting one or more candidate service providers available to service one or more selected past non-shuttle service requests. The method may also include deriving one or more candidate shuttle service routes, wherein the one or more candidate shuttle service routes are derived based on one or more selected past non-shuttle service requests. The method may also include selecting one or more candidate shuttle service routes for use in providing the shuttle service. The selected one or more candidate shuttle service routes may be selected based on the one or more selected candidate service providers.

In another exemplary embodiment, a method for managing a shuttle service is described. The method may include searching a database of past transportation-related requests to identify a plurality of past non-shuttle service requests. Each past non-shuttle service request may include a start time and a route defined by at least an original location and an arrival location. The method may also include selecting one or more potential users for the shuttle service. One or more selected potential users may be identified as price sensitive users. The method may also include selecting one or more past non-shuttle service requests. The one or more selected past non-shuttle service requests may be requests previously sent by one of the selected potential users. Alternatively or additionally, the one or more selected past non-shuttle service requests may be unassigned, unmatched, and/or canceled requests. The method may also include deriving a candidate shuttle service route for use in providing shuttle service, wherein the candidate shuttle service route is derived based on one or more selected past non-shuttle service requests.

In another exemplary embodiment, a method for managing a shuttle service is described. The method may include searching a database of past transportation-related requests to identify a plurality of past non-shuttle service requests received from a plurality of users. Each past non-shuttle service request may include a start time and a route defined by at least an original location and an arrival 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 the 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 past non-shuttle service requests if the past non-shuttle service request is a request previously sent by one or more selected potential users. Alternatively or additionally, the method may include selecting one or more past non-shuttle service requests if the past non-shuttle service request is an unassigned, unmatched, and/or canceled request. there is. Alternatively or additionally, the method selects one or more past non-shuttle service requests if the past non-shuttle service request has at least a portion of a route common to one or more other selected past non-shuttle service requests. may include the step of The method may also include selecting one or more candidate service providers available to service one or more selected past non-shuttle service requests. The method may also include deriving one or more candidate shuttle service routes. One or more candidate shuttle service routes may be derived based on one or more selected past 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 selected candidate service providers.

For a more complete understanding of the present disclosure, exemplary embodiments and advantages thereof, reference is now made to the following description taken in conjunction with the accompanying drawings, wherein like reference numerals denote like features,
1 is a diagram of an exemplary embodiment of a system for managing a shuttle service;
2 is a diagram of an exemplary embodiment of a processor for managing a shuttle service;
3 is a diagram of an exemplary embodiment of a method for managing a shuttle service;
4 is a diagram of another exemplary embodiment of a method for managing a shuttle service;
5 is a diagram of another exemplary embodiment of a method for managing a shuttle service;
Although like reference numbers may be used to refer to like elements in the drawings for convenience, it is to be understood that each of the various illustrative embodiments may be considered a separate modification.
BRIEF DESCRIPTION OF THE DRAWINGS Exemplary embodiments will be described below with reference to the accompanying drawings, which form a part of the present disclosure and which illustrate exemplary embodiments that may be practiced. As used in this disclosure and the appended claims, the terms “embodiment”, “example embodiment”, “exemplary embodiment” and “present embodiment” may, but must not be Reference is not made to a single embodiment, and various illustrative embodiments may be readily combined and/or interchanged without departing from the scope or spirit of the illustrative embodiment. Also, the terminology used in this disclosure and the appended claims is for the purpose of describing exemplary embodiments only and is not intended to be limiting. In this regard, as used in this disclosure and the appended claims, the term “in” may include “in” and “on” and the term “in” “,” “an,” and “the” may include singular and plural references. Also, as used in this disclosure and the appended claims, the term “by” may also mean “from” depending on the context. Also, as used in this disclosure and the appended claims, the term “if” may mean “when” or “upon” depending on the context. Also, as used in this disclosure and the appended claims, the word “and/or” may refer to and encompass any and all possible combinations of one or more associated enumerated items.

Recent developments in computing technology continue to improve the ability of service providers and users to similarly interact. Examples of service providers include traditional and/or online sellers (eg, retail stores, department stores, e-commerce websites, etc.), providers of specialty products and/or services (eg, public transport, personal car rental, limousine services). , transportation-related services such as , shuttles, taxis, motorbike taxis, ride-share, delivery, etc.), intermediaries, resellers, brokers, people who provide platforms/services for comparative shopping and/or reviews (“Service Providers”) may include, but is not limited to. The technical products and solutions provided by these service providers include purchase, reserve, book, add to cart, deposit or partial payment, storage, cancellation and/or sharing of such products and/or services. continues to empower users to interact and/or transact more easily, effectively and/or efficiently.

For example, advances in technology may lead to public transport (trains, buses, etc.), taxis (cars, vans, motorcycles and other types of vehicles), private car rentals, limousine services, shuttles, ride-share, delivery, etc. and other types of vehicles. Transport-related services, such as services, are provided via a website or application (eg, mobile applications, widgets, etc.) on computing devices (eg, desktop computers, laptop computers/ultrabooks, mobile devices and/or wearables). device) to be retrieved, priced, compared, reserved and/or booked (and/or canceled) directly and easily from the device.

Despite recent advances in these technologies, it is recognized in this disclosure that difficulties or problems are often encountered when interacting online, particularly when administering shuttle-related services.

For example, conventional approaches to providing shuttle service are generally driven by a specified or known need or need for transportation service between two or more locations. As a more specific example, a shuttle service may be provided to meet the needs or needs of those who need to travel from a hotel to a convention center for a particular conference or show, and such shuttle service is typically a hotel, convention center, conference or The show organizer and/or one of them will be provided and/or constituted by the shuttle service provider hired, hired, or requested. As another more specific example, a shuttle service may be provided or configured by a company to meet the needs or needs of its employees who need to move from one office location of the company to another office location of the company. For such intentionally provided and/or configured shuttle services, the shuttle service route will generally include a fixed starting location for the shuttle service (which may be an already established bus stop, building entrance, or landmark location), a fixed starting location for the shuttle service, and a fixed starting location for the shuttle service. will include established end locations (which may be other established bus stops, building entrances, or landmark locations) and the start time of the shuttle service. While this traditional approach may satisfy the needs or needs of such related passengers if the organizer of such shuttle service knows or becomes aware of the need or need for such shuttle service between two specified locations, the present disclosure provides for any of the following: It is recognized that there is a need for an on-demand shuttle service, such as when more than one is available: there is no organizer and the departure and arrival locations are unknown and/or unspecified, and the needs or needs are unknown and/or unspecified. , the target user is unknown and/or unspecified, and the like.

The present exemplary embodiments relate generally to and/or include systems, subsystems, processors, apparatus, logic and methods for solving the problems of the prior art, including those described above and in this disclosure, and more specifically In general, exemplary embodiments relate to systems, subsystems, processors, apparatus, logic and methods for managing shuttles and/or shuttle-related services. Although exemplary embodiments may be described in this disclosure for use as pertaining to and/or in connection with passenger-based shuttles and/or shuttle-related services for buses, minibuses and/or other larger multi-passenger vehicles, It should be understood that the exemplary embodiments are also applicable and/or capable of being used in the delivery of parcels, articles, documents, etc., and in other environments, surroundings, circumstances, circumstances and/or applications without departing from the teachings of this disclosure. . Such exemplary embodiments will be described below with reference to the accompanying drawings, which form a part of the present disclosure.

An exemplary embodiment of a system (eg, system 100 ) for managing shuttle services.

As an overview, an exemplary embodiment of a system (eg, system 100 ) for managing a shuttle or shuttle-related service is shown in FIG. 1 . A system (eg, system 10 ) may include one or more identifiers (eg, identifier 150 ). As used in this disclosure, where applicable, reference to an identifier also refers to a computing device, server, cloud-based computing, etc. and/or function of the identifier, computing device, server, cloud-based computing, etc.; can be applied and/or included. System 100 may also include one or more databases (eg, databases 140 , 140a , 140b , 140c , 140d ). System 100 may also include one or more user computing devices (eg, user computing device 110 ). System 100 may also include one or more shuttle or service provider computing devices (eg, shuttle or service provider computing devices 120 ). One or more identifiers 150, databases 140, 140a-d, user computing device 110, and/or shuttle computing device 120 may include the Internet, the World Wide Web, one or more private networks, and the like. They may communicate with each other over one or more networks (eg, network 130 ).

As used herein, exemplary embodiments of shuttle services and/or shuttle-related services (hereinafter "shuttle services") manageable or managed by identification 150 are, among other things, multi-passenger, multiple of-user and/or multi-parcel transport-related services. The shuttle service is multi-passenger, multi-passenger, which may be simultaneously booked and/or serviced by more than one user at a time (eg, serve more than one paying user for each driving route). may be provided by the user and/or multi-parcel vehicle (hereinafter "shuttle, "service provider" or "shuttle service provider"). The shuttle or service provider may be an automobile, sport utility vehicle (SUV). vehicle), minivan, van, minibus, bus, coach, non-land vehicle (eg, boat, vehicle that can move underwater or water, vehicle that can move in the air, airplane, etc.), It may include autonomous and semi-autonomous versions of one or more of the vehicles and/or other multi-passenger vehicles The shuttle service may include, inter alia, a route, one or more stops along a route, a timing component; It may include a cost component and/or a fee or fee component.

In terms of routes, shuttle services may be provided on fixed, semi-fixed and/or variable routes. Each route may be predetermined and/or dynamically derived (eg, derived on-demand) based on one or more considerations and/or criteria. Each route is subject to traffic congestion, construction and/or accidents, situations during the route's service, when a new user just made a reservation for the shuttle, or when the reserved user does not board the shuttle on time (e.g. waiting time exceeded) , cancellation, etc.) may also be adjusted or changed during the service of the route. As further described in this disclosure, each route may include a departure location and an arrival location.

In terms of stops along a route, the shuttle service may include one or more stops along the entire route, which stops may also be predetermined and/or dynamically derived based on one or more considerations and/or criteria. there is. For example, a shuttle service may include a departure location (or an initial location, a starting location, a first location, etc., hereinafter "departure location"). Each starting location may be a single point (eg, a point on a map, latitude/longitude coordinates, GPS coordinates, etc.), a landmark, an address, a location name, an intersection, an area/area, and the like. The shuttle service may also include an arrival location (or final location, end location, last location, etc., hereinafter "arrival location"). Each arrival location may be a single point (eg, a point on a map, latitude/longitude coordinates, GPS coordinates, etc.), landmark, address, and/or area/area. The shuttle service may also include one or more pickup locations or stops (hereinafter “pickup locations” or “pick-up locations”) for picking up or having passengers or parcels picked up or boarded. Each pick-up location may be a single point (eg, a point on a map, latitude/longitude coordinates, GPS coordinates, etc.), landmark, address, and/or area/area. The shuttle service may also include one or more drop-off locations or stops (hereinafter “drop off locations” or “drop-off locations”) for disembarking or disembarking or disembarking passengers or parcels. there is. Each drop-off location may be a single point (eg, a point on a map, latitude/longitude coordinates, GPS coordinates, etc.), landmark, address, and/or area/area. Each stop may also be subject to traffic congestion, construction and/or accidents in the face of accidents, when a new user just made a reservation for the shuttle during the service of the route, or when the reserved user does not board the shuttle on time (e.g. waiting may also be adjusted or changed during the service of the route, such as timeouts, cancellations, etc.). As further described in this disclosure, each route may include a departure location and an arrival location. In this disclosure, it should be understood that the pickup location may be the same location as the drop off location (eg, the location may pick up one user and drop off another user). Additionally, the pickup location may also be the same location as the departure location, and the drop off location may also be the same location as the arrival location.

In terms of timing, a shuttle service may include a start time or duration (or an initial time, origin time, etc., hereinafter "start time" or "starting time"), which may include a shuttle or The date, day, time, duration and/or estimated time or duration date when the shuttle service commences, arrives and/or leaves the original location or is so predicted and/or when the shuttle service commences the entire route. can The shuttle service may also include an end time or duration (or final time, arrival time, etc., hereinafter "end time" or "ending time"), which means that the shuttle or shuttle service arrives at the destination location. It may be the date, day, shuttle or time, duration and/or estimated time or duration when the shuttle service completes its entire route and/or when expected to arrive and/or the shuttle service may also include one or more pickup times. This may be the date, day, time, duration and/or estimated time or duration when the shuttle or shuttle service arrives at or is expected to arrive at the pickup location.The shuttle service may also provide one or more drop off times which may be the date, day, time, duration and/or estimated time or duration when the shuttle or shuttle service arrives at or is expected to arrive at the drop off location.

In terms of cost, the shuttle service may determine the cost associated with providing the shuttle service on each route. For example, the cost may be set to a fixed cost amount and/or a variable amount (eg, based on distance, number of stops, day of week, time of day, discount amount, promotional amount, etc.). The cost may include costs that may be incurred by each shuttle service provider to service each route. These costs include, inter alia, costs associated with fuel, vehicle depreciation, opportunity costs, tolls and/or other additional costs for operating and/or maintaining the vehicle, idle and/or waiting time, costs of moving to the original location of the route, among others. , consignment fees and/or fees paid to others (eg, owners, employers, upper level service providers, platform providers, etc.), transportation considerations, overtime, holidays, etc.

In terms of fees and/or fees, the shuttle service may (or may not) require payment and/or to the passenger or user a fixed amount or (e.g., distance, number of stops, day of week, day of week). may require payment of a flat and/or variable amount (based on mid-time, discount amount, promotional amount, etc.). Fees and/or fees are for each route the number of potential users served on each shuttle, the availability and/or location of each shuttle, the capacity of each shuttle, and each service provider (as described above and in this disclosure). may be determined based on one or more factors or considerations, such as the cost of the service, fees for other types of services, current market rates, fees of competitors, and the like.

As a more specific example, the shuttle service will be provided today to Marina Bay Financial Center and an in-home location set at 6 Shenton Way with two pickup locations and/or one drop-off location along the route with an in-situ start time of 2pm today. a plurality of passengers served by a shuttle (eg bus or minibus) capable of serving seven users or passengers traveling along an entire route in Singapore that is predetermined or dynamically determined between established arrival locations; or It may be a user shuttle service.

As used in this disclosure, exemplary embodiments of non-shuttle services and/or non-shuttle related services (“non-shuttle services”) may be considered non-shuttle services or shuttle services. may include non-transportation-related services. Non-shuttle services can be booked exclusively by one user at a time, or serve one user at a time (for example, serve one paying user for each route, but , these services may include accompanying passengers) and may be provided by vehicles (hereinafter "non-shuttle service providers"). Non-shuttle service providers include automobiles, sport utility vehicles (SUVs), minivans, vans, non-land vehicles (eg, boats, vehicles that can move underwater or on water, vehicles that can move in the air, airplanes, etc.) , autonomous and semi-autonomous versions of one or more of the example vehicles described above, and/or other vehicles. As a more specific example, each non-shuttle service may include a standard or traditional taxi service, a private car service (eg, a GrabCar service provided by Grab), a service provided by a limousine service, and the like.

Exemplary embodiments of a system (eg, system 100 ) may or may not include one or more of the elements described above and elements in this disclosure, may include additional elements, and include equivalent elements. may be formed and/or used in different sequences, actions, combinations and/or configurations, and/or one or more elements (and/or elements of elements) may be combined into a single element or two or more elements can be divided into Communication using technologies other than the Internet is also contemplated in exemplary embodiments without departing from the teachings of this disclosure. These systems 100 and their elements and functions will be further described below with reference to the accompanying drawings.

A user computing device (eg, user computing device 110 ).

1 , system 100 may include one or more computing devices 110 for use by a user (eg, a user sending a shuttle service request and/or a non-shuttle service request). can User computing device 110 is any device, computing device configurable or configured to perform any of the processing of information, wired and/or wireless communication, and/or any of the other actions and/or processes described above and in this disclosure. , a mobile computing device, a processor, a controller, and the like. For example, the user computing device 110 may be configured to perform wireless communication, such as via a 3G network, a 4G network, a 4G LTE network, or the like, via a SIM card installed in the user computing device 110 , or the like. Alternatively or additionally, user computing device 110 may be configured via WLAN, such as Wi-Fi networks and Li-Fi networks, and/or via other forms such as Bluetooth, NFC, and other forms of wireless signals. and may be configured to perform wireless communication. One or more of the foregoing communications may be of a 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 . It may be between example embodiments. The user computing device 110 may be configured to communicate wirelessly or wiredly with the processor 150 (eg, via an application or a mobile application installed on the user computing device, via a web browser, etc.) sending service requests and/or non-shuttle service requests, viewing available shuttle service routes, receiving notifications of new and/or existing shuttle service routes, booking shuttle service and/or non-shuttle service, and the like.

In an exemplary embodiment, the user computing device 110 described above and in this disclosure is a mobile computing device, smart phone, mobile phone, PDA phablet, tablet, portable computer, laptop, notebook, ultrabook, reader, electrical device. , media players, specialized devices (eg, dedicated or specialized devices that communicate with and/or operate within system 100 or portions thereof), a plurality of computing devices that interact, in part or in whole, together, and other It may relate to and/or include specialized computing devices and industry-specific computing devices. The user computing device 110 described herein may also relate to and/or include a wearable computing device including a watch (such as an Apple Watch), eyeglasses, and the like. User computing device 110 may also relate to and/or include a virtual machine, computer, node, instance, host, or machine in a networked computing environment. Such a networked environment and/or cloud may be a collection of machines connected by communication channels that facilitate communication between machines and allow the machines to share resources. These resources include 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 It may include any type of resource for running an instance, including non-hardware resources or a combination thereof.

A shuttle computing device (eg, shuttle computing device 120 ).

As shown at least in FIG. 1 , system 100 may include one or more computing devices 120 for use by a shuttle (ie, providing shuttle service). Shuttle computing device 120 may be any device, computing device, configurable or configured to perform processing of information, wired and/or wireless communications, and/or any other actions and/or processes described above and/or in this disclosure; It may be a mobile computing device, a processor, a control unit, or the like. For example, the shuttle computing device 120 may be configured to perform wireless communication, such as via a 3G network, a 4G network, a 4G LTE network, etc., via a SIM card installed in the service provider computing device 120 , etc. , may also be configured or may be configured to perform vehicle-to-vehicle communication. Alternatively or alternatively, the shuttle computing device 120 performs wireless communication via WLAN, such as Wi-Fi networks and Li-Fi networks, and/or via other forms such as Bluetooth, NFC, and other forms of wireless signals. can be configured to One or more of the aforementioned communications may be of a 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 . It may be between example embodiments. Shuttle computing device 120 may be configured to communicate wirelessly or wiredly with processor 150 (eg, via an application or mobile application installed on the shuttle computing device, via a web browser, etc.) This may include receiving shuttle services and shuttle service routes available or needing to be serviced, viewing available shuttle service routes, receiving notifications of new and/or existing shuttle service routes, accepting shuttle services or service of shuttle service routes, etc. there is.

In an exemplary embodiment, the shuttle computing device 120 described above and in this disclosure is a mobile computing device, smart phone, mobile phone, PDA phablet, tablet, portable computer, laptop, notebook, ultrabook, reader, electrical device. , media players, specialized devices (eg, dedicated or specialized devices that communicate with and/or operate within system 100 or portions thereof), a plurality of computing devices that interact, in part or in whole, together, and other It may relate to and/or include specialized computing devices and industry-specific computing devices. Shuttle computing device 120 may also be part of or integrated into a shuttle, including such shuttles that are autonomous vehicles, semi-autonomous vehicles, and non-autonomous vehicles. The shuttle computing device 120 described herein may also relate to and/or include a wearable computing device including a watch (such as an Apple Watch), eyeglasses, and the like. Shuttle computing device 120 may also relate to and/or include a virtual machine, computer, node, instance, host, or machine in a networked computing environment. Such a networked environment and/or cloud may be a collection of machines connected by communication channels that facilitate communication between machines and allow the machines to share resources. These resources include 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 It may include any type of resource for running an instance, including non-hardware resources or a combination thereof. Shuttle computing device 120 and user computing device 110 in the present disclosure may be any computing device operable to perform information processing and wireless communication, and shuttle computing device 120 and user computing device 110 are similar or may be the same type of computing device.

A processor (eg, processor 150).

As shown at least in FIGS. 1 and 2 , system 100 may include one or more processors (eg, processor 150 ). Exemplary embodiments of processor 150 include one or more non-shuttle service request identifiers (eg, non-shuttle service request identifiers 151), one or more non-shuttle service request selectors (eg, Non-shuttle service request selector 152), one or more candidate service route generators (eg, candidate service route generator 153), one or more candidate shuttle service route selectors (eg, candidate shuttle services) route selector 156), one or more potential user selectors (eg, potential user selectors 154), one or more candidate service provider selectors (eg, candidate service provider selector 155); One or more shuttle service route managers (eg, shuttle service route managers 157), one or more shuttle-side notification and dispatch controls (eg, shuttle-side notification and dispatch controls 158), and/or one or more user-side notifications and one or more functions of a reservation control unit (eg, user-side notification and reservation control unit 159). The processor 150 also includes a non-shuttle service request identification unit 151 , a non-shuttle service request selection unit 152 , a candidate service route generation unit 153 , a potential user selection unit 154 , and a candidate service provider selection unit 155 , one or more operations, functions of the candidate shuttle service route selection unit 156 , the shuttle service route management unit 157 , the shuttle-side notification and dispatch control unit 158 , and/or the user-side notification and reservation control unit 159 . )/configurable or configurable to perform a function and/or process.

Processor 150 (and/or elements described above and described in this disclosure) is configurable to perform processing of information, voice and/or data communications and/or other actions described above and described in this disclosure, inter alia, or It may be any processor, server, device, computing device, server, controller, microprocessor, microcontroller, microchip, semiconductor device, virtual machine, etc. configured. Alternatively or additionally, processor 150 (and/or elements thereof as described in this disclosure) may be configured as a virtual machine, cloud-based computing, processor, computer, node, virtual machine, including those in a networked computing environment, may include and/or be part of an instance, host or machine. As used in this disclosure, such a network and/or cloud may be a collection of devices connected by a communication channel that facilitates communication between devices and enables devices to share resources. These resources include 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 It may include any type of resource for running an instance, including non-hardware resources or a combination thereof. A network or cloud may include, but is not limited to, a computing grid system, a peer-to-peer system, a mesh-like system, a distributed computing environment, a cloud computing environment, and the like. Such networks or clouds may include hardware and/or software infrastructure configured to form a virtual organization composed of multiple resources that may be located in geographically dispersed locations. A network may also refer to an interprocess communication medium on the same device. As also mentioned herein, a network element, node or server may be a device arranged to execute a program that acts as a socket listener and may include an instance of software.

Exemplary embodiments of the processor 150 may or may not include one or more of the elements and/or functions described above and described in this disclosure, and may include additional elements and/or functions, in different sequences; may be formed and/or used in an action, combination and/or composition, and/or one or more elements and/or functions (and/or elements of elements and/or functions of elements) may be a single element, a single function and/or may be combined into a process, may be divided into two or more elements, and/or may be divided into two or more functions and/or processes. The processor 150, and its elements and functions, will be further described below with reference to the accompanying drawings.

Non-shuttle service request identification unit (eg, non-shuttle service request identification unit 151).

Processor 150 may include (and/or configurable or configurable to perform one or more functions thereof) one or more non-shuttle service request identifiers (eg, non-shuttle service request identifier 151 ). there is. The non-shuttle service request identification unit 151 is configured to identify one or more past non-shuttle service requests in a database (eg, a database 140a of past transportation-related requests, a database 140b of past non-shuttle service requests). ), the database 140c of past shuttle service requests, and/or the user's database 140d). Alternatively or additionally, the non-shuttle service request identification unit 151 may identify past shuttle service requests and/or non-shuttle service requests (eg, the processor 150, an element of the processor 150, one configurable or configurable to receive one or more past non-shuttle service requests (from one or more databases 140a-d, etc.) and identify one or more past non-shuttle service requests. Such retrieval, reception, and/or identification may be performed continuously (eg, whenever a non-shuttle service request is received by the system 100) and continuously (eg, when a predetermined number of non-shuttle service requests are received by the system 100) intermittently (eg, once per hour, once per day, once per week, once per month, etc.), and/or periodically (e.g., once per month, etc.); For example, whenever a predetermined number of price-sensitive users are identified, whenever a predetermined number of unassigned, unmatched, and/or canceled service requests for non-shuttle service reach a predetermined number , whenever the demand for shuttle service reaches a predetermined number, whenever supply for shuttle service reaches a predetermined number, etc.) may be scheduled based on other considerations. Identified past non-shuttle service requests include service requests successfully matched with a service provider, service requests booked and completed successfully, service requests not successfully matched with a service provider, unassigned service requests, abandoned service requests, and user requests. It should be understood that this may include service requests canceled by and/or service requests canceled by service providers.

Each identified past non-shuttle service request has a start time (eg, the time the request was initiated on the user computing device 110 , the time the request was sent by the user computing device 110 , the time the request was sent to the processor 150 ) The time received by the processor 150, the request (e.g., a request matched with a service provider, a reserved request, a request not matched with a service provider, an unassigned request, a canceled request, a abandoned request, etc.) time processed by , the non-shuttle service start time, etc.). Each identified past non-shuttle service request may also include an original location (eg, initial location, starting location, desired location, pickup location, etc.). Each identified past non-shuttle service request may also include an arrival location (eg, final location, end location, drop off location, etc.). Each identified past non-shuttle service request may also include one or more routes, which may be defined by at least an origin location and an arrival location. For example, each identified past non-shuttle service request may include a best or most optimal route based on the above-described start time, and may also include other optional, alternative or less optimal routes. .

In an exemplary embodiment, the non-shuttle service request identifier 151 may include a geographic area, time or period (eg, year, month, week, day, hour, minute, second, etc.), requested service type (eg, For example, taxi, private car, public transport, limousine, rideshare, delivery, etc.), location (e.g. initial location, origin location, starting location, desired location, pickup location, destination location, etc.), route, user- one or more considerations such as certain criteria (which may be performed by the potential user selector 154 ), availability and/or location of the shuttle (which may be performed by the candidate service provider selector 155 ), and/or Configurable or configurable to retrieve, receive, and/or identify past non-shuttle service requests based on criteria. With respect to the geographic area, the non-shuttle service request identification unit 151 is a country, a region, a province, a state, a city, a county, a district, a specific area (eg, within a specific city block, a specific on the road, in a geometric shape drawn on a map, etc.), and the like). Regarding the period, the non-shuttle service request identification unit 151 identifies past non-shuttle service requests based on year, month, week, day, specific time(s) and/or minute, peak time, rush hour, etc. can be configured to With respect to the user-specific criteria, the non-shuttle service request identification unit 151 determines whether the user of the request is a price-sensitive user, a history of unassigned requests, a history of unmatched requests, a history of canceled requests, may be configured to identify past non-shuttle service requests based on a history of abandoned requests, whether the requesting user is a frequent user of low cost services such as shuttle, rideshare, and the like. With respect to routes, non-shuttle service request identifiers 151 are identified with similar, identical and/or overlapping routes (and such routes may include best or most optimal routes, secondary routes, etc.) may be configured to identify past non-shuttle service requests. With respect to the availability and/or location of the shuttle, the non-shuttle service request identifier 151 may determine the location of the shuttle at which the location associated with the request (eg, the origin location and/or the arrival location) is or will become available. may be configured to identify past non-shuttle service requests based on whether or not there will be in the vicinity of .

As a more specific example, the non-shuttle service request identification unit 151 may include one or more original locations in one or more predetermined or dynamically generated areas of a city's central business district (CBD), one or more locations in the city's CBD. Price-sensitive users (and/or unassigned, unmatched, cancelled) with arrival locations in predetermined or dynamically generated areas and start times during morning rush hours (eg, between 8-815 AM) and/or identify non-shuttle requests from users who have a history of made and/or abandoned requests. In this example, the non-shuttle service request identifier 151 may also determine the original location of another (eg, adjacent) predetermined or dynamically generated area of the city's CBD, another (eg adjacent) location of the city's CBD. For example, price-sensitive users (and/or unassigned, mismatched, canceled and/or abandoned) having the same and/or different start times, and/or arrival locations of adjacent) predetermined or dynamically generated areas. may be configured to identify past non-shuttle service requests from users with a history of requests made.

One or more including geographic area, start time, time or duration, origin location, arrival location, user-specific criteria, availability and/or location of the shuttle used by the non-shuttle service request identifier 151 in this disclosure. It is recognized that a reference and/or parameter may be any reference and/or parameter thereof (eg, any amount, period, type, etc.) without departing from the teachings of this disclosure.

Non-shuttle service request selection unit (eg, non-shuttle service request selection unit 152).

Processor 150 may include (and/or configurable or configured to perform one or more functions) one or more non-shuttle service request selectors (eg, non-shuttle service request selector 152). there is. The non-shuttle service request selection unit 152 is configurable or may be configured to select one or more past non-shuttle service requests. Selection may be performed from past non-shuttle service requests identified by the non-shuttle service request identification unit 151 . Alternatively or additionally, the non-shuttle service request selector 152 may select a previously selected (or previously unselected) past shuttle and/or non-shuttle service request (eg, the processor 150 ). , elements of processor 150, one or more databases 140a-d, etc.) or may be configurable.

In an exemplary embodiment, selection and/or reception by the non-shuttle service request selector 152 is continuous (eg, whenever a non-shuttle service request is identified), continuously (eg, a predetermined whenever a number of non-shuttle service requests have been identified) intermittently, periodically (eg, once per hour, once per day, once per week, once per month, etc.); and/ or (e.g., whenever a predetermined number of price-sensitive users are selected, a predetermined number of unassigned, unmatched and/or canceled service requests for non-shuttle service reach a predetermined number each time the demand for shuttle service reaches a predetermined number, whenever supply for shuttle service reaches a predetermined number, etc.) may be scheduled based on other considerations.

Selected past non-shuttle service requests include service requests successfully matched with service providers, service requests that have been successfully booked and completed, service requests not successfully matched with service providers, unassigned service requests, abandoned service requests, and service requests that have been abandoned by the user. It should be understood that this may include service requests canceled by the service provider and/or service requests canceled by the service provider.

Each selected past non-shuttle service request has a start time (eg, the time the request was initiated on the user computing device 110 , the time the request was sent by the user computing device 110 , the time the request was sent to the processor 150 ) time received by the processor 150, the request (eg, a request matched with a service provider, a reserved request, a request not matched with a service provider, an unassigned request, a canceled request, an abandoned request, etc.) processing time, non-shuttle service start time, etc.). Each selected past non-shuttle service request may also include an original location (eg, initial location, starting location, desired location, pickup location, etc.). Each selected past non-shuttle service request may also include an arrival location (eg, final location, end location, drop off location, etc.). Each selected past non-shuttle service request may also include one or more routes, which may be defined by at least an origin location and an arrival location. For example, each selected past non-shuttle service request may include a best or most optimal route based on the start time described above, as well as other optional, alternative or less optimal routes.

In an exemplary embodiment, the non-shuttle service request selector 152 may include a geographic area, time or period (eg, year, month, week, day, hour, minute, second, etc.), requested service type (eg, year, month, week, day, hour, minute, second, etc.) For example, taxi, private car, public transport, limousine, rideshare, delivery, etc.), location (e.g., initial location, origin location, starting location, desired location, pickup location, arrival location, etc.), user-specific criteria (which may be performed by the potential user selector 154), the availability and/or location of the shuttle (which may be performed by the candidate service provider selector 155), etc. Configurable or configurable to select and/or receive past non-shuttle service requests based on The non-shuttle service request selector 152 may also include the system 100 with one or more other elements, such as the potential user selector 154, the candidate service provider selector 155, the databases 140, 140a-d, etc. selection can be made through the collaboration of With respect to the geographic area, the non-shuttle service request selection unit 152 may be a country, a region, a province, a state, a city, a county, a district, a specific area (eg, within a specific city block, a specific on the road, within a geometric shape drawn on a map, etc.) may be configured to select past non-shuttle service requests. Regarding the period, the non-shuttle service request selection unit 152 selects a past non-shuttle service request based on year, month, week, day, specific time(s) and/or minute, peak time, rush hour, etc. can be configured to With respect to the user-specific criteria, the non-shuttle service request selection unit 152 determines whether the user of the request is a price-sensitive user, a history of unassigned requests, a history of unmatched requests, a history of canceled requests, with potential user selector 154, which may assist in identifying and/or selecting past non-shuttle service requests based on a history of abandoned requests, whether the requesting user is a frequent user of low cost services such as shuttle, rideshare, etc. Collaboration can be configured to pick up past non-shuttle service requests. Regarding routes, the non-shuttle service request selector 152 selects past non-shuttle service requests based on whether one or more routes associated with the request have similar, identical, and/or overlapping routes or portions of routes. can be configured to select. Such one or more routes may include best or most optimal routes, secondary routes, and the like among them. With respect to the availability and/or location of the shuttle, the non-shuttle service request selector 152 determines the location of the shuttle at which the location associated with the request (eg, the origin location and/or the arrival location) is or will become available. may be configured to select past non-shuttle service requests based on whether or not there will be in the vicinity of . One or more including geographic area, start time, time or duration, origin location, arrival location, user-specific criteria, availability and/or location of the shuttle used by the non-shuttle service request selector 152 in this disclosure. It is recognized that a reference and/or parameter may be any reference and/or parameter thereof (eg, any amount, period, type, etc.) without departing from the teachings of this disclosure.

In an exemplary embodiment, the non-shuttle service request selector 152 may be configured to: one or more past non-shuttle services having at least a portion of one or more of a route common to one or more other selected and/or identified past non-shuttle service requests. It may be configured to select a request.

As described above and in this disclosure, alternatively or in addition to the route-based selection process by the non-shuttle service request selector 152 , the potential user selector 154 may select one or more Potential users may be identified and/or selected. One or more potential users may be users identified as being price-sensitive users. Alternatively or additionally, one or more potential users may also be users identified as having a history of unassigned, mismatched, canceled and/or abandoned requests. The non-shuttle service request selector 152 then identifies one or more past non-shuttle service requests identified and/or selected by the potential user selector 154 as being requests previously sent by the one or more selected potential users. can be configured to select. Alternatively or additionally, the non-shuttle service request selector 152 identifies and/or selects one or more past non-shuttle service requests that are unassigned, mismatched, canceled and/or abandoned requests. It can be configured to select

In an exemplary embodiment, the non-shuttle service request selection unit 152 and the non-shuttle service request identification unit 151 may be combined and/or integrated into a single or integrated element and/or process, in which case such integration A specified element or process may be configurable or configured to perform the searching, receiving, identifying and/or selecting operations as described above and described in this disclosure.

A candidate service route generator (eg, the candidate service route generator 153).

The processor 150 may include (and/or be configurable or configured to perform one or more functions thereof) one or more candidate service route generators (eg, the candidate service route generator 153 ). The candidate service route generator 153 is configurable or may be configured to derive, generate, and/or dynamically derive and/or generate (hereinafter “derived”) one or more candidate shuttle service routes. The derivation of the one or more candidate shuttle service routes may be based on one or more past non-shuttle service requests selected by the non-shuttle service request selection unit 152 . Alternatively or additionally, the non-shuttle service request selection unit 152 selects, modifies and / or configurable or configurable to adjust.

In an exemplary embodiment, the derivation and/or selection by the candidate service route generator 153 (eg, whenever a non-shuttle service request is selected) in a persistent manner (eg, a predetermined number of in an intermittent manner (e.g., once per hour, once per day, once per week, once per month, etc.) in a periodic manner (e.g., whenever a non-shuttle service request of For example, whenever a predetermined number of price-sensitive users are selected, whenever a predetermined number of unassigned, unmatched, and/or canceled service requests for non-shuttle service reach a predetermined number , whenever the demand for the shuttle service reaches a predetermined number, whenever the supply for the shuttle service reaches a predetermined number, etc.) .

Candidate shuttle service routes include potential users identified as price-sensitive users, potential users who have previously booked shuttle services, potential users who have not previously booked shuttle services, and potential users who have a history of unsuccessful matches with service providers. , a potential user with a history of unassigned service requests, a potential user with a history of abandoned requests, a potential user with a history of canceling service requests, and/or potential users with a history of having the service provider cancel a service request. It should be understood that it can be derived for the user.

In deriving the candidate shuttle service route, the candidate service route generator 153 may derive original locations (eg, initial location, start location, desired location, pickup location, etc.) for each candidate shuttle service route. there is. The original location may be a location from which the candidate shuttle service route will start. 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 at which the candidate shuttle service route starts from, arrives at, and/or leaves the original location of the candidate shuttle service route. The candidate service route generator 153 may also derive an arrival location (eg, a final location, an end location, a drop off location, etc.) for each candidate shuttle service route. The arrival location may be a location where the candidate shuttle service route will end. The candidate service route generator 153 may also derive one or more pickup 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.

In an exemplary embodiment, the candidate service route generating unit 153 may include a geographic area, time or period (eg, a start time of a selected past non-shuttle service request, an end time of a selected past non-shuttle service request, etc.); location (eg, the origin of selected past non-shuttle service requests, arrival location of selected past non-shuttle service requests, etc.), route (eg, route of selected past non-shuttle service requests), user- Based on certain criteria (which may be performed by the potential user selector 154 ), criteria and/or conditions such as availability and/or location of the shuttle (which may be performed by the candidate service provider selector 155 ), etc. Configurable or configurable to derive the candidate shuttle service route, the original location of the candidate shuttle service route, the start time of the candidate shuttle service route, and the arrival location of the candidate shuttle service route. Derivation may also be performed through collaboration with one or more other elements of system 100, such as selector 154, candidate service provider selector 155, and databases 140, 140a-d. In this regard, the candidate service route creation unit 153 may be configured for each country, region, province, state, whose granularity may be based on supply, demand, date, day, time, holiday or special event, etc. It may be configured to derive candidate shuttle service routes for a city, county, district, specific area (eg, within a specific city block, on a specific road, within a geometry drawn on a map, etc.), etc. With respect to duration, The candidate service route generator 153 may be configured to derive a candidate shuttle service route for each year, month, week, day, specific hour(s) and/or minute, peak hour, rush hour, etc. User- With respect to the specific criteria, the candidate service route creation unit 153 may include a specific user or user type (eg, a price-sensitive user, a user who is a frequent user of a low-cost service, and/or users with a history of unassigned requests, unmatched requests, canceled requests, abandoned requests, etc.) through collaboration with the potential user selector 154 to consider and/or target It may be configured to derive a service route. Regarding the routes, the candidate service route generating unit 153 is configured to configure the candidate shuttle service routes based on the number or frequency of selected past non-shuttle service routes having similar, identical, and/or overlapping routes or portions of routes. It can be configured to derive With respect to the availability and/or location of the shuttle, the candidate service route creation unit 153 determines whether a potential service provider of the shuttle service is available or available, and whether or not has a location near the original location of the candidate shuttle service route. and derive a candidate shuttle service route based on whether the One including geographic area, start time, time or duration, origin location, arrival location, route, user-specified criteria, availability and/or location of a shuttle, etc. used by the candidate service route generator 153 in the present disclosure. It is recognized that the above criteria and/or parameters may be any criteria and/or parameters thereof (eg, any amount, period, type, etc.) without departing from the teachings of this disclosure.

Potential user selector (eg, potential user selector 154).

As described above and in this disclosure, processor 150 includes (and/or is configurable or configured to perform one or more functions thereof) one or more potential user selectors (eg, potential user selectors 154 ). )can do. Potential user selector 154 is configurable or may be configured to perform analysis, identification and/or selection of potential users of the shuttle service. The analysis, identification and/or selection of potential users of the Shuttle Service may depend, inter alia, on user information and/or settings, user priority levels, user loyalty levels, user payment histories (payment forms and amounts), user reservation histories (such as , low cost service reservation history, shuttle service reservation history, price-sensitive history, unassigned service request history, unmatched service request history, canceled service request history, abandoned service request history, etc.), databases 140, 140a- may be based on one or more past non-shuttle service requests stored in d), one or more identified and/or selected past non-shuttle service requests, and the like. Alternatively or additionally, the potential user selector 154 is configurable or configurable to select and/or drop potential users previously selected (or not previously selected) by the potential user selector 154 . can be

In an exemplary embodiment, analysis, identification, and/or selection by potential user selector 154 may be performed on a continuous, intermittent, or periodic basis (eg, once per hour, once per day) for some or all users. once a week, once a week, once a month, etc.), and/or one or more other considerations (eg, new users, new service areas, changes in user activity levels, changes in services used by users, etc.); It may be performed dynamically or non-dynamically in a scheduled manner based on the

A candidate service provider selection unit (eg, a candidate service provider selection unit 155).

As described above and in this disclosure, the processor 150 includes (and/or is configurable to perform one or more functions of) one or more candidate service provider selection units (eg, candidate service provider selection units 155 ). or configure). The candidate service provider selector 155 may be configurable or configured to perform analysis, identification, and/or selection of candidate shuttles (or candidate service providers) for providing shuttle services. The analysis, identification, and/or selection of candidate shuttles for providing shuttle service may be determined, inter alia, on availability of candidate shuttles, existing schedules for service shuttle routes, current services of shuttle routes, current locations of candidate shuttles, projections of candidate shuttles, among others. It can be based on /planned/predicted/estimated location, etc. Alternatively or additionally, the candidate service provider selection unit 155 is configurable to select and/or drop candidate shuttles previously selected (or not previously selected) by the candidate service provider selection unit 155 . or may be configured.

In an exemplary embodiment, analysis, identification, and/or selection by candidate service provider selector 155 may be performed for some or all shuttle service providers in a continuous, intermittent, periodic (eg, hourly basis) once, once per day, once per week, once per month, etc.) and/or based on one or more other considerations (eg, to the shuttle service provider based on activity level, new service area, etc.) It may be performed dynamically or non-dynamically in a scheduled manner.

A candidate shuttle service route selector (eg, a candidate shuttle service route selector 156).

The processor 150 may include (and/or be configurable or configured to perform one or more functions thereof) one or more candidate shuttle service route selectors (eg, candidate shuttle service route selectors 156 ). The candidate shuttle service route selector 156 is configurable or configurable to select one or more of the derived candidate shuttle service routes (derived by the candidate shuttle service route generator 153 ) to provide the shuttle service. . Alternatively or additionally, the candidate shuttle service route selector 156 selects, modifies and/or selects, modify and/or select a candidate shuttle service route previously selected (or not previously selected) by the candidate shuttle service route selector 156 . or configurable or configurable to adjust.

In performing the selection of one or more derived candidate shuttle service routes for providing shuttle service, the candidate shuttle service route selector 156 and/or one or more other elements of the processor 150 are configured to select one or more candidate shuttle service routes. Configurable or configurable to first perform the planning, estimation and/or prediction of the number of potential users. The candidate shuttle service route selector 156 and/or one or more other elements of the processor 150 may also determine the availability and/or location of, and/or the location of, potential shuttle service providers capable of servicing one or more candidate shuttle service routes, among others. Configurable or configurable to perform planning, estimation, and/or forecasting of the number of required shuttle service providers that may be required to service each candidate shuttle service route based on the planned, estimated and/or predicted number of potential users can be

The candidate shuttle service route selector 156 and/or one or more other elements of the processor 150 may also analyze and/or analyze the costs to be incurred by each shuttle service provider to service each candidate shuttle service route therein. Configurable or configurable to perform derivation. These costs include, inter alia, fuel costs, vehicle depreciation costs, opportunity costs, tolls and/or other additional fees, idle and/or waiting times, costs of moving to the original location of a candidate shuttle service route, commissioning fees and/or other fees, among others. Fees paid to people (eg owners, employers, platform providers, etc.), transportation considerations, etc. may be taken into account.

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 a fee or fee to be charged to a user of the shuttle service. This fee may be a flat fee or variable fee based on distance, number of stops, date, day, time, public holiday, traffic, and the like. In determining these fees, various factors may be considered, including the number of potential users, availability and location of potential shuttle service providers, costs to the shuttle service provider, fees to other services, current market fees, competitor fees etc. may also be considered.

It should be understood that other cost-related, fee-related, income-related and/or benefit-related considerations may also be considered. Alternatively or additionally, the candidate shuttle service route selector 156 may be previously analyzed, derived, planned, predicted and/or estimated (each applicable) by the candidate shuttle service route selector 156 (or Configurable to select, correct, and/or adjust potential users, potential shuttle service providers, costs, fees, income and/or profit information not previously analyzed, derived, planned, predicted, and/or estimated and each applicable) or can be configured.

The candidate shuttle service route selector 156 may then select a shuttle service based on one or more of potential users, potential shuttle service providers, costs, fees, income, and/or benefit considerations as described above and in this disclosure. Configurable or configurable to select one or more of the derived candidate shuttle service routes to provide.

Selection of the one or more derived candidate shuttle service routes by the candidate shuttle service route selector 156 (eg, each time a candidate shuttle service route is derived) in a continuous manner (eg, a predetermined number in an intermittent manner (e.g., once per hour, once per day, once per week, once per month, etc.) in a periodic manner (eg, once per hour, once per month, etc.); and/or (eg, whenever a predetermined number of price-sensitive users are selected, when a predetermined number of unassigned, unmatched, and/or canceled service requests for non-shuttle service reach a predetermined number) every time, whenever the demand for shuttle service reaches a predetermined number, whenever supply for shuttle service reaches a predetermined number, etc.) may be performed dynamically in a scheduled manner based on other considerations.

Candidate shuttle service routes include potential users identified as price-sensitive users, potential users who have previously booked shuttle services, potential users who have not previously booked shuttle services, and potential users who have a history of unsuccessful matches with service providers. , a potential user with a history of unassigned service requests, a potential user with a history of abandoned requests, a potential user with a history of service request cancellations, and/or a potential user with a history of having service requests canceled by the service provider It should be understood that it can be selected for

Each selected candidate shuttle service route may have an original location (eg, an initial location, a starting location, a desired location, a pickup location, etc.). The original location may be a location where the selected candidate shuttle service route will start. Each selected candidate shuttle service route may also have a start time. The start time may be a time at which the selected candidate shuttle service route is scheduled to depart from, arrive at, and/or depart from the original location of the selected candidate shuttle service route. Each selected candidate shuttle service route may also have an arrival location (eg, final location, end location, drop off location, etc.). The arrival location may be a 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 a candidate shuttle service route, the candidate shuttle service route selector 156 may select a candidate shuttle service route with fewer drop-off and/or pickup locations.

In an exemplary embodiment, the candidate shuttle service route selector 156 is configured to match a geographic area, time or duration (eg, a closest match and/or start time and end time match to that of a selected past non-shuttle service request). most number of matches, etc.), location (e.g., nearest match and/or most number of matches of origin and arrival locations to those of selected past non-shuttle service requests, etc.), route (e.g. , closest match and/or most number of matches in the route to that of the selected non-shuttle service request), user-specific criteria (eg, to closest match and/or that of a price-sensitive user, and/or location, start time, and/or most number of matches of the route for that of an unassigned, unmatched, canceled, and/or abandoned service request), availability and/or location of the shuttle (e.g., most candidate shuttle service based on one or more other criteria, such as nearest matches and/or the majority of matches in origin, arrival location and/or start time to that of a shuttle service provider that is available and/or will become available); Configurable or configurable to select a route. Candidate shuttle service route selector 156 may also collaborate with one or more other elements of system 100, such as potential user selector 154, candidate service provider selector 155, databases 140, 140a-d, and the like. selection can be made through With respect to geographic area, candidate shuttle service route selector 156 may be configured for each country, region, province, state, the granularity of which may be based on supply, demand, date, day, time, public holiday or special event, etc. It may be configured to select a candidate shuttle service route for a state, city, county, district, specific area (eg, within a specific city block, on a specific road, within a geographic form drawn on a map), and the like. With respect to duration, the candidate shuttle service route selector 156 is configured to select a candidate shuttle service route for each year, month, week, day, specific hour(s) and/or minutes, peak hours, rush hours, etc. can be With respect to user-specific criteria, the candidate shuttle service route selector 156 may determine the specific user or type of user (eg, price-sensitive users, users who are frequent users of low-cost services, and/or unassigned requests; (users with a history of unmatched requests, canceled requests, abandoned requests, etc.) and/or select a candidate shuttle service route through collaboration with a potential user selector 154 that may target and/or target them. can be configured. With respect to routes, the candidate shuttle service route selector 156 determines the candidate shuttle service routes based on the number or frequency of selected past non-shuttle service routes having similar, identical and/or overlapping routes or portions of routes. can be configured to select With respect to the availability and/or location of the shuttle, the candidate shuttle service route selector 156 may determine whether an available or to be made available shuttle or service provider of the shuttle service has a location near the original location of the candidate shuttle service route; may be configured to select a candidate shuttle service route based on whether to have or not. including geographic area, start time, time or duration, origin location, arrival location, route, user-specific criteria, availability and/or location of shuttle, etc. used by candidate shuttle service route selector 156 in this disclosure; It is recognized that one or more criteria and/or parameters may be any criteria and/or parameters thereof (eg, any amount, period, type, etc.) without departing from the teachings of this disclosure.

Shuttle service route management unit (eg, shuttle service route management unit 157).

Processor 150 may include (and/or be configurable or configured to perform one or more functions thereof) one or more shuttle service route managers (eg, shuttle service route managers 157 ). The shuttle service route management unit 157 may be configurable or configured to manage the shuttle service route selected by the candidate shuttle service route selection unit 156 . In doing so, the shuttle service route manager 157 may be configured to allow the user to report and/or make reservations for one or more selected shuttle service routes. The shuttle service route management unit 157 may also be configured to enable the shuttle service provider to verify services of one or more selected shuttle service routes. The shuttle service route management unit 157 may also cooperate with the shuttle-side notification and dispatch control unit 158 and/or the user side notification and reservation control unit 159 to manage the selected shuttle service route.

Shuttle-side notification and dispatch control (eg, shuttle-side notification and dispatch control 158).

Processor 150 may include (and/or be configurable or configured to perform one or more functions thereof) one or more shuttle-side notification and dispatch controls (eg, shuttle-side notification and dispatch controls 158 ). Shuttle-side notification and dispatch control 158 is configurable or configurable to provide notifications to a shuttle service provider of a selected shuttle service route.

The notification provided by the shuttle-side notification and dispatch control 158 is a predetermined distance of the original location and/or arrival location of the selected shuttle service route, within a geographic area covering the original location and/or arrival location of the selected shuttle service route. All shuttle service providers registered and/or located (or planned, predicted, or estimated to be located) within (and/or travel time), and/or to specific shuttle service providers based on one or more considerations; can be

For example, a notification may be provided to a shuttle service provider that is or will be available for service of the selected shuttle service route at the start time of the selected shuttle service route. As another example, a notification may be provided to a shuttle service provider that has vehicle capacity to service a planned, predicted, or estimated number of potential users. As another example, the notice may be provided to a shuttle service provider that previously provided shuttle service. Other exemplary considerations, including those described above and provided in this disclosure, may also be considered without departing from the teachings of this disclosure.

Shuttle-side notification and dispatch control 158 also controls (start time, origin location, arrival location, pickup location(s), drop off location(s), fees to be charged or collected for each user, predicted, planned or estimated users) To accept delegation from a shuttle service provider and to dispatch the shuttle service provider(s) to accept, confirm and/or agree to service the selected shuttle service route (including providing information about one or more of the number, etc.) can be

User-side notification and reservation control (eg, user-side notification and reservation control 159).

The processor 150 may include (and/or be configurable or configured to perform one or more functions thereof) one or more user-side notification and reservation controls (eg, user-side notification and reservation controls 159 ). The user-side notification and reservation control 159 is configurable or configurable to provide notifications to potential users of the selected shuttle service route.

User-side notifications and notifications provided by the reservation control 159 may include a predetermined distance ( and/or all users registered and/or located (or planned, predicted, or expected to be located) within the travel time, and/or specific users based on one or more considerations.

For example, the notice indicates that a transport-related service will be required at the start time of a shuttle service route selected from one of the original locations and/or pick-up locations along the route, to one of the arrival locations and/or drop-off locations along the route, etc. Planned, predicted and/or anticipated users may be provided. As another example, a notification may be provided to a user identified as being a potential user. As another example, a notification may be provided to a user who has previously booked a shuttle service. Other exemplary considerations, including those described above and provided in this disclosure, are also contemplated without departing from the teachings of this disclosure.

The user-side notification and reservation control 159 may also accept reservations from the user and/or the start time, origin location, arrival location, pickup location(s), drop off location(s), fees to be charged or collected for each user; for the selected shuttle service route, including one or more of the details of the shuttle service provider (e.g., make and model of vehicle, license plate, color, driver name, etc.), predicted, planned, or estimated total number of users; may be configured to provide ascertained details.

A method for managing a shuttle service based on a route (eg, method 300 ).

At least an exemplary embodiment of a method (eg, method 300 ) for managing a shuttle service shown in FIG. 3 and described above and further described in this disclosure includes, among others, the in situ location of past non-shuttle service requests; It may be based on arrival location, route, start time and/or end time. The method 300 may include searching a database of past transportation-related requests to identify a plurality of past non-shuttle service requests (eg, action 302 ). Each past non-shuttle service request may include a start time and route. A route may be defined by at least an original location and an arrival location.

The method 300 may also include selecting a plurality of past non-shuttle service requests (eg, action 304 ). One or more of the selected past non-shuttle service requests may include at least a portion of a route that is common (or overlapping) with at least a portion of one or more other selected past non-shuttle service requests. The selection may be based on such past non-shuttle service requests having a start time within a first threshold period (eg, a 5, 10, 15, 20 or 30 minute period, etc.). Selection may also include past fields having an original location located within a first critical area (eg, 5, 10, 20, 30, 50, 100 meter radius, equal distance, equal intersection, same building or complex, customized area, etc.) -Can be based on shuttle service request. The selection may also include those having an arrival location located within a second critical area (eg, 5, 10, 20, 30, 50, 100 meter radius, equal distance, equal intersection, same building or complex, customized area, etc.) It may be based on past non-shuttle service requests. In an exemplary embodiment, the selection may also include selecting past non-shuttle service requests that were not assigned, did not match, canceled and/or abandoned. One or more of the selected past non-shuttle service requests may also include requests for taxi services, private car services, and/or rideshare services. Also, each past non-shuttle service request may be a transportation-related request that is not a request for a 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 include selecting one or more potential users for the shuttle service, wherein at least one of the selected potential users is a user identified as being price sensitive. Selecting the one or more past non-shuttle service requests may include selecting one or more past non-shuttle service requests previously sent by the one or more selected potential users.

The method 300 may also include deriving a candidate shuttle service route for use in providing the shuttle service (eg, action 306 ). The candidate shuttle service route may be derived based on one or more of the selected past non-shuttle service requests. In an exemplary embodiment, the derivation of a candidate shuttle service route may be based on at least one of a start time, route, origin location and/or arrival location of one or more selected past 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 original location for the candidate shuttle service route and the arrival 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, original location, and/or arrival location of one or more selected past non-shuttle service requests.

The method may further include refining, adjusting and/or modifying the candidate service route to minimize the amount of pickup and/or drop-off along the candidate service route. Refinements, adjustments, and/or changes to candidate service routes may also be based on one or more considerations and/or criteria described above and described in this disclosure. Improvements, adjustments and/or changes to the candidate service route may include start and/or end times for the candidate shuttle service route, the original location for the candidate shuttle service route, the arrival location for the candidate shuttle service route, the pickup location(s); drop off location(s), costs, fees or charges, and the like.

In an exemplary embodiment, the database of past transportation-related requests may also include a plurality of past shuttle service requests, in which case derivation of a candidate shuttle service route may be further based on one or more past shuttle service requests. .

The method 300 may also include deriving a start time for the candidate shuttle service route, an original location for the candidate shuttle service route, and an arrival location for the candidate shuttle service route. The start time for the candidate shuttle service route, the original location for the candidate shuttle service route, and the arrival location for the candidate shuttle service route are based on the start time, original location, and/or arrival location of one or more selected past non-shuttle service requests. can be derived.

The method 300 may also include selecting one or more potential users for the shuttle service and communicating with one or more of the selected potential users. Such communication may include providing information regarding a 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 the service provider with a candidate shuttle service route. The service provider matching process may be based on minimizing travel distance and/or travel time by the matched service provider between servicing the previous candidate shuttle service route and servicing the candidate service route. Alternatively or additionally, the service provider matching process may be based on minimizing travel distance and/or travel time by the matched service provider between servicing the candidate service route and servicing the next candidate shuttle service route. can

A method for managing shuttle service based on available and/or nearby shuttles (eg, method 400 ).

As shown at least in FIG. 4 and as described above and further described herein, exemplary embodiments of a method (eg, method 400 ) for managing shuttle services include those available and/or nearby. It may be based on a shuttle or a shuttle service provider. The method 400 may include searching a database of past transportation-related requests to identify a plurality of past non-shuttle service requests (eg, action 402 ). Each past non-shuttle service request may include a start time and a route defined by at least an original location and an arrival location.

The method 400 may also include selecting one or more past non-shuttle service requests (eg, action 404). Each selected past non-shuttle service request may include at least a portion of a route common to one or more other selected past non-shuttle service requests. The selection of the one or more past non-shuttle service requests may be based on past non-shuttle service requests having a start time within the first threshold period. Alternatively or additionally, selection of one or more past non-shuttle service requests may be based on past non-shuttle service requests having an original location located within the first critical region. Alternatively or additionally, selection of one or more past non-shuttle service requests may be based on past non-shuttle service requests having an arrival location located within the second critical region.

In example embodiments, selection of past non-shuttle service requests may include selecting past non-shuttle service requests that were unassigned, mismatched, canceled and/or abandoned. Additionally, one or more of the selected past non-shuttle service requests may include requests for taxi services, private car services, and/or rideshare services. Each past non-shuttle service request may be a transportation-related request that is not a request for shuttle service.

The method 400 may also include performing an analysis to identify one or more users who may be price sensitive. The method 400 may include selecting one or more potential users for shuttle service. At least one of the selected potential users may be a user identified as being price sensitive. Selecting the one or more past non-shuttle service requests may include selecting one or more past non-shuttle service requests previously sent by the one or more selected potential users.

The method 400 may also include selecting one or more candidate service providers available to service one or more selected past non-shuttle service requests (eg, action 406 ). The selection of the candidate service provider may be based on minimizing travel distance and/or travel time by the candidate service provider between servicing the previous candidate shuttle service route and servicing the candidate service route. Alternatively or additionally, selection of a candidate service provider may be based on minimizing travel distance and/or travel time by the candidate service provider between servicing the candidate service route and servicing the next candidate shuttle service route. can

The method 400 may also include deriving one or more candidate shuttle service routes (eg, action 408 ). One or more candidate shuttle service routes may be derived based on one or more selected past non-shuttle service requests. The derivation of the candidate shuttle service route may be based on the start time, route, origin location, and/or arrival location of at least one or more selected past non-shuttle service requests.

The method 400 may also include deriving a start time for the candidate shuttle service route, an original location for the candidate shuttle service route, and an arrival location for the candidate shuttle service route. The start time for the candidate shuttle service route, the original location for the candidate shuttle service route, and the arrival location for the candidate shuttle service route are based on the start time, original location, and/or arrival location of one or more selected past non-shuttle service requests. can be derived.

The method 400 may also include deriving one or more drop off and/or one or more pickup locations between the original location for the candidate shuttle service route and the arrival 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, original location, and/or arrival location of one or more selected past non-shuttle service requests.

The method 400 may further include refining, adjusting, and/or modifying the candidate service route to minimize the amount of pickup and/or drop-off along the candidate service route. Refinements, adjustments, and/or changes to candidate service routes may also be based on one or more considerations and/or criteria described above and described in this disclosure. Improvements, adjustments and/or changes to the candidate service route may include start and/or end times for the candidate shuttle service route, the original location for the candidate shuttle service route, the arrival location for the candidate shuttle service route, the pickup location(s); drop off location(s), costs, fees or charges, and the like.

In an exemplary embodiment, the database of past transportation-related requests may also include a plurality of past shuttle service requests, in which case derivation of a candidate shuttle service route may be further based on one or more past shuttle service requests. .

Method 400 may also include selecting one or more candidate shuttle service routes for use in providing shuttle service (eg, action 410 ). The selected one or more candidate shuttle service routes may be selected based on the one or more selected candidate service providers.

The method 400 may further include selecting one or more potential users for the shuttle service and communicating with one or more of the selected potential users. The communication may include providing information regarding a candidate shuttle service route and/or an opportunity to receive shuttle service on the candidate shuttle service route.

A method (eg, method 500 ) for managing shuttle service based on potential users and/or previously unassigned, unmatched and/or canceled requests.

As shown at least in FIG. 5 and as described above and further described in this disclosure, an exemplary embodiment of a method (eg, method 500 ) for managing a shuttle service is provided, among others, by potential users and/or previously It may be based on unassigned, unmatched, canceled and/or abandoned requests. The method 500 may include searching a database of past transportation-related requests to identify a plurality of past non-shuttle service requests (eg, action 502 ). Each past non-shuttle service request may include a start time and a route defined by at least an original location and an arrival location.

The method 500 may also include selecting one or more potential users for the shuttle service (eg, action 504 ). One or more of the selected potential users may be identified as price-sensitive users.

The method 500 may also include selecting one or more past non-shuttle service requests (eg, action 506 ). One or more of the selected past non-shuttle service requests may be requests previously sent by one of the selected potential users. Alternatively or additionally, one or more of the selected past non-shuttle service requests may be unassigned, unmatched, canceled and/or abandoned requests. Each selected past non-shuttle service request may include at least a portion of a route common to one or more other selected past non-shuttle service requests. The selection of the one or more past non-shuttle service requests may be based on past non-shuttle service requests having a start time within the first threshold period. Alternatively or additionally, selection of one or more past non-shuttle service requests may be based on past non-shuttle service requests having an original location located within the first critical region. Alternatively or additionally, selection of one or more past non-shuttle service requests may be based on past non-shuttle service requests having an arrival location located within the second critical region. One or more of the selected past non-shuttle service requests may include requests for taxi services, private car services, and/or rideshare services. Also, each past non-shuttle service request may be a transportation-related request that is not a request for a shuttle service.

The method 500 may also include deriving a candidate shuttle service route for use in providing the shuttle service (eg, action 508 ). The candidate shuttle service route may be derived based on one or more of the selected past non-shuttle service requests. The derivation of the candidate shuttle service route may be based on the start time, route, origin location, and/or arrival location of at least one or more selected past non-shuttle service requests.

The method 500 may also include deriving a start time for the candidate shuttle service route, an original location for the candidate shuttle service route, and an arrival location for the candidate shuttle service route. The start time for the candidate shuttle service route, the original location for the candidate shuttle service route, and the arrival location for the candidate shuttle service route are based on the start time, original location, and/or arrival location of one or more selected past non-shuttle service requests. can be derived.

The method 500 may also include deriving one or more drop off and/or one or more pickup locations between the original location for the candidate shuttle service route and the arrival 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, original location, and/or arrival location of one or more selected past non-shuttle service requests.

In an exemplary embodiment, the database of past transportation-related requests may also include a plurality of past shuttle service requests, in which case derivation of a candidate shuttle service route may be further based on one or more past 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 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. Further, selecting one or more past non-shuttle service requests may include selecting one or more past non-shuttle service requests previously sent by one or more of the selected potential users.

The method 500 may further include communicating with one or more of the selected potential users. The communication may include providing information regarding a 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 the service provider with a candidate shuttle service route. The service provider matching process may be based on minimizing travel distance and/or travel time by the matched service provider between servicing the previous candidate shuttle service route and servicing the candidate service route. The service provider matching process may also be based on minimizing travel distance and/or travel time by the matched service provider between servicing a candidate service route and servicing a next candidate shuttle service route.

Exemplary embodiments 300 , 400 and/or 500 of a method for managing a shuttle service as described above and as described in this disclosure include or include one or more actions and/or functions described above and in this disclosure. may not, may include additional actions and/or functions, may be performed and/or used in different sequences, combinations and/or configurations, and/or may include one or more actions and/or functions in a single action and/or function. can be combined and/or divided into two or more actions and/or functions.

While various embodiments in accordance with the disclosed principles have been described above, it is to be understood that they have been presented by way of example only and not limitation. Accordingly, the breadth and scope of the exemplary embodiments described in this disclosure should not be limited by any of the exemplary embodiments described above, but should be defined only in accordance with the claims issued from this disclosure and their equivalents. Further, while the above-described advantages and features are provided in the described embodiments, it will not limit the application of the claims so issued to processes and structures that achieve any or all of the above-described advantages.

For example, as referred to herein, a processor, device, computing device, telephone, phone, server, gateway server, communication gateway server and/or control unit may be any processor, computing device and/or control unit. It may be a communication device and may include a virtual machine, computer, node, instance, host, or machine in a networked computing environment. As also referred to herein, a network or cloud may be or include a collection of machines connected by a communication channel that facilitates communication between machines and enables the machines to share resources. A network may also refer to a communication medium between processes on the same machine. As also referred to herein, a network element, node or server may be a machine arranged to execute a program acting as a socket listener and may include an instance of software.

A database (or memory or storage) may include any collection and/or arrangement of volatile and/or non-volatile components suitable for storing data. For example, the memory may include a random access memory (RAM) device, a read-only memory (ROM) device, a magnetic storage device, an optical storage device, a solid state device, and/or any other suitable data storage device. In certain embodiments, a database may represent, in part, a computer-readable storage medium having computer instructions and/or logic encoded thereon. The database may represent any number of memory components within, locally to, and/or accessible by the processor and/or computing device.

Various terms used herein have special meanings in the art. Whether a particular term should be construed as a "technical term" depends on the context in which the term is used. These terms should be interpreted in light of the context in which they are used in this disclosure, and those skilled in the art will understand these terms in the context of the disclosure. The above definitions do not exclude other meanings that may be assigned to these terms based on the context in which they are disclosed.

Words of comparison, measurement, and timing, such as "at that time," "equivalent," "in between," "perfect," etc. complete," and the like, where "substantially" means that such comparisons, measurements, and timings are feasible, either implicitly or explicitly, to achieve the stated desired results.

Additionally, section headings and subject headings herein are provided for consistency with proposals under various patent provisions and conventions, or otherwise to provide organizational cues. These headings shall not characterize or limit the embodiments recited in any claims that may be issued from this disclosure. Specifically, a description of a technology in the “background” should not be construed as an admission that the technology is prior art to any embodiment of the present disclosure. Also, any reference to the singular “invention” in this disclosure should not be used to assert only one novelty in this disclosure. A plurality of inventions may be set forth in accordance with the limits of the claims issued from this disclosure, and such claims thus define the invention(s) and their equivalents covered thereby. In all instances, the scope of these claims will be considered to their advantage in light of this disclosure, but should not be limited by the headings herein.

Claims (41)

A method of administering a shuttle service, comprising:
The method is implemented by at least one processor,
At least one 'non-shuttle service request identification unit to search a database of historical transport-related requests to identify a plurality of historical non-shuttle service requests ', wherein each past non-shuttle service request includes a start time and a route defined by at least an original location and an arrival location, the at least one processor being configured to communicate with the database;
operating at least one 'non-shuttle service request selector' to select a plurality of past non-shuttle service requests from the database, wherein the one or more selected past non-shuttle service requests are selected from one or more other selected past non-shuttle service requests. having at least a portion of a route common to the service requests; and
operating at least one 'candidate service route generator' to derive a candidate shuttle service route for use in providing shuttle service, the candidate shuttle service route comprising: one or more of the selected past non-shuttle service requests; Derived based on the step, including;
At least one of the selected past non-shuttle service requests,
past non-shuttle service requests sent and received from the user computing device and successfully matched with the service provider;
past non-shuttle service requests sent and received from the user computing device but canceled or abandoned; or
past non-shuttle service requests from users identified as frequent users of low cost services. According to claim 1,
The candidate shuttle service route is:
derived based at least on a start time, route, origin location and/or arrival location of one or more of the selected past non-shuttle service requests. According to claim 1,
The one or more past non-shuttle service requests are:
start times within the first threshold period;
original locations located within the first critical region; and/or
arrival locations located within the second critical area;
selected based on past non-shuttle service requests with According to claim 1,
The step of operating the at least one 'candidate service route generator' includes:
deriving a start time for the candidate shuttle service route, an original location for the candidate shuttle service route, and an arrival location for the candidate shuttle service route;
The start time for the candidate shuttle service route, the location for the candidate shuttle service route, and the arrival location for the candidate shuttle service route are the start time, original location, and/or arrival of one or more of the selected past non-shuttle service requests. a method derived based on location. 5. The method of claim 4,
The step of operating the at least one 'candidate service route generator' includes:
deriving one or more drop off and/or one or more pickup locations between the original location for the candidate shuttle service route and the arrival location for the candidate shuttle service route;
wherein the one or more drop off and/or one or more pickup locations are derived based on a start time, origin location and/or arrival location of one or more of the selected past non-shuttle service requests. According to claim 1,
A method, wherein one or more of the following apply:
one or more of the selected past non-shuttle service requests include requests for taxi service, personal car service and/or rideshare service; and/or
Each past non-shuttle service request is a transportation-related request that is not a request for shuttle service. According to claim 1,
operating at least one 'potential user selector' to perform an analysis to identify one or more price sensitive users and to select one or more potential users for the shuttle service;
at least one of the selected potential users is a user identified as being price sensitive;
and selecting the one or more past non-shuttle service requests comprises selecting one or more past non-shuttle service requests previously sent by a user computing device of one or more of the selected potential users. 8. The method of claim 7,
wherein the one or more past non-shuttle service requests previously sent are by the user identified as being price sensitive. According to claim 1,
the database of past transportation-related requests further includes a plurality of past shuttle service requests, sent from a user computing device of a plurality of users; And
wherein the derivation of the candidate shuttle service route is further based on one or more of the past shuttle service requests. The method of claim 1,
The step of operating the at least one 'candidate service route generator' includes:
refining the candidate service route to minimize the amount of pickups and/or drop-offs along the candidate service route. 11. The method of claim 10,
The step of improving the candidate service route includes:
adjusting the start time for the candidate shuttle service route, adjusting the original location for the candidate shuttle service route, and/or adjusting the arrival location for the candidate shuttle service route. According to claim 1,
operating at least one 'potential user selector' to select one or more potential users for the shuttle service; and
operating at least one 'user-side notification and reservation control' to communicate to a user computing device of one or more of the selected potential users, the communication comprising: information regarding the candidate shuttle service route and/or on the candidate shuttle service route; A method, further comprising: providing an opportunity to receive shuttle service. According to claim 1,
performing a service provider matching process to match a service provider with the candidate shuttle service route. 14. The method of claim 13,
wherein the service provider matching process is based on one or more of the following:
minimizing travel distance and/or travel time by the matched service provider between servicing a previous candidate shuttle service route and servicing the candidate service route; and/or
minimizing travel distance and/or travel time by the matched service provider between servicing the candidate service route and servicing the next candidate shuttle service route. A method of administering a shuttle service, comprising:
The method is implemented by at least one processor,
operating at least one 'non-shuttle service request identifier' to search a database of past transportation-related requests to identify a plurality of past non-shuttle service requests, each past non-shuttle service request starting a route defined by time and at least an original location and an arrival location, wherein the at least one processor is configured to communicate with the database;
operating at least one 'non-shuttle service request selector' to select one or more of the past non-shuttle service requests from the database;
operating at least one 'candidate service provider selector' to select one or more candidate service providers available to service one or more of the selected past non-shuttle service requests;
operating at least one 'candidate service route generator' to derive one or more candidate shuttle service routes, the one or more candidate shuttle service routes being derived based on one or more of the selected past non-shuttle service requests; step; and
operating at least one 'candidate shuttle service route selector' to select one or more of the candidate shuttle service routes for use in providing shuttle service, wherein the selected one or more candidate shuttle service routes are selected from one or more of the selected candidate service providers. selected based on the steps, including;
At least one of the selected past non-shuttle service requests,
past non-shuttle service requests sent and received from the user computing device and successfully matched with the service provider;
past non-shuttle service requests that were sent and received from the user computing device but were canceled or abandoned; or
past non-shuttle service requests from users identified as frequent users of low cost services. 16. The method of claim 15,
and each selected past non-shuttle service request includes at least a portion of a route common to one or more other selected past non-shuttle service requests. 16. The method of claim 15,
The candidate shuttle service route is:
derived based at least on a start time, route, origin location, and/or arrival location of one or more of the selected past non-shuttle service requests. 16. The method of claim 15,
The one or more past non-shuttle service requests are:
start times within the first threshold period;
original locations located within the first critical region; and/or
arrival locations located within the second critical area;
selected based on past non-shuttle service requests with 16. The method of claim 15,
The step of operating the at least one 'candidate service route generator' includes:
deriving a start time for the candidate shuttle service route, an original location for the candidate shuttle service route, and an arrival location for the candidate shuttle service route;
The start time for the candidate shuttle service route, the original location for the candidate shuttle service route, and the arrival location for the candidate shuttle service route include a start time, an original location, and/or one or more of the selected past non-shuttle service requests. derived based on the arrival location. 20. The method of claim 19,
The step of operating the at least one 'candidate service route generator' includes:
deriving one or more drop off and/or one or more pickup locations between the original location for the candidate shuttle service route and the arrival location for the candidate shuttle service route;
wherein the one or more drop off and/or one or more pickup locations are derived based on a start time, origin location and/or arrival location of one or more of the selected past non-shuttle service requests. 16. The method of claim 15,
A method, wherein one or more of the following apply:
the selection of past non-shuttle service requests includes selecting past non-shuttle service requests that were unassigned, unmatched, and/or canceled;
one or more of the selected past non-shuttle service requests include requests for taxi service, personal car service and/or rideshare service; and/or
Each past non-shuttle service request is a transportation-related request that is not a request for shuttle service. 16. The method of claim 15,
operating at least one 'potential user selector' to perform an analysis to identify one or more price sensitive users and to select one or more potential users for the shuttle service;
at least one of the selected potential users is a user identified as being price sensitive;
and selecting the one or more past non-shuttle service requests comprises selecting one or more past non-shuttle service requests previously sent by a user computing device of one or more of the selected potential users. 16. The method of claim 15,
the database of past transportation-related requests further includes a plurality of past shuttle service requests; And
wherein the derivation of the candidate shuttle service route is further based on one or more of the past shuttle service requests. 16. The method of claim 15,
operating the at least one 'candidate service route generator' to refine the candidate service route to minimize the amount of pickups and/or drop-offs along the candidate service route. 25. The method of claim 24,
The step of improving the candidate service route includes:
adjusting the start time for the candidate shuttle service route, adjusting the original location for the candidate shuttle service route, and/or adjusting the arrival location for the candidate shuttle service route. 16. The method of claim 15,
operating at least one 'potential user selector' to select one or more potential users for the shuttle service;
operating at least one 'user-side notification and reservation control' to communicate to a user computing device of one or more of the selected potential users, wherein the communication includes information regarding the candidate shuttle service route and/or a shuttle on the candidate shuttle service route. A method, further comprising; providing an opportunity to receive a service. 16. The method of claim 15,
wherein the candidate service providers are selected based on one or more of the following:
minimizing travel distance and/or travel time by the candidate service providers between servicing a previous candidate shuttle service route and servicing the candidate service route; and/or
minimizing travel distance and/or travel time by the candidate service providers between servicing the candidate service route and servicing the next candidate shuttle service route. A method of administering a shuttle service, comprising:
The method is implemented by at least one processor,
operating at least one 'non-shuttle service request identifier' to search a database of past transportation-related requests to identify a plurality of past non-shuttle service requests, each past non-shuttle service request starting a route defined by time and at least an original location and an arrival location, wherein the at least one processor is configured to communicate with the database;
operating at least one 'potential user selector' to select one or more potential users for the shuttle service, wherein one or more of the selected potential users are identified as price sensitive users who frequently use low cost services;
operating at least one 'non-shuttle service request selector' to select one or more of the past non-shuttle service requests, wherein one or more of the selected past non-shuttle service requests are:
a request previously sent by a user computing device of one of the selected potential users identified as being a price-sensitive user, and/or
a request sent and received from a user computing device that has been abandoned or canceled; and
operating at least one 'candidate service route generator' to derive a candidate shuttle service route for use in providing the shuttle service, wherein the candidate shuttle service route is identified as being a price sensitive user. based on one or more of the selected past non-shuttle service requests previously sent by a user computing device of potential users; 29. The method of claim 28,
and each selected past non-shuttle service request includes at least a portion of a route common to one or more other selected past non-shuttle service requests. 29. The method of claim 28,
wherein the derivation of the candidate shuttle service route is based at least on a start time, route, origin location, and/or arrival location of one or more of the selected past non-shuttle service requests. 29. The method of claim 28,
The selection of the one or more past non-shuttle service requests is
start times within the first threshold period;
original locations located within the first critical region; and/or
arrival locations located within the second critical area;
based on past non-shuttle service requests with 29. The method of claim 28,
The step of operating the at least one 'candidate service route generator' includes:
deriving a start time for the candidate shuttle service route, an original location for the candidate shuttle service route, and an arrival location for the candidate shuttle service route;
The start time for the candidate shuttle service route, the original location for the candidate shuttle service route, and the arrival location for the candidate shuttle service route include a start time, an original location, and/or one or more of the selected past non-shuttle service requests. derived based on the arrival location. 33. The method of claim 32,
The step of operating the at least one 'candidate service route generator' includes:
deriving one or more drop off and/or one or more pickup locations between the original location for the candidate shuttle service route and the arrival location for the candidate shuttle service route;
wherein the one or more drop off and/or one or more pickup locations are derived based on a start time, origin location and/or arrival location of one or more of the selected past non-shuttle service requests. 29. The method of claim 28,
A method, wherein one or more of the following apply:
one or more of the selected past non-shuttle service requests include requests for taxi service, personal car service and/or rideshare service; and/or
Each past non-shuttle service request is a transportation-related request that is not a request for shuttle service. 29. The method of claim 28,
the database of past transportation-related requests further includes a plurality of past shuttle service requests; And
wherein the derivation of the candidate shuttle service route is further based on one or more of the past shuttle service requests. 29. The method of claim 28,
The step of operating the at least one 'candidate service route generator' includes:
refining the candidate service route to minimize the amount of pickups and/or drop-offs along the candidate service route. 37. The method of claim 36,
The step of improving the candidate service route includes:
adjusting the start time for the candidate shuttle service route, adjusting the original location for the candidate shuttle service route, and/or adjusting the arrival location for the candidate shuttle service route. 29. The method of claim 28,
operating at least one 'user-side notification and reservation control' to communicate to one or more of the selected potential users;
wherein the communication comprises providing information regarding the candidate shuttle service route and/or an opportunity to receive shuttle service on the candidate shuttle service route. 29. The method of claim 28,
operating a 'candidate service provider selection unit' to perform a service provider matching process to match a service provider with the candidate shuttle service route. 40. The method of claim 39,
wherein the service provider matching process is based on one or more of the following:
minimizing travel distance and/or travel time by the matched service provider between servicing a previous candidate shuttle service route and servicing the candidate service route; and/or
minimizing travel distance and/or travel time by the matched service provider between servicing the candidate service route and servicing the next candidate shuttle service route. A method of administering a shuttle service, comprising:
The method is implemented by at least one processor,
operating at least one 'non-shuttle service request identifier' to search a database of past transportation-related requests to identify a plurality of past non-shuttle service requests received from a user computing device of a plurality of users; each past non-shuttle service request includes a start time and a route defined by at least an original location and an arrival location, the at least one processor being configured to communicate with the database;
operating at least one 'potential user selector' to perform an analysis to identify one or more price-sensitive users based on frequency of use of the low cost service;
operating at least one 'potential user selector' to select one or more potential users for the shuttle service, wherein at least one of the selected potential users is identified as a price sensitive user;
operating at least one 'non-shuttle service request selector' to select one or more of the past non-shuttle service requests, the selection being based on one or more of the following:
the past non-shuttle service request is a request previously sent by a user computing device of one or more of the selected potential users identified as being a price sensitive user;
the past non-shuttle service request is a request sent and received from a user computing device but has been abandoned or canceled;
operating at least one 'candidate service provider selector' to select one or more candidate service providers available to service one or more of the selected past non-shuttle service requests;
operating at least one 'candidate shuttle service route generator' to derive one or more candidate shuttle service routes, wherein the one or more candidate shuttle service routes are derived based on one or more of the selected past non-shuttle service requests. , step;
operating at least one 'candidate shuttle service route generator' to select one of the candidate shuttle service routes for use in providing the shuttle service, wherein the selected candidate shuttle service route includes one or more of the selected candidate service providers. A method comprising; a step selected based on

Images