Patent ID: 12194916

DETAILED DESCRIPTION

As required, detailed embodiments of the present disclosure are disclosed herein; however, it is to be understood that the disclosed embodiments are merely exemplary of the disclosure that may be embodied in various and alternative forms. The figures are not necessarily to scale; some features may be exaggerated or minimized to show details of particular components. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a representative basis for teaching one skilled in the art to variously employ the present disclosure.

Zone lighting features may enable illumination of the area around a vehicle. In an example, such features may allow people around the vehicle to be tracked, such that the lights of the vehicle may be aimed or activated to follow the people around the vehicle. Users may be tracked using wireless signal techniques such as monitoring of Bluetooth Low Energy (BLE) signal strength to a device carried by a user, and/or tracking of Ultra-Wideband (UWB) radio frequency round-trip time-of-flight (RF-ToF) between a user's device and the vehicle. Other tracking techniques for following may be used as well based on vehicle features, such as use of cameras, light detection and ranging (LiDAR), radio detection and ranging (RADAR), ultrasound, sound navigation and ranging (SONAR), etc.

Zone lighting features may be extended to multiple vehicle situations, where a group of vehicles may be collectively controlled to provide additional features both for work situations and recreation.

To begin utilizing multi-vehicle coordinated lighting features, a customer may link their vehicle to other vehicles. This may be accomplished, for example, using the touch screen and BLE/UWB functionality for communication with the other vehicles and/or with other users. The vehicles being linked may accept to be part of the group (e.g., as a work-crew, for a family outing, for a business gathering, for a club, etc.).

An exterior lighting level may then be selected for each vehicle of the group. For instance, the user may set all lights to be on (e.g., the lights including puddle, head, backup, curtain, bed, etc.). The user may set for lighting to be activated by movement within a specific distance from the vehicle. The user may also set a combination of static-ON or movement activated lighting.

Some vehicles may have aimable headlights. Also, some vehicles may be equipped with dynamic light emitting diode (LED) headlights that can shape the light output, and/or those with movable/aimed light. Some vehicles (e.g., police cruisers or off-road vehicles) may also have spotlights or other aftermarket lights that may be aimed electronically. Using such systems, a user may set a position on a screen map or desired area to be illuminated. The vehicles may individually select lights to illuminate this spot based on their orientation and capability. This may be used to allow the group of vehicles to collectively light an area such as a ski hill, a site for nighttime working (e.g., brick layers, road construction site, etc.), a sports event (e.g., a volleyball, soccer, or baseball field), or another outdoor gathering such as a party.

The group of vehicles may also collectively light the area surrounding a user. For example, a worker or sledder may carry a tracking device having a BLE or UWB transceiver, which may allow the vehicles to track the user's location. The vehicles may accordingly be able to direct the crowdsourced lights on towards the tracked location of the user. This tracking device may be the user's phone in an example. In another example, the tracking device may be a fob or an active custom device. In yet a further example, the user may be tracked without a tracking device, such as via tracking techniques that use RADAR, SONAR, LiDAR, etc. sensors of the vehicle.

The intensity of the lighting may be collectively controlled to provide a specific intensity, to prevent the vehicles from over- or under-illuminating the user. For example, vehicles father away from the user may provide brighter illumination of the area than vehicles closer to the user. Or vehicles nearest to the user may shut off their lights to let other adjacent vehicles illuminate. Depending on the location to be illuminated (e.g., street, driveways, grass field, dirt lot, etc.), some vehicles may be on different inclines. As a user traverses in the Z-axis (either up or down), the vehicles with the corresponding up or down incline may be given primary duty to illuminate the target.

In some examples, other devices may be added to the group. In one example, portable lights may also be added to the group to allow fill lighting. The portable lamps may have wireless capabilities to become part of the vehicle group collective. In another example, a tethered drone may also provide fill light for positions the vehicles cannot reach. The drone light power and flight power may be provided via the tether. The drone may also utilize left-right, up-down direction capability or a swivel light to aid in aiming the lighting towards the target user or area.

