System and Method for Procuring a Reservation Within a Heterogeneous Transportation Network

A system and method for procuring a reservation within a heterogeneous transportation network are disclosed. In one embodiment of the system, a database stores information for various transportation modes forming multiple transportation routes within the heterogeneous transportation network. For each fee collecting entity along the multiple transportation routes and for the various transportation modes, the database has an attribute including GIS data defining a virtual perimeter for a real-world geographic area corresponding to the fee collecting entity, an attribute including a valueless coefficient defining a payment term for the fee collecting entity, and an attribute including a value-based coefficient defining a payment basis for the fee collecting entity. The system determines a fee due to the fee collecting entities based on the three attributes.

TECHNICAL FIELD OF THE INVENTION

This invention relates, in general, to procuring a reservation and, in particular, to procuring a reservation within a heterogeneous transportation network, including multiple modes of transportation, requiring coordinating many distinct arrangements for a single itinerary.

BACKGROUND OF THE INVENTION

Transportation is becoming increasingly complex. It is now common for travelers to need reservations across a heterogeneous transportation network, including multiple modes of transportation, through varying juristic boundaries. Travelers desire a platform that is accessible from anywhere and at any time to make these reservations. Travelers also prefer a single reservation purchase. Existing platforms, however, have proven cumbersome and the process of distributing payments and fees across the heterogeneous transportation network has proven difficult when a traveler makes a single reservation. Accordingly, there is a need for improved systems and methods for procuring reservations within a heterogeneous transportation network, including multiple modes of transportation, requiring coordinating many distinct arrangements for a single itinerary.

SUMMARY OF THE INVENTION

It would be advantageous to introduce systems and methods that further procure reservations within a heterogeneous transportation network, including multiple modes of transportation, requiring coordinating many distinct arrangements for a single itinerary. It would also be desirable to enable a computer-based solution that would improve the quality and quantity of information about reservations for single itinerary through varying juristic boundaries. To better address one or more of these concerns, a system and method for procuring a reservation within a heterogeneous transportation network is disclosed. In one embodiment of the system, a database stores information for various transportation modes forming multiple transportation routes within the heterogeneous transportation network. For each fee collecting entity along the multiple transportation routes and for the various transportation modes, the database has an attribute including GIS data defining a virtual perimeter for a real-world geographic area corresponding to the fee collecting entity, an attribute including a valueless coefficient defining a payment term for the fee collecting entity, and an attribute including a value-based coefficient defining a payment basis for the fee collecting entity. The system determines a fee due to the fee collecting entities based on the three attributes. These and other aspects of the invention will be apparent from and elucidated with reference to the embodiments described hereinafter.

DETAILED DESCRIPTION OF THE INVENTION

Referring initially toFIG. 1, a system10for procuring a reservation within a heterogenous transportation network T. The heterogeneous transportation network T includes multiple transportation modes forming many transportation routes. The transportation modes may include high-speed rail, light rail, streetcar, transportation-for-hire, autonomous vehicles (including unmanned autonomous vehicles and autonomous vehicles with pilots), semi-autonomous vehicles, bus, and the like. Autonomous vehicles and semi-autonomous vehicles include those with on-ground and off-ground effects. The autonomous vehicles, semi-autonomous vehicles, as well as other vehicles utilizing airspace, may include Automatic Dependent Surveillance-Broadcast (ADS-B) systems, which represent a surveillance technology in which an aircraft determines its position via satellite navigation or other sensors and periodically broadcasts it, enabling it to be tracked. Information may be received by air traffic control ground stations as a replacement or supplement for secondary surveillance radar, as no interrogation signal is needed from the ground. The information may also be received by other aircraft to provide situational awareness and allow self-separation.

