Method and system for defined autonomous service

Abstract

To provide methods and systems used to provide for self-functioning autonomous services via "Defined Autonomous Services Platform" (DASP).SOLUTION: A DASP 122 consists of system component(s) and / or sub-component(s) 124-142 and / or systems provided by Service Provider(s) 120 that manages relevant functions and activities which are part of a program plan, which transport at a specific time, people, products, and / or services from and to specific location(s), at specific time(s), and within a specific geographically boundary that are all pre-defined. An operator 124 is an individual, or a group of individual(s) that actively programs, operates, and / or maintains the DASP. A program fully consists of functions such scheduling, availability of use, routing, energy use and power consumption, service validation and authorization, user identification, payment services, service maintenance, or field support services.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application is related to U.S. Provisional Patent Application No. 62,696,827, filed July 11, 2018, and U.S. Nonprovisional Patent Application No. 16 / 116,895, filed August 29, 2018, the disclosures of which are incorporated herein by reference. [Background technology]

[0002] An embodiment of the present invention comprises a method and system used to provide self-functioning autonomous services via a "Defined Autonomous Services Platform" (DASP) that allows for the transportation of people, products and / or services between specific locations, at specific times, within specific geographical boundaries, with effective energy and power management all pre-defined and fully automatic so as not to require end-user intervention, thereby enabling methods relevant for religiously specific use cases, e.g. following Judaism. Strict adherence to being a "shomer" (observant), observing the Sabbath (also known as Shabbos in Yiddish, or Shabbat / Shabbat in Hebrew), and observing Jewish holidays as outlined in the Torah (doctrine) are standards of orthodox practice and have merit and legal implications in the manner of being Jewish as understood by religious courts with regard to faith in Judaism. Shomer is the observance of mitzvot (commandments), including the performance of certain duties, the abstention from certain activities of creation or creative acts (known as forms of melach), and the restriction of the transportation of objects and / or movement from private to public lands (territories) during certain times of the day, such as from dawn (or sunrise) to dusk (or twilight), as well as the observance of the weekly Sabbath. In addition, there are other areas of activity that are prohibited on the Sabbath under halakha (Jewish law), many of which are also restricted to Jewish holidays.

[0003] As embodiments of the present invention relate to transportation and other related services that have traditionally been considered prohibited activities for being a shomer, the Defined Autonomous Services Platform (DASP) implements various architectural design considerations to ensure that individuals adhere to the general guidelines for being a shomer on Shabbat and holidays.

[0004] The traditional "Schomer" problems addressed include:

[0005] I. Autonomy: The Defined Autonomous Services Platform (DASP) enables the ability to create, manage and execute a predefined program (or set of programs) whereby an autonomous robot or a fleet of autonomous robotic units travels a predefined path on ground and / or air and / or sea within a geographical boundary and performs a predefined task (or set of tasks) fully automatically without the need for end user intervention. Furthermore, the predefined autonomy programs consist of functions such as scheduling, availability, routing, energy management, user identification, payment services, service verification and approval, maintenance, field support services, and other robotic business process automation handled by interconnected service providers.

[0006] II. Mobility Management: A "Defined Autonomous Service Platform" (DASP) will enable the ability to constrain the operation of an autonomous robot or swarm of autonomous robotic units moving on land and / or in the air and / or at sea within a geographic boundary "Eruv" (or geographic enclosure) that, when defined, will integrate multiple private and public geographic areas into one vast private domain.

[0007] III. Energy & Power Management: "Defined Autonomous Services Platform" (DASP): 1. Utilizes an autonomous robot or fleet of autonomous robotic units operating on a battery-powered system and solid-state electronics that automatically manage the positioning, navigation, motion, control, maintenance, and safety functions of the units, whereas traditional automotive units utilize a combustion-based power engine that consumes and / or burns (by fire) gasoline or gasoline-based fuel. 2. A predefined program (or set of programs) is fully pre-planned and managed, power and energy are distributed, and power source voltage, current, and resistance are actively managed without making, opening, or closing electrical circuits, and energy requirements are maintained consistently regardless of use, demand, or physical weight load. Summary of the Invention