FIG.1illustrates an example vehicle102for use in a system100providing collective zone lighting features. The vehicle102may include various types of automobile, crossover utility vehicle (CUV), sport utility vehicle (SUV), truck, recreational vehicle, boat, plane or other mobile machine for transporting people or goods. Such vehicles102may be human-driven or autonomous. In many cases, the vehicle102may be powered by an internal combustion engine. As another possibility, the vehicle102may be a battery electric vehicle powered by one or more electric motors. As a further possibility, the vehicle102may be a hybrid electric vehicle powered by both an internal combustion engine and one or more electric motors, such as a series hybrid electric vehicle, a parallel hybrid electrical vehicle, or a parallel/series hybrid electric vehicle.

The vehicle102may include a plurality of controllers configured to perform and manage various vehicle102functions under the power of the vehicle battery and/or drivetrain. The controllers may include various types of computing devices in support of performance of the functions of the controllers described herein. In an example, the controllers may include one or more processors configured to execute computer instructions, and a storage medium on which the computer-executable instructions and/or data may be maintained. A computer-readable storage medium (also referred to as a processor-readable medium or storage) 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 the processor(s)). In general, the processor receives instructions and/or data, e.g., from the storage, etc., to a memory and executes the instructions using the data, thereby performing one or more processes, including one or more of the processes described herein. Computer-executable instructions may be compiled or interpreted from computer programs created using a variety of programming languages and/or technologies, including, without limitation, and either alone or in combination, JAVA, C, C++, C #, FORTRAN, PASCAL, VISUAL BASIC, PYTHON, JAVASCRIPT, PERL, etc. Further aspects of the computing devices are shown with respect toFIG.10.

As depicted, the example vehicle controllers are represented as discrete controllers (e.g., a powertrain controller104, a body controller106, a location controller112, a HMI controller114, and a telematics controller116). However, the vehicle controllers may share physical hardware, firmware, and/or software, such that the functionality from multiple controllers may be integrated into a single controller, and that the functionality of various such controllers may be distributed across a plurality of controllers.

The powertrain controller104may be configured to provide control of engine operating components (e.g., idle control components, fuel delivery components, emissions control components, etc.) and for monitoring status of such engine operating components (e.g., status of engine codes).

The body controller106may be configured to manage various power control functions such as exterior lighting122, keyless entry, remote start, and point of access status verification (e.g., closure status of the hood, doors and/or trunk of the vehicle102). The body controller106may be in communication with a wireless transceiver108. The wireless transceiver108may be configured to facilitate communication with tracking devices120using wireless protocols such as BLE or UWB. The tracking devices120may include key fobs, mobile phones, or dedicated devices that are configured to communicate wirelessly with the wireless transceiver108to facilitate identification and location of a user. The wireless transceiver108may allow the body controller106to identify the locations of key fobs, mobile phones, or other devices that may identify users for access to the vehicle102. In an example, the body controller106may unlock doors of the vehicle102responsive to detection of an approach of an authorized user via the wireless transceiver108(e.g., detected based on increased BLE signal strength or decreasing RF-ToF of the approaching tracking device120).

The exterior lighting122may include various lights on the exterior of the vehicle102. These may include, for example, headlights that shine forwards in front of the vehicle102(e.g., low and/or high beams), taillights that shine rearwards behind the vehicle102, a center high mounted stop light (CHMSL), curtain lighting that shines to the sides of the vehicle102, bed lights in the bed of a truck bed, and/or puddle lamps that shine downwards from under the side mirrors. Some vehicles102may have aimable headlights that can be steered into different directions. Also, some vehicles102may be equipped with dynamic LED headlights that can shape the light output. Some vehicles102(e.g., police cruisers or off road vehicles) may also have spotlights or other aftermarket lights that may be aimable or otherwise controllable. The exterior lighting122of the vehicle102may be adjusted in orientation and intensity by the body controller106.

The location controller112may be configured to provide vehicle location information. For example, the location controller112may allow the vehicle102to receive time and location information from a global navigation satellite system (GNSS) constellation of satellites.

