Methods and systems for predefined autonomous services

Abstract

This invention provides a method and system used to provide autonomous on-demand services for transporting people, products, and / or services at specific times between specific locations predefined within a specific geographical boundary. [Solution] A predefined autonomous service platform (DASP) creates, manages, and executes pre-planned programs so that an autonomous robot or group of autonomous robots, consisting of one or more passenger cars, delivery vehicles, commercial trucks, robotic units, UAVs, drones, or other mechanical units, can travel along predetermined routes on land and / or in the air and / or at sea within a geographical boundary, can perform defined tasks or sets of defined tasks fully automatically, without requiring end-user intervention, in accordance with the religious use cases of the person acting as the showman, and in accordance with the guidelines of observing the Sabbath or holidays under Orthodox Judaism.

Description

[[Technical Field]]

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

[0002] Embodiments of the present invention comprise methods and systems used for providing self-functioning autonomous services via a "Defined Autonomous Service Platform" (DASP) that enables transportation of people, products and / or services between specific locations, at specific times, within specific geographic boundaries, wherein effective energy and power management is all predefined and performed fully automatically without requiring end user intervention, thereby enabling methods related to, for example, religiously specific use cases in accordance with Judaism. Adherence to being a "Shomer (observer)", observing the Sabbath (also known as Shabbos in Yiddish, or Shabbat in Hebrew), and observing Jewish holidays as set forth in the Torah, is a standard of orthodox practice, and has advantages and legal ramifications for the manner of being a Jew as understood by religious courts regarding faith in Judaism. Being a Shomer means observing the mitzvot, performing certain obligations, refraining from certain activities of creation or creative acts (known as forms of melacha), and includes restrictions on the transportation of objects and / or movement of objects from private property to public property (domains) during certain time periods of the day, such as from dawn (or sunrise) to sunset (or dusk) on specific days, similar to the observance of the weekly Sabbath. Furthermore, even under Halacha (Jewish law), there are other areas of activity prohibited on the Sabbath, many of which are also restricted on Jewish holidays.

[0003] Embodiments of the present invention relate to transportation and other related services that have traditionally been considered prohibited activities for individuals to become Sabbath and holiday Sabbath attendants, and the “Predefined Autonomous Service Platform” (DASP) conducts various architectural design studies to ensure adherence to general guidelines for individuals to become Sabbath and holiday Sabbath attendants.

[0004] The traditional "Schomer" problems that will be addressed include the following:

[0005] I. Autonomy: The “Predefined Autonomous Service Platform” (DASP) enables the creation, management, and execution of predetermined programs (or sets thereof) so that autonomous robots or groups of autonomous robotic units can travel along predetermined paths on land and / or in the air and / or at sea within geographical boundaries and perform predetermined tasks (or sets thereof) completely automatically without requiring end-user intervention. Furthermore, the predefined autonomous programs consist of functions such as scheduling, availability, routing, energy management, user identification, payment services, service verification and approval, maintenance, and field support services, with other automation of robotic business processes handled by interconnected service providers.

[0006] II. Mobility Management: The “Predefined Autonomous Service Platform” (DASP) enables the ability to restrict the movement of autonomous robots or swarms of autonomous robotic units moving on land and / or in the air and / or at sea within a geographical boundary “Eruv” (or geographical enclosure) which, when defined, consolidates numerous private and public geographical areas into one vast private property.

[0007] III. Energy & Power Management: “Predefined Autonomous Service Platform” (DASP): 1. A group of autonomous robots or autonomous robotic units operating on a battery-powered system, utilizing solid-state electronic components to automatically manage the positioning, operation, movement, control, maintenance, and safety functions of the units, while conventional automotive units utilize power engines that consume and / or burn gasoline or gasoline-based fuels. 2. A predetermined program (or set of programs) is fully planned and managed in advance, power and energy are distributed, the voltage, current and resistance of the power supply are actively managed without creating, opening or closing electrical circuits, and energy requirements are consistently maintained regardless of use, demand or physical weight load. [Overview of the project]

[0008] Embodiments of the present invention consist of methods and systems that enable an autonomous robot or a group of autonomous robots to function during specific times or periods associated with being a Shoma on the Sabbath or a holiday under Orthodox Judaism, without requiring end-user intervention, and in strict adherence to prohibitions against certain creative activities (known as forms of Melah).