[0008] Embodiments of the present invention comprise methods and systems that enable an autonomous robot or swarm of autonomous robots to function in a manner that adheres to the non-performance of prohibitions against certain creative activities (known as forms of melach) without end-user intervention during specific times or periods associated with being a shomer on a Sabbath or holiday under Orthodox Judaism.

[0009] The "Defined Autonomous Services Platform" (DASP) enables the transportation of people, products and / or services between specific locations, at specific times, and within specific geographic boundaries, and the described functionality includes end-to-end pre-planning, execution and operational management of a given program of an autonomous robot (or a fleet of autonomous robots), which may consist of passenger cars, delivery vehicles, commercial trucks, robotic units, UAVs and / or drones.

[0010] Further, the Defined Program is fully configured with functions such as scheduling, availability, routing, energy usage and power consumption, service validation and authorization, user identification, payment services, service maintenance management, or field support services, and is connected to a network of communication wired and / or wireless systems and interconnected to service providers that are capable of operating, supporting, and enabling management of the various elements required to operate the Defined Autonomous Service Platform (DASP) and provide its capabilities. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 illustrates a “Defined Autonomous Services Platform” (DASP) and system architecture design used to create, manage, and execute predefined programs for an autonomous robot or fleet of autonomous robots that transport people, products, and / or services between specific predefined locations, at specific times, and within specific geographic boundaries, all of which are predefined. [Diagram 2] FIG. 2 is a process flow diagram illustrating aspects of a program plan used by an autonomous robot or a fleet of autonomous robots to transport people, products and / or services between specific locations, at specific times, and within specific geographic boundaries, all predefined. [Diagram 3] FIG. 3 illustrates a geospatial representation of a program plan used by an autonomous robot or a fleet of autonomous robots to transport people, products and / or services between specific locations, at specific times, and within specific geographic boundaries, all predefined. [Figure 4] FIG. 4 is a spreadsheet showing detailed steps and system parameters of a program plan for use by an autonomous robot or a fleet of autonomous robots to transport people, products and / or services between specific locations, at specific times, and within specific geographic boundaries, all predefined. [Diagram 5]FIG. 5 is a process flow diagram illustrating aspects of a program plan used by an autonomous robot or a fleet of autonomous robots to transport people, products and / or services between specific locations, at specific times, and within specific geographic boundaries, all predefined. [Figure 6] FIG. 6 is a process flow diagram illustrating management of energy and power used by an autonomous robot or a fleet of autonomous robots to transport people, products and / or services between specific locations, at specific times, and within specific geographic boundaries, all pre-defined. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] FIG. 1 illustrates a “Defined Autonomous Services Platform” (DASP) and system architecture design used to create, manage, and execute predefined programs for an autonomous robot or fleet of autonomous robots that transport people, products, and / or services between specific predefined locations, at specific times, and within specific geographic boundaries, all of which are predefined.

[0013] 100: An autonomous robot, such as a passenger vehicle, delivery vehicle, commercial truck, robotic unit, UAV, drone or other mechanical unit.

[0014] 102: Eruv is a geographic boundary (or geographic enclosure) that restricts field activities or operations only within the domain of the autonomous robot 100.

[0015] 104: Travel path identification number [i.e., 1, 2, 3, 4, 5 in FIG. 1 or 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 in FIG. 3] is a unique identifier indicating a particular travel path between a given location and another given location.

[0016] 106: A travel route corresponding to the travel route identification number 104, which is a set of roads, land transportation routes, air routes and / or sea routes planned for travel between a given location and another given location.

[0017] 108: A starting or destination point indicated by GPS location (three-dimensional {X,Y,Z}, or two-dimensional {X,Y}, Z=o) coordinates, location, or other location demarcation point, predefined within a predetermined travel route 106 and within an elve 102, which is a geographic boundary (or geographic enclosure) that restricts field activities or operations only within that area [i.e., A, B, C, D, E in Figure 1 or A, B, C, D, E, F, G, H, I, J, K, L, M, N in Figure 3].