A server12, which includes a housing14, has access to an entity database16, a transportation database18, and a reservation database20. The server12is connected via the Internet or other network connection to various fee collecting entities22and computing devices24. The fee collecting entities22, which are individually labeled22-1,22-2, . . . ,22-n, are juristic or governmental entities, for example, that have a financial interest by way of a fee collection, including a tax, for the operation of the heterogeneous transportation network T within a boundary of the fee collecting entity. An operator of the server12and the fee collecting entities22have the fee arrangements defined by agreements26. By way of example, agreement26-1is between the fee collecting entity22-1and the operator of the server12, agreement26-2is between the fee collecting entity22-2and the operator of the server12, and agreement26-nis between the fee collecting entity22-nand the operator of the server12. As a result of these agreements26, the operator of the server12pays fees28to the various fee collecting entities. By way of example, fee28-1is between the fee collecting entity22-1and the operator of the server12, fee28-2is between the fee collecting entity22-2and the operator of the server12, and fee28-nis between the fee collecting entity22-nand the operator of the server12. Reports30may document the fees paid to the fee collecting entities22-nby the operator of the server12. By way of example, report30-1is between the fee collecting entity22-1and the operator of the server12, report30-2is between the fee collecting entity22-2and the operator of the server12, and report30-nis between the fee collecting entity22-nand the operator of the server12.

Users U1. . . Unrespectfully utilize computing devices24-1. . .24-nto communicate with the server12and make reservations for travel within the heterogeneous transportation network T. As shown, funds32are exchanged for transportation reservations34. More particularly, with respect to the user U1, funds32-1are exchanged for transportation reservation34-1and, with respect to user Un, funds32-nare exchanged for transportation reservation34-n. The server12may furnish a user interface module that provides a user interface for the computing devices24. The user interface provides functionality for a user, such as user U1or user Un, to at least browse reservation information within the heterogeneous transportation network T and select a transportation reservation34. The server12then communicates with the heterogeneous transportation network T to verify reservations and provide reservation information as shown by verification36and reservation information38.

In one operational embodiment, the entity database16and the transportation database18within the server12, which is a computer data storage device, stores and organizes information for the multiple transportation modes within the heterogeneous transportation network T. The various transportation modes form multiple transportation routes. The information being organized within the entity database16and the transportation database18is stored in accordance with a logical data model that includes the information about the fee collecting entities22, and relationships defining the manner in which the information is stored and organized in the logical data model including, for each of the fee collecting entities22for each of the transportation modes various attributes, which are utilized to determine the fee or fees due to the fee collecting entities22. With each reservation made and verified, the system10determines the fees due. More particularly, by way of example, the server12receives confirmation of the transportation reservation34-1including at least one of the transportation routes within the heterogenous transportation network T. The server12then accesses the computer data storage device for access to the entity database16, the transportation database18, and the reservation database20. For each of the fee collecting entities22for the transportation reservation34-1, fees28due to each one of the fee collecting entities22is determined.

Referring now toFIG. 2, successive conceptual grid diagrams depict some embodiments of the operations of the system10. The heterogeneous transportation network T is represented by a network flow model n, where various origins, destinations, and intermediate points are labeled as nodes, n1, n2, n3, n4, n5, n6, n7, n8, n9, n10, n11, n12, n13, n14, n15, n16, with transportation links or arcs interconnecting the nodes n1-n16. A GIS-based attribute that includes GIS data defining a virtual perimeter for a real-world geographic area corresponding to the various fee collecting entities22is utilized to create the network flow model n. In one implementation, nodal data represents passenger exchange locations for the various modes of transportation as individual nodes n1-n16, such as high-speed rail, light rail, streetcar, transportation-for-hire, autonomous vehicle, semi-autonomous vehicle, and bus, for example, with the arcs being the transportation lines.

Once the network flow model n is created, the various types of fees28potentially collected by the fee collecting entities22are combined into a comprehensive measure that permits measuring anywhere through the space. As shown, the cost surface is modeled as a series of raster grids. Each of the cells within a raster grid may correspond to one of the nodes n1-n16. A second attribute includes a valueless coefficient, a1, a2, a3, a4, as, a6, a7, a8, a9, a10, a11, a12, a13, a14, a15, a16, defining a payment term for the fee collecting entity. The valueless coefficient, a1, a2, a3, a4, a5, a6, a7, a8, a9, a10, a11, a12, a13, a14, a15, a16, may a value relative to a sales tax, a property tax, or a transaction payment, for example.