[0009] A “Predefined Autonomous Service Platform” (DASP) enables the transport of people, products, and / or services between specific locations, at specific times, and within specific geographical boundaries, and the described functions include thorough pre-planning, execution, and management of a predetermined program for autonomous robots (or swarms of autonomous robots), which may consist of passenger cars, delivery vehicles, commercial trucks, robotic units, UAVs, and / or unmanned aerial vehicles.

[0010] Furthermore, the predefined programs are fully comprised of functions such as scheduling, availability, routing, energy use and power consumption, service verification and authorization, user identification, payment services, service maintenance, or field support services, and are connected to a network of wired and / or wireless communication systems that enable the operation, support, and effective management of various elements necessary for the operation and provision of the “Predefined Autonomous Service Platform” (DASP), and interconnected with service providers. [Brief explanation of the drawing]

[0011] [Figure 1] Figure 1 shows a "Predefined Autonomous Service Platform" (DASP) and its system architecture design, which is used to create, manage, and execute predetermined programs for autonomous robots or groups of autonomous robots that transport people, products, and / or services between specific, predefined locations, at specific times, and within specific geographical boundaries. [Figure 2] Figure 2 is a processing flow diagram illustrating a model of a program plan used by an autonomous robot or a group of autonomous robots to transport people, products, and / or services within specific geographical boundaries, at specific times, and all within predefined locations. [Figure 3] Figure 3 shows a geospatial representation of a program plan used by an autonomous robot or a group of autonomous robots to transport people, products, and / or services within specific geographical boundaries, at specific times, and all within predefined locations. [Figure 4] Figure 4 is a summary table showing detailed steps and system parameters of a program plan for use by an autonomous robot or a group of autonomous robots to transport people, products, and / or services within specific geographical boundaries, at specific times, and all within predefined locations. [Figure 5]Figure 5 is a processing flow diagram illustrating a model of a program plan used by an autonomous robot or a group of autonomous robots to transport people, products, and / or services within specific geographical boundaries, at specific times, and all within predefined locations. [Figure 6] Figure 6 is a process flow diagram illustrating the management of energy and power used by autonomous robots or groups of autonomous robots to transport people, products, and / or services within specific geographical boundaries, at specific times, and all within predefined locations. [Modes for carrying out the invention]

[0012] Figure 1 shows a "Predefined Autonomous Service Platform" (DASP) and its system architecture design, which is used to create, manage, and execute predetermined programs for autonomous robots or groups of autonomous robots that transport people, products, and / or services between specific, predefined locations, at specific times, and within specific geographical boundaries.

[0013] 100: Autonomous robots such as passenger cars, delivery vehicles, commercial trucks, robotic units, UAVs, unmanned aerial vehicles, or other mechanical units.

[0014] 102: Eruv is a geographical boundary (or geographical enclosure) that restricts field activities or movements to only within the area of ​​the autonomous robot 100.

[0015] 104: A travel path identification number [i.e., 1, 2, 3, 4, 5 in Figure 1 or 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 in Figure 3] is a unique identifier that indicates a specific travel path between one given location and another given location.

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

[0017] 108: A starting point or destination point indicated by predefined GPS position (three-dimensional {X,Y,Z}, or two-dimensional {X,Y}, Z=0) coordinates, location, or other position fixed points within a geofence 102 which is a geographical boundary (or geographical enclosure) that limits on-site activities or operations only within and inside the predetermined movement route 106 [that is, A, B, C, D, E in FIG. 1, or A, B, C, D, E, F, G, H, I, J, K, L, M, N in FIG. 3].

[0018] 110: An individual who is mutually transported between starting points or destination points 108 determined by a predetermined program.

[0019] 112: Products and / or services that are mutually transported between starting points or destination points 108 determined by a predetermined program.

[0020] 114: The distance (in miles or kilometers) of the movement route 106 determined by a predetermined program, which is the length of a set of roads, land transport routes, air routes and / or sea lanes planned for mutual movement between starting points or destination points 108 [that is, d1, d2, d3, d4, d5 in FIG. 1].