[0018] 110: An individual who is transported between origin and destination points 108 as determined by a predetermined program.

[0019] 112: Products and / or services transported to or from the origin or destination points 108, as determined by a predetermined program.

[0020] 114: The distance (in miles or km) of the travel path 106 determined by a predetermined program, which is the length of the set of roads, land transportation routes, air routes and / or sea routes planned for traveling between origin or destination points 108 [i.e., d1, d2, d3, d4, d5 in Figure 1].

[0021] 116: The time (based on the localized time zone, i.e., US EST time zone) when traveling between the origin or destination point 108 [i.e., t1, t2, t3, t4, t5, t6 in FIG. 1], as determined by a predetermined program.

[0022] 118: “Network” is a wired and / or wireless communications system that provides communications connectivity for transmitting necessary data and / or information to one or more technical system components necessary for the successful operation of a “Defined Autonomous Services Platform” (DASP), any of its subordinate components and / or service providers.

[0023] 120: A “Service Provider” is an external entity that provides technology system components and / or services and / or data and / or information required for one or more technology system components that are required for the “Defined Autonomous Services Platform” (DASP) or required by any of its subordinate components.

[0024] 122: A "Defined Autonomous Service Platform" (DASP) is comprised of system components and / or subordinate components [described in 124, 126, 128, 130, 132, 134, 136, 138, 140, 142] and / or systems provided by a service provider 120 that manages related functions and activities that are part of a program plan to transport people, products and / or services at specific times, within specific geographic boundaries, between specific locations that are all predefined.

[0025] 124: “Operator” is an individual or group of individuals who actively programs, operates, and / or manages the “Defined Autonomous Services Platform” (DASP) 122 .

[0026] 126: “Program Policy Manager” is a subset of the “Defined Autonomous Services Platform” (DASP) 122 that may be managed by the service provider 120 and manages all system technical parameters and service guidelines of the system components and / or subordinate components [described in 124, 128, 130, 132, 134, 136, 138, 140, 142] and / or systems that the service provider 120 provides.

[0027] 128: “Travel & Motion Planning Manager” is a subset of the “Defined Autonomous Services Platform” (DASP) 122 and may be managed by the service provider 120 to define travel itineraries, travel routes, logistics and operations including travel route identification number 104, travel route 106, origin or destination points 108 to be performed during program planning within the eruv 102, which is a geographic boundary (or geographic enclosure) that restricts field activities or operations only within its area.

[0028] 130: The “Payment Manager” is a subset of the “Defined Autonomous Services Platform” (DASP) 122 that may be managed by the service provider 120 and processes pre-planned transaction payments and collected fees for services performed in a fully automated manner so as to require no end-user intervention while meeting program plan requirements. Since all payments made are made in advance, it functions to ensure strict observance without end-user intervention during specific times or periods associated with being a shomer on a Sabbath or holiday under Orthodox Judaism.

[0029] 132: The “Fleet Manager” is a subset of the “Defined Autonomous Services Platform” (DASP) 122 that may be managed by the service provider 120 and fully automatically manages the allocation, configuration, and delivery or release of autonomous robotic units or fleets of autonomous robots 100 between origin or destination points 108 within an eruv 102, which is a geographic boundary (or geographic enclosure) that restricts field activities or operations only within that area, maintenance of the units, operations performed and required during the provision of services, and authentication and operational verification, without end user intervention, to meet program plan requirements and to be a shomer for Shabbat or holidays under Orthodox Judaism.

[0030] 134: “Route Planning Manager” is a subset of “Defined Autonomous Services Platform” (DASP) 122 that may be managed by the service provider 120 and processes tactical operational planning of travel routes 106 including a set of roads, land transportation routes, air routes and / or sea routes planned to travel between predetermined locations, fully automatically, without end user intervention, while also meeting program planning requirements, with operational limitations of the eruv 102. Travel logistics within the geographic boundaries of the eruv 102 during specific times or periods associated with being a shomer for a Sabbath or holiday under Orthodox Judaism.

