Systems, apparatus, methods, and computer program products for stabilized vehicle-related interface components

Abstract

Systems, apparatuses, methods, and computer program products are provided herein. For example, a method may include receiving head motion data from a wearable device. In some embodiments, the method includes generating eye movement data by applying the head movement data to an eye movement determination model. In some embodiments, the method includes detecting device motion data associated with a device. In some embodiments, the method includes generating vehicle-related stability data by applying the eye motion data and the device motion data to a vehicle-related stability model. In some embodiments, the method includes generating a stabilized vehicle-related interface component based on the vehicle-related stabilization data and vehicle-related device display data. In some embodiments, the method includes presenting the stabilized vehicle-related interface component to an interface of the device.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 593,860, filed October 27, 2023, and Indian Provisional Patent Application No. 202411057947, filed July 31, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The embodiments disclosed herein relate in general to systems, apparatus, methods, and computer program products for stable vehicle-related interface components. Background Technology

[0004] The applicant has recognized the numerous technical challenges and difficulties associated with unstable vehicle-related interface components. Through exerted effort, ingenuity, and innovation, the applicant has addressed the problems related to unstable vehicle-related interface components by developing solutions embodied in this disclosure, which are described in detail below. Summary of the Invention

[0005] The various implementation schemes described herein relate to systems, apparatuses, methods, and computer program products for stable vehicle-related interface components.

[0006] According to one aspect of this disclosure, a method is provided. In some embodiments, the method includes receiving head motion data from a wearable device. In some embodiments, the wearable device is in contact with an occupant of a vehicle. In some embodiments, the method includes generating eye motion data by applying the head motion data to an eye motion determination model. In some embodiments, the method includes detecting device motion data associated with the device. In some embodiments, the method includes generating vehicle-related stability data by applying the eye motion data and the device motion data to a vehicle-related stability model. In some embodiments, the method includes generating a stable vehicle-related interface component based on the vehicle-related stability data and vehicle-related device display data. In some embodiments, the method includes rendering the stable vehicle-related interface component onto the device's interface.

[0007] In some implementations, head movement data is received when the vehicle is in motion.

[0008] In some implementations, the method includes remapping one or more touch areas based on eye movement data and device motion data.

[0009] In some implementations, the equipment is a vehicle-mounted device.

[0010] In some implementations, the on-board vehicle equipment is physically fixed to the vehicle.

[0011] In some embodiments, the device is a mobile device.

[0012] In some embodiments, the wearable device is in contact with at least a portion of the head of the occupant.

[0013] In some embodiments, the wearable device is at least one of eyewear, earphones, or a head-mounted display.

[0014] In some embodiments, the method includes identifying vehicle-related device display data.

[0015] In some embodiments, the method includes generating a vehicle-related interface component based on the vehicle-related device display data.

[0016] In some embodiments, the method includes causing the vehicle-related interface component to be presented to an interface of the device.

[0017] In some embodiments, the head motion data is received from the wearable device in response to an occupant unstable action or a vehicle unstable event.

[0018] In some embodiments, the stable vehicle-related interface component includes one or more stable vehicle-related device display items.

[0019] In some embodiments, the eye motion determination model includes a vestibulo-ocular reflex model.

[0020] According to another aspect of the disclosure, an apparatus is provided. In some embodiments, the apparatus includes a memory and one or more processors communicatively coupled to the memory. In some embodiments, the one or more processors are configured to receive head motion data from a wearable device. In some embodiments, the wearable device is in contact with an occupant of a vehicle. In some embodiments, the one or more processors are configured to generate eye motion data by applying the head motion data to an eye motion determination model. In some embodiments, the one or more processors are configured to detect device motion data associated with the device. In some embodiments, the one or more processors are configured to generate vehicle-related stabilization data by applying the eye motion data and the device motion data to a vehicle-related stabilization model. In some embodiments, the one or more processors are configured to generate a stable vehicle-related interface component based on the vehicle-related stabilization data and vehicle-related device display data. In some embodiments, the one or more processors are configured to cause the stable vehicle-related interface component to be presented to an interface of the device.

[0021] In some embodiments, the head motion data is received while the vehicle is in motion.

[0022] In some embodiments, the one or more processors are configured to remap the one or more touch regions based on the eye motion data and the device motion data.

[0023] In some embodiments, the device is a vehicle-mounted vehicle device or a mobile device.

[0024] In some embodiments, the wearable device is in contact with at least a portion of the head of the occupant.

[0025] In some embodiments, the wearable device is at least one of eyewear, earphones, or a head-mounted display.

[0026] In some embodiments, the head motion data is received from the wearable device in response to an occupant unstable action or a vehicle unstable event.

[0027] According to another aspect of the disclosure, a computer program product is provided. In some embodiments, the computer program product includes at least one non-transitory computer-readable storage medium having computer program code stored thereon. In some embodiments, the computer program code, when executed with at least one processor, configures the computer program product to receive head motion data from a wearable device. In some embodiments, the wearable device is in contact with an occupant of a vehicle. In some embodiments, the computer program code, when executed with at least one processor, configures the computer program product to generate eye motion data by applying the head motion data to an eye motion determination model. In some embodiments, the computer program code, when executed with at least one processor, configures the computer program product to detect device motion data associated with the device. In some embodiments, the computer program code, when executed with at least one processor, configures the computer program product to generate vehicle-related stability data by applying the eye motion data and the device motion data to a vehicle-related stability model. In some embodiments, the computer program code, when executed with at least one processor, configures the computer program product to generate a stabilized vehicle-related interface component based on the vehicle-related stability data and vehicle-related device display data. In some embodiments, the computer program code, when executed with at least one processor, configures the computer program product for causing the stabilized vehicle-related interface component to be presented to an interface of the device.

[0028] The foregoing summary is provided only to introduce some example embodiments and is not intended to limit the scope of the disclosure or the protection sought. Thus, it should be appreciated that the foregoing is a summary of only some embodiments and is not to be considered an exhaustive list of possibilities or ways to implement the disclosure. It should also be appreciated that the scope of the disclosure is not limited to only those embodiments summarized above, but rather, the scope of the disclosure encompasses many possible embodiments, some of which are described further below. BRIEF DESCRIPTION OF DRAWINGS

[0029] Reference will now be made to the drawings. Components shown in the Figures can or can not be present in certain embodiments described herein. Some embodiments can include fewer (or more) than those components shown in the Figures according to example embodiments of the present disclosure.

[0030] Figure 1 An example block diagram illustrating an environment in which embodiments of the present disclosure can operate is shown;

[0031] Figure 2 An example block diagram illustrating an example apparatus that can be specially configured according to one or more embodiments of the present disclosure is shown;

[0032] Figure 3 An example interface component according to one or more embodiments of the present disclosure is shown;

[0033] Figure 4 An interface component according to one or more embodiments of the present disclosure is shown;

[0034] Figure 5 A flow diagram of an example method according to one or more embodiments of the present disclosure is shown; and

[0035] Figure 6 A flow diagram of an example method according to one or more embodiments of the present disclosure is shown. DETAILED DESCRIPTION

[0036] Some embodiments of the disclosure will now be described with reference to the drawings, in which some embodiments of the disclosure are shown. It should be appreciated, however, that the disclosure is not limited in scope to the embodiments illustrated, but rather the embodiments are intended as examples. Moreover, further embodiments of the disclosure will become apparent to those of ordinary skill in the art upon reading the contents of this disclosure. Various embodiments of the disclosure are described in detail below.

[0037] As used herein, the term “including” means including, but not limited to, and should be interpreted in the manner described in U.S. Patent law and to mean the inclusion of elements, but not the exclusion of other non-enumerated elements. The use of the term “comprising” (and other like terms such as “comprises” or “composed of”) should be interpreted as a mere provision of chosen features that can be used in some embodiments, but can not necessarily be used in other embodiments.

[0038] The phrases “in one embodiment,” “according to one embodiment,” “in some embodiments,” and the like generally mean that the particular feature, structure, or characteristic following the phrase can be included in at least one embodiment of the present disclosure, and can be included in more than one embodiment of the present disclosure (importantly, such phrases are not necessarily referring to the same embodiment).

[0039] The words “example” or “exemplary” are used herein to mean “serving as an example, instance, or illustration.” Any implementation described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other implementations.

[0040] If the specification states a component, or feature “may,” “could,” “should,” “would,” “can,” “typically,” “optionally,” “exemplary,” “usually,” “often,” “probably,” “typically,” “optionally,” “for example,” “generally,” or “potentially” (or other such language) be included or have a property, it is not required for the specific component or feature to be included or have the property. Such a component or feature can be optionally included in some embodiments, or it can be excluded.

[0041] Use of the term “circuitry” as used herein with respect to components of a system or device should be understood to include specific hardware configured to carry out the functions associated with the particular circuitry as described herein. The term “circuitry” should be interpreted broadly to encompass both a purely hardware circuit implementation, as well as a hardware circuit solution combined with software, in some embodiments. For example, in some embodiments, “circuitry” can include processing circuitry, communication circuitry, input / output circuitry, etc. In some embodiments, other elements can provide or supplement the functionality of a particular circuitry. Alternatively or additionally, in some embodiments, other elements of the systems and / or devices described herein can provide or supplement the functionality of another particular circuitry group. For example, a processor can provide processing functionality to any of the circuitry groups, a memory can provide storage functionality to any of the circuitry groups, a communication circuit can provide network interface functionality to any of the circuitry groups, etc.

[0042] SUMMARY

