System and method for monitoring marshalling state transition of automated vehicle

Abstract

The invention provides a system and a method for monitoring a grouping state transition of an automated vehicle. A method includes monitoring an exchange of one or more messages with an infrastructure system, performing an analysis of the one or more messages, generating a virtual dynamic boundary associated with a marshalling environment, and getting off the vehicle in response to a current location of the vehicle being outside of the virtual dynamic boundary.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to monitoring marshalling state transitions associated with a vehicle. More specifically, the present disclosure relates to monitoring state transitions of a vehicle within a particular area of a marshalling environment. BACKGROUND

[0002] The statements in this section merely provide background information related to the present disclosure and can not constitute prior art.

[0003] Marshalling one or more vehicles within an operational design domain presents challenges associated with accurate boarding and deboarding of the one or more vehicles with infrastructure systems. Variability and / or range limitations in communication between the one or more vehicles and the infrastructure systems can also present challenges. For example, failure to facilitate successful deboarding and / or boarding of the vehicles can result in a violation of industry standards. Further, the type of communication used can limit the range over which the infrastructure can communicate with the one or more vehicles.

[0004] The present disclosure addresses these and other issues related to monitoring marshalling state transitions associated with one or more vehicles. SUMMARY

[0005] This section provides a general summary of the present disclosure and is not a comprehensive disclosure of its full scope or all of its features.

[0006] The present disclosure provides a method comprising: monitoring, by a vehicle marshaling algorithm of a vehicle, an exchange of one or more messages with an infrastructure system; performing an analysis of the one or more messages; generating a virtual dynamic boundary associated with a marshaling environment based on the analysis of the one or more messages; and causing the vehicle to deboard in response to a current location of the vehicle being outside of the virtual dynamic boundary; further comprising: causing the vehicle to board in response to the current location of the vehicle reentering the virtual dynamic boundary; further comprising: monitoring a state transition of the vehicle, wherein the state transition comprises the deboard of the vehicle and the board of the vehicle; wherein monitoring the exchange of the one or more messages comprises: monitoring at least one of a pattern associated with the one or more messages, a distance associated with the one or more messages, a radio frequency related behavior associated with the one or more messages, or a combination thereof; wherein the analysis of the one or more messages comprises: determining one or more characteristics associated with the one or more messages exchanged between the vehicle and one or more wayside units; and determining one or more characteristics associated with the one or more messages exchanged between the vehicle and one or more transmission points; wherein the one or more characteristics associated with the one or more messages exchanged between the vehicle and one or more wayside units and the one or more transmission points comprises a congestion level, a received signal strength indicator level, a PSID, a ranging distance, a change in frequency lock, a change in physical cell identifier received from a neighboring cell, a radio frequency related performance, a latency, a RTT, an IPG, a degradation in signal strength, a signal to interference noise ratio, an interference, a packet loss, a throughput, or a combination thereof; and further comprising: transmitting the analysis of the one or more messages to a cloud system, wherein the transmission of the analysis comprises snapshot data associated with the current location of the vehicle; and causing a timestamp and a virtual dynamic real-time heat map to be generated based on the transmission of the analysis.

[0007] The present disclosure provides a system comprising: an infrastructure system configured to receive one or more messages from a vehicle; and a vehicle system configured to: monitor an exchange of the one or more messages with the infrastructure system by a vehicle consist algorithm of the vehicle, perform an analysis of the one or more messages, generate a virtual dynamic boundary associated with a consist environment based on the analysis of the one or more messages, and cause the vehicle to de-consist in response to a current location of the vehicle being outside of the virtual dynamic boundary; wherein the vehicle system is further configured to: cause the vehicle to consist in response to the current location of the vehicle re-entering the virtual dynamic boundary; wherein the vehicle system is further configured to: monitor a state transition of the vehicle, wherein the state transition comprises the de-consist of the vehicle and the consist of the vehicle; wherein the vehicle system configured to monitor the exchange of the one or more messages is further configured to: monitor at least one of a pattern associated with the one or more messages, a distance associated with the one or more messages, a radio frequency related behavior associated with the one or more messages, or a combination thereof; wherein the vehicle system configured to analyze the one or more messages is further configured to: determine one or more characteristics associated with the one or more messages exchanged between the vehicle and one or more wayside units; and determine one or more characteristics associated with the one or more messages exchanged between the vehicle and one or more transmission points; wherein the one or more characteristics associated with the one or more messages exchanged between the vehicle and the one or more wayside units and the one or more transmission points comprise a congestion level, a received signal strength indicator level, a PSID, a ranging distance, a change in frequency lock, a change in a physical cell identifier received from a neighboring cell, a radio frequency related performance, a latency, a RTT, an IPG, a degradation in signal strength, a signal to interference noise ratio, an interference, a packet loss, a throughput, or a combination thereof; and wherein the vehicle system is further configured to: transmit the analysis of the one or more messages to a cloud system, wherein the transmission of the analysis comprises snapshot data associated with the current location of the vehicle; and cause a timestamp and a virtual dynamic real-time heat map to be generated based on the transmission of the analysis.

[0008] The present 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: monitor, by a vehicle marshaling algorithm of a vehicle, an exchange of one or more messages with an infrastructure system; perform an analysis of the one or more messages; generate, based on the analysis of the one or more messages, a virtual dynamic boundary associated with a marshaling environment; and cause the vehicle to de-vehicle in response to a current location of the vehicle being outside of the virtual dynamic boundary; wherein the at least one processor is further caused to: cause the vehicle to vehicle in response to the current location of the vehicle re-entering the virtual dynamic boundary; wherein the at least one processor is further caused to: monitor a state transition of the vehicle, wherein the state transition comprises the de-vehicle of the vehicle and the vehicle in; wherein the at least one processor caused to monitor the exchange of the one or more messages is further caused to: monitor at least one of a pattern associated with the one or more messages, a distance associated with the one or more messages, a radio frequency related behavior associated with the one or more messages, or a combination thereof; wherein the at least one processor caused to analyze the one or more messages is further caused to: determine one or more characteristics associated with the one or more messages exchanged between the vehicle and one or more wayside units; and determine one or more characteristics associated with the one or more messages exchanged between the vehicle and one or more transmission points, wherein the one or more characteristics associated with the one or more messages exchanged between the vehicle and the one or more wayside units and the one or more transmission points comprise a congestion level, a received signal strength indicator level, a PSID, a ranging distance, a change in frequency lock, a change in a physical cell identifier received from a neighboring cell, a radio frequency related performance, a latency, a RTT, an IPG, a degradation in signal strength, a signal to interference noise ratio, an interference, a packet loss, a throughput, or a combination thereof; wherein the at least one processor is further caused to: transmit the analysis of the one or more messages to a cloud system, wherein the transmission of the analysis comprises snapshot data associated with the current location of the vehicle; and cause a timestamp and a virtual dynamic real-time heat map to be generated based on the transmission of the analysis.