[0031] 136: The “Operations & Maintenance Manager” is a subset of the “Defined Autonomous Services Platform” (DASP) 122 that may be managed by the service provider 120 and fully automatically handles all operations and maintenance tasks (which may include robotic automation of tasks) without end user intervention, to meet program plan requirements, and to serve as a Shabbat or holiday shomer under Orthodox Judaism.

[0032] 138: “Energy & Power Manager” is a subset of the “Defined Autonomous Services Platform” (DASP) 122, which may be managed by the service provider 120, and provides all energy and power management, as well as fully automated control so as to require no end user intervention while meeting program plan requirements. Also, energy and power consumption limits are fully managed and are not affected by weight or volume from the operation of the autonomous robot 100 and / or services provided, if applicable, the amount of energy consumed does not change, and is powered by a rechargeable battery fuel source. Also, all power consumption management is consistently distributed and maintained regardless of use, demand, or physical weight load. Additionally, operation is managed such that no end user intervention is required and observance is possible during specific times or periods associated with being a shomer on a Sabbath or holiday under Orthodox Judaism.

[0033] 140: “User Identification & Services Manager” is a subset of the “Defined Autonomous Services Platform” (DASP) 122 that may be managed by the service provider 120 and includes all user identification and authentication (which may include facial / voice recognition, fingerprint / retina scan, and / or other methodologies) for services provided by the service provider 120 and performed fully automatically such that no end user intervention is required while meeting program plan requirements [described in 124, 126, 128, 130, 132, 134, 136, 138, 142] and / or technology required by the system, thereby functioning to adhere to, without end user intervention, during specific times or periods associated with being a shomer on a Sabbath or holiday under Orthodox Judaism.

[0034] 142: The Field Support Services Manager is a subset of the Defined Autonomous Services Platform (DASP) 122 that may be managed by the service provider 120 and automatically processes any field maintenance tasks required for operation and system components and / or subordinate components provided by the service provider 120 that are performed fully automatically so as not to require end user intervention while meeting program plan requirements [described in 124, 126, 128, 130, 132, 134, 136, 138, 140] and / or emergency support alerts required for the system, thereby functioning to adhere to, without end user intervention, during specific times or periods associated with what is to be a shomer of Shabbat or a holiday under Orthodox Judaism.

[0035] FIG. 2 is a process flow diagram illustrating aspects of a program plan used by an autonomous robot or a fleet of autonomous robots to transport people, products and / or services between specific locations, at specific times, and within specific geographic boundaries, all predefined.

[0036] 200: "Start" step is the beginning of the process of establishing a predefined program plan for the "Defined Autonomous Services Platform" (DASP) 122 to execute.

[0037] 202: The “Program Creation” step establishes a template for defining a predefined program plan to be executed by the “Defined Autonomous Services Platform” (DASP) 122 based on technical parameters and service guidelines established by the Program Policy Manager 126 and the Operations & Maintenance Manager 136 and the Field Support Services Manager 142.

[0038] 204: The “Configure Transport Equipment for Use” step is based on the transport fleet manager 132 which includes adding and configuring approved and certified autonomous robots 100 to be used for a program to transport people, products and / or services between specific predefined locations within specific geographical boundaries at specific times.

[0039] 206: “Define Movement and Motion Plan” step is the definition of movement (point) and motion plan, which is a sequence of events and other actions that occur at a given location within a given set program based on the Movement & Motion Plan Manager 128 and the Path Plan Manager 134.

[0040] 208: “Configure Energy and Power Management” step includes the configuration of all energy consumption and power management needs to comply with requirements by the Energy & Power Manager 138 .

[0041] 210: "Set up Service Users" step includes configuration of all users and payments for use in compliance with requirements by the User Identification & Service Manager 140.

[0042] 212: “Set up service payments” step involves configuration of all users and payments for use in compliance with requirements by the Payment Manager 130 .

