System and method for parking management

Abstract

The present disclosure provides "systems and methods for parking management." A method includes receiving an access-related request associated with a vehicle, determining whether a task associated with the access-related request can be performed within a time-related threshold, aggregating the access-related request with a plurality of pending access-related requests in response to determining that the access-related request cannot be performed within the time-related threshold, and causing a transition of a state associated with the vehicle.

Description

Technical Field

[0001] This disclosure relates to a parking management system, and more specifically, to a parking management system that provides vehicle accessibility based on one or more use cases associated with a vehicle. Background Technology

[0002] The statements in this section are provided only as background information in connection with this disclosure and may not constitute prior art.

[0003] At any given time between manufacturing and delivery, a large number of vehicles can be stored in parking locations. However, storing such a large number of vehicles presents inherent challenges associated with vehicle inventory management, as vehicles are grouped in and out of parking locations for various needs. These challenges may involve the efficient use of space within parking locations, optimization of access, and so on. Inefficiencies may also exist related to the typical methods and / or systems upon which managing the vehicle inventory within parking locations relies, such as the inability to optimally rearrange vehicles within parking locations and / or the inability to predict the time required for rearranging vehicles within said parking locations.

[0004] This disclosure addresses these and other issues related to the inventory of parked vehicles within a managed marshalling environment. Summary of the Invention

[0005] This section provides a general overview of this disclosure and is not a full disclosure of its entire scope or all its features.

[0006] This disclosure provides a method comprising: receiving, by an infrastructure system, an access-related request associated with a vehicle; determining whether a first task associated with the access-related request can be executed within a time-related threshold; in response to determining that the access-related request cannot be executed within the time-related threshold, aggregating the access-related request with a plurality of pending access-related requests; and causing a posture change associated with the vehicle in response to the aggregation of the access-related request with the plurality of pending access-related requests; wherein the access-related request includes one or more vehicle characteristics, a location associated with the execution of the first task, a priority associated with the first task, the time-related threshold associated with the first task, an expected duration for completing the execution of the first task, or a combination thereof; wherein each of the pending access-related requests is associated with a second task, and wherein each of the pending access-related requests includes one or more vehicle characteristics, a location associated with the execution of the second task, a priority associated with the second task, a time-related threshold associated with the second task, an expected duration for completing the execution of the second task, or a combination thereof; the method further comprising: determining the completion of the first task... The method further includes: determining whether the expected duration of execution of the second task satisfies the time-related threshold associated with the first task; and causing the second task to be executed in parallel with the execution of the first task on the vehicle in response to determining that the expected duration of execution of the second task satisfies the time-related threshold associated with the first task; the method also includes: assigning a priority to the one or more parking locations based on accessibility associated with each of the one or more parking locations in the grouping environment; assigning the vehicle to a parking location in response to completion of the first task executed on the vehicle; and causing the vehicle to move to the parking location in response to the assignment of the vehicle to the parking location; wherein assigning the vehicle to the parking location further includes: matching the expected duration of the vehicle being parked in the grouping environment with the assigned priority of the parking location; and wherein the attitude associated with the vehicle includes an orientation and position corresponding to the vehicle, and wherein causing the attitude change associated with the vehicle further includes: determining a future orientation and position that allows access to one or more tasks to be executed on another vehicle; and causing the vehicle to move to the future orientation and position.

[0007] This disclosure provides a system comprising: an infrastructure system configured to: receive an access-related request associated with a vehicle; determine whether a first task associated with the access-related request can be executed within a time-related threshold; aggregate the access-related request with a plurality of pending access-related requests in response to determining that the access-related request cannot be executed within the time-related threshold; and cause an attitude change associated with the vehicle in response to the aggregation of the access-related request with the plurality of pending access-related requests; and the vehicle is configured to: receive one or more grouping commands from the infrastructure system; and cause an attitude change associated with the vehicle in response to receiving the one or more grouping commands. The attitude change associated with the vehicle; wherein the access-related request includes one or more vehicle characteristics, a location associated with the execution of the first task, a priority associated with the first task, a time-related threshold associated with the first task, an expected duration for completing the execution of the first task, or a combination thereof; wherein each access-related request in the pending access-related requests is associated with a second task, and wherein each access-related request in the pending access-related requests includes one or more vehicle characteristics, a location associated with the execution of the second task, a priority associated with the second task, a time-related threshold associated with the second task, an expected duration for completing the execution of the second task, or a combination thereof; wherein the infrastructure is further configured to: determine whether the expected duration for completing the execution of the second task satisfies the time-related threshold associated with the first task; and in response to determining that the expected duration for completing the execution of the second task satisfies the time-related threshold associated with the first task, cause the second task to be executed in parallel with the execution of the first task on the vehicle; wherein the infrastructure is further configured to: assign a priority to the one or more parking locations based on the accessibility associated with each of the one or more parking locations within the grouping environment; and assign the vehicle to the one or more parking locations in response to the completion of the first task executed on the vehicle. A parking location among multiple parking locations; and causing the vehicle to move to the parking location in response to the vehicle's allocation to the parking location; wherein the infrastructure system configured to allocate the vehicle to the parking location is further configured to: match the expected duration of the vehicle's parking within the grouping environment with the assigned priority of the parking location; and wherein the attitude associated with the vehicle includes an orientation and position corresponding to the vehicle, and wherein the infrastructure system configured to cause the attitude change associated with the vehicle is further configured to: determine a future orientation and position that allows access to one or more tasks to be performed on another vehicle; and cause the vehicle to move to the future orientation and position.

