New Field of View: Development of the Prerequisites
Field of View - Development of the Prerequisites
Introduction – Advanced Sensing Technology - Field of View Concept Development
In the realm of the necessary prerequisites (including “Field of View”) for the Occupant Sensing System, there are elements related to the development of the requirements for the execution of high-vehicle functions, such as Occupant Detection, Location and Classification. In order to derive the set of requirements for a specific sensor and the overall subsystem, it is necessary to review what is given (potentially constant) for the application. It begins with the review of the vehicle geometry:
- Specifically, height of the vehicle for the best position of the sensor placement
- Followed by the Volume related to the vehicle size to determine the necessary sensor coverage
Consequently, this article delves on the definition of the “Field of View” concept to assist in the development of the sensor requirements. Fundamentally, this is necessary for the potential technology applications intended to monitor occupants’ behavior around and within the Vehicle Interior for the Vehicle level Occupant Protection functions.
General Review: Vehicle Geometry
Conversely, overall review of the general population of the contemporary vehicles may yield interesting observations (see the referenced website for more information and pictures below). Sequentially, presented here are examples of the dimensions taken from the pictures:
- Starting from the lowest to tallest height is found to be: from 1196 mm to 1990 mm
- Looking at the length – from shortest to longest: from 3700 mm to 4904 mm
- The width from the narrowest to the widest: from 1665 mm to 1945 mm
Consequently, the overall sensing capabilities shall account for these general parameters. In addition, for example, the sensor placed in the center of the roof shall oversee the Field of View necessary for the Vehicle level defined functions, including some volume outside and most of the occupiable volume inside.
Reference website: https://www.automobiledimension.com/
Content to be covered in the Usecases:
Basically, reiterating the article covering the development of the Usecases, here are the relevant notes (see the referenced article):
- Starting with all of the Occupant related scenarios
- Including, all of the Vehicle based behaviors
- Additionally, all potential environmental influences, weather, temperature, light and dark time of the day, etc.
- Other possible combinations
- Etc.
Generally, it is preferably to already have the library of the Usecases to pull from. Consequently, decide on their applicability to the content of the functions for specific Vehicle Variant. Possibly, modify or add Usecases, as necessary. For example, the Van may have the rear entrance door, while the small car may not. Moreover, there is always an opportunity to add a new scenario related to the occupant behavior related to the specific Vehicle Variant.
Defining Necessary Coverage: “Field of View” and “Boundary Condition”
Having established the general parameters for the definition of the sensor Field of View, it is relevant to actually define the specific Field of View for the specific application. Consequently, It would be the Vehicle size will define the Field of View. Therefore, specifying the coverage necessary for the subsystem capability to facilitate the data acquisition right after the power initiation. Hence, this is true for the Vehicle Variant application (and intended remote functions): the Field of View is the Volume of space, where the Data Acquisition can be executed with the expected level of reliability and collected until the criteria for the signal output is achieved / verified.
Once established properly – the Field of View (for the content, which is expected functionality based on the remote sensing), it will influence the decision making related to choosing the single sensor or sensor array, necessary to cover the defined volume.
In addition, for the specific Vehicle Variant – there is a need to define the “Boundary condition” related to the Vehicle Interior and decision-making criteria related to the simple Occupant Presence within the Field of View. Therefore, the “Boundary condition” can be defined as: the Vehicle Interior Surfaces and the plane of the entries, within which the occupant can be judged as Present in the Vehicle.
Finally, the concept of “Boundary condition” is necessary for the Presence Detection function specifically, also basic logic which will carry over the known status of the Occupants for other functions and communication purposes.
Notes – Corner Cases Examples Discussion
Firstly, let’s briefly mention that in certain condition or a Usecase, it is possible for the Occupant within the Field of View to be not visible for the sensor, or decision on the presence cannot be made properly or on time. Either due to the occlusion / interference or time of processing, initiation of power, or some other condition. Therefore, this can be considered a corner case and needs to be investigated to understand to root causes and potential solutions.
Consequently, here is an example scenario:
A person is in a process to get into the vehicle. The Vehicle is stationary, the Power is On and the data acquisition is taking place. The person is within the Field of View and in process of crossing the Boundary Condition. While he is in motion, the decision on his presence cannot be made. Unless, there is criteria set based on the size (classification of the body) already established – for the presence based on the fraction of the classified size. (This level of sophistication is possible but needs to be developed.
Continuing with the scenario:
While person is in transition across the Boundary Condition, there is instantaneous event taking place. Either another vehicle crashes or even some medical condition occurs, as the result of which the person loses consciousness.
The Notification Feature, tasked with communicating to the third party, shall make an assessment and execute the communication information set. Including the following answers to the functions related to the Occupant Protection (referencing the picture):
- Are these people present in the vehicle?
- Where are they located
- Other applications of the known presence and location possible
Logically, both presence and location of the half present occupant would be judged against the Boundary Condition criteria set.
Notes on the Potential AI Application:
See the references:
Referencing Virtual Development: https://georgedallen.com/virtual-development-embracing-tomorrow-today/
Referencing “Virtualization” definition: https://en.wikipedia.org/wiki/Virtualization
Conclusion: Field of View as the Requirement for the Sensor Selection
In conclusion, the establishment of the Field of View for the specific Vehicle Variant is one of the fundamental prerequisites. It is not difficult to derive from the given vehicle geometry and approved functional content. The same sensing capabilities maybe used for the progressive and self-verifiable logic-protocol with possibility to execute several functions serving various Vehicle Features (see references).
The Boundary condition is a derivative of the Vehicle Interior (volume) and easily comprehended. However, the System’s logic needs to be developed to include it as a logical requirements. In addition, it will be applicable to the possible Usecases, in order to support the overall system processing and decision-making.
References:
- The Systems Engineering Method: https://georgedallen.com/navigating-chaos-systems-engineering-in-vehicle-occupant-sensing/
- Develop System Requirements: https://georgedallen.com/new-system-function-development-of-clear-requirements/
- Develop Vehicle Level Requirement: https://georgedallen.com/development-of-clear-requirements-new-vehicle-function/
- Development of Prerequisites: https://georgedallen.com/development-of-the-prerequisites-new-passive-safety-features/
- Development of Usecases: https://georgedallen.com/usecases-development-of-the-prerequisites-new-databases/
- Utilization of the Usecase: https://georgedallen.com/utilization-of-the-usecase-deep-dive-new-technology-development/
- Passive Safety Features: https://georgedallen.com/development-of-the-prerequisites-new-passive-safety-features/
About George D. Allen Consulting:
George D. Allen Consulting is a pioneering force in driving engineering excellence and innovation within the automotive industry. Led by George D. Allen, a seasoned engineering specialist with an illustrious background in occupant safety and systems development, the company is committed to revolutionizing engineering practices for businesses on the cusp of automotive technology. With a proven track record, tailored solutions, and an unwavering commitment to staying ahead of industry trends, George D. Allen Consulting partners with organizations to create a safer, smarter, and more innovative future. For more information, visit www.GeorgeDAllen.com.
Contact:
Website: www.GeorgeDAllen.com
Email: inquiry@GeorgeDAllen.com
Phone: 248-509-4188
Unlock your engineering potential today. Connect with us for a consultation.