[0009] Further areas of applicability will become apparent from the description provided herein. It should be understood that the description and specific examples are intended for purposes of illustration only and are not intended to limit the scope of the present disclosure. BRIEF DESCRIPTION OF DRAWINGS

[0010] So that the disclosure can be well understood, various forms thereof will now be described by way of example with reference to the drawings in which: Figure 1A system for automated vehicle marshaling is shown in accordance with one or more embodiments of the present disclosure; Figure 2 A system for automated vehicle marshaling is shown in accordance with one or more embodiments of the present disclosure; Figure 1 An example vehicle marshaled by the system shown in Figure 3 A system for automated vehicle marshaling is shown in accordance with one or more embodiments of the present disclosure; Figure 4 is a flowchart showing an example method for monitoring, analyzing, and notifying of vehicle disembarking status in accordance with one or more embodiments of the present disclosure; and Figure 5 is a block diagram showing an example computer system in accordance with one or more embodiments of the present disclosure.

[0011] The accompanying drawings described herein are for purposes of illustration only and are not intended to limit the scope of the present disclosure in any way. DETAILED DESCRIPTION

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

[0013] One or more examples described herein provide an apparatus for monitoring, analyzing, and notifying of vehicle disembarking status, with robust operational domain limits that can prevent erroneous vehicle maneuvering and / or erroneous vehicle boarding outside of a specified operational design domain. For example, comprehensive monitoring and / or reporting is provided that enhances the overall reliability of a vehicle operating in an autonomous manner.

[0014] One or more embodiments also provide a robust wireless communication means that utilizes various wireless communication protocols to facilitate message exchange between a vehicle and an infrastructure system. For example, such a communication approach can provide reliable and / or redundant data exchange. In one or more embodiments, a multi-layered localization approach is also provided that does not simply rely on infrastructure-based sensing to determine a vehicle’s location within an operational design domain. Rather, for example, a multi-layered architecture is employed that utilizes various wireless communication protocols and / or algorithms to track a vehicle’s location and / or status.

[0015] One or more embodiments provide accurate state recognition that allows for correct identification of the state of the vehicle, which facilitates reliable autonomous maneuvering of the vehicle. For example, real-time monitoring capabilities enable accurate state detection across a variety of marshalling use cases (e.g., factory marshalling, yard marshalling, valet parking, hands-free charging, etc.). One or more embodiments provide reliable state recognition that ensures that correct state transitions are achieved when the vehicle leaves the operational design domain, thereby preventing further autonomous control of the vehicle (e.g., by the infrastructure system) without the vehicle re-entering the operational design domain. For example, this ensures acceptable operation of the vehicle within and outside of the operational design domain.

[0016] One or more embodiments provide enhanced reliability and redundancy when used in conjunction with other methods of identifying the location of the vehicle within the operational design domain. For example, the reliability of the system is enhanced and provides redundancy to support potential individual system insufficiencies. One or more embodiments provide reliable operation of the vehicle within and outside of the boundaries of the operational design domain. For example, malicious agents can be prevented from intercepting the vehicle and / or performing unexpected behavior through standard communication channels.

[0017] One or more embodiments provide adherence to industry standardization that is designed to operate within the operational design domain of the vehicle, thereby ensuring adherence to industry standards. For example, adherence to industry-acceptable guidelines enhances the reliability of the operation of the vehicle. One or more embodiments provide adaptability across global markets with a common platform that can serve the automation industry across different markets and / or applications. One or more embodiments provide comprehensive reporting and / or analytics with detailed reporting and / or analytics that inform the infrastructure system and vehicle manufacturing cloud of the vehicle entering the drop-off state, radio frequency related performance metrics, the location of the vehicle, sensor data, a virtual dynamic real-time heat map of wireless communication coverage, or a combination thereof. This information can enable data-driven decisions and / or continuous system enhancements.

[0018] Figure 1 An illustrative block diagram showing an automated vehicle marshalling (AVM) system 100 is shown. In one or more examples, the AVM system 100 marshals one or more vehicles (e.g., vehicle 102) that are traveling at low speed. However, it should be appreciated that the AVM system 100 can marshal one or more vehicles that are traveling at any speed. It should also be appreciated that the AVM system 100 can marshal semi-autonomous vehicles and / or fully autonomous vehicles.

[0019] The AVM system 100 generally includes a vehicle 102, a vehicle manufacturing cloud system 104, a vehicle delivery manager cloud system 106, a vehicle customer web portal account cloud system 108, and an infrastructure system 110. The vehicle manufacturing cloud system 104 operates as a central cloud system that manages and / or facilitates any manufacturing processes associated with the vehicle 102. The vehicle manufacturing cloud system 104 is configured to wirelessly communicate with the vehicle delivery manager cloud system 106 and / or the infrastructure system 110. The vehicle manufacturing cloud system 104 is also configured to wirelessly communicate with the vehicle 102.

[0020] The vehicle manufacturing cloud system 104 can include an infrastructure-side AVM algorithm 112. The infrastructure-side AVM algorithm 112 processes status information associated with at least the vehicle 102 of the one or more vehicles. It should be appreciated that, in one or more embodiments, the infrastructure-side AVM algorithm 112 processes status information associated with each vehicle (e.g., the vehicle 102) of the one or more vehicles. The vehicle manufacturing cloud system 104 is configured to cause the infrastructure system 110 to monitor the progress of the one or more vehicles (e.g., the vehicle 102) as the vehicles progress through a marshalling environment (e.g., a marshalling environment 314 as shown in FIG. 3). Figure 3 The marshalling environment 314 can represent a factory marshalling setup, an automated charging setup, a yard marshalling setup, or an underground parking setup, for example. As an example, the factory marshalling setup can include instances in which a just manufactured vehicle moves through an in-line test at a vehicle assembly plant via overhead vision sensing (e.g., one or more sensors 114). As another example, the automated charging setup can include instances in which a vehicle is properly assigned to an automated charging modality located outdoors or indoors. As a further example, the yard marshalling setup can include instances in which a fleet of commercial vehicles move through a warehouse and yard to automatically load and / or handle items. As an additional example, the underground parking setup can include instances in which a vehicle moves through an underground or covered parking environment with a potentially inconsistent communication network, such as a global navigation satellite system.

[0021] The vehicle manufacturing cloud system 104 is also configured to cause the infrastructure system 110 to communicate with the one or more vehicles. For example, the vehicle manufacturing cloud system 104 utilizes the infrastructure-side AVM algorithm 112 to send instructions to the infrastructure system 110 and / or to process information received from the infrastructure system 110. The vehicle manufacturing cloud system 104 is also configured to cause the vehicle delivery manager cloud system 106 to facilitate the delivery of the one or more vehicles (e.g., the vehicle 102) to various locations. For example, the vehicle manufacturing cloud system 104 utilizes the infrastructure-side AVM algorithm 112 to send instructions to the vehicle delivery manager cloud system 106 and / or to process information received from the vehicle delivery manager cloud system 106.