[0043] The example implementations disclosed herein address technical problems associated with unstable vehicle-related interface components. As will be appreciated by those skilled in the art to which this disclosure pertains, there are many example scenarios in which a vehicle-related interface component is desired.

[0044] In many applications, it can be desirable to use a vehicle-related interface component. For example, it can be desirable to use a vehicle-related interface component associated with a vehicle-mounted vehicle device (e.g., a device that is a component of a vehicle). As another example, it can be desirable to use a vehicle-related interface component associated with a mobile device (e.g., a personal device of an occupant in a vehicle). In some implementations, it can be desirable to use a vehicle-related interface component to facilitate using a vehicle to travel from a first location to a second location (e.g., using the vehicle-related interface component while the vehicle is in motion).

[0045] In some implementations, a vehicle-related interface component can be affected by an occupant unstable motion and / or a vehicle unstable event. In some implementations, an occupant unstable motion and / or a vehicle unstable event can reduce the utility of a vehicle-related interface component because an occupant unstable motion and / or a vehicle unstable event can cause such a vehicle-related interface component to become unstable (e.g., the vehicle-related interface component can shake and / or blur). For example, an occupant unstable motion and / or a vehicle unstable event can cause a vehicle-related interface component to become unstable such that information displayed on the vehicle-related interface component cannot be read by an occupant of the vehicle (e.g., an operator of the vehicle, a passenger of the vehicle, etc.). As another example, an occupant unstable motion and / or a vehicle unstable event can cause a vehicle-related interface component to become unstable such that an occupant of the vehicle cannot use the vehicle-related interface component while the vehicle is in motion (e.g., to facilitate using the vehicle to travel from a first location to a second location). As another example, an occupant unstable motion and / or a vehicle unstable event can cause a vehicle-related interface component to become unstable such that an occupant of the vehicle is affected by motion sickness (e.g., due to the shaking and / or blurring of the vehicle-related interface component). Accordingly, there is a need for systems, apparatuses, methods, and computer program products for generating a stable vehicle-related interface component even when a vehicle-related interface component is affected by an occupant unstable motion and / or a vehicle unstable event.

[0046] Accordingly, to address these and / or other issues related to vehicle-related interface components, example systems, devices, methods, and computer program products for generating stabilized vehicle-related interface components are disclosed herein. For example, embodiments of the present disclosure described in greater detail below include a method comprising receiving head motion data from a wearable device. In some embodiments, the wearable device is in contact with an occupant of a vehicle. In some embodiments, the method comprises generating eye motion data by applying the head motion data to an eye motion determination model. In some embodiments, the method comprises detecting device motion data associated with the device. In some embodiments, the method comprises generating vehicle-related stabilization data by applying the eye motion data and the device motion data to a vehicle-related stabilization model. In some embodiments, the method comprises generating a stabilized vehicle-related interface component based on the vehicle-related stabilization data and vehicle-related device display data. In some embodiments, the method comprises causing the stabilized vehicle-related interface component to be presented to an interface of the device. Accordingly, the systems, devices, methods, and computer program products for stabilized vehicle-related interface components provided herein enable stabilized vehicle-related interface components even when the vehicle-related interface components are affected by occupant destabilizing actions and / or vehicle destabilizing events.

[0047] Example systems and apparatus

[0048] Embodiments of the present disclosure include systems, devices, methods, and computer program products configured for displaying stabilization herein. It should be readily appreciated that embodiments of the devices, systems, methods, and computer program products described herein can be configured in various additional and alternative ways beyond those explicitly described herein.

[0049] Figure 1 An example block diagram of an environment 100 in which embodiments of the present disclosure can operate is shown. Specifically, Figure 1 A vehicle 110 is shown. In some embodiments, the vehicle 110 can describe any machine, robot, computing device, and / or apparatus composed of hardware, software, firmware, and / or any combination thereof that is maneuvered throughout an environment by any medium. In some cases, the vehicle is used to transport an object, entity (e.g., a person, animal, or other living being), or other on-board cargo. In some cases, the vehicle can not transport an object other than the vehicle itself. The vehicle can be used for transportation on land, in water, in air, or any other medium. Examples of vehicles include an airplane, helicopter, drone, car, truck, submarine, boat, etc. The vehicle is not limited to the examples listed herein and can include any type of transportation device.

[0050] In some embodiments, vehicle 110 is associated with a determinable location. In some embodiments, the determinable location of vehicle 110 represents an absolute location (e.g., GPS coordinates, latitude and longitude location, address, etc.) or a relative location (e.g., an identifier representing a location of vehicle 110 compared to one or more other vehicles, one or more buildings (e.g., a destination of vehicle 110), corporate headquarters, or a general description in the world (e.g., based at least in part on a continent, country, ocean, or other definable region)) of vehicle 110. In some embodiments, vehicle 110 includes and / or is otherwise associated with a location sensor and / or a software-driven location service that provides location data corresponding to vehicle 110. In other embodiments, the location of vehicle 110 is stored and / or otherwise determinable to one or more systems.

[0051] In some embodiments, environment 100 includes occupant 102. In some embodiments, occupant 102 is in vehicle 110 (e.g., occupant 102 is an occupant of vehicle 110). In some embodiments, occupant 102 is an operator of vehicle 110. For example, occupant 102 can be a pilot, a driver, etc. of vehicle 110. In some embodiments, occupant 102 is a passenger of vehicle 110 (e.g., an occupant of vehicle 110 who is not an operator of vehicle 110). In some embodiments, occupant 102 is in vehicle 110 when vehicle 110 is in motion. For example, occupant 102 can be in vehicle 110 traveling from a first location to a second location.

[0052] In some embodiments, environment 100 includes wearable device 140. In some embodiments, wearable device 140 includes eyewear. For example, wearable device 140 can be a pair of smart glasses. In some embodiments, wearable device 140 includes earphones. For example, wearable device 140 can be a pair of over-ear headphones. As another example, wearable device 140 can be a pair of earbuds. In some embodiments, wearable device 140 can include a head-mounted display. For example, wearable device can include a wearable device configured to provide real-world images, virtual reality images, augmented reality images, mixed reality images, etc. to occupant 102. In some embodiments, wearable device is in contact with occupant 102. In some embodiments, wearable device 140 is in contact with at least a portion of a head of occupant 102.

[0053] In some embodiments, the wearable device 140 includes a wearable device sensing component 160A. In some embodiments, the wearable device sensing component 160A is disposed within the wearable device 140. In some embodiments, the wearable device sensing component 160A is configured to capture data associated with the occupant 102. In some embodiments, the wearable device sensing component 160A is configured to capture head motion data associated with the occupant 102. In this regard, for example, the wearable device sensing component 160A includes at least one lidar component configured to capture head motion data and / or other data associated with the occupant 102. As another example, the wearable device sensing component 160A includes at least one inertial measurement unit configured to capture head motion data and / or other data associated with the occupant 102. As another example, the wearable device sensing component 160A includes at least one accelerometer configured to capture head motion data and / or other data associated with the occupant 102. As another example, the wearable device sensing component 160A includes at least one gyroscope configured to capture head motion data and / or other data associated with the occupant 102. As another example, the wearable device sensing component 160A includes at least one radar component (e.g., a millimeter wave-based radar component) configured to capture head motion data and / or other data associated with the occupant 102. As another example, the wearable device sensing component 160A includes at least one global positioning system (GPS) component configured to capture head motion data and / or other data associated with the occupant 102. As another example, the wearable device sensing component 160A includes at least one camera configured to capture head motion data and / or other data associated with the occupant 102.

[0054] In some embodiments, the environment 100 includes an in-vehicle vehicle device 130. In some embodiments, the in-vehicle vehicle device 130 is electronically and / or communicatively coupled to the vehicle 110, the mobile device 150, and / or the wearable device 140. The in-vehicle vehicle device 130 can be located within the vehicle 110. In some embodiments, the in-vehicle vehicle device 130 is physically affixed to the vehicle 110. For example, the in-vehicle vehicle device 130 can be a component of the vehicle 110, such as a center console display. In some embodiments, the in-vehicle vehicle device 130 is configured to provide information associated with the vehicle 110 to the occupant 102. For example, the in-vehicle vehicle device 130 can be configured to provide the speed of the vehicle 110 to the occupant 102. Additionally or alternatively, the in-vehicle vehicle device 130 is configured to provide information associated with the occupant 102 to the occupant 102. In some embodiments, the in-vehicle vehicle device 130 is configured via hardware, software, firmware, and / or a combination thereof to perform one or more types of data ingestion of data, such as head motion data, eye motion data, device motion data, vehicle-related device display data, and the like.

[0055] Additionally or alternatively, in some embodiments, the in-vehicle vehicle device 130 is configured via hardware, software, firmware, and / or a combination thereof to generate and / or transmit commands that control, adjust, or otherwise affect the operation of one or more of the vehicle 110, the in-vehicle vehicle device 130, the mobile device 150, and / or the wearable device 140. For example, the in-vehicle vehicle device 130 can be configured to generate a stabilized vehicle-related interface component. Additionally or alternatively, in some embodiments, the in-vehicle vehicle device 130 is configured via hardware, software, firmware, and / or a combination thereof to perform data reporting, provide data, and / or other data output processes associated with monitoring or otherwise analyzing the operation of one or more of the vehicle 110, the in-vehicle vehicle device 130, the mobile device 150, and / or the wearable device 140. For example, in various embodiments, the in-vehicle vehicle device 130 can be configured to perform and / or carry out one or more operations and / or functions described herein.