[0021] 116: The time (based on a localized time zone, that is, the US EST zone) for travel between starting points or destination points 108 determined by a predetermined program [that is, t1, t2, t3, t4, t5, t6 in FIG. 1].

[0022] 118: A "network" is a wired and / or wireless communication system that provides communication connectivity for transmitting data and / or information required for one or more technical system components necessary for the normal operation of a "Defined Autonomous Service Platform" (DASP), any of its dependent components and / or service providers.

[0023] 120: "Service Provider" means an external entity that provides data and / or information required for technical system components and / or services, and / or required by the "Defined Autonomous Service Platform" (DASP) or for one or more technical system components required by any dependent component thereof.

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

[0025] 124: "Operator" means an individual or group of individuals that actively programs, operates, and / or manages the "Defined Autonomous Service Platform" (DASP) 122.

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

[0027] 128: The “Movement & Action Planning Manager” is a subset of the “Predefined Autonomous Service Platform” (DASP) 122, which may be managed by a service provider 120, and defines the travel itinerary, travel route, logistics and actions, including a travel route identification number 104, a travel route 106, and a departure or destination point 108, to be implemented during program planning within an ELVE 102, which is a geographical boundary (or geographical enclosure) that restricts field activities or actions to only within its area.

[0028] 130: The “Settlement Manager” is a subset of the “Predefined Autonomous Service Platform” (DASP) 122, which may be managed by the service provider 120, and handles pre-planned transaction settlements and fees to be collected for a service that runs fully automatically without requiring end-user intervention, while meeting the requirements of the program plan. All settlements to be made are made in advance, so that it functions to be strictly observed without requiring end-user intervention during certain times or periods related to being a Shoma on the Sabbath or a public holiday under Orthodox Judaism.

[0029] 132: The "Transportation Equipment Group Manager" is a subset of the "Predefined Autonomous Service Platform" (DASP) 122, which may be managed by a service provider 120, and fully automatically manages, without end-user intervention, the allocation, configuration, delivery or release of autonomous robot units or groups of autonomous robots 100 between a departure point or destination point 108 within an Elb 102, which is a geographical boundary (or geographical enclosure) that restricts field activities or operations to within its area only, the maintenance of units, the operations performed during the provision of services, and the authentication and operational verification, to meet the requirements of the program plan and to be a shoma under Orthodox Judaism.

[0030] 134: The “Route Planning Manager” is a subset of the “Predefined Autonomous Service Platform” (DASP) 122, which may be managed by a service provider 120, and fully automatically handles the tactical operational planning of travel routes 106, including a set of roads, land routes, air routes and / or sea routes planned for travel between given locations, without requiring end-user intervention and also meeting program planning requirements, subject to the operational limitations of the Elb 102. Travel logistics within the geographical boundaries of the Elb 102 during a specific time or period are related to becoming a shoma on a Sabbath or holiday under Orthodox Judaism.

[0031] 136: The “Operations & Maintenance Manager” is a subset of the “Predefined Autonomous Service Platform” (DASP) 122, which may be managed by a service provider 120, and which handles all operations and maintenance tasks (including the automation of task processing by robots) fully automatically, without requiring end-user intervention, meeting the requirements of the program plan, and acting as a shoma on a Sabbath or holiday under Orthodox Judaism.

[0032] 138: The “Energy & Power Manager” is a subset of the “Predefined Autonomous Service Platform” (DASP) 122, which may be managed by the service provider 120, and not only provides management of all energy and power, but also controls it fully automatically without requiring end-user intervention while meeting the requirements of the program plan. Energy and power consumption limits are fully managed and are not affected by the weight or volume from the operation of the autonomous robot 100 and / or the services provided, and where applicable, the amount of energy consumed does not change and is powered by a rechargeable battery fuel source. All power consumption management is also consistently distributed and maintained regardless of use, demand or physical weight load. Furthermore, operation is managed so that it can be strictly observed without requiring end-user intervention during certain times or periods related to being a Sabbath or holiday shoma under Orthodox Judaism.

