Patent ID: 12243503

DETAILED DESCRIPTION

Overview

The present disclosure describes a vehicle configured to enable a vehicle user/occupant to operate a user device (e.g., a laptop, a tablet, etc.) from inside the vehicle using vehicle components (or vehicle input devices). The vehicle input devices may include, for example, vehicle display screens, track pads, a monostable shifter, and/or the like. The vehicle input devices may be communicatively coupled to the user device and may be configured to provide inputs to the user device. Specifically, the user may control or operate the user device via one or more vehicle input devices. In some aspects, the vehicle may include a workspace management system/unit (“system”) that may be configured to manage (e.g., activate or deactivate) the vehicle input devices for the user device to enable the user to operate the user device via the vehicle input devices.

The system may be communicatively coupled to a vehicle camera that may capture images of the vehicle user (and other users) in the vehicle. The system may obtain the images and may determine that the vehicle user may be operating (or desires to operate) the user device in the vehicle. For example, the system may determine that the vehicle user has opened the laptop or (a laptop desk) to operate the laptop in the vehicle. Responsive to the determination that the vehicle user may be operating (or desires to operate) the user device in the vehicle, the system may determine vehicle input devices availability and may activate the vehicle input devices for the user device when respective vehicle input devices may be available. For example, the system may configure the vehicle display screen to act as an extended screen for the user device (or augment user device screen), the track pad to act as a mouse for the user device, and the monostable shifter to act as a joystick for the user device, when respective vehicle input devices may be available for the user device.

In some aspects, the system may receive a request from the user (e.g., via the user device or the vehicle display screen) to use/allocate a vehicle input device for the user device to enable the user to use the user device via the vehicle input device. Responsive to receiving the request, the system may determine the vehicle input device availability and accordingly activate the vehicle input device for the user device when the vehicle input device may be available.

When the vehicle includes more than one occupant, the system may be configured to detect a count of users that may be operating their respective user devices in the vehicle, and may be configured to prioritize vehicle input device access based on the detection. In some aspects, the system may prioritize the access based on sitting position of each user in the vehicle. For example, a user sitting at a driver sitting area may get preference to use a display screen in proximity to a vehicle front portion, as opposed to users sitting in a passenger sitting area or a rear sitting area. In further aspects, the system may allow multiple users to share a vehicle input device. For example, a first screen portion may be allocated to one user and a second screen portion may be allocated to another user.

The present disclosure discloses a vehicle that assists the vehicle user to use the user device via the vehicle input devices, which may increase user productivity in the vehicle. In addition, the system may enable multiple users to share the vehicle display screen amongst each other, which may increase screen utilization. Furthermore, the system may enable multiple users to share content on different portions of a single screen without getting physically close to each other in the vehicle, which may prevent spreading of viruses or illness.

These and other advantages of the present disclosure are provided in detail herein. The systems and method of the present disclosure should not be permitted unless the vehicle is in park, off, not in motion, and/or otherwise in a safe operational mode for enjoyment of the disclosure systems and methods, which mode may include operating in a fully autonomous vehicle, as an example.

ILLUSTRATIVE EMBODIMENTS

The disclosure will be described more fully hereinafter with reference to the accompanying drawings, in which example embodiments of the disclosure are shown, and not intended to be limiting.

FIG.1depicts an example environment100in which techniques and structures for providing the systems and methods disclosed herein may be implemented. The environment100may include a vehicle102that may take the form of any passenger or commercial vehicle such as, for example, a car, a work vehicle, a crossover vehicle, a truck, a van, a minivan, a taxi, a bus, etc. The vehicle102may be a manually driven vehicle, and/or may be configured to operate in a partially autonomous mode, and may include any powertrain such as, for example, a gasoline engine, one or more electrically-actuated motor(s), a hybrid system, etc. A vehicle user104(or a driver104) may be sitting inside the vehicle102. In some aspects, the vehicle102may be stationary and may not be moving.