[0056] In some embodiments, the on-vehicle vehicle device 130 includes an on-vehicle vehicle device sensing component 160B. In some embodiments, the on-vehicle vehicle device sensing component 160B is disposed within the on-vehicle vehicle device 130. In some embodiments, the on-vehicle vehicle device sensing component 160B is configured to capture data associated with the on-vehicle vehicle device 130. In some embodiments, the on-vehicle vehicle device sensing component 160B is configured to capture device motion data associated with the on-vehicle vehicle device 130. In this regard, for example, the on-vehicle vehicle device sensing component 160B includes at least one lidar component configured to capture device motion data and / or other data associated with the on-vehicle vehicle device 130. As another example, the on-vehicle vehicle device sensing component 160B includes at least one inertial measurement unit configured to capture device motion data and / or other data associated with the on-vehicle vehicle device 130. As another example, the on-vehicle vehicle device sensing component 160B includes at least one accelerometer configured to capture device motion data and / or other data associated with the on-vehicle vehicle device 130. As another example, the on-vehicle vehicle device sensing component 160B includes at least one gyroscope configured to capture device motion data and / or other data associated with the on-vehicle vehicle device 130. As another example, the on-vehicle vehicle device sensing component 160B includes at least one radar component (e.g., a millimeter wave-based radar component) configured to capture device motion data and / or other data associated with the on-vehicle vehicle device 130. As another example, the on-vehicle vehicle device sensing component 160B includes at least one global positioning system (GPS) component configured to capture device motion data and / or other data associated with the on-vehicle vehicle device 130. As another example, the on-vehicle vehicle device sensing component 160B includes at least one camera configured to capture device motion data and / or other data associated with the on-vehicle vehicle device 130.

[0057] In some embodiments, environment 100 includes mobile device 150. In some embodiments, mobile device 150 is electronically and / or communicatively coupled to vehicle 110, in-vehicle vehicle devices 130, and / or wearable device 140. Mobile device 150 can be located within vehicle 110. In some embodiments, mobile device 150 is mobile and can be removed from vehicle 110. In some embodiments, mobile device 150 is associated with occupant 102. For example, mobile device 150 can be a personal device of occupant 102. In some embodiments, mobile device 150 is not physically affixed to vehicle 110. In some embodiments, mobile device 150 is configured to provide information associated with vehicle 110 to occupant 102. Additionally or alternatively, mobile device 150 is configured to provide information associated with occupant 102 to occupant 102. For example, mobile device 150 can be configured to provide travel directions for vehicle 110 and / or occupant 102 to occupant 102. In some embodiments, mobile device 150 is configured via hardware, software, firmware, and / or combinations thereof to perform one or more types of data ingestion of data, such as head motion data, eye motion data, device motion data, vehicle-related device display data, and the like.

[0058] Additionally or alternatively, in some embodiments, mobile device 150 is configured via hardware, software, firmware, and / or combinations thereof to generate and / or transmit commands that control, adjust, or otherwise affect the operation of one or more of vehicle 110, mobile device 150, in-vehicle vehicle devices 130, and / or wearable device 140. For example, mobile device 150 can be configured to generate stabilized vehicle-related interface components. Additionally or alternatively, in some embodiments, mobile device 150 is configured via hardware, software, firmware, and / or combinations thereof to perform data reporting, provide data, and / or other data output processes associated with monitoring or otherwise analyzing the operation of one or more of vehicle 110, mobile device 150, in-vehicle vehicle devices 130, and / or wearable device 140. For example, in various embodiments, mobile device 150 can be configured to perform and / or implement one or more operations and / or functions described herein.

[0059] In some embodiments, the mobile device 150 includes a mobile device sensing component 160C. In some embodiments, the mobile device sensing component 160C is disposed within the mobile device 150. In some embodiments, the mobile device sensing component 160C is configured to capture data associated with the mobile device 150. In some embodiments, the mobile device sensing component 160C is configured to capture device motion data associated with the mobile device 150. In this regard, for example, the mobile device sensing component 160C includes at least one lidar component configured to capture device motion data and / or other data associated with the mobile device 150. As another example, the mobile device sensing component 160C includes at least one inertial measurement unit configured to capture device motion data and / or other data associated with the mobile device 150. As another example, the mobile device sensing component 160C includes at least one accelerometer configured to capture device motion data and / or other data associated with the mobile device 150. As another example, the mobile device sensing component 160C includes at least one gyroscope configured to capture device motion data and / or other data associated with the mobile device 150. As another example, the mobile device sensing component 160C includes at least one radar component (e.g., a millimeter wave-based radar component) configured to capture device motion data and / or other data associated with the mobile device 150. As another example, the mobile device sensing component 160C includes at least one global positioning system (GPS) component configured to capture device motion data and / or other data associated with the mobile device 150. As another example, the mobile device sensing component 160C includes at least one camera configured to capture device motion data and / or other data associated with the mobile device 150.

[0060] Furthermore, although Figure 1 While certain components are shown as separate, standalone entities, the various embodiments are not limited to this configuration. In other embodiments, one or more components can be directly connected and / or shared hardware, etc.

[0061] Figure 2 An example block diagram of an example apparatus that can be specially configured in accordance with example embodiments of the present disclosure is shown. Specifically, Figure 2An example computing device 200 (“device 200”) configured specifically in accordance with at least some example embodiments of the present disclosure is depicted. For example, the computing device 200 can be embodied as one or more of a specially configured personal computing device, a specially configured cloud-based computing device, a specially configured embedded computing appliance (e.g., configured for edge computing, etc.). Examples of the device 200 can include, but are not limited to, the mobile device 150, the in-vehicle vehicle device 130, and / or the wearable device 140. The device 200 includes a processor 202, a memory 204, input / output circuitry 206, communication circuitry 208, and / or optional artificial intelligence (“AI”) and machine learning circuitry 210. In some embodiments, the device 200 is configured to perform and carry out the operations described herein.

[0062] While components are described with respect to functional limitations, it should be understood that a particular implementation necessarily includes the use of particular computing hardware. It should also be understood that, in some embodiments, certain of the components described herein include similar or common hardware. For example, in some embodiments, both sets of circuitry utilize the use of the same processor, memory, circuitry, etc. to carry out their associated functions, such that each set of circuitry does not require duplicative hardware.

[0063] In various embodiments, the computing device 200, such as the mobile device 150, the in-vehicle vehicle device 130, and / or the wearable device 140, can refer to, for example, one or more computers, computing entities, desktop computers, mobile phones, tablet computers, phablets, notebooks, laptops, distributed systems, servers, etc., and / or any combination of devices or entities suitable for carrying out the functionality, operations, and / or processes described herein. Such functionality, operations, and / or processes can include, for example, transmitting, receiving, operating, processing, displaying, storing, determining, creating / generating, monitoring, evaluating, comparing, and / or similar terms that can be used herein. In one embodiment, these functionality, operations, and / or processes can be carried out on data, content, information, and / or similar terms that can be used herein. In this regard, as described herein, the device 200 embodies a specially configured particular computing entity that is transformed to enable the particular operations described herein and provide the particular advantages associated therewith.

[0064] The processor 202, or processor circuit 202, can be embodied in a number of different ways. In various embodiments, the use of the term“processor” should be understood as including a single core processor, multi-core processors, multiple processors in a device 200, and / or one or more remote or“cloud” processors in various embodiments. In some example embodiments, the processor 202 can include one or more processing devices configured to function independently. Alternatively or additionally, the processor 202 can include one or more processors configured in series via a bus to enable independent execution of operations, instructions, pipelines, and / or multithreading.

[0065] In example embodiments, the processor 202 can be configured to execute instructions stored in the memory 204 or otherwise accessible to the processor. Alternatively or additionally, the processor 202 can be configured to execute hard coded functionality. Thus, whether configured by hardware or software methods, or by a combination thereof, the processor 202 can represent an entity capable of performing operations according to embodiments of the present disclosure while configured accordingly. Alternatively or additionally, the processor 202 can be embodied as a

[0066] In some embodiments, the processor 202 (and / or a co-processor, or any other processing circuitry that assists the processor or is otherwise associated with the processor) communicates with the memory 204 via a bus for passing information among the components of the device 200.

[0067] The memory 204, or memory circuit 204, can be non-transitory and can include, for example, one or more volatile memory and / or non-volatile memory. In some embodiments, the memory 204 includes or embodies electronic storage devices (e.g., computer readable storage medium). In some embodiments, the memory 204 is configured to store information, data, content, applications, instructions, etc. for enabling the device 200 to perform various operations and / or functions in accordance with example embodiments of the present disclosure.

[0068] Input / output circuitry 206 can be included in the apparatus 200. In some embodiments, the input / output circuitry 206 can provide output to the user and / or receive input from the user. The input / output circuitry 206 can communicate with the processor 202 to provide such functionality. The input / output circuitry 206 can include one or more user interfaces. In some embodiments, a user interface can include a display screen that includes an interface to a web user interface, an application program user interface, a user device, a backend system. In some embodiments, the input / output circuitry 206 also includes a keyboard, a mouse, a joystick, a touch screen, a touch area, soft keys, a microphone, a speaker, or other input / output mechanisms. The processor 202 and / or the input / output circuitry 206 including a processor can be configured to control one or more operations and / or functions of one or more user interface elements through computer program instructions (e.g., software and / or firmware) stored on a memory accessible to the processor, such as, for example, memory 204 or the like. In some embodiments, the input / output circuitry 206 includes or utilizes a user-facing application program to provide input / output functionality to a computing device and / or other display associated with a user.