[0022] The vehicle manufacturing cloud system 104 is also configured to directly communicate with the one or more vehicles to cause the one or more vehicles to begin, stop, or pause progress through the staging environment 314. The vehicle manufacturing cloud system 104 is also configured to control the staging speed of the one or more vehicles as the one or more vehicles travel through (e.g., traverse) the staging environment 314. For example, the vehicle manufacturing cloud system 104 utilizes the infrastructure-side AVM algorithm 112 to send instructions to the vehicles 102 and / or process information received from the vehicles 102.

[0023] The infrastructure system 110 includes one or more sensors 114, a wireless communication component 116, a multi-access edge computing (MEC) system 118, and one or more traffic lights 120. It should be understood that the MEC system 118 is configured to support communication between the wireless communication component 116 and the vehicles 102. However, it should be understood that the MEC system 118 is also configured to support communication between the wireless communication component 116 and any of the vehicle manufacturing cloud system 104, the vehicle delivery manager cloud system 106, and / or the vehicle customer web portal account cloud system 108. For example, the wireless communication component 116 can utilize GPS, Wi-Fi, satellite, 3G / 4G / 5G, and / or Bluetooth ® to communicate with the one or more vehicles.

[0024] The wireless communication component 116 also communicates with one or more sensors 114 that are configured to manage and / or include, for example, one or more of a camera, a lidar, a radar, and / or an ultrasonic device. The one or more sensors 114 monitor the movement of the one or more vehicles as the vehicles are staged through the staging environment 314. Additionally, the wireless communication component 116 also communicates with the traffic lights 120. For example, the wireless communication component 116 can cause the traffic lights 120 to direct the traffic of the one or more vehicles as the vehicles are staged through the staging environment 314. It should be understood that the infrastructure system 110 can forward instructions received from the vehicle manufacturing cloud system 104 to the vehicles 102. However, it should also be understood that the infrastructure system 110 can send instructions directly to the vehicles 102, for example, by utilizing the MEC system 118.

[0025] The vehicle 102 includes a vehicle-side AVM algorithm 122, a wireless transmission module 124, a vehicle central gateway module 126, a vehicle infotainment system 128, one or more vehicle sensors 130, a vehicle battery 132, a vehicle GNSS 134, a vehicle navigation mapping system 136, and a controller area network (CAN) vehicle bus 138. The wireless transmission module 124 can be a transmission control unit (TCU) and / or can be supported by a telematics-supported subsystem. The wireless transmission module 124 includes one or more sensors configured to collect data and send signals to other components of the vehicle 102. The one or more sensors of the wireless transmission module 124 can include a vehicle speed sensor (not shown) configured to determine a current speed of the vehicle 102, a wheel speed sensor (not shown) configured to determine whether the vehicle 102 is traveling uphill or downhill, a throttle position sensor (not shown) configured to determine whether a downshift or upshift of one or more gears associated with the vehicle 102 is needed in a current state of the vehicle 102, and / or a turbo speed sensor (not shown) configured to send data associated with a speed of a torque converter of the vehicle 102.

[0026] The wireless transmission module 124 communicates information collected by the one or more sensors to the vehicle-side AVM algorithm 122. In one embodiment, the vehicle-side AVM algorithm 122 can be set as a component within the wireless transmission module 124. For example, the vehicle 102 utilizes the vehicle-side AVM algorithm 122 to process information collected by the one or more sensors and send the information to the infrastructure system 110. As another example, the vehicle 102 utilizes the vehicle-side AVM algorithm 122 to process information collected by the one or more sensors and send the information directly to the vehicle manufacturing cloud system 104. The vehicle-side AVM algorithm 122 is configured to communicate information and / or instructions received from the infrastructure system 110 and / or the vehicle manufacturing cloud system 104 to the wireless transmission module 124.

[0027] The vehicle central gateway module 126 operates as an interface between various vehicle domain bus systems, such as engine compartment bus (not shown), interior bus (not shown), optical bus for multimedia (not shown), diagnostic bus for maintenance (not shown), or vehicle CAN bus 138. The vehicle central gateway module 126 is configured to distribute data transmitted to it from each of the various domain bus systems to other components of the vehicle 102. The vehicle central gateway module 126 is also configured to distribute information received from the vehicle-side AVM algorithm 122 to the various domain bus systems. The vehicle central gateway module 126 is also configured to send information received from the various domain bus systems to the vehicle-side AVM algorithm 122. For example, the vehicle 102 uses the vehicle-side AVM algorithm 122 to process information received from the vehicle central gateway module 126 and sends the information to the infrastructure system 110. As another example, the vehicle 102 uses the vehicle-side AVM algorithm 122 to process information received from the vehicle central gateway module 126 and sends the information directly to the vehicle manufacturing cloud system 104. The vehicle-side AVM algorithm 122 is configured to transmit information and / or instructions received from the infrastructure system 110 and / or the vehicle manufacturing cloud system 104 to the vehicle central gateway module 126.

[0028] The vehicle infotainment system 128 delivers a combination of information and entertainment content and / or services to a user 140 of vehicle 102. It should be understood that in some examples, the vehicle infotainment system 128 may only deliver entertainment content to the user 140 of vehicle 102. It should also be understood that in other examples, the vehicle infotainment system 128 may deliver information services to anyone associated with vehicle 102. As an example, the vehicle infotainment system 128 includes a built-in vehicle computer that combines one or more functions, such as a digital radio, a built-in camera, and / or a television. The vehicle infotainment system 128 transmits information associated with the built-in vehicle computer or processor to a vehicle-side AVM algorithm 122. For example, vehicle 102 utilizes the vehicle-side AVM algorithm 122 to process information received from the vehicle infotainment system 128 and transmits said information to infrastructure system 110. As another example, vehicle 102 utilizes the vehicle-side AVM algorithm 122 to process information received from the vehicle infotainment system 128 and transmits said information directly to vehicle manufacturing cloud system 104. The vehicle-side AVM algorithm 122 is configured to transmit information and / or instructions received from the infrastructure system 110 and / or the vehicle manufacturing cloud system 104 to the vehicle infotainment system 128.

[0029] The one or more vehicle sensors 130 can be, for example, one or more of a camera, a lidar, a radar, and / or an ultrasonic device. For example, an ultrasonic device used as the one or more vehicle sensors 130 emits high frequency sound waves that hit an object (e.g., a wall or another vehicle) and are then reflected back to the vehicle 102. Based on the amount of time it takes for the sound waves to return to the vehicle 102, the vehicle 102 can determine a distance between the one or more vehicle sensors 130 and the object. As another example, a camera device used as the one or more vehicle sensors 130 provides a visual indication of the space around the vehicle 102. As an additional example, a radar device used as the one or more vehicle sensors 130 emits electromagnetic wave signals that hit an object and are then reflected back to the vehicle 102. Based on the amount of time it takes for the electromagnetic waves to return to the vehicle 102, the vehicle 102 can determine a range, a speed, and an angle of the vehicle 102 relative to the object.