In some aspects, the vehicle102may be configured to provide a work-environment to the vehicle user104(or other users or vehicle occupants) such that the vehicle user104may conveniently operate a user device106associated with the vehicle user104inside the vehicle102via one or more vehicle components (or vehicle input devices). The user device106may include, but is not limited to, a laptop, a mobile phone, a computer, a tablet, a wearable device, or any other similar device with communication capabilities. The vehicle input devices may include, but are not limited to, a display screen108(or a vehicle touch screen), a vehicle track pad (shown as track pad302inFIG.3), a monostable shifter (shown as monostable shifter304inFIG.3), and/or the like. The vehicle input devices may be communicatively coupled to the user device106(or other user devices) via a network (shown as network208inFIG.2). Further, the vehicle input devices may be configured to provide inputs to the user device106when the vehicle user104operate the user device106via the vehicle input devices.

The vehicle102may further include a vehicle workspace management unit (shown as workspace management unit214inFIG.2) that may be configured to manage the vehicle input devices to enable the vehicle user104to use the user device106inside the vehicle102. In some aspects, the vehicle workspace management unit (or unit) may be configured to receive inputs (e.g., images) from a vehicle camera110and may determine that the vehicle user104may be operating (or desires to operate) the user device106based on the inputs. For example, the unit may determine that user has opened the laptop to work inside the vehicle102based on the images captured from the camera110(or based on user inputs). In other aspects, the unit may determine that the vehicle user104desires to operate the user device106via the vehicle input devices based on user inputs received from the vehicle user104. In some aspects, the unit may receive the user inputs from the user device106or from the vehicle input devices (e.g., via the display screen108).

Responsive to the determination that the vehicle user104may be operating (or may want/desire to operate) the user device106, the unit may determine availability of one or more vehicle input device(s). The unit may allocate the vehicle input device(s) to the vehicle user104based on the vehicle input device availability. The unit may further activate the vehicle input device(s) to enable the vehicle user104to operate the user device106via the vehicle input device(s) when the vehicle input device(s) is available. For example, the unit may activate the display screen108for the user device105to enable the vehicle user104to operate (or to provide inputs to) the user device106via the display screen108. Stated another way, the unit may control the display screen108such that the display screen108may act as an extended screen of the user device106. In such scenarios, the display screen108may display content associated with the user device106. In a similar manner, the unit activate the vehicle track pad and/or the monostable shifter for the user device106to enable the vehicle user104to operate the user device106via respective vehicle input device(s).

Further details of the vehicle102are described below in conjunction withFIG.2.

The vehicle102and/or the vehicle user104implement and/or perform operations, as described here in the present disclosure, in accordance with the owner manual and safety guidelines.

FIG.2depicts a block diagram of an example system200for managing vehicle workspace in accordance with the present disclosure. While describingFIG.2, references may be made toFIGS.3,4and5.FIG.3depicts example vehicle input devices used to operate a user device in accordance with the present disclosure.FIG.4depicts a first example embodiment to control multiple vehicle input devices, andFIG.5depicts a second example embodiment to control multiple vehicle input devices in accordance with the present disclosure.

The system200may include a vehicle202, a user device204, and one or more servers206communicatively coupled with each other via one or more networks208. The vehicle202may be same as the vehicle102described in conjunction withFIG.1. The user device204may be same as the user device106. The server(s)206may be part of a cloud-based computing infrastructure and may be associated with and/or include a Telematics Service Delivery Network (SDN) that provides digital data services to the vehicle202and other vehicles (not shown inFIG.2) that may be part of a commercial vehicle fleet. In some aspects, the server206may be configured to store information associated with vehicle input devices allocation or assignment.