[0008] This disclosure provides one or more non-transitory computer-readable media storing processor-executable instructions that, when executed by at least one processor, cause the at least one processor to: receive an access-related request associated with a vehicle; determine whether a first task associated with the access-related request can be executed within a time-related threshold; aggregate the access-related request with a plurality of pending access-related requests in response to determining that the access-related request cannot be executed within the time-related threshold; and cause a posture change associated with the vehicle in response to the aggregation of the access-related request with the plurality of pending access-related requests; wherein the access-related request includes one or more vehicle characteristics, a location associated with the execution of the first task, a priority associated with the first task, the time-related threshold associated with the first task, an expected duration for completing the execution of the first task, or a combination thereof; and wherein each of the pending access-related requests is associated with a second task; and further, wherein each of the pending access-related requests includes one or more vehicle characteristics, a location associated with the execution of the second task, a priority associated with the second task, a time-related threshold associated with the second task, an expected duration for completing the execution of the second task, or a combination thereof. The combination; wherein the at least one processor is further caused to: determine whether the expected duration for completing the execution of the second task satisfies the time-related threshold associated with the first task; and in response to determining that the expected duration for completing the execution of the second task satisfies the time-related threshold associated with the first task, cause the second task to be executed in parallel with the execution of the first task on the vehicle; wherein the at least one processor is further caused to: assign priority to the one or more parking locations based on the accessibility associated with each of the one or more parking locations within the grouping environment; and assign the vehicle to the one or more parking locations in response to the completion of the first task executed on the vehicle. A parking location among multiple parking locations; and in response to the allocation of the vehicle to the parking location, causing the vehicle to move to the parking location; wherein at least one processor that is caused to allocate the vehicle to the parking location is also caused to: match the expected duration of the vehicle being parked within the grouping environment with the assigned priority of the parking location; and wherein the attitude associated with the vehicle includes an orientation and position corresponding to the vehicle, and wherein at least one processor that is caused to cause a change in the attitude associated with the vehicle is also caused to: determine a future orientation and position that allows access to one or more tasks to be performed on another vehicle; and cause the vehicle to move to the future orientation and position.

[0009] Further applicability will become apparent from the description provided herein. It should be understood that the descriptions and specific examples are intended for illustrative purposes only and are not intended to limit the scope of this disclosure. Attached Figure Description

[0010] To better understand this disclosure, various forms of the disclosure will now be described by way of example with reference to the accompanying drawings, in which: Figure 1 A system for automated vehicle grouping according to one or more embodiments of the present disclosure is shown; Figure 2 One or more embodiments of the present disclosure are shown. Figure 1 The system shown is used to group example vehicles; Figures 3A to 3D This is a process flowchart illustrating an example method for parking management of one or more vehicles; Figure 4 A display depicting a grouping environment according to one or more embodiments of the present disclosure is shown; Figure 5 This is a flowchart illustrating an example method for parking management of one or more vehicles according to one or more embodiments of the present disclosure; and Figure 6 This is a block diagram illustrating an example computer system according to one or more embodiments of the present disclosure.

[0011] The accompanying drawings described herein are for illustrative purposes only and are not intended to limit the scope of this disclosure in any way. Detailed Implementation

[0012] The following description is merely exemplary in nature and is not intended to limit this disclosure, its application, or its uses. It should be understood that throughout the drawings, corresponding reference numerals indicate the same or corresponding parts and features.

[0013] The one or more examples described herein provide systems and methods for parking management of one or more vehicles. More specifically, the systems and methods of this disclosure provide means for optimizing parking locations and / or directional areas therein, based on use cases associated with each vehicle, the time required to move each vehicle to a specific organization for a particular purpose and / or access, and the duration of a specific task performed on each vehicle within a schedule. In one or more examples, the systems and methods of this disclosure may provide a systematic organization of vehicles for multiple purposes over time and / or sequentially within different time allocations for one or more purposes, reducing the number of times vehicles need to be moved (or relocated) within parking locations, or reducing the number of times vehicles need to be reorganized. Such systematic organization can reduce the time required for system operators to locate and interact with vehicles, which improves operational efficiency overall.

[0014] In one or more examples, the systems and methods of this disclosure can provide de-prioritization of access to less urgent tasks associated with a vehicle movement schedule, and then re-prioritize the vehicles when more urgent tasks are scheduled to be performed on the same vehicles. In one or more examples, the systems and methods of this disclosure can provide prioritization of a group of vehicles based on the scheduling tasks associated with each vehicle in the group. This efficiently organizes the vehicles in such a way that a system operator can perform tasks on each vehicle in the same area of ​​the parking location, saving the system operator time that would otherwise have to move through all the vehicles parked in the parking location to perform the tasks.

[0015] In one or more examples, the systems and methods of this disclosure can provide a priority ordering of the vehicle inventory relative to the vehicle inventory associated with the parking location, such that the vehicle inventory can be dynamically rearranged to accommodate new vehicles at any time without affecting access to vehicles prioritized for the scheduling service. In one or more examples, the systems and methods of this disclosure provide predictions of the time associated with vehicle rearrangement, as well as the completion of actions that serve as the basis for reducing the total number of vehicles that need to be moved, which generally effectively reduces the total time for vehicle rearrangement.

[0016] In one or more examples, the systems and methods of this disclosure allow service operators to perform tasks more efficiently by prioritizing and aggregating requests based on input from the requester to ensure tasks are completed on a priority basis, and by providing means and opportunities to perform multiple tasks simultaneously on the same vehicle.

[0017] Figure 1A schematic block diagram of an Automated Vehicle Grouping (AVM) system 100 is shown. In one or more examples, the AVM system 100 groups one or more vehicles (e.g., vehicle 102) that are traveling at low speeds. However, it should be understood that the AVM system 100 can group one or more vehicles that are traveling at any speed. It should also be understood that the AVM system 100 can group semi-autonomous vehicles and / or fully autonomous vehicles.

[0018] AVM system 100 typically includes vehicle 102, central server 104, system operator 106, cloud system 108, and infrastructure system 110. Central server 104 operates as the central communication point associated with AVM system 100 and manages and / or facilitates any manufacturing processes associated with vehicle 102. For example, central server 104 facilitates the grouping of one or more vehicles, enabling one or more vehicles to travel through (e.g., traverse) a grouping environment (e.g., a factory floor or parking lot).

[0019] Central server 104 is configured to communicate directly and wirelessly with each of the components of AVM system 100 (e.g., vehicle 102, system operator 106, cloud system 108, and infrastructure system 110), and may include infrastructure-side AVM algorithm 112. Central server 104 is also configured to provide vehicle 102 with logical interface information received from infrastructure system 110. Additionally, central server 104 is configured to calculate one or more maneuvers (e.g., movement) associated with vehicle 102.

[0020] The infrastructure-side AVM algorithm 112 processes state information associated with at least one or more vehicles 102. It should be understood that the infrastructure-side AVM algorithm 112 processes state information associated with each of the one or more vehicles. The central server 104 is configured to utilize the infrastructure-side AVM algorithm 112 to transmit one or more instructions and / or process information received from each of the components of the AVM system 100 (e.g., vehicle 102, system operator 106, cloud system 108, and infrastructure system 110). For example, the received information may relate to, but is not limited to, grouping vehicles 102 and / or vision-based communication with vehicles 102.

[0021] Specifically, based on direct communication with one or more vehicles, the central server 104 is also configured to cause one or more vehicles to start, stop (e.g., at a specific parking location), or pause their progress through the formation environment. The central server 104 is also configured to control the formation speed of one or more vehicles as they travel through the formation environment.