The HMI controller114may be configured to receive user input via various buttons or other controls, as well as provide vehicle status information to a driver, such as fuel level information, engine operating temperature information, and current location of the vehicle102. The HMI controller114may be configured to provide information to various displays within the vehicle102, such as a center stack touchscreen, a gauge cluster screen, etc.

The telematics controller116, sometimes referred to as a telematics control unit (TCU), may include network hardware configured to facilitate communication between the other vehicle controllers104-114and with other devices of the system100. The telematics controller116may include or otherwise access a modem124configured to facilitate communication with other vehicles102or with infrastructure. The modem124may, additionally, be configured to communicate over a broadcast peer-to-peer protocol (such as PC5), to facilitate C-V2X communications with devices such as other vehicles102. The telematics controller116may be further configured to communicate over various other protocols, such as with a communication network over a network protocol (such as Uu). It should be noted that these protocols are merely examples, and different peer-to-peer and/or cellular technologies may be used.

The controllers104-116of the vehicle102may make use of various sensors126in order to receive information with respect to the surroundings of the vehicle102. In an example, these sensors126may include one or more of cameras (e.g., advanced driver assistance system (ADAS) cameras), ultrasonic sensors, radar systems, and/or lidar systems. The sensors126may be used to allow the vehicle102to image its surroundings. For instance, camera sensors126mounted on the front, rear, and sides of the vehicle102may be used to capture visual images of the surroundings of the vehicle102. An image coordinate transformation (e.g., via a homogeneous transform matrix) may be performed on the images by the controllers to generate a top-down view of the surroundings, in an example.

A vehicle bus128may include various methods of communication available between the vehicle controllers104-116. As some non-limiting examples, the vehicle bus128may include one or more of a vehicle controller area network (CAN), an Ethernet network, and a media-oriented system transfer (MOST) network. While a single vehicle bus128is illustrated, it should be noted that in many examples, multiple vehicle buses128are included, with a subset of the controllers104-116connected to each vehicle bus128.

FIG.2illustrates an example group of vehicles102in an area200. As shown, the area200includes three vehicles102: vehicle102A, vehicle102B, and vehicle102C. Each of the vehicles102A-C is parked facing a clearing. Vehicle102A is facing one side of the area200, while vehicles102B and102C are facing the same general spot from another side. Each of the vehicles102may use its respective location controller112to identify its location. The location controllers112of the vehicles102may also use GNSS and/or a compass to determine vehicle102orientation.

The vehicles102may use their wireless communications features to communicate with one another. In an example, wireless messages202may be sent between the vehicles102using wireless protocols such as BLE or UWB via the wireless transceiver108. For instance, the vehicles102may communicate their locations to one another via the wireless messages202. The wireless messages202may also include other information about the vehicles102. For instance, information regarding the appearance of the vehicles102, such as color, model, user name, etc., may be included in the wireless messages202. In an example, the vehicles102may periodically broadcast the wireless messages202. In another example, a lead vehicle102may broadcast a wireless message202that, if received by other vehicles102, causes the other vehicles102to provide their locations to the lead vehicle102in response wireless messages202.

FIG.3illustrates an example300of an HMI302illustrating vehicle indications304of the vehicles102relative to one another on a map306. In an example, the HMI302may be displayed via a screen controlled by the HMI controller114of one of the vehicles102. In another example, the HMI302may be displayed via a screen of a mobile phone used as a tracking device120of one of the vehicles102.

As shown, vehicle indications302A-C of the vehicles102A-C are illustrated in a top-down view consistent with their actual locations and orientations of the vehicles102A-C shown inFIG.2. The vehicle indications302A-C may further be shown consistent with attributes of the respective vehicles102, such as the same color, same model, etc.

The map306may include information to provide context to the user. In an example, the map306data may include predefined image tiles stored to the vehicle102or received by the vehicle102from a cloud mapping service. In another example, the maps306may include real-time image data collected by the sensors126of the vehicles102A-C. For instance, the vehicles102may use their camera sensors126to capture visual images of their surroundings, which may be wirelessly shared among the vehicles102and used to instead of or in addition to the predefined image times to augment the maps306with live information.