The network(s)208illustrates an example communication infrastructure in which the connected devices discussed in various embodiments of this disclosure may communicate. The network(s)208may be and/or include the Internet, a private network, public network or other configuration that operates using any one or more known communication protocols such as, for example, transmission control protocol/Internet protocol (TCP/IP), Bluetooth®, BLE®, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) standard 802.11, ultra-wideband (UWB), and cellular technologies such as Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), High-Speed Packet Access (HSPDA), Long-Term Evolution (LTE), Global System for Mobile Communications (GSM), and Fifth Generation (5G), to name a few examples.

The vehicle202may include a plurality of units including, but not limited to, an automotive computer210, a Vehicle Control Unit (VCU)212, and a workspace management unit214. The VCU212may include a plurality of Electronic Control Units (ECUs)216disposed in communication with the automotive computer210.

The user device204may connect with the automotive computer210and/or the workspace management unit214via the network208, which may communicate via one or more wireless connection(s), and/or may connect with the vehicle202directly by using near field communication (NFC) protocols, Bluetooth® protocols, Wi-Fi, Ultra-Wide Band (UWB), and other possible data connection and sharing techniques.

In some aspects, the automotive computer210and/or the workspace management unit214may be installed in a vehicle engine compartment (or elsewhere in the vehicle202), in accordance with the disclosure. Further, the automotive computer210may operate as a functional part of the workspace management unit214. The automotive computer210may be or include an electronic vehicle controller, having one or more processor(s)218and a memory220. Moreover, the workspace management unit214may be separate from the automotive computer210(as shown inFIG.2) or may be integrated as part of the automotive computer210.

The processor(s)218may be disposed in communication with one or more memory devices disposed in communication with the respective computing systems (e.g., the memory220and/or one or more external databases not shown inFIG.2). The processor(s)218may utilize the memory220to store programs in code and/or to store data for performing aspects in accordance with the disclosure. The memory220may be a non-transitory computer-readable storage memory storing a workspace management program code. The memory220can include any one or a combination of volatile memory elements (e.g., dynamic random-access memory (DRAM), synchronous dynamic random-access memory (SDRAM), etc.) and can include any one or more nonvolatile memory elements (e.g., erasable programmable read-only memory (EPROM), flash memory, electronically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), etc.).

In accordance with some aspects, the VCU212may share a power bus with the automotive computer210and may be configured and/or programmed to coordinate the data between vehicle systems, connected servers (e.g., the server(s)206), and other vehicles (not shown inFIG.2) operating as part of a vehicle fleet. The VCU212can include or communicate with any combination of the ECUs216, such as, for example, a Body Control Module (BCM)222, an Engine Control Module (ECM)224, a Transmission Control Module (TCM)226, a telematics control unit (TCU)228, a Driver Assistances Technologies (DAT) controller230, etc. The VCU212may further include and/or communicate with a Vehicle Perception System (VPS)232, having connectivity with and/or control of one or more vehicle sensory system(s)234. The vehicle sensory system234may include one or more vehicle sensors including, but not limited to, a Radio Detection and Ranging (RADAR or “radar”) sensor configured for detection and localization of objects inside and outside the vehicle202using radio waves, sitting area buckle sensors, sitting area sensors, a Light Detecting and Ranging (LiDAR or “lidar”) sensor, door sensors, proximity sensors, temperature sensors, wheel sensors, vehicle internal and external cameras, etc. In some aspects, the vehicle interior camera (e.g., the camera110) may be configured to capture images of the vehicle user104or other vehicle users/occupants in the vehicle202.

In some aspects, the VCU212may control vehicle operational aspects and implement one or more instruction sets received from the user device204, from one or more instruction sets stored in the memory220, including instructions operational as part of the workspace management unit214.

The TCU228may be configured and/or programmed to provide vehicle connectivity to wireless computing systems onboard and off board the vehicle202, and may include a Navigation (NAV) receiver236for receiving and processing a GPS signal, a BLE® Module (BLEM)238, a Wi-Fi transceiver, a UWB transceiver, and/or other wireless transceivers (not shown inFIG.2) that may be configurable for wireless communication (including cellular communication) between the vehicle202and other systems (e.g., a vehicle key fob, not shown inFIG.2), computers, and modules. The TCU228may be disposed in communication with the ECUs216by way of a bus.