[0022] Vehicle 102 includes a vehicle-side AVM algorithm 114. In one or more embodiments, vehicle 102 utilizes the vehicle-side AVM algorithm 114 to process and transmit information collected by one or more components associated with the configuration of vehicle 102, such as components disposed internally and / or externally in relation to vehicle 102. For example, although not shown, components associated with the configuration of vehicle 102 may include a wireless transmission module, a vehicle central gateway module, a vehicle infotainment system, one or more vehicle sensors, a vehicle battery, a vehicle global navigation satellite (e.g., GNSS), a vehicle navigation map system, and / or a controller area network (CAN) vehicle bus. It should be understood that the grouping of vehicle 102 within AVM system 100 can be supported by utilizing any of one or more components associated with the configuration of vehicle 102.

[0023] More specifically, and refer to Figure 2 Vehicle 102 can be powered in various forms and in various ways, such as by using an electric motor and / or an internal combustion engine. It should be understood that vehicle 102 can be any type of vehicle powered by an electric motor and / or an internal combustion engine, such as a car, truck, robot, aircraft, and / or boat. Vehicle 102 typically includes a vehicle controller 200, one or more actuators 202, multiple onboard sensors 204, a human-machine interface (HMI) 206, and a vehicle system 208. Vehicle 102 also has a reference point 210, i.e., a designated point within the space defined by the vehicle body, which identifies the position of vehicle 102. For example, reference point 210 is the geometric center point where the respective longitudinal and lateral center axes of vehicle 102 intersect. As another example, reference point 210 is the point where vehicle 102 is located when navigating toward a waypoint (such as parking vehicle 102).

[0024] In some examples, vehicle controller 200 is configured or programmed to control the operation of one or more of the following: vehicle braking, propulsion (e.g., controlling the acceleration of vehicle 102 by controlling one or more of an internal combustion engine, electric motor, hybrid engine, etc.), steering, climate control, interior and / or exterior lights, etc. In other examples, vehicle controller 200 is also configured or programmed to determine whether and when vehicle controller 200 (rather than a human operator) controls such operations associated with vehicle 102. It should be understood that any operation associated with vehicle 102 can be facilitated via automated, semi-automated, or manual modes. For example, an automated mode can facilitate complete control of any operation by vehicle controller 200 without the assistance of a human operator. As another example, a semi-automated mode can facilitate at least partial control of any operation by a human operator in combination with vehicle controller 200. As yet another example, a manual mode can facilitate complete control of operation by a human operator without the assistance of vehicle controller 200.

[0025] Vehicle controller 200 includes one or more processors (not shown), or can be communicatively coupled to one or more processors (e.g., via a vehicle communication bus). For example, the one or more processors may be controllers included in vehicle 102, used to monitor and / or control various vehicle controllers, such as powertrain controllers, brake controllers, steering controllers, etc. Vehicle controller 200 is typically arranged to communicate over a vehicle communication network (not shown) (which may include buses in vehicle 102, such as a CAN bus, etc.) and / or other wired and / or wireless mechanisms.

[0026] Vehicle controller 200 transmits messages to and / or receives messages from various devices (e.g., one or more actuators 202, HMI 206, etc.) in vehicle 102 via a vehicle network. Alternatively or additionally, where vehicle controller 200 includes multiple devices, a vehicle communication network is used for communication between such devices represented by vehicle controller 200 in this disclosure. Furthermore, as discussed below, various other controllers and / or sensors provide data to vehicle controller 200 via the vehicle communication network.

[0027] Additionally, the vehicle controller 200 is configured via vehicle-side AVM algorithm 114 to communicate through a vehicle-to-infrastructure communication network, such as communicating with an infrastructure controller (not shown). The vehicle controller 200 is also configured via vehicle-side AVM algorithm 114 to communicate with other traffic objects (e.g., vehicles, infrastructure, etc.) through a wireless vehicle communication interface, such as via a vehicle-to-vehicle communication network. The vehicle communication network refers to one or more mechanisms by which the vehicle controller 200 of vehicle 102 communicates with other traffic objects. As an example, the vehicle communication network can be one or more wireless communication mechanisms, including any desired combination of wireless (e.g., cellular, wireless, satellite, microwave, and / or radio frequency) communication mechanisms, and any desired network topology (or multiple topologies utilizing multiple communication mechanisms). Examples of vehicle communication networks include cellular, Bluetooth®, IEEE 802.11, Dedicated Short Range Communication (DSRC), and / or Wide Area Network (WAN) (including the Internet) providing data communication services.

[0028] One or more actuators 202 are implemented via circuits, chips, or other electronic and / or mechanical components that can actuate various vehicle subsystems according to appropriate control signals. One or more actuators 202 can be used to control the braking, acceleration, and / or steering of the vehicle 102. The vehicle controller 200 can be programmed to activate one or more actuators 202 (including propulsion, steering, and / or braking actuators) based on planned acceleration or deceleration of the vehicle 102.

[0029] The multiple onboard sensors 204 include various means for providing data to the vehicle controller 200. For example, the multiple onboard sensors 204 may include object detection sensors (e.g., lidar sensors) disposed on or in the vehicle 102, which provide the relative position, size, and / or shape of one or more objects (such as attached vehicles, bicycles, robots, drones, etc.) traveling beside, in front of, and / or behind the vehicle 102. As another example, one or more of the multiple onboard sensors 204 may be radar sensors fixed to one or more bumpers of the vehicle 102, which can provide the position of an object relative to the position of each vehicle 102.

[0030] Multiple onboard sensors 204 may include camera sensors that provide images from the area surrounding vehicle 102, such as providing front, side, and rear views. As another example, vehicle controller 200 may be programmed to receive sensor data from camera sensors and implement image processing techniques to detect roads, infrastructure elements, etc. Vehicle controller 200 may also be programmed to determine the current vehicle position based on location coordinates (e.g., GPS coordinates) received from vehicle 102 indicating the position of vehicle 102 determined from a GPS sensor (not shown).

[0031] HMI 206 is configured to receive information from a human operator during operation of vehicle 102. Additionally, HMI 206 is configured to present information to a human operator, such as an occupant of vehicle 102. In some variations, vehicle controller 200 is programmed to receive destination data (e.g., location coordinates) from HMI 206.

[0032] Vehicle system 208 is configured to control each of the subsystems within vehicle 102 and facilitate requests across each of the aforementioned components (e.g., vehicle controller 200, one or more actuators 202, multiple onboard sensors 204, and / or HMI 206). Therefore, at least multiple onboard sensors 204 can be used to autonomously guide vehicle 102 to waypoints. Route selection can be performed using vehicle position, distance traveled, queuing for vehicle grouping, etc.