[0033] 140: The “User Identification & Service Manager” is a subset of the “Predefined Autonomous Service Platform” (DASP) 122, which may be managed by and provided by the Service Provider 120, and which includes all user identification and authentication (which may include facial / voice recognition, fingerprint / retinal scanning, and / or other methodologies) of services provided through the technologies required by the System and / or system components [as described in 124, 126, 128, 130, 132, 134, 136, 138, 142] and / or the technologies required by the System, which are implemented fully automatically without requiring end-user intervention while meeting the requirements of the Program Plan, thereby functioning to ensure strict adherence to certain times or periods related to being a Shoma on the Sabbath or holiday under Orthodox Judaism, without requiring end-user intervention.

[0034] 142: The Field Support Service Manager is a subset of the “Predefined Autonomous Service Platform” (DASP) 122, which may be managed by the Service Provider 120, and automatically handles any field maintenance tasks necessary for operation, and system components and / or dependent components [as described in 124, 126, 128, 130, 132, 134, 136, 138, 140] and / or emergency support alerts required by the system, which are provided by the Service Provider 120 and are performed fully automatically without requiring end-user intervention, in order to meet the requirements of the program plan, thereby functioning to ensure strict adherence to certain times or periods related to being a Sabbath or holiday shoma under Orthodox Judaism, without requiring end-user intervention.

[0035] Figure 2 is a processing flow diagram illustrating a model of a program plan used by an autonomous robot or a group of autonomous robots to transport people, products, and / or services within specific geographical boundaries, at specific times, and all within predefined locations.

[0036] 200: The “start” step is the beginning of the process of establishing a predetermined program plan to be executed by the “predefined autonomous service platform” (DASP) 122.

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

[0038] 204: The “Setting up the transport equipment to be used” step is based on a transport equipment group manager 132, which includes adding and configuring approved and certified autonomous robots 100 to be used in a program to transport people, products and / or services between specific locations predefined within a specific geographical boundary at a specific time.

[0039] 206: The “Defining Movement and Action Plans” step is the definition of movement (points) and action plans, which are a series of events and other actions that occur at predetermined locations within a predetermined configuration program based on the Movement & Action Plan Manager 128 and the Route Plan Manager 134.

[0040] 208: The “Configuration of Energy and Power Management” step includes the configuration of all energy consumption, and power management must comply with the requirements of Energy & Power Manager 138.

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

[0042] 212: The “Set up service payments” step includes all user and payment configurations for use in compliance with the requirements of Payment Manager 130.

[0043] 214: The "Program Complete?" step determines whether the program plan input is complete and any additional programming needs to be predefined, and a series of steps are executed first, starting from the "Setting Up the Transport Equipment to Use" step 204.

[0044] 216: The “Program Activation” step establishes the program plan in the live configuration of the “Predefined Autonomous Service Platform” (DASP) 122 that will be executed.

[0045] 218: The "Finish" step signifies the completion of the program plan creation process.

[0046] Figure 3 shows a geospatial representation of a program plan used by an autonomous robot or a group of autonomous robots to transport people, products, and / or services within specific geographical boundaries, at specific times, and all within predefined locations.

[0047] 300: The geographic map is a representation of a given operational area of ​​a configuration program plan, including all areas defined using the configuration by ELVE 102, which is a geographic boundary (or geographic enclosure) managed by the “Predefined Autonomous Service Platform” (DASP) 122.

[0048] The ELVE as defined in 302:102 is a geographical boundary that functions as a geographical enclosure that restricts operation to only within a configuration area managed by the “Predefined Autonomous Service Platform” (DASP)122.