The ECUs216may control aspects of vehicle operation and communication using inputs from human drivers, inputs from an autonomous vehicle controller, the workspace management unit214, and/or via wireless signal inputs received via the wireless connection(s) from other connected devices, such as the user device204, the server(s)206, among others.

The BCM222generally includes integration of sensors, vehicle performance indicators, and variable reactors associated with vehicle systems, and may include processor-based power distribution circuitry that can control functions associated with the vehicle body such as lights, windows, security, camera(s) including the camera110, audio system(s), speakers, wipers, door locks and access control, and various comfort controls. In some aspects, the BCM222may additionally control operation/function of the display screen108, a track pad302and a monostable shifter304(shown inFIG.3). The BCM222may also operate as a gateway for bus and network interfaces to interact with remote ECUs (not shown inFIG.2).

The DAT controller230may provide Level-1 through Level-3 automated driving and driver assistance functionality that can include, for example, active parking assistance, vehicle backup assistance, adaptive cruise control, and/or lane keeping, among other features. The DAT controller230may also provide aspects of user and environmental inputs usable for user authentication.

In some aspects, the automotive computer210may connect with an infotainment system240. The infotainment system240may include a touchscreen interface portion, and may include voice recognition features, biometric identification capabilities that can identify users based on facial recognition, voice recognition, fingerprint identification, or other biological identification means. In other aspects, the infotainment system240may be further configured to receive user instructions via the touchscreen interface portion, and/or display notifications (including visual alert notifications), navigation maps, etc. on the touchscreen interface portion.

The vehicle202may further include the camera110and the display screen108, as described in conjunction withFIG.1.

The computing system architecture of the automotive computer210, the VCU212, and/or the workspace management unit214may omit certain computing modules. It should be readily understood that the computing environment depicted inFIG.2is an example of a possible implementation according to the present disclosure, and thus, it should not be considered limiting or exclusive.

In accordance with some aspects, the workspace management unit214may be integrated with and/or executed as part of the ECUs216. The workspace management unit214, regardless of whether it is integrated with the automotive computer210or the ECUs216, or whether it operates as an independent computing system in the vehicle202, may include a transceiver242, a processor244, and a computer-readable memory246.

The transceiver242may be configured to receive information/inputs from one or more external devices or systems, e.g., the user device204, the server(s)206, and/or the like via the network208. Further, the transceiver242may transmit inputs or notifications (e.g., alert/alarm signals) to the external devices or systems. In addition, the transceiver242may be configured to receive information/inputs from vehicle components (or vehicle input devices) such as the display screen108, the track pad302, the monostable shifter304(as shown inFIG.3), and the camera110. Further, the transceiver242may transmit notifications (e.g., alert/alarm signals) to the vehicle components such as the infotainment system240, the vehicle input devices, vehicle speaker system, etc.

In some aspects, the vehicle input devices may be communicatively coupled to the user device204(or other user devices) and may be configured to receive/provide inputs from/to user device204via the transceiver242. For example, the track pad302may be used in place of computer/laptop mouse, and may be used to control user device operation. Similarly, the monostable shifter304may be used as a joystick for the user device204, and the display screen108may communicate inputs to the user device204and may display content associated with the user device204.

The processor244and the memory246may be same as or similar to the processor218and the memory220, respectively. In some aspects, the processor244may utilize the memory246to store programs in code and/or to store data for performing aspects in accordance with the disclosure. The memory246may be a non-transitory computer-readable storage memory storing the workspace management program code. In some aspects, the memory246may additionally store information associated with the vehicle202and one or more sensory inputs received from the vehicle sensory system234(e.g., the camera110), user inputs received from the user device204or other devices (e.g., the infotainment system240or the vehicle input devices). The memory246may further store information associated with vehicle input devices allocation, e.g., the display screen108, the track pad302, the monostable shifter304, and/or the like.