[0033] Return to reference Figure 1 Furthermore, in one or more embodiments, as a supplement to or alternative to infrastructure system 110, vehicle-side AVM algorithm 114 may determine state information associated with vehicle 102 based on processed information, as further described herein. In another one or more embodiments, vehicle 102 utilizes vehicle-side AVM algorithm 114 to process information obtained from any component associated with the construction of vehicle 102 and to send it to central server 104 and / or cloud system 108. However, it should be understood that vehicle 102 may utilize vehicle-side AVM algorithm 114 to process information obtained from any component associated with the construction of vehicle 102 and to send it directly to infrastructure system 110 and / or system operator 106. Additionally, vehicle-side AVM algorithm 114 is also configured to process information received from any component of AVM system 100 and to send it to any component associated with the construction of vehicle 102.

[0034] Central server 104 is configured to enable infrastructure system 110 to monitor the progress of one or more vehicles as they move through a grouped environment. Infrastructure system 110 includes sensor components 116 and wireless communication components 118. For example, wireless communication component 118 may utilize GPS, Wi-Fi, satellite, 3G / 4G / 5G, and / or Bluetooth. TM To communicate with one or more vehicles. It should be understood that, by utilizing either sensor component 116 and / or wireless communication component 118, infrastructure system 110 is configured to perform localization functions associated with the grouping of vehicles 102, such as, but not limited to, perception, path planning, detection, control, response, or combinations thereof of vehicles 102.

[0035] Wireless communication component 118 communicates with sensor component 116, which is configured to manage one or more of, such as cameras, lidar, radar, and / or ultrasonic devices. Sensor component 116 monitors the movement of one or more vehicles as they are grouped through a grouped environment.

[0036] System operator 106 may be a human operator responsible for monitoring one or more grouped vehicles by communicating with cloud system 108. It should be understood that cloud system 108 is a backend system that may represent an original equipment manufacturer (OEM) cloud system responsible for the remote engagement and / or disengagement of AVM applications (including the registration and / or deregistration of vehicle 102 from AVM system 100). In one or more embodiments, system operator 106 communicates with and / or monitors one or more vehicles via a user device (not shown) and / or the human eye of a human operator. However, it should be understood that system operator 106 may also be a non-human operator, such as a mainframe controller, a machine learning-based control system, or any neural network. It should also be understood that system operator 106 is responsible for managing and / or supervising the operation of vehicle 102 during automated grouping, boarding processes, and / or at various locations (e.g., via in-facility interfaces). System operator 106 is capable of receiving instructions from central server 104 and forwarding those instructions to one or more vehicles via cloud system 108. For example, the instructions received from the central server 104 may be one or more grouping commands, which may cause one or more vehicles to travel to a vehicle repair shop, a parking location, a future location, or any other location.

[0037] In one or more embodiments, system operator 106 can obtain information associated with the operation of vehicle 102. In one or more embodiments, the obtained information may be displayed on a user device based on one or more determinations made by logistics management system 120 regarding parking vehicle 102 within a grouping environment. For example, the user device may be a tablet computer or any other suitable electronic device. As another example, one or more determinations are made by utilizing at least the sensor components 116 of infrastructure system 110 and / or multiple on-board sensors 204. In another one or more embodiments, infrastructure system 110 is configured to communicate with logistics management system 120 (e.g., via wireless or wired means). Although logistics management system 120 is depicted as being located outside infrastructure system 110, it should be understood that logistics management system 120 may be located inside infrastructure system 110.

[0038] Figures 3A to 3D The illustration shows a process flow for optimizing the management associated with parking one or more vehicles within a grouping environment, according to one or more embodiments. In one or more examples, and as shown... Figure 4 As shown, optimization of one or more parking management processes within the grouping environment can be virtually displayed to the system operator 106 via a display 400 provided by a user device. As another example, the virtual display could be a virtual representation of the manufacturing facility (e.g., a digital twin) that is color-coded so that the system operator 106 can easily identify instances where the infrastructure-AVM algorithm 112 causes a relocation of vehicle 102 and how such a relocation of vehicle 102 might affect access to vehicle 102 relative to other vehicles within the manufacturing facility.

[0039] In one or more embodiments, the infrastructure-side AVM algorithm 112 is configured to determine at step 302 whether vehicle 102 is ready for grouping. In one or more examples, the determination of whether vehicle 102 is ready for grouping may be based on the initiation of the parking management process (at step 304).

[0040] In an instance where vehicle 102 is determined to be ready for grouping, the infrastructure-side AVM algorithm 112 is configured to determine, at step 306, whether there is time to rearrange vehicle 102 at least a second time before vehicle 102 is scheduled for its next use. In one or more examples, the determination of whether there is time to rearrange vehicle 102 at least a second time before vehicle 102 is scheduled for its next use can be based on a schedule (identified at step 308). For example, the schedule can indicate the available time corresponding to the time when vehicle 102 can be rearranged. In a case where it is determined that there is not enough time to rearrange vehicle 102 at least a second time before vehicle 102 is scheduled for its next use, a report can be transmitted to the requester (at step 310), which may include a notification indicating that the request will be scheduled. As an example, the requester can be any entity with the ability to initiate a parking management process, such as a human operator, a neural network powered device, a control system, etc. As another example, the report can cause the parking management process to be reinstated at step 304.

[0041] However, if it is determined that vehicle 102 is not ready for grouping, the infrastructure-side AVM algorithm 112 is configured to add vehicle 102 to the list of vehicles to be grouped at step 312. Additionally, if it is determined that there is sufficient time for at least a second repositioning of vehicle 102 before it is scheduled for its next use, the infrastructure-side AVM algorithm 112 is also configured to add vehicle 102 to the list of vehicles to be grouped at step 312. It should be understood that vehicle 102 can be added to the list of vehicles to be grouped based on a combination of the results of steps 302 and 306. However, it should also be understood that vehicle 102 can be added to the list of vehicles to be grouped based on the individual results of steps 302 or 306.

[0042] The infrastructure-side AVM algorithm 112 is configured to report a list of vehicles available for grouping at step 314 based on a request list. As an example, the report can be transmitted to the requester. In one or more examples, the request list can be stored in a first database 316. It should be understood that the first database 316 can be provided internally to the infrastructure system 110 itself, or externally relative to the infrastructure system 110. As another example, the request list may include, but is not limited to, vehicle information (e.g., vehicle identification number, vehicle type, etc.), the task associated with vehicle 102, the expected duration of task execution, the time of day, the date, the number of vehicles, or combinations thereof.