[0030] The one or more vehicle sensors 130 communicate information associated with the location and / or distance of the vehicle 102 relative to the object to the vehicle-side AVM algorithm 122. For example, the vehicle 102 utilizes the vehicle-side AVM algorithm 122 to process information received from the one or more vehicle sensors 130 and send the information to the infrastructure system 110. As another example, the vehicle 102 utilizes the vehicle-side AVM algorithm 122 to process information received from the one or more vehicle sensors 130 and send the information directly to the vehicle manufacturing cloud system 104. The vehicle-side AVM algorithm 122 is configured to communicate information and / or instructions received from the infrastructure system 110 and / or the vehicle manufacturing cloud system 104 to the one or more vehicle sensors 130.

[0031] The vehicle battery 132 is controlled by a battery management system (not shown) that provides instructions to the vehicle battery 132. For example, the battery management system provides instructions to the vehicle battery 132 based on a temperature of the vehicle battery 132. However, it should be understood that the battery management system can provide instructions to the vehicle battery 132 based on any metric associated with the vehicle battery 132, such as a power status of the vehicle 102, a period of time during which the vehicle 102 is in an off state for at least a day, or a combination thereof. The battery management system ensures that a current pattern of the vehicle battery 132 is acceptable. For example, an acceptable current pattern prevents overvoltage, overcharging, and / or overheating of the vehicle battery 132. As another example, a temperature of the vehicle battery 132 indicates whether any of the acceptable current patterns are within an acceptable temperature range to the battery management system. The battery management system associated with the vehicle battery 132 communicates information associated with the temperature of the vehicle battery 132 to the vehicle-side AVM algorithm 122. For example, the vehicle 102 utilizes the vehicle-side AVM algorithm 122 to process the received information about the vehicle battery 132 and sends the information to the infrastructure system 110. As another example, the vehicle 102 utilizes the vehicle-side AVM algorithm 122 to process the information about the vehicle battery 132 and sends the information directly to the vehicle manufacturing cloud system 104. The vehicle-side AVM algorithm 122 is configured to communicate information and / or instructions received from the infrastructure system 110 and / or the vehicle manufacturing cloud system 104 to the vehicle battery 132.

[0032] The vehicle GNSS 134 is configured to communicate with satellites such that the vehicle 102 can determine a specific location of the vehicle 102. The vehicle navigation mapping system 136 can display the specific location of the vehicle 102 to a user 140 via a display screen (not shown). The vehicle GNSS 134 communicates geographic information associated with the vehicle 102 to the vehicle-side AVM algorithm 122. For example, the vehicle 102 utilizes the vehicle-side AVM algorithm 122 to process information received from the vehicle GNSS 134 and send the information to the infrastructure system 110. As another example, the vehicle 102 utilizes the vehicle-side AVM algorithm 122 to process information from the vehicle GNSS 134 and send the information directly to the vehicle manufacturing cloud system 104. The vehicle-side AVM algorithm 122 is configured to communicate information and / or instructions received from the infrastructure system 110 and / or the vehicle manufacturing cloud system 104 to the vehicle GNSS 134. As another example, the vehicle 102 utilizes the vehicle-side AVM algorithm 122 to process information associated with the vehicle navigation mapping system 136 and send the information to the infrastructure system 110. As another example, the vehicle 102 utilizes the vehicle-side AVM algorithm 122 to process information from the vehicle navigation mapping system 136 and send the information directly to the vehicle manufacturing cloud system 104. The vehicle-side AVM algorithm 122 is configured to communicate information and / or instructions received from the infrastructure system 110 and / or the vehicle manufacturing cloud system 104 to the vehicle navigation mapping system 136.

[0033] The vehicle 102 is configured to communicate any information associated with any components included within the vehicle 102 to one or more additional vehicles 142. The vehicle 102 is also configured to communicate (e.g., forward) any instructions received from the infrastructure system 110 and / or the vehicle manufacturing cloud system 104 to any of the one or more additional vehicles 142. For example, the communication of the vehicle 102 with the one or more additional vehicles 142 can assist the infrastructure system 110 and / or the vehicle manufacturing cloud system 104 in grouping the one or more additional vehicles 142. It should be appreciated that each of the one or more additional vehicles 142 can include any of the components described as included within the vehicle 102, such as, for example, the vehicle-side AVM algorithm 122, the wireless transmission module 124, the vehicle central gateway module 126, the vehicle infotainment system 128, the one or more vehicle sensors 130, the vehicle battery 132, the vehicle GNSS 134, the vehicle navigation mapping system 136, and / or the CAN vehicle bus 138. It should also be appreciated that any of the one or more additional vehicles 142 are configured to communicate information associated with any components included within the vehicle 102. It should also be appreciated that the one or more additional vehicles 142 can also be configured to establish a direct wireless communication link (e.g., via a communication link) with the infrastructure system 110 and / or the vehicle manufacturing cloud system 104, whereby information can be exchanged directly between the one or more additional vehicles 142 and the infrastructure system 110 and / or the vehicle manufacturing cloud system 104.

[0034] The vehicle delivery manager cloud system 106 is in wireless communication (e.g., receiving and / or sending instructions and / or information) with one or more of a rental agency cloud system 144, a valet parking agency cloud system 146, an insurance agency cloud system 148, and / or a dealer system 150. The vehicle delivery manager cloud system 106 is configured to facilitate delivery of one or more vehicles to a rental agency (not shown) associated with the rental agency cloud system 144, a valet parking agency (not shown) associated with the valet parking agency cloud system 146, an insurance agency (not shown) associated with the insurance agency cloud system 148, and / or any of the dealer system 150. The vehicle delivery manager cloud system 106 is also in wireless communication with the vehicle customer web portal account cloud system 108. It should be appreciated that other cloud systems can be included in one or more examples.

[0035] The delivery manager cloud system 106 wirelessly communicates with user devices 152, such as mobile devices, display panels, and / or computers. The vehicle 102 is also configured to wirelessly communicate directly with the user devices 152. For example, the user 140 engages with the user devices 152 via an application that organizes any information and / or instructions received from the vehicle customer web portal account cloud system 108 and / or the vehicle 102. As another example, the user 140 can send one or more instructions to the vehicle customer web portal account cloud system 108, such as selecting which vehicle the user 140 wants to receive from any of a rental agency associated with the rental agency cloud system 144, a valet parking agency associated with the valet parking agency cloud system 146, an insurance agency associated with the insurance agency cloud system 148, and / or a dealer system 150.