In operation, the processor244may obtain inputs from the camera110, via the transceiver242. The inputs may include images captured by the camera110, which may include images of the vehicle user104and other users/occupants who may be located inside the vehicle202. The processor244may be configured to monitor activity of the vehicle user104and other users/occupants inside the vehicle202based on the images obtained from the camera110. Specifically, the processor244may be configured to determine that the vehicle user104(e.g., a first user104shown inFIG.1, or any other user) may be operating the user device204in the vehicle202based on the obtained images. For example, the processor244may determine that the first user104may have opened a laptop (i.e., the user device204) in the vehicle202.

Responsive to a determination that the first user104(or any other user) may be operating the user device204in the vehicle202, the processor244may determine an availability of a vehicle input device that may assist or enable the first user104to operate the user device106via the vehicle input device. As described above, the vehicle input device may include, but is not limited to, the display screen108, the track pad302and the monostable shifter304. The processor244may be further configured to activate the vehicle input device to enable the first user104to operate the user device106via the vehicle input device when the vehicle input device may be available.

In some aspects, the processor244may obtain information associated with the vehicle input device allocation from the memory246(or the server206), and may determine the vehicle input device availability using the obtained information. For example, the processor244may determine whether the vehicle input device may be allocated to another user/occupant (specifically to their respective user devices) in the vehicle202, and may accordingly determine the vehicle input device availability. Specifically, the processor244may determine the vehicle input device to be available when the vehicle input device may not be allocated to any other user/occupant.

In additional aspects, the processor244may be configured to determine vehicle input device usage when the vehicle input device may be allocated to a user/occupant, and may determine vehicle input device availability based on the usage. Specifically, the processor244may determine that the vehicle input device may be available when no user/occupant may be actively using the vehicle input device, even though the vehicle input device may be allocated to a user/occupant. For example, when the vehicle input device may be allocated to a user (e.g., a second user402in the vehicle202, as shown inFIG.4) and the processor244determines that the second user402may not be using the vehicle input device, the processor244may determine that the vehicle input device may be available, and may allocate the vehicle input device to the first user104(specifically to the user device204). In this case, the processor244may “deactivate” the vehicle input device from the second user402when the processor244allocates the vehicle input device to the first user104. As another example, when the processor244determines that only a single user (e.g., the first user104) may be operating a user device (e.g., the user device204), the processor244may determine that the vehicle input device may be available as no other user may be operating their respective user device(s) in the vehicle202, and may allocate the vehicle input device to the first user104/user device204.

In further aspects, the processor244may be configured to obtain a request, via the transceiver242, from the first user104(or other users/occupants) to use/allocate the vehicle input device to operate the user device204(or respective user devices). In some aspects, the processor244may obtain the request from the first user104via the user device204, the server206, and/or one or more vehicle components (e.g., the infotainment system240, the display screen108, etc.). Responsive to obtaining the request, the processor244may determine vehicle input device(s) availability, and may allocate the vehicle input device to the first user104/user device204when the vehicle input device may be available.

In additional aspects, the processor244may be configured to determine that multiple users may be operating (or desire to operate) their respective user devices in the vehicle202. In such a scenario, the processor244may prioritize vehicle input device(s) access, and may allocate the vehicle input devices to the first user104or the second user402based on the prioritization. In this case, the processor244may obtain images from the camera110(that may capture images of the first user104and the second user402in the vehicle202), and may determine that the first user104and the second user402may be operating (or desire to operate) their respective user devices in the vehicle202based on the obtained images. In alternative aspects, the processor244may obtain respective requests from the first user104and the second user402to use a vehicle input device (e.g., a first vehicle input device such as the display screen108that may be an auxiliary vehicle screen), and may determine that the first user104and the second user402may desire to operate their respective user devices via the display screen108, based on the obtained requests.