[0043] In one or more embodiments, the infrastructure-side AVM algorithm 112 is configured to report a list of available vehicles to be grouped based on a list of vehicles to be grouped and access-related requests for access to the vehicles to be grouped (at step 318). In one or more examples, the access-related request may be made by a requester and received by the infrastructure system 110 as user input. For example, the user input may be a request transmitted wirelessly or an option for a physical selection using a user device. As another example, the access-related request may include, but is not limited to, one or more vehicle characteristics, location associated with task execution, priority associated with the task, time-related thresholds associated with the task, expected duration for completing the task, or combinations thereof.

[0044] The infrastructure-side AVM algorithm 112 is also configured at step 320 to identify each vehicle in the vehicle list that will be used to satisfy the access-related request. The infrastructure-side AVM algorithm 112 is also configured to determine, in instances where multiple requests exist, whether there are enough vehicles to satisfy each request (at step 322). In instances where it is determined that there are not enough vehicles to satisfy each request among the multiple requests, the infrastructure-side AVM algorithm 112 is configured at step 324 to determine whether fewer vehicles from the vehicle list can be used to satisfy each of the multiple requests. In one or more examples, step 324 is performed based on an inquiry transmitted to the requester regarding whether fewer vehicles from the vehicle list can be used to satisfy each of the multiple requests.

[0045] In instances where it is determined, based on a requester's rejection of the request, that fewer vehicles from the vehicle list cannot be used to satisfy each of multiple requests, a report may be transmitted to the requester (at step 310), the report including a notification indicating that the request will be scheduled. As an example, the report may cause the parking management process to be re-initiated at step 304. However, in instances where it is determined, based on a requester's approval of the request, that fewer vehicles from the vehicle list can be used to satisfy each of multiple requests, the infrastructure-side AVM algorithm 112 is configured to allocate vehicles from the vehicle list (at step 326) to perform the requested task and / or calculate the expected duration for task completion based on historical task details.

[0046] In one or more examples, historical task details may be stored in a second database 328. It should be understood that the second database 328 may be provided internally to the infrastructure system 110 itself, or externally relative to the infrastructure system 110. As another example, historical task details may include, but are not limited to, time-related details associated with the task, such as the expected duration of task execution. As yet another example, historical task details may include metrics associated with the historical execution of the task by multiple vehicles, such as the average time to complete the task execution, the length of time considered to be the completion of the task execution, and the speed of completion considered to be associated with the execution of the task. It should be understood that both historical task details and the request list may be stored in the same database. It should be understood that allocating a vehicle from the vehicle list to perform a requested task and / or calculating the expected duration of task execution can be based on a combination of the results of steps 322 and 324. However, it should also be understood that allocating a vehicle from the vehicle list to perform a requested task and / or calculating the expected duration of task execution can be based on the individual results of steps 322 or 324.

[0047] At step 330, the infrastructure-side AVM algorithm 112 is configured to identify and / or quantify vehicles with overlapping functionalities related to multiple uses from the vehicle inventory. The infrastructure-side AVM algorithm 112 is also configured to verify the compatibility of the multi-purpose functionality of each vehicle from the vehicle inventory for collaborative access (at step 332), thereby completing the task based on the request inventory and / or historical task details. However, it should be understood that the verification of the multi-purpose functionality compatibility of each vehicle from the vehicle inventory for collaborative access can be performed on any basis to complete the task.

[0048] The infrastructure-side AVM algorithm 112 is also configured to inventory (at step 334) each identified use case and the expected duration of execution for completing the use case (i.e., task), said use cases including multiple identified use cases. The infrastructure-side AVM algorithm 112 is also configured to initiate a use case series optimization protocol (at step 336). In one or more examples, the use case series optimization protocol is executed based on the implementation of the neural network and / or the inventory obtained at step 334.

[0049] The infrastructure-side AVM algorithm 112 is configured at step 338 to calculate the time required to reposition the vehicle 102 among multiple use case tasks. In one or more examples, the calculation of the time to reposition the vehicle 102 is performed based on the expected duration of the use case execution. As another example, the calculation of the time to reposition the vehicle 102 may also be performed based on the priority and / or requirements associated with the completion of each task. As yet another example, the calculation of the time to reposition the vehicle 102 may also be performed based on the time period within which the requester expects the task to be completed. In one or more embodiments, at step 340, the infrastructure-side AVM algorithm 112 is configured to constrain the task to a date associated with the priority and / or requirements associated with the completion of each task. In one or more embodiments, at step 342, the infrastructure-side AVM algorithm 112 is configured to constrain the task to the time period within which the requester expects the task to be completed.

[0050] The infrastructure-side AVM algorithm 112 is also configured at step 344 to identify the most efficient best series based on the tasks to be performed (including the identified multiple uses). In one or more examples, the identification of the most efficient best series may also be based on the time period during which the requester expects the task to be completed, the priority associated with the completion of the task, or a combination thereof. The infrastructure-side AVM algorithm 112 is also configured at step 346 to generate a schedule indicating the next uninterrupted marshalling period. It should be understood that an uninterrupted marshalling period can be defined as a period during which no vehicles are added to or removed from the marshalling environment.

[0051] The infrastructure-side AVM algorithm 112 is also configured to cause a report (at step 348) to be transmitted to the requester indicating the schedule generated at step 346. It should be understood that the report transmitted at step 348 provides the requester with an opportunity to confirm the schedule generated at step 346. The infrastructure-side AVM algorithm 112 is also configured (at step 350) to determine whether the requester has confirmed the schedule generated at step 346. If the requester has not yet confirmed the schedule generated at 346, the infrastructure-side AVM algorithm 112 is configured to remove the requester's request from the schedule and recalculate the schedule, starting from step 338 (at step 352). In addition to removing the requester's request from the schedule and recalculating the schedule, a report may also be transmitted to the requester (at step 310), which may include a notification indicating that the request will be scheduled.

[0052] However, where the requester has confirmed the schedule generated at step 346, the infrastructure-side AVM algorithm 112 is configured to continue executing the task as scheduled at step 346 (at step 354). In one or more examples, the execution of the task scheduled at step 346 can continue after one or more previously associated tasks have been completed, allowing the positions of vehicles 102 to be rearranged to accommodate access to the next task. At step 356, the infrastructure-side AVM algorithm 112 is also configured to cause one or more vehicles associated with the task to move to the outer area of ​​the grouping environment. It should be understood that one or more vehicles move via an automated grouping device, or, in cases where one or more vehicles cannot be grouped, via, for example, a manual device operated by system operator 106. In one or more examples, the one or more vehicles associated with the task caused to move to the outer area of ​​the grouping environment are positioned in an accessible manner (e.g., allowing pedestrians and / or vehicles to enter the gap between one or more vehicles).