[0036] Reference is made to Figure 2 In various forms, the vehicle 102 can be powered in various ways, such as with an electric motor and / or an internal combustion engine. It should be understood that the vehicle 102 can be any type of vehicle powered by an electric motor and / or an internal combustion engine, such as an automobile, a truck, a robot, an airplane, and / or a boat. The vehicle 102 generally includes a vehicle controller 200, one or more actuators 202, a plurality of on-board sensors 204, a human-machine interface (HMI) 206, and vehicle systems 208. The vehicle 102 also has a reference point 210, which is a designated point within a space defined by the vehicle body that identifies a location of the vehicle 102. For example, the reference point 210 is a geometric center point at which respective longitudinal and lateral center axes of the vehicle 102 intersect. As another example, the reference point 210 is a point at which the vehicle 102 is located when the vehicle 102 is navigating toward a waypoint.

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

[0038] The 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 can be controllers included in the vehicle 102 for monitoring and / or controlling various vehicle controllers, such as powertrain controllers, brake controllers, steering controllers, etc. The vehicle controller 200 is generally arranged for communication over a vehicle communication network (not shown) (which can include a bus in the vehicle 102, such as a controller area network (CAN), etc.) and / or other wired and / or wireless mechanisms.

[0039] The vehicle controller 200 transmits messages to and / or receives messages from various devices in the vehicle 102 (e.g., the one or more actuators 202, the HMI 206, etc.) via the vehicle network. Alternatively or additionally, where the vehicle controller 200 includes multiple device sends, the vehicle communication network is used to represent communication between the device sends of the vehicle controller 200 in this disclosure. Further, as discussed below, various other controllers and / or sensors provide data to the vehicle controller 200 via the vehicle communication network.

[0040] Additionally, the vehicle controller 200 is configured for communication over a vehicle-to-infrastructure communication network, such as with an infrastructure controller (not shown), via the vehicle-side AVM algorithm 212. The vehicle controller 200 is also configured for communication with other traffic objects (e.g., vehicles, infrastructure, etc.) via a wireless vehicle communication interface, such as via a vehicle-to-vehicle communication network, via the vehicle-side AVM algorithm 212. The vehicle communication network represents one or more mechanisms by which the vehicle controller 200 of the vehicle 102 communicates with other traffic objects. As an example, the vehicle communication network can be one or more of a wireless communication mechanism, 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 when 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), etc. that provide data communication services.

[0041] The 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. The one or more actuators 202 can be used to control braking, acceleration, and / or steering of the vehicle 102. The vehicle controller 200 can be programmed to activate the one or more actuators 202 (including propulsion, steering, and / or braking actuators) based on a planned acceleration or deceleration of the vehicle 102.

[0042] The plurality of on-board sensors 204 includes a variety of devices for providing data to the vehicle controller 200. For example, the plurality of on-board sensors 204 can include object detection sensors (e.g., lidar sensors) disposed on or in the vehicle 102 that provide a relative position, size, and / or shape of one or more objects (such as additional vehicles, bicycles, robots, drones, etc.) traveling alongside, in front of, and / or behind the vehicle 102 around the vehicle 102. As another example, one or more of the plurality of on-board sensors 204 can be radar sensors fixed to one or more bumpers of the vehicle 102 that can provide a position of an object relative to a position of each vehicle 102.

[0043] The plurality of on-board sensors 204 can include camera sensors that provide images from areas around the vehicle 102, for example, to provide a forward view, a side view, a rear view, etc. As another example, the vehicle controller 200 can be programmed to receive sensor data from the camera sensors and implement image processing techniques to detect roads, infrastructure elements, etc. The vehicle controller 200 can also be programmed to determine a current vehicle position based on position coordinates (e.g., GPS coordinates) received from the vehicle 102 indicative of a position of the vehicle 102 determined from a GPS sensor (not shown).

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

[0045] The vehicle systems 208 are configured to control each of the subsystems within the vehicle 102 and facilitate requests across each of the aforementioned components (e.g., the vehicle controller 200, the one or more actuators 202, the plurality of on-board sensors 204, and / or the HMI 206). Thus, the vehicle 102 can be autonomously directed to a waypoint using at least the plurality of on-board sensors 204. Route selection can be performed using a vehicle position, a distance traveled, a queuing queue for a vehicle consist, etc.

[0046] In one or more embodiments, Figure 3System 300 is illustrated, configured to provide means for monitoring, analyzing, and / or notifying vehicles 102 (e.g., one or more vehicles 102a-102e) of their disembarkation status (e.g., stopped, unavailable, hibernating, etc.). For example, the means for monitoring, analyzing, and / or notifying vehicles 102 of their disembarkation status is provided via wireless exchange of one or more messages (e.g., infrastructure grouping messages (IMM) and vehicle grouping messages (VMM)) from infrastructure system 110, utilizing vehicle-side AVM algorithm 122 of vehicle 102.

[0047] As Figure 3 As part of the system 300 depicted herein, infrastructure system 110 is configured to communicate with infrastructure server 302. Infrastructure server 302 includes an optimal vehicle route allocation component 304, vehicle attitude, obstacle, and route selection data component 306, and a database 308. Although infrastructure server 302 is depicted as being located outside infrastructure system 110, it should be understood that infrastructure server 302 may be located inside infrastructure system 110. It should also be understood that the components of infrastructure server 302 are not limited to the optimal vehicle route allocation component 304, vehicle attitude, obstacle, and route selection data component 306, and database 308, and may include more or fewer components.

[0048] In one or more embodiments, the vehicle-side AVM algorithm 122 is configured to monitor the exchange of states between vehicle 102 and at least vehicle attitude, obstacle, and route selection data components 306 associated with infrastructure system 110. It should be understood that the states may include boarding states (e.g., identification states), maneuvering states, or disembarking states. However, it should also be understood that the states may include any number of grouping states related to the communication relationship between vehicle 102 and infrastructure system 110. As an example, the monitoring of state exchange is performed using a state stream identification process comprising one or more messages.

[0049] In one or more embodiments, the vehicle-side AVM algorithm 122 is configured to monitor the IMM and VMM exchanged between the vehicle 102 and at least the optimal vehicle route allocation component 304 associated with the infrastructure system 110 to determine one or more characteristics associated with the one or more messages. For example, one or more characteristics may include patterns associated with one or more messages, distances associated with one or more messages, and / or radio frequency related behaviors, or combinations thereof. As another example, one or more messages are wirelessly exchanged between the vehicle 102 and the infrastructure system 110 via broadcast, unicast, multicast, or combinations thereof. It should be understood that the database 308 may be a mass storage device and / or system memory, such as a hard disk drive, memory card, solid-state drive, random access memory (RAM), or combinations thereof. It should also be understood that the database 308 is configured to store information (e.g., data) associated therein with each of the optimal vehicle route allocation component 304 and / or vehicle attitude, obstacles, and route selection data component 306.