FIG.4illustrates an example400of the HMI302showing the sending of an initiation to join a lighting group. In general, the vehicles102may be configured to advertise their willingness to create or join a group of vehicles102to be collectively controlled to provide coordinated lighting features. In an example, one of the vehicles102may be configured to be an organizer vehicle102and may transmit a create group message to be received by other vehicles102within range of the organizer vehicle102.

For instance, a user of the vehicle102A may select from the HMI302to invite other vehicles102to create the lighting group. This may result in the display of a lighting group invite dialog402. The lighting group invite dialog402may include a description404informing the user of the vehicle102A to select from a vehicle list406of the detected vehicles102(here vehicles102B and102C). Once the user has selected the vehicles102to invite, the user may select an invite control408to cause the vehicle102A to send invitations to join the lighting group. Or, if the user elects not to proceed, the user may select a cancel control410to dismiss the lighting group invite dialog402without sending invites. In another example, the invite may be broadcast to all vehicles102within listening range of the inviting vehicle102, without the user making a selection.

FIG.5illustrates an example500of the HMI302showing the receiving of an invitation502to join the lighting group. The invitation502may be received wirelessly by the invited vehicles102B and102C. In an example, the HMI302may be displayed via a screen controlled by the HMI controller114of one of the recipient vehicles102. In another example, the HMI302may be displayed via a screen of a mobile phone used as a tracking device120of one of the recipient vehicles102.

The invitation502may include a description504informing the user that the vehicle102is invited to join a lighting group. The invitation502may also illustrate sender information508about the inviting vehicle102(here, vehicle102A). The sender information508may include information such as a name of the inviting vehicle102, the color of inviting vehicle102, the make of the inviting vehicle102, etc. The invitation502may also include an explanation510that accepting the invitation502may result in the exterior lighting122features of the vehicle102being controlled remotely and asking the user to confirm. The user may select a join control512to cause the vehicle102B or102C to accept the invitation502to join the lighting group. The user may select a decline control514to cause the recipient vehicle102B or102C to elect not to join the lighting group. If at least one potential joined vehicle102responds with an acceptance, the organizer vehicle102may take a leadership role for controlling the light features.

As a variation, a potential joined vehicle102may also send a request to join the group in another example, by selecting from a listing of available lighting groups, where the request may be sent to the leader vehicle102, or any vehicle102of the lighting group to be accepted or declined.

FIG.6illustrates an example600of the activation of the exterior lighting122of one of the vehicles102of the lighting group. As shown, the user may select the vehicle indication302C to activate the exterior lighting122of that specific vehicle102C. For instance, as shown by the hand indication602, the user may touch the vehicle indication302C to activate the exterior lighting122of the vehicle102C. This may result in the providing of illumination areas604A-D (collectively illumination areas604) around the vehicle102C. These may include, for example, the illumination area604A provided in front of the vehicle102C using the headlights, the illumination area604B provided along the drivers side of the vehicle102C via curtain lighting and/or puddle lamps, the illumination area604C provided along the passenger side of the vehicle102C via curtain lighting and/or puddle lamps, and the illumination area604D provided behind the vehicle102C via backup lighting and/or the CHMSL.

In many examples, the HMI302may overlay indications on the map306to illustrate simulated operation of the exterior lighting122. As another possibility, the vehicles102may utilize their sensors to capture actual imagery surrounding the vehicle102, which may be transformed into a bird's-eye view and displayed to illustrate the actual effect of the exterior lighting122.

In many cases, however, it may be desirable to perform collective lighting actions using the exterior lighting122of more than one vehicle102.FIG.7illustrates an example700of the selection of a plurality of vehicles102from the group. As shown, the user may select vehicle indications302A-C to select to perform a collective lighting action using that collection of vehicles102. For instance, as shown by gesture702, the user may perform a swipe action to select each of the vehicle indications302A-C. It should be noted that in other examples, as compared to the selections shown inFIGS.6-7, the default may be for the collective lighting action to be performed using all of the vehicles102of the lighting group.