[0053] The infrastructure-side AVM algorithm 112 is also configured to determine at step 358 whether the requester is on time. If it is determined that the requester is not on time, the infrastructure-side AVM algorithm 112 is configured to transmit a reminder to the requester at step 360. However, if it is determined that the requester is on time, the infrastructure-side AVM algorithm 112 is configured to transmit a task completion report to the requester at step 362.

[0054] In one or more embodiments, the infrastructure-side AVM algorithm 112 is further configured at step 364 to determine whether a vehicle is being added to and / or removed from the vehicle list. If the infrastructure-side AVM algorithm 112 determines that no vehicle is being added to and / or removed from the vehicle list, the infrastructure-side AVM algorithm 112 is configured to continue executing the task as scheduled at step 346 (at step 354). However, if the infrastructure-side AVM algorithm 112 determines that a vehicle is being added to and / or removed from the vehicle list, the infrastructure-side AVM algorithm 112 is configured at step 366 to determine whether adding to and / or removing a vehicle from the vehicle list affects any of the scheduled tasks. If the infrastructure-side AVM algorithm 112 determines that adding to and / or removing a vehicle from the vehicle list does not affect any of the scheduled tasks, the infrastructure-side AVM algorithm 112 is configured to continue executing the task as scheduled at step 346 (at step 354). However, if the infrastructure-side AVM algorithm 112 determines that adding and / or removing a vehicle from the vehicle list would affect any of the planned tasks, the infrastructure-side AVM algorithm 112 is configured to cause the parking management process to be re-initiated at step 304.

[0055] Figure 5This is a flowchart illustrating an example method 500 for optimizing management associated with parking one or more vehicles within a marshalling environment. At operation 502, an infrastructure system (e.g., infrastructure system 110) is configured to receive access-related requests associated with a vehicle (e.g., vehicle 102). In one or more examples, the access-related request may be associated with any vehicle from a vehicle inventory stored within the marshalling environment or parking area. As an example, the access-related request includes one or more vehicle characteristics (e.g., vehicle model, vehicle year, vehicle trim, powertrain type associated with the vehicle, one or more installed options associated with the vehicle, etc.), the location associated with the execution of a first task (e.g., vehicle maintenance and / or inspection), the priority associated with the first task (e.g., assigned by the requester, indicating the date and / or time the first task is expected to be performed), a time-related threshold associated with the first task, the expected duration of the execution of the first task, how many vehicles need access (e.g., indicated by a service provider), and what type of access (e.g., software update, data collection, inspection, system / part replacement, etc.) or a combination thereof. As another example, the access-related request may indicate an acceptable deviation from the expected date and / or time of the first task's execution. It should be understood that the time-related threshold can correspond to any time range. It should also be understood that the acceptable deviation can differ from the range associated with the time-related threshold, provided the first task is completed before the expected date and / or time, in which case the first task will meet or exceed the time-related threshold. As yet another example, in instances where the deviation does not meet the time-related threshold, an infrastructure-side AVM algorithm (e.g., infrastructure-side AVM algorithm 112) is configured to identify whether other service locations are available to cause the vehicle to move to another service location, such that the first task can be completed before the expected date and / or time, as described herein.

[0056] At operation 504, the infrastructure system is further configured to determine whether a first task associated with the access-related request can be executed within a time-related threshold. At operation 506, the infrastructure system is further configured to aggregate the access-related request with a plurality of pending access-related requests. In one or more examples, the aggregation of the access-related request with the plurality of pending access-related requests is performed in response to determining that the access-related request cannot be executed within the time-related threshold. As another example, each of the pending access-related requests is associated with a second task. As yet another example, each of the pending access-related requests includes one or more vehicle characteristics, a location associated with the execution of the second task, a priority associated with the second task, a time-related threshold associated with the second task, an expected duration for completing the execution of the second task, or a combination thereof.

[0057] At operation 508, the infrastructure system is also configured to cause a change in attitude associated with the vehicle or otherwise alter it. In one or more examples, the attitude change is caused in response to the aggregation of the access-related request and the plurality of pending access-related requests. As another example, the attitude associated with the vehicle includes the orientation and position corresponding to the vehicle. In one or more examples, causing the attitude change associated with the vehicle includes the infrastructure system determining a future orientation and position that allows access to one or more tasks to be performed on another vehicle, and causing the vehicle to proceed to the future orientation and position. In one or more examples, the future orientation and position may be an orientation that allows vehicles to continuously flow into / out of the marshalling environment and provides opportunities to perform unique use cases (e.g., tasks) on the vehicle without hindering the progress of other vehicles through the marshalling environment.

[0058] In one or more embodiments, the infrastructure system is configured to determine whether the expected duration of execution of the second task satisfies a time-related threshold associated with the first task. The infrastructure system is also configured to cause the second task to be executed in parallel with the execution of the first task on the vehicle. In one or more instances, the second task is executed in response to determining that the expected duration of execution of the second task satisfies the time-related threshold associated with the first task.

[0059] In one or more embodiments, the infrastructure system is configured to assign priorities to one or more parking locations within a grouping environment. In one or more examples, the priority assignment to the one or more parking locations is based on the reachability associated with each of the one or more parking locations. The infrastructure system is also configured to assign the vehicle to one of the one or more parking locations. As another example, the vehicle-to-parking-location assignment is performed in response to the completion of a first task performed on the vehicle. The infrastructure system is also configured to cause the vehicle to move to the parking location. As yet another example, the vehicle-to-parking-location assignment is caused to proceed to the parking location. In one or more examples, the vehicle-to-parking-location assignment includes matching the expected duration for which the infrastructure system will park the vehicle within the grouping environment with the assigned priority of the parking location. As another example, the vehicle-to-parking-location assignment may be based on an infrastructure-side AVM algorithm configured to identify the vehicle's expected future use and prioritize different parking locations based on the vehicle's expected future use. In other words, the infrastructure-side AVM algorithm is configured to dynamically allocate vehicles and move them to parking positions based on the priority or depriority of the tasks associated with the vehicle. For example, in cases where a vehicle requires a priority parking position, it will be moved to an easily accessible parking position. However, in another example, and in cases where a vehicle requires a depriority parking position, it will be moved to an inaccessible parking position.