[0069] Communication circuitry 208 can be included in the apparatus 200. The communication circuitry 208 can include any means for communicating data from / to a network and / or any other device, circuit, or module in communication with the apparatus 200, such as devices or circuits embodied in hardware or a combination of hardware and software that are configured to receive and / or transmit data from / to the network and / or any other device, circuit, or module in communication with the apparatus 200. In some embodiments, the communication circuitry 208 includes, for example, a network interface for enabling communications with a wired or wireless communication network. Additionally or alternatively, the communication circuitry 208 can include one or more network interface cards, antennas, buses, switches, routers, modems, and supporting hardware, firmware, and / or software, or any other devices that are suitable for supporting communications via one or more communication networks. In some embodiments, the communication circuitry 208 can include circuitry for interacting with an antenna and / or other hardware or software in order to cause transmission of signals via the antenna and / or to process received signals from the antenna. In some embodiments, the communication circuitry 208 enables transmission and / or reception of data to and / or from a user device, one or more sensors, and / or other external computing devices in communication with the apparatus 200.

[0070] Data ingestion circuitry 212 can be included in device 200. Data ingestion circuitry 212 can include hardware, software, firmware, and / or combinations thereof designed and / or configured to capture, receive, request, and / or otherwise collect data associated with operations of vehicle 110. In some embodiments, data ingestion circuitry 212 includes hardware, software, firmware, and / or combinations thereof that communicates with one or more sensor components, etc. within vehicle 110 to receive particular data associated with such operations of vehicle 110. Additionally or alternatively, in some embodiments, data ingestion circuitry 212 includes hardware, software, firmware, and / or combinations thereof that retrieves particular data associated with vehicle 110 from one or more data repositories accessible to device 200.

[0071] AI and machine learning circuitry 210 can be included in device 200. AI and machine learning circuitry 210 can include hardware, software, firmware, and / or combinations thereof designed and / or configured to request, receive, process, generate, and transmit data, data structures, control signals, and electronic information for training and executing trained AI and machine learning models configured to facilitate operations and / or functionality described herein. For example, in some embodiments, AI and machine learning circuitry 210 includes hardware, software, firmware, and / or combinations thereof that identifies training data and / or utilizes such training data to train particular machine learning models, AI, and / or other models to generate particular output data based at least in part on learning from the training data. Additionally or alternatively, in some embodiments, AI and machine learning circuitry 210 includes hardware, software, firmware, and / or combinations thereof that embodies or retrieves trained machine learning models, AI, and / or other specially configured models for processing input data. Additionally or alternatively, in some embodiments, AI and machine learning circuitry 210 includes hardware, software, firmware, and / or combinations thereof that utilizes one or more algorithms, functions, subroutines, etc. in one or more pre-processing and / or subsequent operations that do not require utilization of machine learning or AI models to process received data.

[0072] Data output circuitry 214 can be included in the apparatus 200. The data output circuitry 214 can include hardware, software, firmware, and / or combinations thereof that configure and / or generate outputs based at least in part on data processed by the apparatus 200. In some embodiments, the data output circuitry 214 includes hardware, software, firmware, and / or combinations thereof that generate a particular report based at least in part on the processed data, e.g., where the report is generated based at least in part on a particular reporting protocol. Additionally or alternatively, in some embodiments, the data output circuitry 214 includes hardware, software, firmware, and / or combinations thereof that configure particular output data objects, output data files, and / or user interfaces for storage, transmission, and / or display. For example, in some embodiments, the data output circuitry 214 generates and / or specifically configures particular data outputs for transmission to another system subsystem for further processing. Additionally or alternatively, in some embodiments, the data output circuitry 214 includes hardware, software, firmware, and / or combinations thereof that cause a specially configured user interface to be presented based at least in part on data received and / or processed by the apparatus 200.

[0073] In some embodiments, two or more of the groups of circuitry 202-214 are combinable. Alternatively or additionally, one or more of the groups of circuitry 202-214 perform some or all of the operations and / or functionality described herein as being associated with another circuit. In some embodiments, two or more of the groups of circuitry 202-214 are combined into a single module embodied in hardware, software, firmware, and / or combinations thereof. For example, in some embodiments, one or more of the groups of circuitry (e.g., the AI and machine learning circuitry 210) are combinable with the processor 202 such that the processor 202 performs one or more of the operations described herein with respect to the AI and machine learning circuitry 210.

[0074] In some embodiments, the in-vehicle vehicle device 130 and / or the mobile device 150 are configured to identify vehicle-related device display data. In some embodiments, the vehicle-related device display data includes one or more data items that represent and / or indicate one or more vehicle-related device display items 304. In some embodiments, a vehicle-related device display item is an item that is configured to be displayed on an interface component to convey and / or indicate information. For example, a vehicle-related device display item can include an image (e.g., a still image), a video, a composite image, a virtual reality image, an extended reality image, an augmented reality image, and / or the like. In this regard, in some embodiments, a vehicle-related device display item is a display item that indicates a speed associated with the vehicle 110. For example, a vehicle-related device display item can be a display item that indicates a speed at which the vehicle 110 is moving. In some embodiments, a vehicle-related device display item is a display item that indicates a fuel amount associated with the vehicle 110. For example, a vehicle-related device display item can be a display item that indicates a fuel amount in the vehicle 110. In some embodiments, a vehicle-related device display item is a display item that indicates an engine parameter associated with the vehicle 110. For example, a vehicle-related device display item can be a display item that indicates an engine temperature of an engine of the vehicle 110.

[0075] In some embodiments, a vehicle-related device display item is a display item that indicates a navigation map associated with the vehicle 110. For example, a vehicle-related device display item can be a display item that indicates a map of an area surrounding the vehicle 110. As another example, a vehicle-related device display item can be a display item that indicates a flight path of the vehicle 110 (e.g., when the vehicle 110 is an aircraft). In some embodiments, a vehicle-related device display item is a display item that indicates an audio control associated with the vehicle 110. For example, a vehicle-related device display item can be a display item that can be used to adjust an audio volume in the vehicle 110. In some embodiments, a vehicle-related device display item is a display item that indicates a display control associated with the vehicle 110. For example, a vehicle-related device display item can be a display item that can be used to adjust a brightness of an interface component in the vehicle 110.

[0076] In some embodiments, the vehicle-related device display items are display items that indicate videos associated with the occupant 102 of the vehicle 110. For example, the vehicle- related device display items can be display items that convey videos being viewed by the occupant 102 of the vehicle 110. In some embodiments, the vehicle-related device display items are display items that indicate internet information associated with the occupant 102 of the vehicle 110. For example, the vehicle-related device display items can be display items that indicate whether the in-vehicle vehicle device 130 and / or the mobile device 150 are connected to the internet. In some embodiments, the vehicle-related device display items are display items that indicate documents associated with the occupant 102 of the vehicle 110. For example, the vehicle- related device display items can be display items that convey documents being viewed by the occupant 102 of the vehicle 110. In some embodiments, the vehicle-related device display items are display items that indicate communications associated with the occupant 102 of the vehicle 110. For example, the vehicle-related device display items can be display items that convey text messages being viewed by the occupant 102 of the vehicle 110.

[0077] Additionally or alternatively, the vehicle-related device display data includes one or more data items that represent and / or indicate the one or more touch areas 306. For example, a touch area of the one or more touch areas 306 can be configured to be used to select one or more of the one or more vehicle-related device display items 304. In this regard, for example, the one or more touch areas 306 can be configured to control the vehicle 110, the in-vehicle vehicle device 130, and / or the mobile device 150.

[0078] In some embodiments, the in-vehicle vehicle device 130 and / or the mobile device 150 are configured to generate the vehicle-related interface component 302. In some embodiments, the vehicle-related interface component 302 is generated based on the vehicle-related device display data. In this regard, in some embodiments, the vehicle-related interface component 302 includes at least one of the one or more vehicle-related device display items 304. In some embodiments, each of the one or more vehicle-related device display items 304 is associated with an original display item location on the vehicle-related interface component 302. In this regard, for example, the original display item location can be a location on the vehicle-related interface component 302 at which the vehicle-related device display item is displayed on and / or located on the vehicle-related interface component 302.

[0079] In some embodiments, the vehicle-related interface component 302 includes one or more touch areas 306. In some embodiments, the one or more touch areas 306 are selectable portions of the vehicle-related interface component 302. For example, the one or more touch areas 306 can be selectable to display information about a vehicle-related device display item of the one or more vehicle-related device display items 304. In some embodiments, the one or more touch areas 306 are associated with an original touch area location on the vehicle-related interface component 302. In this regard, for example, the original touch area location can be a location on the vehicle-related interface component 302 at which a touch area of the one or more touch areas 306 is displayed on and / or positioned on the vehicle-related interface component 302 (e.g., touching the original touch area location can select the touch area).

[0080] In some embodiments, the in-vehicle vehicle device 130 and / or the mobile device 150 are configured such that the vehicle-related interface component 302 is presented to the interface 300, such as Figure 3 In some embodiments, the vehicle-related interface component 302 is presented to the interface 300 of the device. In some embodiments, the vehicle-related interface component 302 is presented to the interface 300 of the in-vehicle vehicle device 130. In this regard, for example, when the vehicle-related interface component 302 is presented to the interface 300 of the in-vehicle vehicle device 130, the vehicle-related interface component 302 can include a vehicle-related device display item indicative of a fuel amount associated with the vehicle 110. In some embodiments, the vehicle-related interface component 302 is presented to the interface 300 of the mobile device 150. In this regard, for example, when the vehicle-related interface component 302 is presented to the interface 300 of the mobile device 150, the vehicle-related interface component 302 can include a vehicle-related device display item indicative of a communication associated with the occupant 102 of the vehicle 110.