FIG.8illustrates an example800of using the HMI302to control collective lighting actions. As shown, the HMI302provides a lighting group configuration dialog802including a listing of options that may allow the group of vehicles102to be controlled. In an example, the lighting group configuration dialog802may be displayed responsive to creation of the group. In another example, the lighting group configuration dialog802may be displayed responsive to the user selecting to configure (or reconfigure) the operation of the lighting group.

The lighting group configuration dialog802may allow the user to select from the various available exterior lighting122. As shown, the lighting group configuration dialog802includes an available lights label804explaining that the user may select from a listing of available exterior lighting types806. This available exterior lighting types806shows the options of headlights, tail lights, puddle lamps, and curtain lamps. It should be noted that these are examples, and more, different, or other types of exterior lighting122may also be listed, if available. For instance, if accessory light racks or spotlights are indicated in the wireless messages202as being available then these may also be included. Or if supplemental fill lighting devices are located in the wireless messages202these may be listed as well.

The lighting group configuration dialog802may also allow the user to select from various collective lightings actions to be performed by the vehicles102in the group using the available exterior lighting types806that are selected. As shown, the lighting group configuration dialog802includes a lighting mode label808explaining that the user may select from a listing of available exterior lighting modes810. As shown, the available exterior lighting modes810include the selected lights being turned on in their default orientation, the selected lights being aimable to a specific location, or the lights being configured to illuminate the area (or areas) surrounding tracked users, e.g., tracked using the tracking devices120, tracked using sensors126of the vehicle102, etc.

The user may select to use the lighting settings by pressing an apply button812. The user may discard the settings and revert to the previous settings by pressing a cancel button814. It should be noted that the options of the lighting group configuration dialog802are illustrative, and more, fewer, or different options may be available. For example, the options may include a mode to flash the lights in time according to audio that is being played back (or audio that is being picked up by a microphone). Or, the options may include to provide dancing, chaser, or other lighting effects without regard to sound.

FIG.9illustrates an example900of the HMI302illustrating the operation of the lighting group in the on mode. As shown, the headlights of each of the vehicle102of the lighting group are engaged. This was selected via the lighting group configuration dialog802shownFIG.8. The HMI302may further illustrate the illumination areas604resulting from the selection. As shown, the vehicle indication302A displayed as providing illumination area604A, the vehicle indication302B is displayed as providing illumination area604B, and the vehicle indication302B is displayed as providing illumination area604B.

In many examples, the HMI302may overlay indications on the map306to illustrate simulated operation of the exterior lighting122. As another possibility, the vehicles102may utilize their sensors to capture actual imagery surrounding the vehicle102, which may be transformed into a bird's-eye view and shared to the controlling vehicle102to allow for the display of the actual effect of the exterior lighting122.

FIG.10illustrates an example1000of the HMI302illustrating the operation of the lighting group in the aim mode. As shown, the user may select a location on the map306to aim the exterior lighting122to that specific location. For instance, as shown by hand indication1002, the user touches a location within range of the headlight exterior lighting122of each of the vehicles102to aim the exterior lighting122of all of the vehicles102of the group to that location. In the example, this may result in the providing of illumination areas604from each of the vehicles102to the selected location. As shown the headlights of the vehicle102A are aimed to the passenger side and the headlights of the vehicle102B are aimed to the driver side to reach the selected location. The headlights of the vehicle102C reach the location at a relatively straight ahead angle. By using the aim mode, the user may be able to collectively illuminate the location using the group of vehicles102.

FIG.11illustrates an example1100of the HMI302illustrating the operation of the lighting group in the follow mode. As compared to the aim mode in which the user selects the location on the map306, in the follow mode the targeted locations for illumination are determined based on tracking of the users via the tracking devices120and/or via the sensors126of the vehicle102.