[0050] In addition to being configured to communicate with infrastructure system 110, infrastructure server 302 is also configured to communicate with vehicle manufacturing cloud system 104. For example... Figure 3 As shown, the vehicle manufacturing cloud system 104 may include a vehicle start / stop component 310. For example, the infrastructure system 110 may use a combination of one or more sensors 114 and vehicle sensors (e.g., onboard sensor 204) to autonomously guide the vehicle 102 toward a waypoint. As another example, the guidance of the vehicle 102 may include a stop or start command based on one or more instructions transmitted from the vehicle start / stop component 310 to the vehicle 102 (e.g., via the infrastructure system 110). However, it should be understood that one or more instructions may be transmitted directly from the vehicle start / stop component 310 to the vehicle 102.

[0051] The vehicle-side AVM algorithm 122 is also configured to perform analysis associated with the exchange of one or more messages and / or the exchange of states. For example, the analysis is used to determine the exit state of vehicle 102, which occurs when vehicle 102 leaves geofence region 312. As another example, the analysis is used to determine the boarding state of vehicle 102, which occurs when vehicle 102 enters (e.g., or re-enters) geofence region 312. As yet another example, the analysis may include algorithmic functions associated with any type of wireless communication means, such as, but not limited to, cellular vehicle-to-the-outside (CV2X-PC5), cellular, Uu, ultra-wideband (UWB), and Bluetooth. ®Low-power (BLE), GNSS, or radio frequency-based communications. However, it should be understood that the analysis may also include algorithmic functions associated with some wired means.

[0052] The vehicle-side AVM algorithm 122 is further configured to generate (e.g., create) a geofence region 312. For example, the geofence region 312 is a boundary based on virtual dynamic radio frequency (RF). As another example, the geofence region 312 is a dynamic virtual geographic region of the operational area associated with the marshalling environment 314. As yet another example, the vehicle-side algorithm 122 utilizes GNSS and / or RF-based wireless communication to generate the geofence region 312.

[0053] The vehicle-side AVM algorithm 122 is also configured to generate bounding boxes 316 (e.g., virtual vehicle layout boxes). For example, the generation (e.g., creation) of the bounding box 316 may be based on ranging locations derived from message exchanges (e.g., exchanges of IMM and VMM) between one or more nodes 318 of the vehicle 102 and one or more anchor points 320 associated with the marshalling environment 314. As an example, one or more nodes 318 may correspond to or represent onboard sensors 204.

[0054] For example, each of the one or more anchor points 320 may be a transceiver configured to transmit and / or receive any communication-related messages (e.g., instructions, signals, etc.). As an example, the infrastructure system 110 and the one or more anchor points 320 are communicatively coupled via a wired connection. As another example, each of the one or more anchor points 320 is also communicatively coupled to each other via a wired connection. However, it should be understood that the one or more anchor points 320 may be wirelessly coupled to each other and / or wirelessly coupled to the infrastructure system 110. For example, the one or more anchor points 320 may be positioned at any distance from each other throughout the marshalling environment 314. As another example, the one or more anchor points 320 may be embedded within the floor of the marshalling environment 314. However, it should be understood that the one or more anchor points 320 may also be positioned on top of the floor of the marshalling environment 314 (e.g., not embedded within the floor). It should also be understood that one or more anchor points 320 may be set in various ways, such as, but not limited to, some of the anchor points 320 being embedded in the floor of the grouping environment 314 and some of the anchor points 320 being set on top of the floor of the grouping environment 314.

[0055] In one or more embodiments, vehicle 102 is configured to communicate with one or more roadside units (RSUs) 322 when vehicle 102 is grouped through (e.g., approaching) grouping environment 314. As yet another example, one or more RSUs 322 are configured to facilitate communication between vehicle 102 and infrastructure system 110 and / or vehicle manufacturing cloud system 104. As yet another example, one or more RSUs 322 are also configured to extend network connectivity to support communication between vehicle 102 and infrastructure system 110 and / or vehicle manufacturing cloud system 104.

[0056] In one or more embodiments, vehicle 102 may be grouped toward geofenced area 312 and may be caused to enter geofenced area 312 via chassis conveyor 324. However, it should be understood that vehicle 102 may enter geofenced area 312 by any means. For example, geofenced area 312 may represent an area within an operational design domain associated with grouping environment 314. When vehicle 102 enters geofenced area 312, vehicle-side algorithm 122 may initiate a boarding process with infrastructure system 110. However, it should be understood that a boarding process may also be initiated before or after vehicle 102 enters geofenced area 312. Vehicle-side algorithm 122 is configured to transmit a request for a specific message (e.g., IMM message query) to at least infrastructure system 110 upon entering geofenced area 312. Vehicle-side algorithm 122 is also configured to transmit an alert to infrastructure system 110 via one or more VMM messages upon entering geofenced area 312. It should be understood that the vehicle-side algorithm 122 can also transmit a request for a specific message in one or more messages (e.g., an IMM message query) when the vehicle 102 re-enters the geofenced area 312. It should also be understood that the vehicle-side algorithm 122 can also transmit an alert to the infrastructure system 110 via one or more VMM messages when the vehicle 102 re-enters the geofenced area 312.

[0057] Once vehicle 102 successfully boards the vehicle infrastructure system 110, it can cross the geofenced area 312 to park at various workstations located therein. Workstations may include, but are not limited to, alignment stations 326, one or more maintenance bays 328, or customer acceptance lines 330. It should be understood that one or more nodes 318 and / or one or more RSUs 322 can assist the infrastructure system 110 and / or the vehicle marshalling cloud system 104 in marshalling vehicle 102 across the geofenced area 312.

[0058] When vehicle 102 is grouped through geofenced area 312, vehicle-side algorithm 122 is configured to determine (e.g., calculate) and / or analyze a first set of one or more characteristics associated with one or more messages exchanged between vehicle 102 and one or more RSUs 322. For example, the first set of one or more characteristics may include congestion level, received signal strength indicator level, provider service identifier, ranging distance, or a combination thereof. As another example, vehicle-side algorithm 122 utilizes CV2X-PC5 wireless communication that supports the exchange of one or more messages between vehicle 102 and one or more RSUs 322 to determine the first set of one or more characteristics.

[0059] When vehicle 102 is grouped through geofence region 312, vehicle-side algorithm 122 is also configured to determine and / or analyze a second set of one or more characteristics associated with one or more messages exchanged between vehicle 102 and one or more macro-identifiers (e.g., cellular Uu base stations or any type of base station providing coverage to an area associated with a wireless communication network). For example, the second set of one or more characteristics may include changes in frequency latches, changes in physical cell identifiers received from neighboring cells, RF correlation performance, latency, round-trip time, inter-packet gap, signal strength degradation, signal-to-interference-to-noise ratio, interference, packet loss, throughput, or combinations thereof. As another example, vehicle-side algorithm 122 utilizes cellular Uu wireless communication supporting the exchange of one or more messages between vehicle 102 and one or more macro-identifiers to determine the second set of one or more characteristics.