[0081] In some embodiments, the in-vehicle vehicle device 130 and / or the mobile device 150 are configured to receive head motion data. In some embodiments, the head motion data includes one or more data items representative of and / or indicative of motion of the head 120 of the occupant 102. In this regard, in some embodiments, the head motion data includes one or more data items representative of and / or indicative of acceleration motion (e.g., motion in the X, Y, and / or Z axes) of the head 120 of the occupant 102. Additionally or alternatively, the head motion data includes one or more data items representative of and / or indicative of angular motion (e.g., azimuth, elevation, and / or roll motion) of the head 120 of the occupant 102.

[0082] In some embodiments, the head motion data is received by the in-vehicle vehicle device 130 and / or the mobile device 150 in response to a passenger unstable action. In some embodiments, the passenger unstable action is an action of the occupant 102 of the vehicle 110 that causes acceleration motion (e.g., motion in the X, Y, and / or Z axes) and / or angular motion (e.g., azimuth, elevation, and / or roll motion) of the occupant 102 (e.g., the head 120 of the occupant 102) and / or the mobile device 150. For example, the passenger unstable action can be an action of the occupant 102 that includes causing acceleration motion and / or angular motion of the head 120 of the occupant 102 (e.g., rotating the head 120 to look at something). As another example, the passenger unstable action can be an action of the occupant 102 that includes causing acceleration motion and / or angular motion of the mobile device 150 (e.g., moving the mobile device while using the mobile device 150).

[0083] Additionally or alternatively, the head motion data is received by the in-vehicle vehicle device 130 in response to a vehicle unstable event. In some embodiments, the vehicle unstable event is an event in which motion of the vehicle 110 causes acceleration motion (e.g., motion in the X, Y, and / or Z axes) and / or angular motion (e.g., azimuth, elevation, and / or roll motion) of the vehicle 110, the occupant 102 (e.g., the head 120 of the occupant 102), the in-vehicle vehicle device 130, and / or the mobile device 150. For example, the vehicle unstable event can be an event that includes driving on a road that causes acceleration motion and / or angular motion of the vehicle 110, the occupant 102 (e.g., the head 120 of the occupant 102), the in-vehicle vehicle device 130, and / or the mobile device 150 (e.g., driving on a bumpy road, etc.).

[0084] In some embodiments, the in-vehicle vehicle device 130 and / or the mobile device 150 is configured to receive head motion data from the wearable device 140. In this regard, in some embodiments, the wearable device 140 is configured to capture head motion data using the wearable device sensing component 160A. For example, the in-vehicle vehicle device 130 and / or the mobile device 150 can be configured to receive head motion data from the wearable device 140 that captures the head motion data using an inertial measurement unit included in the wearable device sensing component 160A. In this regard, in some embodiments, the in-vehicle vehicle device 130 and / or the mobile device 150 is configured to correct for any drift associated with the inertial measurement unit included in the wearable device sensing component 160A. In some embodiments, the in-vehicle vehicle device 130 and / or the mobile device 150 is configured to receive head motion data from the wearable device 140 when the wearable device 140 is in contact with the occupant 102. In some embodiments, the in-vehicle vehicle device 130 and / or the mobile device 150 is configured to receive head motion data from the wearable device 140 when the wearable device 140 is in contact with the head 120 of the occupant 102. In some embodiments, the in-vehicle vehicle device 130 and / or the mobile device 150 is configured to receive head motion data from the wearable device 140 when the vehicle 110 is in motion (e.g., when the vehicle 110 travels from a first location to a second location).

[0085] In some embodiments, the in-vehicle vehicle device 130 and / or the mobile device 150 is configured to generate eye motion data. In some embodiments, the eye motion data includes one or more data items that represent and / or indicate eye gaze motion of the occupant 102. In this regard, in some embodiments, the eye motion data includes one or more data items that represent and / or indicate acceleration motion (e.g., motion in the X, Y, and / or Z axis) of the eye gaze of the occupant 102. In some embodiments, the acceleration motion (e.g., motion in the X, Y, and / or Z axis) of the eye gaze of the occupant 102 is caused by occupant instability action and / or vehicle instability event. Additionally or alternatively, the eye motion data includes one or more data items that represent and / or indicate angular motion (e.g., azimuth, elevation, and / or roll motion) of the eye gaze of the occupant 102. In some embodiments, the angular motion (e.g., azimuth, elevation, and / or roll motion) of the eye gaze of the occupant 102 is caused by occupant instability action and / or vehicle instability event.

[0086] In some embodiments, the eye motion data is generated by applying the head motion data to an eye motion determination model. In some embodiments, the eye motion determination model is a data entity that describes parameters, hyperparameters, and / or defined operations of a rule-based and / or machine learning model configured to generate the eye motion data. In this regard, in some embodiments, the eye motion determination model is configured to utilize one or more of any type of machine learning, rule-based, and / or artificial intelligence techniques, including one or more of computer vision techniques, supervised learning (e.g., using user feedback), unsupervised learning, semi-supervised learning, reinforcement learning, computer vision techniques, sequence modeling techniques, language processing techniques, neural network techniques, generative artificial intelligence techniques, filtering techniques, grouping techniques, ranking techniques, trending techniques, correlation techniques, anomaly detection techniques, clustering techniques, etc. In some embodiments, the eye motion determination model includes a vestibulo-ocular reflex model. In this regard, in some embodiments, the eye motion determination model is configured to determine an acceleration motion (e.g., motion in X, Y, and / or Z axes) and / or an angular motion (e.g., azimuth, elevation, and / or roll motion) of the eye gaze of the occupant 102.

[0087] In some embodiments, the in-vehicle vehicle device 130 and / or the mobile device 150 is configured to detect device motion data. In some embodiments, the device motion data includes one or more data items representative of and / or indicative of motion of the in-vehicle vehicle device 130. In this regard, in some embodiments, the device motion data includes one or more data items representative of and / or indicative of acceleration motion (e.g., motion in X, Y, and / or Z axes) of the in-vehicle vehicle device 130. In some embodiments, the acceleration motion (e.g., motion in X, Y, and / or Z axes) of the in-vehicle vehicle device 130 is caused by the vehicle instability event. Additionally or alternatively, the eye motion data includes one or more data items representative of and / or indicative of angular motion (e.g., azimuth, elevation, and / or roll motion) of the in-vehicle vehicle device 130. In some embodiments, the angular motion (e.g., azimuth, elevation, and / or roll motion) of the in-vehicle vehicle device 130 is caused by the vehicle instability event. In some embodiments, the in-vehicle vehicle device 130 and / or the mobile device 150 is configured to detect the device motion data using the in-vehicle vehicle device sensing components 160B.

[0088] Additionally or alternatively, the device motion data includes one or more data items representing and / or indicative of motion of the mobile device 150. In this regard, in some embodiments, the device motion data includes one or more data items representing and / or indicative of acceleration motion (e.g., motion in the X-axis, Y-axis, and / or Z-axis) of the mobile device 150. In some embodiments, the acceleration motion (e.g., motion in the X, Y, and / or Z axis) of the mobile device 150 is caused by the occupant unstable action and / or the vehicle unstable event. Additionally or alternatively, the eye motion data includes one or more data items representing and / or indicative of angular motion (e.g., azimuth, elevation, and / or roll motion) of the mobile device 150. In some embodiments, the angular motion (e.g., azimuth, elevation, and / or roll motion) of the mobile device 150 is caused by the occupant unstable action and / or the vehicle unstable event. In some embodiments, the in-vehicle vehicle device 130 and / or the mobile device 150 are configured to detect the device motion data using the mobile device sensing component 160C.

[0089] In some embodiments, the in-vehicle vehicle device 130 and / or the mobile device 150 are configured to generate vehicle-related stability data. In some embodiments, the vehicle-related stability data includes one or more data items representing and / or indicative of an estimated change in position of an eye gaze of the occupant 102 of the vehicle 110 caused by the occupant unstable action and / or the vehicle unstable event. Additionally or alternatively, the vehicle-related stability data includes one or more data items representing and / or indicative of an estimated change in position of the in-vehicle vehicle device 130 and / or the mobile device 150 caused by the occupant unstable action and / or the vehicle unstable event.

[0090] In some embodiments, the in-vehicle vehicle device 130 and / or the mobile device 150 are configured to generate vehicle-related stabilization data by applying the eye movement data and / or the device movement data to a vehicle-related stabilization model. In some embodiments, the vehicle-related stabilization model is a data entity that describes parameters, hyperparameters, and / or defined operations of a rule-based and / or machine learning model configured to generate the vehicle-related stabilization data. In this regard, in some embodiments, the vehicle-related stabilization model is configured to utilize one or more of any type of machine learning, rule-based, and / or artificial intelligence techniques, including one or more of computer vision techniques, supervised learning (e.g., using user feedback), unsupervised learning, semi-supervised learning, reinforcement learning, computer vision techniques, sequence modeling techniques, language processing techniques, neural network techniques, generative artificial intelligence techniques, filtering techniques, grouping techniques, ranking techniques, trending techniques, correlation techniques, anomaly detection techniques, clustering techniques, and the like. In this regard, in some embodiments, the vehicle-related stabilization model is configured to determine, using the eye movement data and / or the device movement data, an estimated change in position of an eye gaze of the occupant 102 of the vehicle 110 due to occupant destabilizing actions and / or vehicle destabilizing events. Additionally or alternatively, the vehicle-related stabilization model is configured to determine, using the eye movement data and / or the device movement data, an estimated change in position of the in-vehicle vehicle device 130 and / or the mobile device 150 due to occupant destabilizing actions and / or vehicle destabilizing events.