When the processor244determines that both the first user104and the second user402desire to operate their respective user devices via the display screen108, in some aspects, the processor244may determine respective sitting positions of the first user104and the second user402inside the vehicle202. In some aspects, the processor244may determine the sitting positions based on inputs obtained from the sensory system234. Responsive to determining the sitting positions, the processor244may prioritize access/allocation of the display screen108to either the first user104or the second user402based on the determined sitting position.

For example, the processor244may determine that the first user104may be sitting in the driver sitting area and the second user402may be sitting in a front passenger sitting area (as depicted inFIG.4) based on the inputs obtained from the sensory system234. In this case, the processor244may prioritize allocation of the display screen108to the first user104(or the user device204) over the second user402, and may allocate the display screen108to the first user104. Stated another way, in an exemplary aspect, a user sitting in a driver sitting area may get priority over a user sitting in a passenger sitting area to access the display screen108to operate the user device204. The processor244may activate the display screen108to enable the first user104to control the user device204via the display screen108. In such scenarios, the display screen108may display content associated with the user device204.

In further aspects, the processor244may prioritize display screen108access (or any other vehicle input device) based on a time of receiving the request from respective users. For example, the processor244may provide access to a user who transmitted the request first. Furthermore, although the example described above describes an aspect where the user sitting in the driver sitting area is given priority over the passenger, the present disclosure is not limited to such a prioritization criterion. In other aspects, the user sitting in the passenger sitting area (or any other position inside the vehicle202) may get priority over the user sitting in the driver sitting area to access one or more vehicle input devices, without departing from the present disclosure scope.

In further aspects, the processor244may determine display screen108usage (or any other vehicle input device) responsive to the activating the display screen108to enable the first user104to operate the user device204via the display screen108. Specifically, the processor244may determine whether the first user104is actually using the display screen108to operate the user device204. In some aspects, the processor244may determine display screen usage when the processor244determines that the second user402may be operating a user device associated with the second user402and may desire to use the display screen108(based on images obtained from the camera110or a request received from the user device associated with the second user402). Responsive to a determination that the first user104may not be using the display screen108for a predefined time duration, the processor244may determine that the display screen108may be available for “re-allocation”. In this case, the processor244may re-allocate the display screen108to the second user402(specifically to the user device associated with the second user402). In such a scenario, the processor244may activate the display screen108to enable the second user402to control operation of the user device associated with the second user402via the display screen108. In this case, the display screen108may display content associated with the user device associated with the second user402.

In additional aspects, the processor244may enable the first user104and the second user402to share the display screen108, which may increase display screen utilization. For example, the processor244may display the content associated with the user device204on the display screen108when the first user104may be viewing the display screen108(as determined via the images obtained from the camera110, such as by tracking the eyes of the first user). Further, the processor244may display the content associated with the user device associated with the second user402when the second user402may be viewing the display screen108(as determined via the images obtained from the camera110).

In further aspects, when the vehicle202includes an extended vehicle display screen, the processor244may enable the first user104and the second user402to share the extended vehicle display screen such that a first display screen portion may be allocated to the first user104, and a second display screen portion may be allocated to the second user402. The first display screen portion may be in front of a first user sitting area position, and the second display screen portion may be in front of a second user sitting area position. In this manner, both the first user104and the second user402may view the extended vehicle display screen simultaneously. The content displayed on the first display screen portion and the second display screen portion may be same or different. For example, when the first user104desires to show content associated with the user device204to the second user402, the first user104may use the first display screen portion and the second display screen portion to show the same content conveniently.