[0060] Additionally, vehicle-side algorithm 122 is configured to determine and / or analyze a third set of one or more characteristics associated with one or more messages exchanged between vehicle 102 and one or more anchor points 320. For example, the third set of one or more characteristics may include information (e.g., data) associated with precise ranging distance, received signal strength indicators, or combinations thereof. As another example, vehicle-side algorithm 122 utilizes UWB and / or BLE wireless communications supporting the exchange of one or more messages between vehicle 102 and one or more anchor points 320 to determine the third set of one or more characteristics.

[0061] When vehicle 102 leaves geofenced area 312, vehicle-side algorithm 122 can initiate an abort procedure using infrastructure system 110. However, it should be understood that the abort procedure can also be initiated before or after vehicle 102 leaves geofenced area 312. When vehicle 102 leaves geofenced area 312, vehicle-side algorithm 122 also causes vehicle 102 to transmit an alarm (e.g., one or more signals) to vehicle manufacturing cloud system 104 and / or infrastructure system 110. For example, the alarm notifies vehicle manufacturing cloud system 104 and / or infrastructure system 110 that vehicle 102 will abort from infrastructure system 110.

[0062] In one or more embodiments, the vehicle-side algorithm 122 is configured to notify at least the vehicle manufacturing cloud system 104 of radio frequency (RF) related performance metrics (e.g., a first set of one or more features, a second set of one or more features, a third set of one or more features, or a combination thereof). In another one or more embodiments, the vehicle-side algorithm 122 is also configured to generate a timestamp and a virtual dynamic RF-based coverage heatmap associated with the marshalling environment 314. For example, the RF-based coverage heatmap is generated in response to a verification of the position of vehicle 102 based on snapshot data matching between the coordinates (e.g., X, Y, and / or Z coordinates) of vehicle 102 and the position of vehicle 102.

[0063] In one or more embodiments, the vehicle-side algorithm 122 is also configured to notify the infrastructure system 110, based on analysis, that the vehicle 102 has initiated the disembarkation process. The vehicle-side algorithm 122 is also configured to notify the infrastructure system 110, based on analysis, that the vehicle will cease requesting specific messages in one or more messages (e.g., IMM message queries and / or VMM message alerts).

[0064] Figure 4 This is a flowchart illustrating an example method 400 for monitoring, analyzing, and notifying a vehicle (e.g., vehicle 102) of its disembarkation status. At operation 402, the exchange of one or more messages with an infrastructure system (e.g., infrastructure system 110) is monitored. For example, the exchange of one or more messages is monitored via a vehicle grouping algorithm (e.g., vehicle-side AVM algorithm 122). In one or more embodiments, monitoring the exchange of one or more messages includes monitoring at least one of the following: patterns associated with the one or more messages, distances associated with the one or more messages, radio frequency-related behaviors associated with the one or more messages, or combinations thereof.

[0065] At operation 404, analysis of one or more messages is performed. In one or more embodiments, the analysis of one or more messages includes determining one or more characteristics (e.g., a first set of one or more characteristics) associated with one or more messages exchanged between a vehicle and one or more roadside units (e.g., one or more RSUs 322) and / or determining one or more characteristics (e.g., a third set of one or more characteristics) associated with one or more messages exchanged between a vehicle and one or more transmission points (e.g., one or more anchor points 320). For example, the one or more characteristics associated with the one or more messages exchanged between the vehicle and the one or more roadside units and / or the one or more transmission points include congestion level, received signal strength indicator level, PSID, ranging distance, frequency latch variation, variation of physical cell identifier received from neighboring cells, RF correlation performance, delay, RTT, IPG, signal strength degradation, signal-to-interference-to-noise ratio, interference, packet loss, throughput, or a combination thereof.

[0066] At operation 406, a virtual dynamic boundary (e.g., geofence region 312) is generated. For example, based on the analysis of one or more messages, the virtual dynamic boundary is associated with a grouping environment (e.g., grouping environment 314). At operation 408, the vehicle is dismounted in response to its current location being outside the virtual dynamic boundary.

[0067] In one or more embodiments, the vehicle is boarded in response to its current location re-entering the virtual dynamic boundary. In one or more embodiments, state transitions of the vehicle are monitored. For example, state transitions include vehicle disembarkation and vehicle boarding. In one or more embodiments, analysis of one or more messages is transmitted to a cloud system (e.g., vehicle manufacturing cloud system 104). For example, the transmission of analysis includes snapshot data associated with the vehicle's current location. As another example, timestamps and / or real-time heatmaps of the virtual dynamic boundary are generated based on the transmission of analysis.

[0068] Figure 5An operating environment facilitating the execution of one or more systems and methods described herein is illustrated. More specifically, the systems and methods described herein may be implemented using computing device 502. For example, computing device 502 may 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 502 are not exhaustive, and computing device 502 may be any type of processing or computing device. Computing device 502 typically includes a processor 504, a display adapter 506, one or more input / output ports 508, one or more input / output components 510, a network adapter 512, a power supply 514, and memory 516. However, it should be understood that computing device 502 may include any of the listed components, and is not required to include any of them.

[0069] Processor 504 is configured to provide instructions to computing device 502, enabling computing device 502 to perform 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 502 may include any number of processors 504. Display adapter 506 may be a graphics card or video board that provides computing device 502 with the ability to display content on display device 518. For example, display device 518 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, mainframe, wearable computer, supercomputer, or a combination thereof. However, it should be understood that the foregoing examples of display device 518 are not exhaustive, and display device 518 may be any type of device capable of providing visual display.

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

[0071] Network adapter 512 can be any type of network interface controller configured to provide means for communicating with another computing device (such as remote computing device 522) via network 520. For example, remote computing device 522 can be a user device such as a cellular phone, smartphone, tablet computer, laptop computer, or a combination thereof. Power supply 514 is configured to convert alternating high-voltage current (e.g., AC) into direct current (e.g., DC) to provide power to other components of computing device 502 (e.g., processor 504, display adapter 506, one or more input / output ports 508, one or more input / output components 510, network adapter 512, and memory 516).

[0072] Additionally, memory 516 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 516 is configured to provide storage for instructions and data associated with the operation of computing device 502. Memory 516 may typically include operating system 524, state transition software 526, and state transition data 528 to perform one or more operations as described in more detail herein. For example, operating system 524 is configured to manage and / or process any of the data and / or instructions associated with state transition software 526 and / or state transition data 528, as described in more detail herein.