[0091] In some embodiments, the in-vehicle vehicle device 130 and / or the mobile device 150 are configured to generate a stabilized vehicle-related interface component 400. In some embodiments, the stabilized vehicle-related interface component 400 is configured to be generated based on the vehicle-related stabilization data and / or the vehicle-related device display data. In this regard, in some embodiments, the stabilized vehicle-related interface component 400 includes one or more stabilized vehicle-related device display items 404 that correspond to one or more vehicle-related device display items 304. For example, the stabilized vehicle-related interface component 400 can include one or more stabilized vehicle-related device display items 404 that indicate a speed associated with the vehicle 110. As another example, the stabilized vehicle-related interface component 400 can include one or more stabilized vehicle-related device display items 404 that indicate a fuel amount associated with the vehicle 110. As another example, the stabilized vehicle-related interface component 400 can include one or more stabilized vehicle-related device display items 404 that indicate an engine parameter associated with the vehicle 110.

[0092] As another example, the stable vehicle-related interface component 400 can include one or more stable vehicle-related device display items 404 that indicate a navigation map associated with the vehicle 110. As another example, the stable vehicle-related interface component 400 can include one or more stable vehicle-related device display items 404 that indicate an audio control associated with the vehicle 110. As another example, the stable vehicle-related interface component 400 can include one or more stable vehicle-related device display items 404 that indicate a display control associated with the vehicle 110. As another example, the stable vehicle-related interface component 400 can include one or more stable vehicle-related device display items 404 that indicate a video associated with the occupant 102 of the vehicle 110. As another example, the stable vehicle-related interface component 400 can include one or more stable vehicle-related device display items 404 that indicate internet information associated with the occupant 102 of the vehicle 110. As another example, the stable vehicle-related interface component 400 can include one or more stable vehicle-related device display items 404 that indicate a document associated with the occupant 102 of the vehicle 110. As another example, the stable vehicle-related interface component 400 can include one or more stable vehicle-related device display items 404 that indicate a communication associated with the occupant 102 of the vehicle 110.

[0093] In some embodiments, each of the one or more stable vehicle-related device display items 404 is associated with a stable display item location on the stable vehicle-related interface component 400. In this regard, for example, the stable display item location can be a location on the stable vehicle-related interface component 400 at which the stable vehicle-related device display item is displayed on and / or positioned on the stable vehicle-related interface component 400. In some embodiments, the stable display item location can be a different location than the original display item location. In other words, in some embodiments, the stable vehicle-related interface component 400 is configured such that the estimated location changes in the occupant’s 102 eyes gaze of the vehicle 110 and / or the estimated location changes in the in-vehicle vehicle device 130 and / or the mobile device 150 due to occupant unstable actions and / or vehicle unstable events are taken into account when displaying the display item.

[0094] In some embodiments, the stabilized vehicle-related interface component 400 includes one or more remapped touch areas 406. In this regard, in some embodiments, the in-vehicle vehicle device 130 and / or the mobile device 150 are configured to remap one or more touch areas 306 based on the eye movement data and / or the device movement data. In some embodiments, the one or more remapped touch areas 406 are selectable portions of the stabilized vehicle-related interface component 400. For example, the one or more remapped touch areas 406 can be selectable to display information about a stabilized vehicle-related device display item of the one or more stabilized vehicle-related device display items 404.

[0095] In some embodiments, the one or more remapped touch areas 406 are associated with remapped touch area locations on the stabilized vehicle-related interface component 400. In this regard, for example, a remapped touch area location can be a location on the stabilized vehicle-related interface component 400 at which a remapped touch area of the one or more remapped touch areas 406 is displayed on and / or located on the stabilized vehicle-related interface component 400 (e.g., touching the remapped touch area location can select the remapped touch area). In other words, for example, the one or more remapped touch areas 406 can correspond to the one or more touch areas 306 but be located in different locations to account for occupant instability actions and / or vehicle instability events.

[0096] In some embodiments, the in-vehicle vehicle device 130 and / or the mobile device 150 are configured to cause the stabilized vehicle-related interface component 400 to be presented to the interface 300, such as Figure 4 In some embodiments, the stabilized vehicle-related interface component 400 is presented to the interface 300 of the device. In some embodiments, the stabilized vehicle-related interface component 400 is presented to the interface 300 of the in-vehicle vehicle device 130. In this regard, for example, when the stabilized vehicle-related interface component 400 is presented to the interface 300 of the in-vehicle vehicle device 130, the stabilized vehicle-related interface component 400 can include a stabilized vehicle-related device display item indicating a fuel amount associated with the vehicle 110. In some embodiments, the stabilized vehicle-related interface component 400 is presented to the interface 300 of the mobile device 150. In this regard, for example, when the stabilized vehicle-related interface component 400 is presented to the interface 300 of the mobile device 150, the stabilized vehicle-related interface component 400 can include a stabilized vehicle-related device display item indicating a communication associated with the occupant 102 of the vehicle 110.

[0097] Example methods

[0098] Referring now toFigure 5 FIG. 5 shows a flow diagram that provides an example method 500. In this regard, Figure 5 The operations shown can be performed by the in-vehicle vehicle device 130, the mobile device 150, and / or the wearable device 140. In some embodiments, the method 500 includes operations for generating a stabilized vehicle-related interface component, as described above. In some embodiments, the example method 500 defines a computer- implemented process that can be performed by any of the devices and / or systems embodied in hardware, software, firmware, and / or combinations thereof, as described herein. In some embodiments, computer program code comprising one or more computer program instructions is stored in at least one non-transitory computer-readable storage medium such that execution of the computer program code by a computer initiates performance of the method 500.

[0099] As shown in block 502, the method 500 includes receiving head motion data from the wearable device. As described above, in some embodiments, the head motion data includes one or more data items that represent and / or indicate motion of the occupant’s head. In this regard, in some embodiments, the head motion data includes one or more data items that represent and / or indicate translational motion (e.g., motion in the X, Y, and / or Z axes) of the occupant’s head. Additionally or alternatively, the head motion data includes one or more data items that represent and / or indicate angular motion (e.g., azimuth, elevation, and / or roll motion) of the occupant’s head.

[0100] In some embodiments, the head motion data is received by the in-vehicle vehicle device and / or the mobile device in response to an occupant destabilizing action. In some embodiments, the occupant destabilizing action is an action of an occupant of the vehicle that causes translational motion (e.g., motion in the X, Y, and / or Z axes) and / or angular motion (e.g., azimuth, elevation, and / or roll motion) of the occupant (e.g., the occupant’s head) and / or the mobile device. For example, the occupant destabilizing action can be an action of the occupant that includes causing translational motion and / or angular motion of the occupant’s head (e.g., rotating the head to look at something). As another example, the occupant destabilizing action can be an action of the occupant that includes causing translational motion and / or angular motion of the mobile device (e.g., moving the mobile device while using the mobile device).

[0101] Additionally or alternatively, the head motion data is received by the in-vehicle vehicle device in response to a vehicle instability event. In some embodiments, the vehicle instability event is an event in which motion of the vehicle causes acceleration motion (e.g., motion in the X, Y, and / or Z axes) and / or angular motion (e.g., azimuth, elevation, and / or roll motion) of the vehicle, the occupant (e.g., the occupant’s head), the in-vehicle vehicle device, and / or the mobile device. For example, the vehicle instability event can be an event that includes driving on a road that causes acceleration motion and / or angular motion of the vehicle, the occupant (e.g., the occupant’s head), the in-vehicle vehicle device, and / or the mobile device (e.g., driving on a bumpy road, etc.).

[0102] In some embodiments, the in-vehicle vehicle device and / or the mobile device is configured to receive the head motion data from the wearable device. In this regard, in some embodiments, the wearable device is configured to capture the head motion data using the wearable device sensing components. For example, the in-vehicle vehicle device and / or the mobile device can be configured to receive the head motion data from the wearable device that captures the head motion data using an inertial measurement unit included in the wearable device sensing components. In this regard, in some embodiments, the in-vehicle vehicle device and / or the mobile device is configured to correct for any drift associated with the inertial measurement unit included in the wearable device sensing components. In some embodiments, the in-vehicle vehicle device and / or the mobile device is configured to receive the head motion data from the wearable device when the wearable device is in contact with the occupant. In some embodiments, the in-vehicle vehicle device and / or the mobile device is configured to receive the head motion data from the wearable device when the wearable device is in contact with the occupant’s head. In some embodiments, the in-vehicle vehicle device and / or the mobile device is configured to receive the head motion data from the wearable device when the vehicle is in motion (e.g., when the vehicle is driving from a first location to a second location).

[0103] As represented by block 504, the method 500 includes generating eye motion data by applying the head motion data to an eye motion determination model. As noted above, in some embodiments, the eye motion data includes one or more data items representative of and / or indicative of motion of the occupant’s eye gaze. In this regard, in some embodiments, the eye motion data includes one or more data items representative of and / or indicative of acceleration motion (e.g., motion in the X, Y, and / or Z axes) of the occupant’s eye gaze. In some embodiments, the acceleration motion (e.g., motion in the X, Y, and / or Z axes) of the occupant’s eye gaze is caused by occupant instability action and / or vehicle instability event. Additionally or alternatively, the eye motion data includes one or more data items representative of and / or indicative of angular motion (e.g., azimuth, elevation, and / or roll motion) of the occupant’s eye gaze. In some embodiments, the angular motion (e.g., azimuth, elevation, and / or roll motion) of the occupant’s eye gaze is caused by occupant instability action and / or vehicle instability event.