The vehicles102may track the locations of the tracking devices120based on wireless signals received from the tracking devices120. Based on the positions of the tracking devices120, the vehicles102may determine which, if any, of the exterior lighting122has range to cover the locations of the tracking devices120. If the vehicle102has suitable exterior lighting122, then that exterior lighting122may be engaged and/or aimed to provide light to the location of the tracking device120. If the vehicle102lacks suitable exterior lighting122, then the vehicle102may consider the tracking device120to be out of range and may not provide illumination. As shown, a tracking device120A is within range of the exterior lightings122of each of vehicles102A-102C. Thus, the tracking device120A is being illuminated by illumination area604A from vehicle102A, by illumination area604B from vehicle102B, and by illumination area604C from vehicle102C.

Also, a tracking device120B is being illuminated by illumination area604D from vehicle102A, but here from a curtain light as that light is closest to the tracking device120B. The other vehicles102B-C are not also illuminating the tracking device120B as they lack exterior lighting122within range of the tracking device120B.

Additionally, a tracking device120C is between vehicles102B-102C. This tracking device120C is illuminated by illumination area604E from the curtain lighting of vehicle102B and also by illumination area604F from the curtain lighting of vehicle102C.

In another example, the vehicles102may track the users without reliance on the tracking devices120. For instance, the vehicles102may utilize RADAR, SONAR, and/or LiDAR sensors126of the vehicle102to identify movement around the vehicles102. The locations of this movement may be used as the locations of the users to be tracked. For instance, if the vehicles102are a fleet of ships, then SONAR may be used to track other boats for illumination. Or, if the intended users to illuminate are planes or drones, then RADAR or LiDAR may be used to track those airborne vehicles102for illumination. It should be noted that these techniques are not limited to specific types of vehicle102, and SONAR, RADAR, LiDAR, etc. may be used for tracking by any of various types of vehicles102.

FIG.12illustrates an alternate example group of vehicles102in the area200including additional devices to provide fill lighting. As shown, the area200includes three vehicles102: vehicle102A, vehicle102B, and vehicle102C. However, in this example a drone1202is also available to be added to the group. Additionally, two portable lanterns1204A,1204B (collectively lanterns1204) are also available for control. As with the vehicles102, the drones1202and lanterns1204may be wirelessly controlled (e.g., via BLE, UWB, Wi-Fi, etc.). For instance, these additional devices may also communicate their locations and receive instructions via the wireless messages202.

FIG.13illustrates the alternate example group of vehicles102including the additional devices in the HMI302. Similar to the control of the vehicles102, the drone1202and lanterns1204may also be used to provide illumination areas604. As shown, the vehicle indication302A displayed as providing illumination area604A, the vehicle indication302B is displayed as providing illumination area604B, and the vehicle indication302B is displayed as providing illumination area604B. Additionally, a drone indication1302corresponding to the drone1202is shown as providing illumination area604D, a lantern indication1304A corresponding to the lantern1204A is shown as providing illumination area604E, and a lantern indication1304B corresponding to the lantern1204B is shown as providing illumination area604F.

It should be noted that the lanterns1204may have different functionality as compared to the vehicles102. In an example, while some lanterns1204may provide aiming, in other examples the lanterns1204may lack aiming capabilities and may simply allow for intensity control. In another example, the drone1202may allow for movement, such that the drone1202may move to follow a tracking device120, as opposed to aiming its lights while remaining at a fixed location.

FIG.14illustrates an example process1400for the creation and control of a lighting group. In an example, the process1400may be performed by one or more controllers104-116of one of the plurality of vehicles102in the context of the system100discussed herein.

At operation1402, the vehicle102identifies one or more other vehicles102available for a lighting group. In an example, the vehicle102utilizes the wireless transceiver108to identify the one or more other vehicles102. For instance, wireless messages202may be sent between the vehicles102using wireless protocols such as BLE or UWB via the wireless transceiver108. The vehicles102may communicate their locations to one another via the wireless messages202. The wireless messages202may also include other information about the vehicles102. For instance, information regarding the appearance of the vehicles102, such as color, model, user name, etc., may be included in the wireless messages202. In an example, the vehicles102may periodically broadcast the wireless messages202. In another example, a lead vehicle102may broadcast a wireless message202that, if received by other vehicles102, causes the other vehicles102to provide their locations to the lead vehicle102in response wireless messages202.