In further aspects, the processor244may be configured to determine sitting positions of the first user104and the second user402inside the vehicle202(e.g., based on the images obtained from the camera110) and may allocate different vehicle input devices to the first and second users104,402based on respective sitting positions. For example, as depicted inFIG.5, the first user104may be sitting in a driver sitting area and the second user402may be sitting at a rear sitting area. Responsive to determining the sitting positions, the processor244may determine that a second vehicle input device (e.g., a second display screen502that may be communicatively coupled to the user device associated with the second user402) may be in proximity to the second user sitting position, and the display screen108may be in proximity to the first user sitting position. The processor244may be further configured to activate the second display screen502for the user device associated with the second user402to enable the second user402to operate the user device associated with the second user402via the second display screen502. Similarly, the processor244may activate the display screen108for the user device204to enable the first user104to operate the user device204via the display screen108. Stated another way, the processor244may select the vehicle input device(s) based on the sitting positions of vehicle users/occupants in the vehicle202, and activate the select vehicle input device(s) accordingly. In some aspects, the processor244may determine availability of the display screen108and the second display screen502before allocating respective devices to the first user104and/or the second user402. In some aspects, the processor244may perform automatic assignment of vehicle input devices based on the sitting position. For example, when a user sits on a sitting position in the vehicle202, the processor244may automatically assign the display screen in front of the user to the user.

In further aspects, the processor244may be configured to track usage of all activated vehicle input devices, and may deactivate the vehicle input devices based on respective usage. For example, when the usage of a vehicle input device (e.g., the display screen108) is below a predefined usage threshold, the processor244may deactivate the display screen108or put the display screen108in sleep mode (e.g., activate a sleep mode for the display screen108) to reduce energy utilization in the vehicle202.

In addition, the processor244may monitor (e.g., based on the images obtained from the camera110) orientation of each user in the vehicle202who may be using the vehicle input devices (e.g., the display screen108and the second display screen502) to operate respective user devices. Based on the orientation, the processor244may determine whether the first user104and the second user402may be viewing (or using) the display screen108and the second display screen502, respectively. When the first user104and/or the second user402may not be viewing respective display screens for a predefined time interval/duration, the processor244may reduce/adjust brightness of respective display screens to reduce energy utilization in the vehicle202.

In further aspects, the processor244may be configured to obtain images from the camera110, and may control audio devices in the vehicle202(e.g., to provide audio feedback to users) based on the obtained images. Specifically, the processor244may prioritize the audio device(s) in the similar manner as the vehicle input devices described above based on the images, and activate the audio devices based on prioritization. For example, the processor244may activate the audio device for entire vehicle202when a single user may be present in the vehicle202, and may activate ceiling/headrest speakers and noise cancellation when multiple users may be present in the vehicle202(e.g., to isolate each occupant/user from other occupants/users).

The vehicle202may further include electrochromic windows that may be configured to tint window glasses. In certain aspects, the processor244may be configured to determine that the first user104(or any other user) may be experiencing glare on the display screen108, based on the inputs obtained from the sensory system234and/or images obtained from the camera110. For example, the processor244may perform such determination by obtaining images from the camera110and performing image processing on the obtained images to determine if the first user104may be experiencing glare. In additional aspects, the processor244may determine that the first user104may be experiencing glare based on user inputs obtained via the display screen108or the user device204. Responsive to a determination that the first user104may be experiencing glare, the processor244may cause the electrochromic windows to tint the window glasses. In some aspects, the processor244may cause tinting of all the window glasses. In other aspects, the processor244may select one or more window glasses to be tinted. The selection of the one or more window glasses may be based on the first user sitting position in the vehicle202.

In further aspects, the processor244may monitor the content displayed on each screen (e.g., the display screen108and the second display screen502), and may change/adjust refresh-rate based on the content displayed or the operation performed using the screen. For example, the processor244may increase the refresh-rate when a game or a movie may be displayed on the screen, but may not increase the refresh rate when music may be playing. In addition, the processor244may determine user preferences to use the vehicle input devices based on user inputs obtained from the user device203, and may activate the vehicle input devices based on the user preferences.