[0049] 304: A designated route travel path from one loading / unloading site to another, defined by the travel path 106 [i.e., #306 / location B to #308 / location C in Figure 3], is a set of roads, land transport routes, air routes and / or sea routes planned for travel between one designated site and another within Elb 302, which is a geographical boundary (or geographical enclosure) that restricts field activities or operations to within that area only.

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

[0051] 308, 310, 312, 314, 316, 318, 320, 322: The current valid loading / unloading location using a predetermined program, defined by point 108 (origin or destination) [i.e., locations A, B, C, D, F, G, I, and J in Figure 3], is a predetermined location within a travel path within Elb 302 [i.e., A, B, C, D, E in Figure 1], which is a geographical boundary (or geographical enclosure) that restricts field activities or movements to within that area only.

[0052] 324: A future designated route, such as designated route 304 [i.e., #320 / location J to #328 / location M in Figure 3], which is a set of roads, land transport routes, air routes and / or sea routes planned in the future for travel between one designated location and another designated location.

[0053] 326: This is a future designated route travel identifier such as designated route travel identifier 306 [i.e., #320 / location J to #328 / location M in Figure 3].

[0054] 328, 330, 332, 334, 336, 338: Locations of future loading / unloading sites defined by point 108 (origin or destination) [i.e., locations E, H, K, L, M, and N in Figure 3] used in a predetermined future program, and destination locations indicated by a set of geographic coordinates within the ELBE 302, which is a geographical boundary (or geographical enclosure) that restricts field activities or operations to that area only, or locations that are predetermined places in the travel route.

[0055] Figure 4 is a summary table showing detailed steps and system parameters of a program plan for use by an autonomous robot or a group of autonomous robots to transport people, products, and / or services within specific geographical boundaries, at specific times, and all within predefined locations.

[0056] 400: The date in the calendar year [i.e., a date in the form of the Gregorian and Hebrew calendars] on which the “Predefined Autonomous Service Platform” (DASP) 122 executes a given program plan.

[0057] 402: Program start time is the start time to execute a given program plan in order to adhere to a predetermined time to complete [TTC] 408, which is a predetermined scheduled time to complete a given entire program managed by the “Predefined Autonomous Service Platform” (DASP) 122 [i.e., based on localized time zones and the time of the day before the Sabbath in the U.S. EST zones].

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

[0059] 406: Stop-Break Time (SBT) is the time (in minutes) that a system is stopped following the completion of a defined travel path within a given program plan, managed by a Predefined Autonomous Service Platform (DASP) 122.

[0060] 408: The target completion time [TTC] is the time (i.e., the day before the Sabbath in the US EST time zone) that is scheduled to be completed by the “Predefined Autonomous Service Platform” (DASP) 122.

[0061] 410: The program process based on the template of program creation step 202 for defining the program based on technical parameters and service guidelines includes all travel routes [i.e., nine valid travel route IDs (412): 1, 2, 3, 4, 5, 6, 7, 8, 9 present in Figure 4], or designated route travel route identifiers 306, and its operation is completed by a target completion time [TTC] 408 managed by the "Predefined Autonomous Service Platform" (DASP) 122.

[0062] 412: The Travel Path ID (TPI) is a unique identifier such as the Travel Path Identification Number 104 or the Designated Travel Path Identifier 306 [i.e., 1, 2, 3, 4, 5, 6, 7, 8, or 9 in Figure 4], and is a single travel path within a given program managed by the “Predefined Autonomous Service Platform” (DASP) 122.

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

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

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

[0066] 420: Total Path Distance (TPD) is the total path distance (in miles or kilometers) of a single travel path, such as travel path ID (TPI) 412, within a program journey 410.

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

[0068] 424: Actual travel time (ATI) is the total time (i.e., in minutes) elapsed from the start of a single travel path within a given program, and may be affected by the maximum travel speed [MTS] 404, which is the maximum speed (in miles / hour or kilometers / hour) of the autonomous robot's movement within, for example, a program step 410.

[0069] 426: Actual cumulative travel time (ACTT) is the sum of the actual elapsed cumulative travel time [i.e., in minutes], and is determined, for example, by adding up all the time that has elapsed during the actual travel time (ATT) 424 [i.e., in minutes] of the completed travel route within program step 410.

[0070] 428: The time taken to stop moving (TST2) is the time taken when arriving at the destination within a given program, such as within program itinerary 410 (i.e., based on the localized time zone, the US EST zone), and can be calculated as follows: TST2 = (TST + ATT / (24 * 60).

[0071] 430: The type of processing operation is, for example, an operation that is completed during the stop time in program step 410 [i.e., loading and unloading of passengers = users, loading and unloading of luggage = goods, etc.].

[0072] 432: Scheduled Stop and Break Time (PSBT) is the total time of stop and break [i.e., in minutes] that includes the time of operational interruptions and other scheduled interruptions that occur during a period such as within program stroke 410.

[0073] 434: The time to complete the journey (TCT2) is the time when the scheduled stop-and-break time (PSBT) 432 is completed within the program step 410, etc. (i.e., based on the localized time zone, the US EST zone).

[0074] 436: Total Cumulative Time (TCT) is the cumulative time [i.e., in minutes] it takes for the entire travel path to be completed within program step 410, etc.

[0075] Figure 5 is a processing flow diagram illustrating a model of a program plan used by an autonomous robot or a group of autonomous robots to transport people, products, and / or services within specific geographical boundaries, at specific times, and all within predefined locations.

[0076] 500: The "Start" step initiates the "Predefined Autonomous Service Platform" (DASP) 122 and the program startup step 216, which is performed based on the calendar year date 400, the program start time 402, and the program process 410.

[0077] 502: The "Transportation Device Assignment" step involves activating the Transportation Device Group Manager 132 to assign the autonomous robot or group of autonomous robots 100, which are transport devices, thereby delivering the transport device unit from its storage location or other predetermined location, such as a program step 410 indicated by a predetermined program, to the starting point 108 (origin or destination).

[0078] 504: The “Execute a Predetermined Program” step initiates processing, in which the predetermined program starts its assigned dependent components, namely the Movement & Operation Planning Manager 128, Route Planning Manager 134, Energy & Power Manager 138, User Identification & Service Manager 140, Settlement Manager 130, Operation & Maintenance Manager 136, and Field Support Service Manager 142. The program process 410 is executed, including all movement routes [i.e., nine movement routes with IDs 1, 2, 3, 4, 5, 6, 7, 8, and 9 exist in Figure 4], and its operation is completed by the predetermined program’s target completion time [TTC] 408.

[0079] 506: In the “path travel” step, the execution step 504 of a predetermined program and its dependent components activate an autonomous robot 100, which is a transport device, to travel along a path from a starting point to a destination point, which is defined by a travel path 106, which is a set of roads, land transport routes, air routes and / or sea routes planned to travel between one predetermined location and another predetermined location, such as a program journey 410 indicated by the predetermined program.

[0080] 508: In the “Arrival at destination” step, the execution step 504 of a predetermined program and its dependent components activate the autonomous robot 100, which is a transport device, to establish that it will arrive at the destination destination, stop point ID (SPI2) 416, such as the program path 410 indicated by the predetermined program.

[0081] 510: In the “processing of actions” step, the execution step 504 of a predetermined program and its dependent components activate the autonomous robot 100, which is a transport device, to process an action or set of actions so as to be completed for each type 430 of processing actions, which are actions indicated by the predetermined program and performed during stop times, for example, during a movement stop time in a program step 410 [i.e., loading and unloading passengers = users, loading and unloading luggage = goods, etc.].

[0082] 512: In the "Movement complete?" step, the execution step 504 of the predetermined program and its dependent components determine whether the predetermined program has completed. If it has completed, proceed to the next step 514; otherwise, proceed to 506 to continue the predetermined program.

[0083] 514: In the “Return of Transport Device” step, the transport device group manager 132 activates the transport device, which is an autonomous robot or a group of autonomous robots 100, to move it from its current location to another predetermined location indicated by the “Predefined Autonomous Service Platform” (DASP) 122.

[0084] 516: In the "Termination" step, the "Predefined Autonomous Service Platform" (DASP) 122 and its dependent components complete a predetermined program execution process.

[0085] Figure 6 is a process flow diagram illustrating the management of energy and power used by autonomous robots or groups of autonomous robots to transport people, products, and / or services within specific geographical boundaries, at specific times, and all within predefined locations.

[0086] 600: The "Getting Started" step begins with the "Predefined Autonomous Service Platform" (DASP) 122.

[0087] 602: The “Execute a Predetermined Program” step initiates processing, where the predetermined program is loaded to be executed based on the Execute a Predetermined Program step 504, and the program process 410 is executed including all travel paths [i.e., nine travel paths with IDs 1, 2, 3, 4, 5, 6, 7, 8, and 9 exist in Figure 4], and its operation is completed by the target completion time [TTC] 408 of the predetermined program.

[0088] 604: The “Setting Energy and Power Management Settings” step executes a predetermined program for each subset of Energy & Power Manager 138 and Energy & Power Management Configuration Step 208.

[0089] 606: The “Perform Energy and Power Configuration Measurements” step performs the reading of all necessary measurements from the group of autonomous robots or autonomous robot units established in the control cycle defined by the program policy manager 126 and the energy and power manager 138.

[0090] 608: The “Readjust Energy and Power Configuration Settings” step performs all energy and power adjustments for the operation of the autonomous robot or group of autonomous robot units established by the Program Policy Manager 126 and the Energy & Power Manager 138.

[0091] 610: In the "Movement complete?" step, the execution step 602 of the predetermined program determines whether the predetermined program has been completed. If it has been completed, the process proceeds to the termination step 612. If it has not been completed, the process proceeds to the energy and power configuration measurement step 606 to continue the execution of the predetermined program.

[0092] 612: In the "Termination" step, the "Predefined Autonomous Service Platform" (DASP) 122 completes the predetermined program execution process.

Claims

1. It is a system, The system comprises a processor, computer-readable instructions, geographical map representations, geographical boundaries (or geographical enclosures), network connectivity, and at least one autonomous robot capable of transporting people and / or products and / or services at specific times between specific locations predefined within specific geographical boundaries, with effective energy and power management being conducted without any user intervention, thereby entirely managed by the system ["Predefined Autonomous Service Platform" (DASP)] and / or service providers [technical system components and / or services, and / or external entities providing data and / or information required for one or more technical system components required by the "Predefined Autonomous Service Platform" (DASP) or any of its dependent components]. system.

2. The Program Policy Manager (autonomy) manages the system technical parameters and service guidelines for all predetermined programs of the system components and / or dependent components, and the Operator is an individual or group of individuals who actively programs, operates, and / or manages the “Predefined Autonomous Service Platform” (DASP). The method according to claim 1.

3. A mobility and movement planning manager (mobility management) defines the movement routes, routes, logistics, and movements of a given program, which are performed within a geographical boundary (or geographical enclosure) that restricts field activities or movements to within a defined area, and which are carried out during program planning. The method according to claim 2.

4. The transport equipment group manager manages the allocation and configuration of autonomous robot units or groups of autonomous robots, the delivery or release of units between origin and destination points within the geographical boundary (or geographical enclosure) that restricts field activities or operations to within the said area, the maintenance of units, and the operations performed during service provision. The method according to claim 2.

5. The route planning manager fully automatically processes tactical operational plans for travel routes, including sets of roads, land transport routes, air routes, and / or sea routes, planned for travel between designated locations within a geographical area, without requiring end-user intervention, despite operational limitations, and while also meeting program planning requirements. The method according to claim 2.

6. The User Identification & Service Manager includes all user identification and user authentication (which may include facial / voice recognition, fingerprint / retinal scanning, and / or other methodologies) for any or all services provided through the necessary technologies of the system components and / or dependent components, which are performed fully automatically in a manner that does not require the intervention of the end user while meeting the requirements of the program plan, and thereby function without requiring the intervention of the end user. The method according to claim 2.

7. The settlement manager processes the settlement or collection of fees for pre-planned transaction activities for pre-executed services that are fully automated and pre-executed, without requiring any intervention from the end user, while meeting the requirements of the program plan. The method according to claim 2.

8. The Energy & Power Manager (Power Management) not only provides management of all energy and power, but also controls it fully automatically without requiring end-user intervention while meeting the requirements of the program plan, and fully manages that energy and power consumption limits are not affected by the weight or volume from the operation of the autonomous robot unit and / or the services provided, that the amount of energy consumed does not change, that all power is generated by a rechargeable battery fuel source, that all distributed power consumption management is maintained consistently regardless of use, demand or physical weight load, and furthermore, that operations are managed to meet the requirements of the program plan without requiring end-user intervention. The method according to claim 2.

9. The operations and maintenance manager fully automates all operations and maintenance tasks of the autonomous robot or group of autonomous robots (including the automation of tasks performed by the robots) without requiring intervention from the end user, in order to meet the requirements of the program plan. The method according to claim 2.

10. The field support service manager automatically handles any field maintenance tasks necessary for the operation of the autonomous robot or the group of autonomous robots, and immediate or urgent support alerts required for the system components and / or dependent components, which are performed fully automatically in accordance with the requirements of the program plan and without requiring intervention from the end user. The method according to claim 2.

Images