[0060] Figure 6An operating environment, such as a computer system, is shown that facilitates the execution of one or more systems and methods described herein. More specifically, the systems and methods described herein can be implemented using computing device 602. For example, computing device 602 can be a personal computer, desktop computer, laptop computer, tablet computer, handheld computer, server, workstation, mainframe, wearable computer, supercomputer, or a combination thereof. However, it should be understood that the foregoing examples of computing device 602 are not exhaustive, and computing device 602 can be any type of processing or computing device. Computing device 602 typically includes a processor 604, a display adapter 606, one or more input / output ports 608, one or more input / output components 610, a network adapter 612, a power supply 614, and memory 616. However, it should be understood that computing device 602 may include any additional components and does not need to include the listed components (e.g., processor 604, display adapter 606, one or more input / output ports 608, one or more input / output components 610, network adapter 612, power supply 614, and memory 616).

[0061] Processor 604 is configured to provide instructions to computing device 602, enabling computing device 602 to process one or more tasks, including implementing software programs to perform one or more operations as described in more detail herein. It should also be understood that computing device 602 may include any number of processors 604. Display adapter 606 may be a graphics card or video board that provides computing device 602 with the ability to display content on display device 618. For example, display device 618 may be any screen, monitor, and / or light-emitting component associated with any of a personal computer, desktop computer, laptop computer, tablet computer, handheld computer, server, workstation, host computer, wearable computer, supercomputer, or a combination thereof. However, it should be understood that the foregoing examples of display device 618 are not exhaustive, and display device 618 may be any type of device capable of providing visual display.

[0062] Input / output port 608 provides multiple interfaces (e.g., jacks) for one or more cables to connect to computing device 602. It should be understood that any number of input / output ports 608 may be present on computing device 602. For example, input / output port 608 provides computing device 602 with means to receive signals and / or data from external devices connected to computing device 602 via one or more cables. As another example, input / output port 608 provides computing device 602 with means to transmit signals and / or data to external devices connected to computing device 602 via one or more cables. Input / output component 610 may include one or more components supporting input / output port 608, such as, but not limited to, switches, buttons, pressure pads, float switches, keypads, radio receivers, or combinations thereof.

[0063] Network adapter 612 can be any type of network interface controller configured to provide a device for communicating with another computing device (such as remote computing device 622) via network 620. For example, remote computing device 622 can be a user device such as a cellular phone, smartphone, tablet computer, laptop computer, or a combination thereof. Power supply 614 is configured to convert high-voltage alternating current (e.g., AC) into direct current (e.g., DC) to provide power to other components of computing device 602 (e.g., processor 604, display adapter 606, one or more input / output ports 608, one or more input / output components 610, network adapter 612, and memory 616).

[0064] Additionally, memory 616 may be a mass storage device and / or system memory, such as a hard disk drive, memory card, solid-state drive, RAM, or a combination thereof. Memory 616 is configured to provide storage for instructions and data associated with the operation of computing device 602. Memory 616 may typically include operating system 624, parking software 626, and parking data 628 to perform one or more operations as described in more detail herein. For example, operating system 624 is configured to manage and / or process any of the data and / or instructions associated with parking software 626 and / or parking data 628, as described in more detail herein.

[0065] Furthermore, a system bus 630 is also included within a computing device 602, which is configured to connect each of its various components (e.g., processor 604, display adapter 606, one or more input / output ports 608, one or more input / output components 610, network adapter 612, power supply 614, and memory 616). It should also be understood that the functions associated with each component of the computing device 602 and with each component of the computing device 602 can be implemented within a remote computing device 622. Although Figure 6The operating environment shown herein depicts a specific configuration associated with at least computing device 602, network 620, and remote computing device 622; however, it should be understood that the operating environment can be configured in any manner.

[0066] Therefore, one or more examples of this disclosure provide an apparatus for optimizing a parking management system by utilizing one or more methods and systems employing infrastructure-side automated vehicle grouping algorithms described herein. One or more examples provide accessibility to said vehicle based on one or more use cases associated with a vehicle among a plurality of vehicles located within a parking location in a grouping environment.

[0067] Unless otherwise expressly indicated herein, all numerical values ​​indicating mechanical / thermal properties, percentage of composition, dimensions and / or tolerances or other characteristics should be understood as being modified by the words “about” or “approximately” when describing the scope of this disclosure. Such modification is desired for various reasons, including: industrial practice; material, manufacturing and assembly tolerances; and testing capabilities.

[0068] As used herein, the phrases A, B, and C at least one should be interpreted as representing logic (A or B or C) using the non-exclusive logic "or", and should not be interpreted as representing "at least one of A, at least one of B, and at least one of C".

[0069] In this application, the terms “controller” and / or “module” may refer to, be part of, or include the following: application-specific integrated circuit (ASIC); digital, analog, or mixed analog / digital discrete circuit; digital, analog, or mixed analog / digital integrated circuit; composable logic circuit; field-programmable gate array (FPGA); processor circuitry (shared, dedicated, or grouped) that executes code; memory circuitry (shared, dedicated, or grouped) that stores code executed by the processor circuitry; other suitable hardware components that provide the described functionality; or combinations of some or all of the foregoing, such as in a system-on-a-chip.

[0070] The term memory is a subset of the term computer-readable medium. As used herein, the term computer-readable medium does not cover transient electrical or electromagnetic signals propagated through a medium (such as on a carrier wave); therefore, the term computer-readable medium can be considered tangible and non-transient. Non-limiting examples of non-transient tangible computer-readable media include non-volatile memory circuits (such as flash memory circuits, erasable programmable read-only memory circuits, or mask read-only circuits), volatile memory circuits (such as static random access memory circuits or dynamic random access memory circuits), magnetic storage media (such as analog magnetic tape or digital magnetic tape or hard disk drives), and optical storage media (such as CDs, DVDs, or Blu-ray discs).

[0071] The apparatus and methods described in this application can be implemented, in part or in whole, by a dedicated computer created by configuring a general-purpose computer to perform one or more specific functions embodied in a computer program. Function blocks, flowchart components, and other elements described above serve as software specifications that can be translated into computer programs through the routine work of a technician or programmer.

[0072] The description in this disclosure is merely exemplary in nature, and therefore, variations without departing from the spirit and scope of this disclosure are intended to be made within its scope. Such variations should not be considered as departing from the spirit and scope of this disclosure.