[0043] 214: The "Program Complete?" step determines whether the program plan entry is complete and additional programming needs to be predefined, and a series of steps are performed starting with the "Set Transport Device to Use" step 204.

[0044] 216: A "Program Initiation" step establishes the program plan into the live configuration of the "Defined Autonomous Services Platform" (DASP) 122 to be executed.

[0045] 218: The "END" step is the completion of the program planning process.

[0046] FIG. 3 illustrates a geospatial representation of a program plan used by an autonomous robot or a fleet of autonomous robots to transport people, products and / or services between specific locations, at specific times, and within specific geographic boundaries, all predefined.

[0047] 300: The geographic map is a representation of the given operational area of ​​the configured program plan, including all areas defined using the configuration by the eruv 102, which are the geographic boundaries (or geographic enclosures) managed by the “Defined Autonomous Services Platform” (DASP) 122.

[0048] An Eruv, as defined in 302:102, is a geographic boundary that acts as a geographic enclosure that restricts operation only within a set area managed by a "Defined Autonomous Service Platform" (DASP) 122.

[0049] 304: Designated route from one unloading location to another, defined by travel route 106 [i.e., #306 / location B to #308 / location C in FIG. 3], is a set of roads, land transportation routes, air routes and / or sea routes planned for travel between a given location and another given location within erve 302, a geographic boundary (or geographic enclosure) that restricts field activities or operations only within that area.

[0050] 306: A designated travel route identifier [i.e., 1, 2, 3, 4, 5, 6, 7, 8 and 9 in FIG. 3] defined in the travel route identification number 104, which is a unique identifier indicating a specific travel route between a predetermined location and another predetermined location.

[0051] 308, 310, 312, 314, 316, 318, 320, 322: The current valid loading and unloading location locations [i.e., Location A, Location B, Location C, Location D, Location F, Location G, Location I and Location J in FIG. 3] using a given program defined by point 108 (origin or destination) are given locations within a travel route [i.e., A, B, C, D, E in FIG. 1] within erve 302, which is a geographic boundary (or geographic enclosure) that restricts field activities or operations only within that area.

[0052] 324: Future designated route travel routes such as designated route travel route 304 [i.e., #320 / position J to #328 / position M in FIG. 3], which are a set of roads, land transportation routes, air routes and / or sea routes planned in the future for travel between a given location and another given location.

[0053] 326: A future designated route travel path identifier such as the designated route travel path identifier 306 [that is, #320 / position J to #328 / position M in FIG. 3].

[0054] 328, 330, 332, 334, 336, 338: Locations of future loading and unloading locations defined by points 108 (start or destination) [i.e., location E, location H, location K, location L, location M and location N in FIG. 3] used for possible future predetermined programs, which are destination points indicated by a set of geographic coordinates within erve 302, which is a geographic boundary (or geographic enclosure) that restricts field activities or operations only within that area, or a location that is also a predetermined location within the travel route.

[0055] FIG. 4 is a spreadsheet showing detailed steps and system parameters of a program plan for use by an autonomous robot or a fleet of autonomous robots to transport people, products and / or services between specific locations, at specific times, and within specific geographic boundaries, all predefined.

[0056] 400: The date in the calendar year [i.e., date in Gregorian and Hebrew calendar format] on which the Defined Autonomous Services Platform (DASP) 122 executes a given program plan.

[0057] 402: Program Start Time is the start time for executing a given program plan to adhere to a Target Time to Completion [TTC] 408 [i.e., based on the localized time zone and the time of the day before Shabbat in the US EST zone], which is the predetermined scheduled time for completing the entire given program managed by the Defined Autonomous Services Platform (DASP) 122.

[0058] 404: Maximum Travel Speed ​​[MTS] is the maximum speed of travel (in miles / hour or km / hour) of the autonomous robot 100 managed by the “Defined Autonomous Services Platform” (DASP) 122.

[0059] 406: The Stoppage Time (SBT) is the time (in minutes) of stoppage following the completion of one defined travel path within a given program plan managed by the “Defined Autonomous Services Platform” (DASP) 122.

[0060] 408: Target Time to Completion [TTC] is the planned time to complete the entire given program managed by the Defined Autonomous Services Platform (DASP) 122 (i.e., the day before Sabbath in the US EST time zone).

[0061] 410: Program creation for defining a program based on technical parameters and service guidelines The template-based program itinerary of step 202 includes all travel routes [i.e., nine valid travel route IDs (412): 1, 2, 3, 4, 5, 6, 7, 8, 9 are present in FIG. 4 ] or designated travel route identifiers 306, whose operations are completed by the target time of completion [TTC] 408 managed by the “Defined Autonomous Service Platform” (DASP) 122.

[0062] 412: Travel Path ID (TPI) is a unique identifier such as a travel path identification number 104 or a designated travel path identifier 306 [i.e., 1, 2, 3, 4, 5, 6, 7, 8, or 9 in FIG. 4 ], which is a single travel path within a given program managed by the “Defined Autonomous Services Platform” (DASP) 122.

[0063] 414: Start Point ID (SPI1) is a unique identifier, such as the origin or destination point 108 or a current valid loading and unloading point location 308, 310, 312, 314, 316, 318, 320, 322, which is the starting point to a destination indicated by a set of geographic coordinates or a location, a predetermined location within a given program travel path of a single travel path, such as within a program leg 410 [i.e., A, B, C, D, F, G, J, I in FIG. 4].

[0064] 416: Stop Point ID (SPI2) is a unique identifier, such as an origin or destination point 108 or a current valid loading / unloading point location 308, 310, 312, 314, 316, 318, 320, 322, a stop point at a destination indicated by a set of geographic coordinates or a location, a predetermined location within a travel path [i.e., A, B, C, D, F, G, J, I in FIG. 4], such as within a program leg 410.

[0065] 418: Travel Start Time (TST) is the start time (based on a localized time zone, i.e., US EST time zone) of the single travel path and program leg 410 from the starting point ID (SPI1) 414.

[0066] 420: Total Route Distance (TPD) is the total route distance (in miles or km) of a single travel route, such as travel route ID (TPI) 412, for example within a program leg 410.

[0067] 422: Cumulative Path Distance (CPD) is the cumulative path distance (in miles or km) from the start of a single travel path within a given program plan, calculated by adding up all completed travel paths, such as the associated total path distance 420, within a program leg 410.

[0068] 424: Actual Travel Time (ATI) is the total time (i.e., in minutes) that elapses from the start of a single movement path within a given program, and may be affected by Maximum Travel Speed ​​[MTS] 404, which is the maximum speed (in miles / hour or km / hour) of movement of the autonomous robot, for example, within a program leg 410.

[0069] 426: Actual Accumulative Travel Time (ACTT) is the sum of the actual elapsed accumulated travel time [i.e., in minutes], determined, for example, by adding up all the time elapsed during the Actual Travel Time (ATT) 424 [i.e., in minutes] of the completed travel path within the program leg 410.

[0070] 428: Travel Stop Time (TST2) is the time (i.e., based on the localized time zone, US EST time zone) upon arrival at a destination point within a given program, such as within a program leg 410, and can be calculated as TST2=(TST+ATT / (24*60).

[0071] 430: Type of processing operation, for example, an operation that is completed during a travel stop time in the program leg 410 [ie, loading / unloading passengers=users, loading / unloading baggage=items, etc.].

[0072] 432: Planned Downtime (PSBT) is the total time [i.e., in minutes] of downtime, including interruptions to operations and other scheduled times, occurring during a period such as within a program run 410.

[0073] 434: Travel Completion Time (TCT2) is the time (i.e., based on a localized time zone, US EST time zone) when the Planned Stoppage Time (PSBT) 432 is completed, such as within the program leg 410.

[0074] 436: Total Cumulative Time (TCT) is the cumulative time [ie, in minutes] for an entire travel path to be completed, such as within a program leg 410.

[0075] FIG. 5 is a process flow diagram illustrating aspects of a program plan used by an autonomous robot or a fleet of autonomous robots to transport people, products and / or services between specific locations, at specific times, and within specific geographic boundaries, all predefined.

[0076] 500: The “Start” step initiates the “Defined Autonomous Services Platform” (DASP) 122 and the program launch step 216 which is executed based on the calendar date 400 , the program start time 402 and the program itinerary 410 .

[0077] 502: The "Assign Transport Device" step initiates the transport device fleet manager 132 to assign an autonomous robot or fleet of autonomous robots 100 as a transport device, thereby delivering the transport device unit from its storage location or other predetermined location, such as a program run 410 indicated by a predetermined program, to a starting point 108 (origin or destination).

[0078] 504: “Execute Prescribed Program” step starts the process, where the prescribed program starts the assigned subordinate components Movement & Motion Planning Manager 128, Route Planning Manager 134, Energy & Power Manager 138, User Identification & Service Manager 140, Payment Manager 130, Operation & Maintenance Manager 136, Field Support Services Manager 142, and the program run 410 is executed including all the travel routes [i.e., nine travel routes with IDs: 1, 2, 3, 4, 5, 6, 7, 8, 9 are present in FIG. 4 ] and the operation is completed by the target time to completion [TTC] 408 of the prescribed program.

[0079] 506: In a "path movement" step, the execution of a predetermined program step 504 and its subordinate components initiate the autonomous robot 100, which is a transport device, to move along a path from a start point to a destination point defined by a travel path 106, which is a set of roads, land transportation routes, air routes and / or sea routes planned for traveling between a predetermined location and another predetermined location, such as a program itinerary 410 indicated by the predetermined program.

[0080] 508: In the “arrive at travel point” step, the execution step 504 of the predetermined program and its subordinate components initiate the autonomous robot 100, which is a transport device, to establish arrival at the destination point, stop point ID (SPI2) 416, such as the program itinerary 410 indicated by the predetermined program.

[0081] 510: In the "Process Actions" step, the execution of the predetermined program step 504 and its subordinate components initiate the autonomous robot 100 which is a transport device to process an action or set of actions to be completed for each type of processing action 430 indicated by the predetermined program and executed during the stop time, e.g., actions completed during the travel stop time in the program itinerary 410 [i.e., loading and unloading passengers = users, loading and unloading luggage = items, etc.].

[0082] 512: In the "Move Complete?" step, the Execute Predefined Program step 504 and its subordinate components determine whether the predefined program is complete and if so, proceeds to the next step 514, otherwise proceeds to 506 to continue the predefined program.

[0083] 514: In a “return transport device” step, the transport device fleet manager 132 launches the transport device, an autonomous robot or fleet of autonomous robots 100, to move it from its current location to another predetermined location indicated by the “defined autonomous service platform” (DASP) 122.

[0084] 516: In the "End" step, the "Defined Autonomous Services Platform" (DASP) 122 and its subordinate components complete the given program execution process.

[0085] FIG. 6 is a process flow diagram illustrating management of energy and power used by an autonomous robot or a fleet of autonomous robots to transport people, products and / or services between specific locations, at specific times, and within specific geographic boundaries, all pre-defined.

[0086] 600: The “Start” step begins with the “Defined Autonomous Services Platform” (DASP) 122 .

[0087] 602: “Execute Predetermined Program” step starts the process, where the predetermined program is loaded for execution based on the execute predetermined program step 504, and the program run 410 is executed including all the travel routes [i.e., there are nine travel routes in FIG. 4 with IDs: 1, 2, 3, 4, 5, 6, 7, 8, 9], and the operation is completed by the target time to completion [TTC] 408 of the predetermined program.

[0088] 604: In the "Configure Energy and Power Management Settings" step, a predetermined program is executed for each subset of the Energy & Power Manager 138 and the Energy and Power Management Configuration step 208.

[0089] 606: In the “Perform Energy and Power Configuration Measurements” step, all necessary measurement readings are performed from the autonomous robot or fleet of autonomous robotic units established in the control cycle defined by the Program Policy Manager 126 and the Energy & Power Manager 138.

[0090] 608: In the “Re-adjust Energy and Power Configuration Settings” step, all energy and power adjustments to the operation of the autonomous robot or fleet of autonomous robotic units established by the Program Policy Manager 126 and the Energy & Power Manager 138 are implemented.

[0091] 610: In the “Move Complete?” step, the Execute Predefined Program step 602 determines whether the predefined program is complete and if so proceeds to End step 612, otherwise proceeds to Perform Energy and Power Configuration Measurements step 606 to continue executing the predefined program.

[0092] At 612: "End" step, the "Defined Autonomous Services Platform" (DASP) 122 completes the given program execution process.

Claims

1. 1. A system comprising: The system comprises at least one of a processor, computer readable instructions, a geographical map representation, a geographical boundary (or geographical enclosure), a network connection, and an autonomous robot that upon initiation and execution enables the transportation of people and / or products and / or services at a particular time between specific predefined locations within a particular geographical boundary, whereby the effective energy and power management does not involve any user intervention, and is all managed by the system ["Defined Autonomous Services Platform" (DASP)] and / or a service provider [an external entity that provides data and / or information required for technical system components and / or services, and / or one or more technical system components required by said "Defined Autonomous Services Platform" (DASP) or required by any of its subordinate components]. system.

2. A Program Policy Manager (Autonomy) manages the system technical parameters and service guidelines for all given programs of system components and / or subordinate components, and an Operator is an individual or group of individuals who actively programs, operates, and / or manages the Defined Autonomous Service Platform (DASP). The method of claim 1.

3. A mobility & motion planning manager (mobility management) defines the travel itinerary, travel routes, logistics and operations of said given program to be carried out during program planning, carried out within a geographical boundary (or geographical enclosure) that restricts field activities or operations only within a defined area. The method of claim 2.

4. A fleet manager manages the allocation, configuration, and delivery or release of autonomous robotic units or fleets of autonomous robots between origin or destination locations within said geographic boundary (or said geographic enclosure) that limits field activities or operations only within said area, the maintenance of units, and operations performed during servicing. The method of claim 2.

5. A route planning manager processes tactical operational planning of travel routes including a set of roads, land transportation routes, air routes and / or sea routes planned to travel between predetermined locations within a geographic region fully automatically, subject to operational constraints, without end user intervention and while still meeting program planning requirements. The method of claim 2.

6. A User Identification & Service Manager includes all user identification and authentication (which may include face / voice recognition, fingerprint / retina scan, and / or other methodologies) for any or all services provided via the technology required by said system components and / or said subordinate components, which is performed completely automatically so as to require no intervention by said end user while meeting the requirements of said program plan, thereby functioning so as to require no intervention by said end user. The method of claim 2.

7. A settlement manager processes settlements or collected fees for pre-scheduled transactional activities for pre-executed services in a fully automated manner so as to meet the requirements of the program plan and without the need for end user intervention. The method of claim 2.

8. An Energy & Power Manager (Power Management) not only provides all energy and power management, but also controls it fully automatically so as not to require intervention from the end user while meeting the requirements of the program plan, energy and power consumption limits are not affected by weight or volume from the operation of the autonomous robotic unit and / or services provided, the amount of energy consumed does not change, all power is generated by a rechargeable battery fuel source, and all power consumption management is maintained consistently regardless of usage, demand, or physical weight load, and further, operation is managed to meet the requirements of the program plan without the need for intervention from the end user. The method of claim 2.

9. An operations & maintenance manager handles all operations and maintenance tasks of the autonomous robot or fleet of autonomous robots (which may include automating tasks by the robots) completely automatically, without the need for intervention by the end user, to meet the requirements of the program plan. The method of claim 2.

10. a field support service manager automatically processes any field maintenance tasks required for operation of the autonomous robot or fleet of autonomous robots and any immediate or emergency support alerts required for the system components and / or subordinate components, which are performed fully automatically so as not to require intervention of the end user while meeting requirements of the program plan; The method of claim 2.

Images