[0104] In some embodiments, the eye motion data is generated by applying the head motion data to an eye motion determination model. In some embodiments, the eye motion determination model is a data entity that describes parameters, hyperparameters, and / or defined operations of a rule-based and / or machine learning model configured to generate the eye motion data. In this regard, in some embodiments, the eye motion determination model is configured to utilize one or more of any type of machine learning, rule-based, and / or artificial intelligence techniques, including one or more of computer vision techniques, supervised learning (e.g., using user feedback), unsupervised learning, semi-supervised learning, reinforcement learning, computer vision techniques, sequence modeling techniques, language processing techniques, neural network techniques, generative artificial intelligence techniques, filtering techniques, grouping techniques, ranking techniques, trend techniques, correlation techniques, anomaly detection techniques, clustering techniques, etc. In some embodiments, the eye motion determination model includes a vestibulo-ocular reflex model. In this regard, in some embodiments, the eye motion determination model is configured to determine acceleration motion (e.g., motion in the X, Y, and / or Z axes) and / or angular motion (e.g., azimuth, elevation, and / or roll motion) of the occupant’s eye gaze.

[0105] As represented by block 506, the method 500 includes detecting device motion data associated with the device. As described above, in some embodiments, the device motion data includes one or more data items representative of and / or indicative of an acceleration motion (e.g., motion in the X-axis, Y-axis, and / or Z-axis) of the in-vehicle vehicle device. In this regard, in some embodiments, the device motion data includes one or more data items representative of and / or indicative of an angular motion (e.g., azimuth, elevation, and / or roll motion) of the in-vehicle vehicle device. In some embodiments, the angular motion (e.g., azimuth, elevation, and / or roll motion) of the in-vehicle vehicle device is caused by the vehicle instability event. Additionally or alternatively, the eye motion data includes one or more data items representative of and / or indicative of an angular motion (e.g., azimuth, elevation, and / or roll motion) of the in-vehicle vehicle device. In some embodiments, the angular motion (e.g., azimuth, elevation, and / or roll motion) of the in-vehicle vehicle device is caused by the vehicle instability event. In some embodiments, the in-vehicle vehicle device and / or the mobile device is configured to detect the device motion data using in-vehicle vehicle device sensing components.

[0106] Additionally or alternatively, the device motion data includes one or more data items representative of and / or indicative of a motion of the mobile device. In this regard, in some embodiments, the device motion data includes one or more data items representative of and / or indicative of an acceleration motion (e.g., motion in the X-axis, Y-axis, and / or Z-axis) of the mobile device. In some embodiments, the acceleration motion (e.g., motion in the X, Y, and / or Z-axis) of the mobile device is caused by the occupant unstable action and / or the vehicle instability event. Additionally or alternatively, the eye motion data includes one or more data items representative of and / or indicative of an angular motion (e.g., azimuth, elevation, and / or roll motion) of the mobile device. In some embodiments, the angular motion (e.g., azimuth, elevation, and / or roll motion) of the mobile device is caused by the occupant unstable action and / or the vehicle instability event. In some embodiments, the in-vehicle vehicle device and / or the mobile device is configured to detect the device motion data using mobile device sensing components.

[0107] As represented by block 508, the method 500 includes generating vehicle-related stability data by applying the eye motion data and the device motion data to a vehicle-related stability model. As described above, in some embodiments, the vehicle-related stability data includes one or more data items representative of and / or indicative of an estimated change in position of an occupant’s eye gaze of the vehicle caused by the occupant unstable action and / or the vehicle instability event. Additionally or alternatively, the vehicle-related stability data includes one or more data items representative of and / or indicative of an estimated change in position of the in-vehicle vehicle device and / or the mobile device caused by the occupant unstable action and / or the vehicle instability event.

[0108] In some embodiments, the in-vehicle vehicle device and / or the mobile device are configured to generate vehicle-related stabilization data by applying the eye movement data and / or the device movement data to a vehicle-related stabilization model. In some embodiments, the vehicle-related stabilization model is a data entity that describes parameters, hyperparameters, and / or defined operations of a rule-based and / or machine learning model configured to generate the vehicle-related stabilization data. In this regard, in some embodiments, the vehicle-related stabilization model is configured to utilize one or more of any type of machine learning, rule-based, and / or artificial intelligence techniques, including one or more of computer vision techniques, supervised learning (e.g., using user feedback), unsupervised learning, semi-supervised learning, reinforcement learning, computer vision techniques, sequence modeling techniques, language processing techniques, neural network techniques, generative artificial intelligence techniques, filtering techniques, grouping techniques, ranking techniques, trending techniques, correlation techniques, anomaly detection techniques, clustering techniques, and the like. In this regard, in some embodiments, the vehicle-related stabilization model is configured to determine, using the eye movement data and / or the device movement data, an estimated change in position of an occupant’s eye gaze of the vehicle due to occupant destabilizing actions and / or vehicle destabilizing events. Additionally or alternatively, the vehicle-related stabilization model is configured to determine, using the eye movement data and / or the device movement data, an estimated change in position of the in-vehicle vehicle device and / or the mobile device due to occupant destabilizing actions and / or vehicle destabilizing events.

[0109] As shown in block 510, the method 500 includes generating a stabilized vehicle-related interface component based on the vehicle-related stabilization data and the vehicle- related device display data. As described above, in some embodiments, the stabilized vehicle- related interface component is configured to be generated based on the vehicle-related stabilization data and / or the vehicle-related device display data. In this regard, in some embodiments, the stabilized vehicle-related interface component includes one or more stabilized vehicle-related device display items corresponding to one or more vehicle-related device display items. For example, the stabilized vehicle-related interface component can include one or more stabilized vehicle-related device display items indicating a speed associated with the vehicle. As another example, the stabilized vehicle-related interface component can include one or more stabilized vehicle-related device display items indicating a fuel amount associated with the vehicle. As another example, the stabilized vehicle-related interface component can include one or more stabilized vehicle-related device display items indicating an engine parameter associated with the vehicle.

[0110] As another example, the stable vehicle-related interface component can include one or more stable vehicle-related device display items that indicate a navigation map associated with the vehicle. As another example, the stable vehicle-related interface component can include one or more stable vehicle-related device display items that indicate an audio control associated with the vehicle. As another example, the stable vehicle-related interface component can include one or more stable vehicle-related device display items that indicate a display control associated with the vehicle. As another example, the stable vehicle-related interface component can include one or more stable vehicle-related device display items that indicate a video associated with an occupant of the vehicle. As another example, the stable vehicle-related interface component can include one or more stable vehicle-related device display items that indicate internet information associated with an occupant of the vehicle. As another example, the stable vehicle-related interface component can include one or more stable vehicle-related device display items that indicate a document associated with an occupant of the vehicle. As another example, the stable vehicle-related interface component can include one or more stable vehicle-related device display items that indicate a communication associated with an occupant of the vehicle.

[0111] In some embodiments, each of the one or more stable vehicle-related device display items is associated with a stable display item location on the stable vehicle-related interface component. In this regard, for example, the stable display item location can be a location on the stable vehicle-related interface component at which the stable vehicle-related device display item is displayed on and / or positioned on the stable vehicle-related interface component. In some embodiments, the stable display item location can be a different location than the original display item location. In other words, in some embodiments, the stable vehicle-related interface component is configured such that the estimated changes in position of the occupant’s eye gaze and / or the in-vehicle vehicle device and / or mobile device due to occupant unstable motion and / or vehicle unstable events are taken into account when displaying the display item.

[0112] As represented by block 512, the method 500 includes causing a stabilized vehicle- related interface component to be presented to an interface of a device. As described above, in some embodiments, the one or more remapped touch areas are selectable portions of the stabilized vehicle-related interface component. For example, the one or more remapped touch areas can be selectable to display information about a stabilized vehicle-related device display item of the one or more stabilized vehicle-related device display items. In some embodiments, the one or more remapped touch areas are associated with a remapped touch area location on the stabilized vehicle-related interface component. In this regard, for example, the remapped touch area location can be a location on the stabilized vehicle-related interface component at which a remapped touch area of the one or more remapped touch areas is displayed on and / or positioned on the stabilized vehicle-related interface component (e.g., touching the remapped touch area location can select the remapped touch area). In other words, for example, the one or more remapped touch areas can correspond to one or more touch areas but be positioned in different locations to account for occupant instability actions and / or vehicle instability events.

[0113] As represented by optional block 514, the method 500 optionally includes remapping one or more touch areas based on eye movement data and device movement data. As described above, in some embodiments, the stabilized vehicle-related interface component is caused to be presented to an interface of a device. In some embodiments, the stabilized vehicle-related interface component is caused to be presented to an interface of an in-vehicle vehicle device. In this regard, for example, when the stabilized vehicle-related interface component is presented to an interface of an in-vehicle vehicle device, the stabilized vehicle-related interface component can include a stabilized vehicle-related device display item indicating a fuel amount associated with the vehicle. In some embodiments, the stabilized vehicle-related interface component is caused to be presented to an interface of a mobile device. In this regard, for example, when the stabilized vehicle-related interface component is presented to an interface of a mobile device, the stabilized vehicle-related interface component can include a stabilized vehicle-related device display item indicating a communication associated with an occupant of the vehicle.

[0114] Referring now to Figure 6 , a flowchart showing an example method 600 is shown. In this regard, Figure 6Operations that can be performed by the in-vehicle vehicle device 130, the mobile device 150, and / or the wearable device 140 are shown. In some embodiments, the method 600 includes operations for generating a vehicle-related interface component, as described above. In some embodiments, the example method 600 defines a computer- implemented process that can be performed by any of the devices and / or systems embodied in hardware, software, firmware, and / or combinations thereof, as described herein. In some embodiments, computer program code comprising one or more computer program instructions is stored to at least one non-transitory computer-readable storage medium, such that execution of the computer program code initiates performance of the method 600.