For each fee collecting entity, J1. . . Jn, for each mode of transportation, T1. . . Tn, a raster grid is populated with the valueless coefficient a1. . . a16with a third attribute, α1. . . αn, including a value-based coefficient defining a payment basis for the fee collecting entity and acting as a mathematical weight for the raster grid. The value-based coefficient may be a ticket price or property value, for example. Once a transportation reservation34is made and verified, then a corresponding transportation route R is determined through the raster grids J1T1. . . J1Tn, J2T1. . . J2Tn, . . . JnT1. . . JnTnsuch that the fee due for the fee collecting entity J1is f1, the fee collecting entity J2is f2, and the fee collecting entity Jnis fnand, more specifically:

Referring now toFIG. 3, one embodiment of the server12as a computing device includes a processor50, memory52, storage54, inputs56, outputs58, and a network adaptor60interconnected with various buses62in a common or distributed, for example, mounting architecture. In other implementations, in the computing device, multiple processors and/or multiple buses may be used, as appropriate, along with multiple memories and types of memory. Further still, in other implementations, multiple computing devices may be provided and operations distributed therebetween. The processor50may process instructions for execution within the server12, including instructions stored in the memory52or in storage54, one or both of which may be non-transitory memory. The memory52stores information within the computing device. In one implementation, the memory52is a volatile memory unit or units. In another implementation, the memory is a non-volatile memory unit or units. Storage54includes capacity that is capable of providing mass storage for the server12. Various inputs56and outputs58provide connections to and from the server12, wherein the inputs56are the signals or data received by the server12, and the outputs58are the signals or data sent from the server12. The network adaptor60couples the server12to a network such that the server12may be part of a network of computers, a local area network (LAN), a wide area network (WAN), an intranet, a network of networks, or the Internet, for example.

The memory52and storage54are accessible to the processor50and include processor-executable instructions that, when executed, cause the processor50to execute a series of operations. A combination of the memory52and the storage54may include a database for storing and organizing information for various transportation modes, T1. . . Tn, within the heterogeneous transportation network T. As previously discussed, the various transportation modes, T1. . . Tn, form multiple transportation routes R. The information is organized within the database in accordance with a logical data model that includes information about the fee collecting entities22. The logical data model includes relationships defining the manner in which the information is stored and organized in the logical data model including, for each of the fee collecting entities22for each of the transportation modes, T1. . . Tn, various attributes. In some embodiments, the attributes include the GIS-based attribute having GIS data defining a virtual perimeter for a real-world geographic area corresponding to the fee collecting entity, J1. . . Jn. The valueless coefficient, another attribute, includes a valueless coefficient, a1. . . a16, defining the payment term for the fee collecting entity, J1. . . Jn. The value-based coefficient, α1. . . αn, defines the payment basis for the fee collecting entity, J1. . . Jn.

In one embodiment, the processor-executable instructions cause the processor50to receive confirmation of the transportation reservation34including at least one of the transportation routes R. The processor50is then caused to access the computer data storage device and create a network flow model based on the GIS-based attribute. In some embodiments, the processor-executable instructions then cause the processor50to create a cost surface having multiple cells. The cellular structure relates to the network flow model. The cost surface may have a value in each of the cells relative to the valueless coefficient, a1. . . a16, and a weight associated with each of the plurality of cells relative to the value-based coefficient, α1. . . αn. The processor50is then caused by the processor-executable instructions to perform a non-optimized cost path analysis using cartographic modeling on the cost surface reflecting the transportation reservation34. It should be appreciated that the non-optimized cost path analysis may include a non-optimized cost distance analysis as well. The fees28due to the fee collecting entity, J1. . . Jn, or fee collecting entities22are then determined.

FIG. 4conceptually illustrates the software architecture of a reservation application100of some embodiments that may make the arrangements and accommodations for a travel reservation within the heterogeneous transportation network T having multiple transportation modes, T1. . . Tn, and multiple transportation routes R. In some embodiments, the reservation application100is a stand-alone application or is integrated into another application, while in other embodiments the application might be implemented within an operating system. Furthermore, in some embodiments, the reservation application100is provided as part of a server-based solution or a cloud-based solution. In some such embodiments, the application is provided via a thin client. That is, the application runs on a server while a user interacts with the application via a separate machine remote from the server. In other such embodiments, the application is provided via a thick client. That is, the application is distributed from the server to the client machine and runs on the client machine.