FIG.6depicts a flow diagram of an example method600for managing vehicle workspace in accordance with the present disclosure.FIG.6may be described with continued reference to prior figures. The following process is exemplary and not confined to the steps described hereafter. Moreover, alternative embodiments may include more or less steps than are shown or described herein and may include these steps in a different order than the order described in the following example embodiments.

The method600starts at step602. At step604, the method600may include obtaining, by the processor244, images from the camera110. As described above, the camera110may capture images of a user (e.g., the first user104) who may be present in the vehicle202. At step606, the method600may include determining, by the processor244, that the first user104may be operating the user device204(e.g., a laptop) associated with the first user104in the vehicle202based on the obtained images.

At step608, the method600may include determining, by the processor244, availability of a vehicle input device (e.g., the display screen108, the track pad302, the monostable shifter304, etc.) responsive to a determination that the first user104may be using the user device204in the vehicle202. At step610, the method600may include activating, by the processor244, the vehicle input device to enable the first user104to operate the user device204via the vehicle input device when the vehicle input device may be available.

The method600ends at step612.

In the above disclosure, reference has been made to the accompanying drawings, which form a part hereof, which illustrate specific implementations in which the present disclosure may be practiced. It is understood that other implementations may be utilized, and structural changes may be made without departing from the scope of the present disclosure. References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a feature, structure, or characteristic is described in connection with an embodiment, one skilled in the art will recognize such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

Further, where appropriate, the functions described herein can be performed in one or more of hardware, software, firmware, digital components, or analog components. For example, one or more application specific integrated circuits (ASICs) can be programmed to carry out one or more of the systems and procedures described herein. Certain terms are used throughout the description and claims refer to particular system components. As one skilled in the art will appreciate, components may be referred to by different names. This document does not intend to distinguish between components that differ in name, but not function.

It should also be understood that the word “example” as used herein is intended to be non-exclusionary and non-limiting in nature. More particularly, the word “example” as used herein indicates one among several examples, and it should be understood that no undue emphasis or preference is being directed to the particular example being described.

A computer-readable medium (also referred to as a processor-readable medium) includes any non-transitory (e.g., tangible) medium that participates in providing data (e.g., instructions) that may be read by a computer (e.g., by a processor of a computer). Such a medium may take many forms, including, but not limited to, non-volatile media and volatile media. Computing devices may include computer-executable instructions, where the instructions may be executable by one or more computing devices such as those listed above and stored on a computer-readable medium.

With regard to the processes, systems, methods, heuristics, etc. described herein, it should be understood that, although the steps of such processes, etc. have been described as occurring according to a certain ordered sequence, such processes could be practiced with the described steps performed in an order other than the order described herein. It further should be understood that certain steps could be performed simultaneously, that other steps could be added, or that certain steps described herein could be omitted. In other words, the descriptions of processes herein are provided for the purpose of illustrating various embodiments and should in no way be construed so as to limit the claims.

Accordingly, it is to be understood that the above description is intended to be illustrative and not restrictive. Many embodiments and applications other than the examples provided would be apparent upon reading the above description. The scope should be determined, not with reference to the above description, but should instead be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled. It is anticipated and intended that future developments will occur in the technologies discussed herein, and that the disclosed systems and methods will be incorporated into such future embodiments. In sum, it should be understood that the application is capable of modification and variation.

All terms used in the claims are intended to be given their ordinary meanings as understood by those knowledgeable in the technologies described herein unless an explicit indication to the contrary is made herein. In particular, use of the singular articles such as “a,” “the,” “said,” etc. should be read to recite one or more of the indicated elements unless a claim recites an explicit limitation to the contrary. Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments could include, while other embodiments may not include, certain features, elements, and/or steps. Thus, such conditional language is not generally intended to imply that features, elements, and/or steps are in any way required for one or more embodiments.