[0115] As shown in block 602, the method 600 includes identifying vehicle-related device display data. As described above, in some embodiments, the vehicle-related device display data includes one or more data items that represent and / or indicate one or more vehicle-related device display items. In some embodiments, a vehicle-related device display item is an item that is configured to be displayed on an interface component to convey and / or indicate information. For example, a vehicle-related device display item can include an image (e.g., a still image), a video, a composite image, a virtual reality image, an extended reality image, an augmented reality image, and / or the like. In this regard, in some embodiments, a vehicle-related device display item is a display item that indicates a speed associated with a vehicle. For example, a vehicle-related device display item can be a display item that indicates a speed at which a vehicle is moving. In some embodiments, a vehicle-related device display item is a display item that indicates a fuel amount associated with a vehicle. For example, a vehicle-related device display item can be a display item that indicates an amount of fuel in a vehicle. In some embodiments, a vehicle-related device display item is a display item that indicates an engine parameter associated with a vehicle. For example, a vehicle-related device display item can be a display item that indicates an engine temperature of an engine of a vehicle.

[0116] In some embodiments, a vehicle-related device display item is a display item that indicates a navigation map associated with a vehicle. For example, a vehicle-related device display item can be a display item that indicates a map of an area surrounding a vehicle. As another example, a vehicle-related device display item can be a display item that indicates a flight path of a vehicle (e.g., when the vehicle is an aircraft). In some embodiments, a vehicle-related device display item is a display item that indicates an audio control associated with a vehicle. For example, a vehicle-related device display item can be a display item that can be used to adjust a volume of audio in a vehicle. In some embodiments, a vehicle-related device display item is a display item that indicates a display control associated with a vehicle. For example, a vehicle-related device display item can be a display item that can be used to adjust a brightness of an interface component in a vehicle.

[0117] In some embodiments, the vehicle-related device display item is a display item that indicates a video associated with an occupant of the vehicle. For example, the vehicle- related device display item can be a display item that conveys a video being viewed by an occupant of the vehicle. In some embodiments, the vehicle-related device display item is a display item that indicates internet information associated with an occupant of the vehicle. For example, the vehicle-related device display item can be a display item that indicates whether the in-vehicle vehicle device and / or the mobile device is connected to the internet. In some embodiments, the vehicle-related device display item is a display item that indicates a document associated with an occupant of the vehicle. For example, the vehicle- related device display item can be a display item that conveys a document being viewed by an occupant of the vehicle. In some embodiments, the vehicle-related device display item is a display item that indicates a communication associated with an occupant of the vehicle. For example, the vehicle-related device display item can be a display item that conveys a text message being viewed by an occupant of the vehicle.

[0118] Additionally or alternatively, the vehicle-related device display data includes one or more data items that represent and / or indicate one or more touch areas. For example, a touch area of the one or more touch areas can be configured to select one or more vehicle-related device display items of the one or more vehicle-related device display items. In this regard, for example, the one or more touch areas can be configured to control the vehicle, the in-vehicle vehicle device, and / or the mobile device.

[0119] As shown in block 604, the method 600 includes generating a vehicle-related interface component based on the vehicle-related device display data. As described above, in some embodiments, the vehicle-related interface component is generated based on the vehicle- related device display data. In this regard, in some embodiments, the vehicle-related interface component includes at least one vehicle-related device display item of the one or more vehicle-related device display items. In some embodiments, each vehicle-related device display item of the one or more vehicle-related device display items is associated with an original display item location on the vehicle-related interface component. In this regard, for example, the original display item location can be a location on the vehicle-related interface component at which the vehicle-related device display item is displayed and / or located on the vehicle-related interface component.

[0120] In some embodiments, the vehicle-related interface component includes one or more touch areas. In some embodiments, the one or more touch areas are selectable portions of the vehicle- related interface component. For example, the one or more touch areas can be selectable to display information about a vehicle-related device display item of the one or more vehicle- related device display items. In some embodiments, the one or more touch areas are associated with an original touch area location on the vehicle-related interface component. In this regard, for example, the original touch area location can be a location on the vehicle- related interface component at which a touch area of the one or more touch areas is displayed on and / or positioned on the vehicle-related interface component (e.g., touching the original touch area location can select the touch area).

[0121] As represented by block 606, the method 600 includes causing the vehicle-related interface component to be presented to an interface of a device. As described above, in some embodiments, the vehicle-related interface component is caused to be presented to an interface of a device. In some embodiments, the vehicle-related interface component is caused to be presented to an interface of an in-vehicle vehicle device. In this regard, for example, when the vehicle-related interface component is presented to an interface of an in-vehicle vehicle device, the vehicle-related interface component can include a vehicle-related device display item that indicates a fuel amount associated with a vehicle. In some embodiments, the vehicle-related interface component is caused to be presented to an interface of a mobile device. In this regard, for example, when the vehicle-related interface component is presented to an interface of a mobile device, the vehicle-related interface component can include a vehicle-related device display item that indicates a communication associated with an occupant of a vehicle.

[0122] Operations and / or functions of the present disclosure have been described herein, such as in flowcharts. It should be understood that computer program instructions can be loaded onto a computer or other programmable apparatus (e.g., hardware) to produce a machine, such that the resulting computer or other programmable apparatus implements the operations and / or functions specified in the flowchart blocks herein. These computer program instructions can also be stored in a computer-readable memory that can direct a computer, processor, or other programmable apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture that implements the operations and / or functions specified in the flowchart blocks. The computer program instructions can also be loaded onto a computer, processor, or other programmable apparatus to cause a series of operations to be performed on the computer, processor, or other programmable apparatus, thereby producing a computer-implemented process such that the instructions executed on the computer, processor, or other programmable apparatus provide operations for implementing the functions and / or operations specified in the flowchart blocks. The flowchart blocks support combinations of means for performing the specified operations and / or functions with combinations of operations and / or functions for performing the specified operations and / or functions. It will be understood that one or more blocks of the flowchart, and combinations of blocks in the flowchart, can be implemented by special purpose computer systems that execute specific computer programs thereon or combinations of special purpose hardware and computer instructions.

[0123] While this specification contains many specific implementation details, these should not be construed as limitations on the scope of any disclosures or of what can be claimed, but as descriptions of particular implementations of specific disclosures. Certain features that are described in this specification in the context of separate implementations can also be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation can also be implemented separately or in any suitable subcombination. Moreover, although features can be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination and the claimed combination can be directed to a subcombination or variation of a subcombination.

[0124] While operations and / or functions are illustrated in the drawings in a particular order, this should not be understood as requiring such order, nor inhibiting the practice thereof in a different order, nor requiring all illustrated operations and / or functions to be performed, to achieve desirable results. In certain circumstances, parallel ordering of operations and / or functions can be advantageous. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results.

[0125] Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring such an order, nor that all illustrated operations be performed, to accomplish such an operation. In certain circumstances, multitasking and parallel processing can be advantageous. Moreover, the separation of various operation components in the embodiments described should not be understood as requiring such separation in all implementations, and it should be understood that the described program components can generally be integrated together in a single program.

Claims

1. A method, the method comprising: Receive head movement data from a wearable device, wherein the wearable device is in contact with the occupants of the vehicle; Eye motion data is generated by applying the head motion data to an eye motion determination model; Detect equipment motion data associated with the equipment; Vehicle-related stability data is generated by applying the eye motion data and the device motion data to a vehicle-related stability model. A stable vehicle-related interface component is generated based on the vehicle-related stability data and vehicle-related device display data. as well as The stable vehicle-related interface components are then displayed on the device's interface.

2. The method of claim 1, wherein the head movement data is received when the vehicle is in motion.

3. The method according to claim 1, further comprising: One or more touch areas are remapped based on the eye movement data and the device motion data.

4. The method according to claim 1, wherein the device is an on-board vehicle device.

5. The method of claim 4, wherein the vehicle-mounted equipment is physically fixed to the vehicle.

6. The method of claim 1, wherein the device is a mobile device.

7. The method of claim 1, wherein the wearable device is in contact with at least a portion of the occupant's head.

8. The method of claim 1, wherein the wearable device is at least one of glasses, headphones, or a head-mounted display.

9. An apparatus comprising a memory and one or more processors communicatively coupled to the memory, the one or more processors being configured to: Head movement data is received from a wearable device, wherein the wearable device is in contact with the occupants of the vehicle; Eye motion data is generated by applying the head motion data to an eye motion determination model; Detect equipment motion data associated with the equipment; Vehicle-related stability data is generated by applying the eye motion data and the device motion data to a vehicle-related stability model. A stable vehicle-related interface component is generated based on the vehicle-related stability data and vehicle-related device display data. as well as The stable vehicle-related interface components are then displayed on the device's interface.

10. A computer program product comprising at least one non-transitory computer-readable storage medium having computer program code stored thereon, the computer program code configuring the computer program product, when executed by at least one processor, to: Head movement data is received from a wearable device, wherein the wearable device is in contact with the occupants of the vehicle; Eye motion data is generated by applying the head motion data to an eye motion determination model; Detect equipment motion data associated with the equipment; Vehicle-related stability data is generated by applying the eye motion data and the device motion data to a vehicle-related stability model. A stable vehicle-related interface component is generated based on the vehicle-related stability data and vehicle-related device display data. as well as The stable vehicle-related interface components are then displayed on the device's interface.

Images