The reservation application100includes a user interface (UI) interaction and generation module102, a transportation listing tool104, a reservation information tool106, map tool108, transportation description tools110, reservation inquiry tools112, reservation verification tools114, reservation confirmation tools116, financial transaction tools118, and an accounting application manager120. The reservation application100has access to inventory databases122and presentation instructions124. The inventory databases122include information about travel accommodation availability, price, reservation availability, travel descriptions, and travel routes, for example. The presentation instructions124store the user presentation editing operations that the reservation application100performs as a set of instructions. In some embodiments, the inventory databases122and the presentation instructions124are all stored in one physical storage. In other embodiments, the storages represented by the inventory databases122and the presentation instructions124are all stored in separate physical storages, or one of the storages is in one physical storage while the other is in a different physical storage.

The transportation listing tool104accesses the inventory databases122to create a travel listing in response to a search by a user, such as a passenger. The reservation information tool106may provide the travel listings with availability and reservation information. The map tool108augments the travel listing with information about the route that may presented as an annotated map, for example. The transportation description tools110add descriptive information to the travel listing with details about the modes of operation such as boarding information, seating, and amenities, for example. The reservation inquiry tools112handle acquiring such information as the user's or potential passenger's name, address, telephone number, payment information, number of passengers, one way/roundtrip, and other appropriate information relative to a reservation. The reservation verification tools114present an interface for the user or potential passenger to verify this information. The reservation confirmation tools116execute the reservation and provide the necessary confirmation. The financial transaction tools118work with an appropriate financial transaction server to complete all needed financial transactions. As will be appreciated, the reservation confirmation tools116and financial transaction tools118work in combination together. The accounting application manager120handles communication with an accounting application150(seeFIG. 5).

In the illustrated embodiment,FIG. 4also includes an operating system130that includes input device drivers132and a display module134. In some embodiments, as illustrated, the device drivers132and display module134are part of the operating system130even when the image editing application is an application separate from the operating system. The input device drivers132may include drivers for translating signals from a keyboard, mouse, touchpad, tablet, touch screen, gyroscope, accelerometer, etc. A user interacts with one or more of these input devices, which send signals to their corresponding device driver. The device driver then translates the signals into user input data that is provided to the UI interaction and generation module102.

FIG. 5conceptually illustrates the software architecture of the accounting application150of some embodiments that may determine the fees28due to the various fee collecting entities22based on the transportation reservation34. In some embodiments, the accounting application150is a stand-alone application or is integrated into another application such as the accounting application manager120of the reservation application100ofFIG. 4, while in other embodiments the accounting application150might be implemented within an operating system.

Furthermore, in some embodiments, the accounting application150is provided as part of a server-based solution or a cloud-based solution. In some such embodiments, the application is provided via a thin client. That is, the application runs on a server while a user interacts with the application via a separate machine remote from the server. In other such embodiments, the application is provided via a thick client. That is, the application is distributed from the server to the client machine and runs on the client machine.

The accounting application150includes a user interface (UI) interaction and generation module152, management (user) interface modules154, entity management modules156, transportation management modules158, reservation management modules159, network flow modules160, analysis modules162, report modules164, fee distribution tools166, and a reservation application manager168. The management (user) interface modules154provide the software by which the user and a computer system, such as the server12, interact within the system10. The entity management modules156have access to the entity data16and manage the entity database16. The transportation management modules158have access to the transportation data18and manage the transportation database18. The reservation management modules159have access to the reservation database20and manage the reservation database20. The network flow modules160analyze the entity database16and the transportation database18to develop the network flow model, which is analyzed by the analysis modules162. The report modules164prepare various routine and custom reports for the users. The fee distribution tools166ensure the appropriate fees are distributed to the fee collecting entities. The reservation application manager168provides the interface for the accounting application150to the reservation application100. Presentation instructions170store the user presentation editing operations that the accounting application150performs as a set of instructions. In some embodiments, the entity database16, the transportation database18, the reservation database20, and the presentation instructions170are all stored in one physical storage. In other embodiments, the storages represented by the entity database16, the transportation database18, the reservation database20, and the presentation instructions170are all stored in separate physical storages, or one of the storages is in one physical storage while the other is in a different physical storage.