[0073] Furthermore, a system bus 530 is also included within the computing device 502, configured to couple each of the various components of the computing device 502 (e.g., processor 504, display adapter 506, one or more input / output ports 508, one or more input / output components 510, network adapter 512, power supply 514, and memory 516). It should also be understood that the functions associated with each component of the computing device 502 and with each component of the computing device 502 can be implemented within a remote computing device 522. AlthoughFigure 5 The operating environment shown herein depicts a specific configuration associated with at least computing device 502, network 520, and remote computing device 522; however, it should be understood that the operating environment can be configured in any manner.

[0074] Therefore, one or more examples of this disclosure provide an apparatus for monitoring, analyzing, and notifying a vehicle’s alighting status, at least based on generating a geofenced area within an operational design domain and determining whether a vehicle is inside or outside the boundary of the geofenced area such that it can perform an boarding or alighting status.

[0075] 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.

[0076] 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".

[0077] 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.

[0078] 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).

[0079] 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.

[0080] 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.

[0081] According to the present invention, one or more non-transitory computer-readable media storing processor-executable instructions, which, when executed by at least one processor, cause the at least one processor to: monitor the exchange of one or more messages with an infrastructure system via a vehicle grouping algorithm; perform analysis of the one or more messages; generate a virtual dynamic boundary associated with a grouping environment based on the analysis of the one or more messages; and disembark the vehicle in response to the vehicle's current position being outside the virtual dynamic boundary.

[0082] According to an embodiment, the at least one processor also causes the vehicle to board in response to the vehicle's current position re-entering the virtual dynamic boundary.

[0083] According to an embodiment, the at least one processor is also configured to monitor state transitions of the vehicle, wherein the state transitions include the alighting from the vehicle and the boarding of the vehicle.

[0084] According to an embodiment, the at least one processor monitoring the exchange of the one or more messages is also caused to monitor at least one of the following: a pattern associated with the one or more messages, a distance associated with the one or more messages, radio frequency related behavior associated with the one or more messages, or a combination thereof.

[0085] According to an embodiment, the at least one processor that analyzes one or more messages is further caused to: determine one or more characteristics associated with the one or more messages exchanged between the vehicle and one or more roadside units; and determine one or more characteristics associated with the one or more messages exchanged between the vehicle and one or more transmission points, wherein the one or more characteristics associated with the one or more messages exchanged between the vehicle and the one or more roadside units and the one or more transmission points include congestion level, received signal strength indicator level, PSID, ranging distance, frequency latch variation, physical cell identifier variation received from neighboring cells, radio frequency correlation performance, delay, RTT, IPG, signal strength degradation, signal-to-interference-to-noise ratio, interference, packet loss, throughput, or a combination thereof.

[0086] According to an embodiment, the at least one processor is also configured to: transmit the analysis of the one or more messages to a cloud system, wherein the transmission of the analysis includes snapshot data associated with the current location of the vehicle; and generate a timestamp and a virtual dynamic real-time heatmap based on the transmission of the analysis.

Claims

1. A method comprising: monitoring, by a vehicle marshaling algorithm of a vehicle, an exchange of one or more messages with an infrastructure system; performing an analysis of the one or more messages; generating, based on the analysis of the one or more messages, a virtual dynamic boundary associated with a marshaling environment; and causing the vehicle to deboard in response to a current location of the vehicle being outside of the virtual dynamic boundary.

2. The method of claim 1, further comprising: causing the vehicle to board in response to the current location of the vehicle reentering the virtual dynamic boundary.

3. The method of claim 2, further comprising: monitoring state transitions of the vehicle, wherein the state transitions include the deboarding of the vehicle and the boarding of the vehicle.

4. The method of claim 1, wherein monitoring the exchange of the one or more messages comprises: monitoring at least one of a pattern associated with the one or more messages, a distance associated with the one or more messages, a radio frequency related behavior associated with the one or more messages, or a combination thereof.

5. The method of claim 1, wherein the analysis of the one or more messages comprises: determining one or more characteristics associated with the one or more messages exchanged between the vehicle and one or more wayside units.

6. The method of claim 1, wherein the analysis of the one or more messages comprises: determining one or more characteristics associated with the one or more messages exchanged between the vehicle and one or more transmission points.

7. The method of claim 6, wherein the one or more characteristics associated with the one or more messages exchanged between the vehicle and one or more wayside units and the one or more transmission points include a congestion level, a received signal strength indicator level, a PSID, a ranging distance, a change in frequency lock, a change in a physical cell identifier received from a neighboring cell, a radio frequency related performance, a latency, a RTT, an IPG, a degradation in signal strength, a signal to interference noise ratio, an interference, a packet loss, a throughput, or a combination thereof.

8. The method of claim 1, further comprising: transmitting the analysis of the one or more messages to a cloud system, wherein the transmitting of the analysis includes snapshot data associated with the current location of the vehicle; and causing a timestamp and a virtual dynamic real-time heat map to be generated based on the transmitting of the analysis.

9. A system comprising: an infrastructure system configured to receive one or more messages from a vehicle; and a vehicle system configured to: monitor, by a vehicle marshaling algorithm of the vehicle, an exchange of the one or more messages with the infrastructure system, perform an analysis of the one or more messages, generate, based on the analysis of the one or more messages, a virtual dynamic boundary associated with a marshaling environment, and cause the vehicle to deboard in response to a current location of the vehicle being outside of the virtual dynamic boundary.

10. The system of claim 9, wherein the vehicle system is further configured to: ​ causing the vehicle to de-board in response to the current location of the vehicle re-entering the virtual dynamic boundary.

11. The system of claim 10, wherein the vehicle system is further configured to: monitor state transitions of the vehicle, wherein the state transitions include the de-boarding of the vehicle and the boarding of the vehicle by the vehicle.

12. The system of claim 9, wherein the vehicle system configured to monitor the exchange of the one or more messages is further configured to: monitor at least one of a pattern associated with the one or more messages, a distance associated with the one or more messages, a radio frequency related behavior associated with the one or more messages, or a combination thereof.

13. The system of claim 9, wherein the vehicle system configured to analyze the one or more messages is further configured to: determine one or more characteristics associated with the one or more messages exchanged between the vehicle and one or more roadside units; and determine one or more characteristics associated with the one or more messages exchanged between the vehicle and one or more transmission points.

14. The system of claim 13, wherein the one or more characteristics associated with the one or more messages exchanged between the vehicle and the one or more roadside units and the one or more transmission points include a congestion level, a received signal strength indicator level, a PSID, a ranging distance, a change in frequency lock, a change in physical cell identifier received from a neighboring cell, a radio frequency related performance, a latency, a RTT, an IPG, a degradation in signal strength, a signal to interference noise ratio, an interference, a packet loss, a throughput, or a combination thereof.

15. The system of claim 9, wherein the vehicle system is further configured to: transmit the analysis of the one or more messages to a cloud system, wherein the transmission of the analysis includes snapshot data associated with the current location of the vehicle; and cause a timestamp and a virtual dynamic real-time heat map to be generated based on the transmission of the analysis.

Images