[0073] According to the present invention, one or more non-transitory computer-readable medium storage processors execute instructions that, when executed by at least one processor, cause the at least one processor to: receive an access-related request associated with a vehicle; determine whether a first task associated with the access-related request can be performed within a time-related threshold; aggregate the access-related request with a plurality of pending access-related requests in response to determining that the access-related request cannot be performed within the time-related threshold; and cause a posture change associated with the vehicle in response to the aggregation of the access-related request with the plurality of pending access-related requests.

[0074] According to an embodiment, the access-related request includes one or more vehicle characteristics, a location associated with the execution of the first task, a priority associated with the first task, a time-related threshold associated with the first task, an expected duration for completing the execution of the first task, or a combination thereof; and wherein each of the pending access-related requests is associated with a second task; and further, wherein each of the pending access-related requests includes one or more vehicle characteristics, a location associated with the execution of the second task, a priority associated with the second task, a time-related threshold associated with the second task, an expected duration for completing the execution of the second task, or a combination thereof.

[0075] According to an embodiment, the at least one processor is further caused to: determine whether the expected duration for completing the execution of the second task satisfies the time-related threshold associated with the first task; and, in response to determining that the expected duration for completing the execution of the second task satisfies the time-related threshold associated with the first task, cause the second task to be executed in parallel with the execution of the first task on the vehicle.

[0076] According to an embodiment, the at least one processor is also caused to: assign a priority to the one or more parking locations based on the accessibility associated with each of the one or more parking locations within the grouping environment; assign the vehicle to a parking location among the one or more parking locations in response to the completion of the first task performed on the vehicle; and cause the vehicle to move to the parking location in response to the vehicle's assignment to the parking location.

[0077] According to an embodiment, at least one processor that is caused to assign the vehicle to the parking location is also caused to match the expected duration for which the vehicle is parked in the grouping environment with the allocation priority of the parking location.

[0078] According to an embodiment, the attitude associated with the vehicle includes an orientation and position corresponding to the vehicle, and wherein at least one processor that is caused to cause a change in the attitude associated with the vehicle: determines a future orientation and position that allows access to one or more tasks to be performed on another vehicle; and causes the vehicle to move toward the future orientation and position.

Claims

1. A method comprising: The infrastructure system receives access-related requests associated with the vehicle. Determine whether the first task associated with the access-related request can be executed within a time-related threshold; In response to determining that the access-related request cannot be executed within the time-related threshold, the access-related request is aggregated with multiple pending access-related requests; as well as The attitude change associated with the vehicle is caused in response to the aggregation of the access-related request and the plurality of pending access-related requests.

2. The method of claim 1, wherein the access-related request includes one or more vehicle characteristics, a location associated with the execution of the first task, a priority associated with the first task, a time-related threshold associated with the first task, an expected duration for completing the execution of the first task, or a combination thereof.

3. The method of claim 1, wherein each of the pending access-related requests is associated with a second task, and wherein each of the pending access-related requests includes one or more vehicle characteristics, a location associated with the execution of the second task, a priority associated with the second task, a time-related threshold associated with the second task, an expected duration for completing the execution of the second task, or a combination thereof.

4. The method of claim 3, further comprising: Determine whether the expected duration for completing the second task satisfies the time-related threshold associated with the first task; as well as In response to determining that the expected duration for completing the second task satisfies the time-related threshold associated with the first task, the second task is executed in parallel with the execution of the first task on the vehicle.

5. The method of claim 1, further comprising: Priorities are assigned to the one or more parking locations based on their accessibility to each of the one or more parking locations within the grouping environment; In response to the completion of the first task performed on the vehicle, the vehicle is assigned to a parking location among the one or more parking locations; as well as In response to the allocation of the vehicle to the parking position, the vehicle is moved to the parking position.

6. The method of claim 5, wherein the allocation of the vehicle to the parking location further comprises: The expected duration for which the vehicle is parked within the grouping environment is matched with the allocation priority of the parking location.

7. The method of claim 1, wherein the attitude associated with the vehicle includes the orientation and position corresponding to the vehicle.

8. The method of claim 1, wherein causing the attitude change associated with the vehicle further comprises: Determine the future orientation and location where access is permitted for one or more tasks to be performed on another vehicle; as well as This causes the vehicle to move to the future orientation and position.

9. A system comprising: Infrastructure system, the infrastructure system being configured as follows: Receive access-related requests associated with the vehicle. Determine whether the first task associated with the access-related request can be executed within a time-related threshold. In response to determining that the access-related request cannot be executed within the time-related threshold, the access-related request is aggregated with multiple pending access-related requests, and In response to the aggregation of the access-related request and the plurality of pending access-related requests, a posture change associated with the vehicle is caused; and The vehicle is configured as follows: Receive one or more marshalling commands from the infrastructure system, and The attitude change associated with the vehicle is caused in response to receiving one or more grouping commands.

10. The system of claim 9, wherein the access-related request includes one or more vehicle characteristics, a location associated with the execution of the first task, a priority associated with the first task, the time-related threshold associated with the first task, an expected duration for completing the execution of the first task, or a combination thereof.

11. The system of claim 9, wherein each of the pending access-related requests is associated with a second task, and wherein each of the pending access-related requests includes one or more vehicle characteristics, a location associated with the execution of the second task, a priority associated with the second task, a time-related threshold associated with the second task, an expected duration for completing the execution of the second task, or a combination thereof.

12. The system of claim 11, wherein the infrastructure is further configured to: Determine whether the expected duration for completing the second task satisfies the time-related threshold associated with the first task; and In response to determining that the expected duration for completing the second task satisfies the time-related threshold associated with the first task, the second task is executed in parallel with the execution of the first task on the vehicle.

13. The system of claim 9, wherein the infrastructure is further configured to: Priorities are assigned to the one or more parking locations based on their accessibility to each of the one or more parking locations within the grouping environment; In response to the completion of the first task performed on the vehicle, the vehicle is assigned to a parking location among the one or more parking locations; as well as In response to the allocation of the vehicle to the parking position, the vehicle is moved to the parking position.

14. The system of claim 13, wherein the infrastructure system configured to assign the vehicle to the parking location is further configured to: The expected duration for which the vehicle is parked within the grouping environment is matched with the allocation priority of the parking location.

15. The system of claim 9, wherein the attitude associated with the vehicle includes an orientation and position corresponding to the vehicle, and wherein the infrastructure system configured to cause a change in the attitude associated with the vehicle is further configured to: Determine the future orientation and location that will allow access to one or more tasks to be performed on another vehicle; and This causes the vehicle to move to the future orientation and position.

Images