In the illustrated embodiment,FIG. 5also includes an operating system180that includes input device driver(s)182and a display module184. In some embodiments, as illustrated, the input device drivers182and display module184are part of the operating system180even when the image editing application is an application separate from the operating system180. The input device drivers182may include drivers for translating signals from a keyboard, mouse, touchpad, tablet, touch screen, gyroscope, accelerometer, etc. A user interacts with one or more of these input devices, which send signals to their corresponding device driver. The device driver then translates the signals into user input data that is provided to the UI interaction and generation module152.

FIG. 6illustrates an exemplary method for procuring a reservation using the system10. The method starts at block200and at decision block202the methodology may handle management of the database with attributes or handle the procurement of a reservation by a passenger. At block204, various agreements between the operator of the system and the fee collecting entities are received and following analysis of the agreements, the databases are appropriately populated with attributes at block206. The network flow model is then maintained at block208before an updated cost surface is created at block210. The methodology then returns to decision block202.

At decision block202, with respect to procurement of the reservation by the passenger, the methodology advances to block212, where the server receives a travel availability request from the passenger. As alluded above, the travel request may be communicated over the Internet from a passenger at a smart device or a computer, may be received at call center from a user of a telephone, or may be received by the server in any other appropriate manner. Again, all references below to the communication through a network between the passenger—or someone, including people as well as partially and fully automated systems, making the reservation on behalf of the passenger—and server apply equally to communications between server and an operator at call center and communications between the operator and a user of a telephone. The travel availability request may include one or more parameters that a reservation must meet, such as a location, dates of availability, travel accommodation, or any other suitable parameters. At block214, the server determines one or more available reservations that meet the parameters of the request by accessing information stored in the inventory databases. If the server determines at decision block216that no reservations meet the parameters, then the server communicates a message to the passenger at block218indicating that no travel arrangements meeting the request are available. The method may then return to the decision block202where the server may allow the passenger to try another search, for example.

If the server determines at decision blocks220and222that the requested reservation meets the parameters of the request, then the server communicates a list of available reservations with travel accommodations to the passenger. At block224, the server receives the passenger information and processes the passenger information to create the reservation at block226. The finalized reservation information is then communicated at block228. A non-optimized cost path analysis is performed at block230based on the finalized reservation. At block232, the fees due to various fee collecting entities are determined. At block234, the system may verify that the reservation was utilized before setting any fees to be sent at block236. The methodology then ends at block238.

The present application describes a system10that provides users, such as potential passengers or reservation specialists, for example, with a platform for procuring reservations within a heterogeneous transportation network T, including multiple modes of transportation, T1. . . Tn, requiring coordinating many distinct arrangements for a single itinerary. The computer-based solution improves the quality and quantity of information about reservations for single itinerary through varying juristic and governmental boundaries by ensuring various entities, such as juristic and governmental entities, collect any required fees28. The present application describes a system10that coordinates plural reservations, e.g. plural trip segments, and the payment of associated fees28by providing route searching, route guidance, and multimodal routing, i.e., combining two or more modes of transportation, where the modes can be any of form.

Embodiments according to the teachings presented herein will now be illustrated by reference to the following non-limiting working examples wherein modes of transportation and entity boundaries are solely representative of those which can be employed and are not exhaustive of those available and operative. Referring now toFIG. 7, the heterogeneous transportation network T shown inFIG. 1is depicted in additional detail. With respect to fee collecting entities22, as indicated in the legend toFIG. 7, countries C (i.e., CA, CB), counties O (i.e., OA, OB, OC, OD), cities I (i.e., IA, IB, IC, ID, IE, IF, IG, IH), and districts D (i.e., DA, DB, DC, DD) are depicted. The countries C, counties O, and cities I are examples of governmental fee collecting entities and the districts D are examples of juristic fee collecting entities. As shown various modes of transportation, such as high-speed rail, light rail, bus, plane, car (including autonomous vehicle and semi-autonomous vehicle), and pedestrian, traverse the countries C (i.e., CA, CB), counties O (i.e., OA, OB, OC, OD), cities I (i.e., IA, IB, IC, ID, IE, IF, IG, IH), and districts D (i.e. DA, DB, DC, DD). The various forms of transportation have transportation nodes N (i.e., N1, N2, N3, N4, N5, N6, N7, N8, N9, N10, N11, N12, N13, N14, N15, N16, N17, N18, N19, N20, N21, N22, N23, N24, N25, N26, N27, N28, N29, N30, N31, N32, N33) representing possible origins, destinations, and intermediate points for passengers.