At operation1404, the vehicle102sends an invitation502to be displayed to at least a subset of the one or more other vehicles102. The vehicle102may send an invitation502message to at least subset of the one or more other vehicles102. The vehicle102may receive, from the one or more other vehicles102, a reply message indicating acceptance to join the group of vehicles102. The vehicle102may add the accepting vehicles102to the group of vehicles102. In an example, the invitation502message is broadcast to any of the one or more other vehicles102within wireless range of the wireless transceiver108. In another example, the vehicle102utilizes the wireless transceiver108to identify the one or more other vehicles102; displays, in the HMI302of the vehicle102, a listing of the one or more other vehicles102; receives, to the HMI302, a selection of which vehicles102of the one or more other vehicles102to invite; and sends the invitation502message to the selected vehicles102of the one or more vehicles102. The invitation502may include a description504informing the user that the vehicle102is invited to join a lighting group. The invitation502may also illustrate sender information508about the inviting vehicle102. The sender information508may include the information specified in the wireless messages202, such as a name of the inviting vehicle102, the color of inviting vehicle102, the make of the inviting vehicle102, etc.

At operation1406, the vehicle102identifies accepting vehicles102. In an example, the vehicle102may receive, from the one or more other vehicles102, reply messages indicating acceptance to join the group of vehicles102. In another example, the vehicle102may receive a request from one of the one or more other vehicles102to join the group of vehicles102. If so the vehicle102may display, in the HMI302, an indication of the request.

At operation1408, the vehicle102creates a group of the vehicles102. In an example, the vehicle102adds the vehicles102accepting the invitation502to the group of vehicles102. In another example, the vehicle102receive inputs from a user of the vehicle102via the HMI302to accept the requesting vehicle102into the group of vehicles102based on the input.

At operation1410, the vehicle102receives input of a collective lighting action. In an example, the vehicle102may receive, as input to the HMI302, a specification of which of the exterior lights of the plurality of the group of vehicles102to activate, wherein to instruct the group of vehicles102to collectively light the area200includes instructing the group of vehicles102to turn on the specified exterior lights. In another example, the vehicle102may receive as input to the HMI302, an indication1002to track one or more users via tracking devices120to illuminate the locations of the one or more tracking devices120and/or via or vehicle sensors126to illuminate the locations of movement surrounding the vehicles102. It yet another example, the vehicle102may receive as input to the HMI302, an indication to illuminate a specific location, e.g., as touch input to an HMI302of the vehicle102.

At operation1412, the vehicle102instructs the group of the vehicles102to perform the collective lighting action. In an example, the vehicle102may send, to the other vehicles102of the group, instructions of which of the exterior lights of the plurality of the group of vehicles102to activate, instructions to track the one or more tracking devices120, and/or instructions to illuminate a specific location. These instructions may be sent, e.g., via wireless messages202from the lead vehicle102to the other vehicles102of the group. After operation1412, the process1400ends.

FIG.15illustrates an example1500of a computing device1502for use in collective zone lighting features. Referring toFIG.6, and with reference toFIGS.1-5, the controllers104-116of the vehicles102, the tracking devices120, the drones1202, and lanterns1204may be examples including such computing devices1502. As shown, the computing device1502includes a processor1504that is operatively connected to a storage1506, a network device1508, an output device1510, and an input device1512. It should be noted that this is merely an example, and computing devices1502with more, fewer, or different components may be used.

The processor1504may include one or more integrated circuits that implement the functionality of a central processing unit (CPU) and/or graphics processing unit (GPU). In some examples, the processors1504are a system on a chip (SoC) that integrates the functionality of the CPU and GPU. The SoC may optionally include other components such as, for example, the storage1506and the network device1508into a single integrated device. In other examples, the CPU and GPU are connected to each other via a peripheral connection device such as peripheral component interconnect (PCI) express or another suitable peripheral data connection. In one example, the CPU is a commercially available central processing device that implements an instruction set such as one of the x86, ARM, Power, or microprocessor without interlocked pipeline stage (MIPS) instruction set families.

Regardless of the specifics, during operation the processor1504executes stored program instructions that are retrieved from the storage1506. The stored program instructions, accordingly, include software that controls the operation of the processors1504to perform the operations described herein. The storage1506may include both non-volatile memory and volatile memory devices. The non-volatile memory includes solid-state memories, such as not and (NAND) flash memory, magnetic and optical storage media, or any other suitable data storage device that retains data when the system is deactivated or loses electrical power. The volatile memory includes static and dynamic random-access memory (RAM) that stores program instructions and data during operation of the system100.

The GPU may include hardware and software for display of at least two-dimensional (2D) and optionally three-dimensional (3D) graphics to the output device1510. The output device1510may include a graphical or visual display device, such as an electronic display screen, projector, printer, or any other suitable device that reproduces a graphical display. As another example, the output device1510may include an audio device, such as a loudspeaker or headphone. As yet a further example, the output device1510may include a tactile device, such as a mechanically raiseable device that may, in an example, be configured to display braille or another physical output that may be touched to provide information to a user.

The input device1512may include any of various devices that enable the computing device1502to receive control input from users. Examples of suitable input devices that receive human interface inputs may include keyboards, mice, trackballs, touchscreens, voice input devices, graphics tablets, and the like.

The network devices1508may each include any of various devices that enable the vehicles152, traffic participants, and cloud server to send and/or receive data from external devices over networks. Examples of suitable network devices1508include an Ethernet interface, a Wi-Fi transceiver, a cellular transceiver, or a BLUETOOTH or BLE transceiver, an UWB transceiver or other network adapter or peripheral interconnection device that receives data from another computer or external data storage device, which can be useful for receiving large sets of data in an efficient manner.

The processes, methods, or algorithms disclosed herein can be deliverable to/implemented by a processing device, controller, or computer, which can include any existing programmable electronic control unit or dedicated electronic control unit. Similarly, the processes, methods, or algorithms can be stored as data and instructions executable by a controller or computer in many forms including, but not limited to, information permanently stored on non-writable storage media such as read-only memory (ROM) devices and information alterably stored on writeable storage media such as floppy disks, magnetic tapes, compact discs (CDs), RAM devices, and other magnetic and optical media. The processes, methods, or algorithms can also be implemented in a software executable object. Alternatively, the processes, methods, or algorithms can be embodied in whole or in part using suitable hardware components, such as Application Specific Integrated Circuits (ASICs), Field-Programmable Gate Arrays (FPGAs), state machines, controllers or other hardware components or devices, or a combination of hardware, software and firmware components.

While exemplary embodiments are described above, it is not intended that these embodiments describe all possible forms encompassed by the claims. The words used in the specification are words of description rather than limitation, and it is understood that various changes can be made without departing from the spirit and scope of the disclosure. As previously described, the features of various embodiments can be combined to form further embodiments of the invention that may not be explicitly described or illustrated. While various embodiments could have been described as providing advantages or being preferred over other embodiments or prior art implementations with respect to one or more desired characteristics, those of ordinary skill in the art recognize that one or more features or characteristics can be compromised to achieve desired overall system attributes, which depend on the specific application and implementation. These attributes can include, but are not limited to strength, durability, life cycle, marketability, appearance, packaging, size, serviceability, weight, manufacturability, ease of assembly, etc. As such, to the extent any embodiments are described as less desirable than other embodiments or prior art implementations with respect to one or more characteristics, these embodiments are not outside the scope of the disclosure and can be desirable for particular applications.

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 certain 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 broadest reasonable constructions and their ordinary meanings as understood by those knowledgeable in the technologies described herein unless an explicit indication to the contrary in 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.

The abstract of the disclosure is provided to allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in various embodiments for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separately claimed subject matter.

While exemplary embodiments are described above, it is not intended that these embodiments describe all possible forms of the invention. Rather, the words used in the specification are words of description rather than limitation, and it is understood that various changes may be made without departing from the spirit and scope of the invention. Additionally, the features of various implementing embodiments may be combined to form further embodiments of the invention.