Example I. A passenger procures a reservation to travel from N22to N23within City IF. (seeFIG. 7) via bus. The ticket cost is $10 and the City IFhas an agreement in place to collect a quarter cent sales tax (0.0025). The following table, Table I, shows the calculation of the fee for Example I.

TABLE IFee Calculation for Example IGIS-basedValuelessValue-BasedEntityAttributeCoefficientCoefficientFeeIFN22to N230.0025$10.00$0.025

Example II. A passenger procures a reservation to travel from N9to N13from City IBto a location in County OA(seeFIG. 7). The ticket cost is $20 and the City IBhas an agreement in place to collect a quarter cent sales tax (0.0025) and the County OAhas an agreement in place to collect a transaction fee of $0.01. The following table, Table II, shows the calculation of the fee for Example II.

Example III. A passenger procures a reservation to travel from N2to N31, that is from City IDwithin Country CAto a location in City IHwithin County OB(seeFIG. 7). The reservation includes high-speed rail (N2to N1), transportation-for-hire (N1to N33), plane (N33to N32), and transportation-for-hire (N32to N31). The ticket cost is $1,000 and several agreements govern the payment of fees. The City IBhas an agreement in place to collect a quarter cent sales tax (0.0025) and the City IChas an agreement in place to collect a quarter cent sales tax (0.0025) also. The Country CAhas an exit fee of $2 per passenger and the Country CBhas an entry fee of $5 per passenger. The City IHhas a right of way agreement in place to collect a transaction fee of $0.01. The following table, Table III, shows the calculation of the fee for Example III.

Example IV. A passenger procures a reservation to travel from N1to N6, that is from County OBwithin Country CAto a location in District DCCity IHwithin County OB(seeFIG. 7). The reservation includes high-speed rail (N1to N2to N3to N4to N5to N6). The ticket cost is $500 and several agreements govern the payment of fees. The District OBhas an agreement in place to collect a tax (0.000025) based on the value of the property and the City ICand the City IDhave an agreement in place to collect a quarter cent sales tax (0.0025). The District DBhas an agreement in place to collect a use fee. The Country CAhas an exit fee of $2 per passenger and the Country CBhas an entry fee of $5 per passenger. The City IEhas a right of way agreement in place to collect a transaction fee of one percent. The County OCcollects a use fee of $0.50 per passenger. The City IFcollects a quarter cent sales tax (0.0025) and the District DCcollects a one percent bond repayment. The following table, Table IV, shows the calculation of the fee for Example IV.

Example V. A passenger procures a reservation to travel from N22to N23within City IF(seeFIG. 7) via an unmanned autonomous vehicle providing an air taxi service. The ticket cost is $50 and the City IFhas an agreement in place to collect a quarter cent sales tax (0.0025). The following table, Table V, shows the calculation of the fee for Example V.

TABLE VFee Calculation for Example VGIS-basedValuelessValue-BasedEntityAttributeCoefficientCoefficientFeeIFN22to N230.0025$50.00$0.125

Example VI. A passenger procures a reservation to travel from N22to N23within City IF(seeFIG. 7) via an unmanned autonomous vehicle providing an air taxi service. The ticket cost is $50 and the City IFhas an agreement in place to collect a quarter cent sales tax (0.0025) based on information collecte3d from an ADS-B system that monitors the taxi service. The following table, Table VI, shows the calculation of the fee for Example VI.

The present working examples described in Example I through Example VI demonstrate a system and a method that coordinates plural reservations, e.g. plural trip segments, while ensuring the payment of associated fees due to various fee collecting entities. In this manner, the systems and methods presented herein enable a single reservation purchase as appropriate fee distribution is ensured.

The order of execution or performance of the methods and data flows illustrated and described herein is not essential, unless otherwise specified. That is, elements of the methods and data flows may be performed in any order, unless otherwise specified, and that the methods may include more or less elements than those disclosed herein. For example, it is contemplated that executing or performing a particular element before, contemporaneously with, or after another element are all possible sequences of execution.