CN117400822A

CN117400822A - Cross bar with illumination

Info

Publication number: CN117400822A
Application number: CN202310800761.4A
Authority: CN
Inventors: A·弗雷德里克森; J·拜尔; C·V·埃德; P·M·洛巴卡罗; Z·J·鲁德尼基; E·R·格拉泽
Original assignee: Rivian IP Holdings LLC
Current assignee: Rivian IP Holdings LLC
Priority date: 2022-07-08
Filing date: 2023-07-03
Publication date: 2024-01-16

Abstract

Particular embodiments may provide a rail having a plurality of light sources and a controller. The controller may be configured to: determining a sequence of vehicles, and in response to determining the sequence, causing a light source of the plurality of light sources to perform an action.

Description

Cross bar with illumination

Cross Reference to Related Applications

The present application claims the benefit of U.S. provisional application No. 63/359,757, filed on 7.8 of 2022, the entire contents of which are hereby incorporated by reference in their entirety.

Introduction to the invention

Many passenger vehicles, sport Utility Vehicles (SUVs) and trucks have vehicle mounting posts thereon. The mounting pole is popular among exploration lovers and can conveniently carry larger items unsuitable for the cargo area of a vehicle, such as bicycles, canoes, kayaks, skis, snowboards, surfboards, camping equipment, and the like. In addition to carrying larger items, the mounting bar greatly expands the carrying capacity of the vehicle.

Disclosure of Invention

While having cargo advantages, conventional crossbars have limited functionality. The crossbars disclosed herein advantageously include light sources, for example, to illuminate a scene in front of, beside, or behind the vehicle. In some embodiments, the crossbars disclosed herein provide a plurality of light sources. In some further embodiments, in response to the determined sequence, a light source of the plurality of light sources performs an action (e.g., a light generating action). For example, in response to determining a vehicle turn sequence, a light source located at an end of the rail is caused to perform a yellow light generating action to signal the vehicle to turn.

In some embodiments, an apparatus comprises: a rail comprising a plurality of light sources; and a controller configured to: determining a sequence of vehicles; and in response to determining the sequence, causing at least one light source of the plurality of light sources to perform an action.

In some embodiments of the apparatus, the sequence comprises a vehicle braking sequence, and the controller is configured to: in response to determining the vehicle braking sequence, a first light source located on the rear side of the rail is caused to generate a first light (e.g., red light) and a second light source located on the front side of the rail is caused to generate a second light (e.g., white light, red light, flash light).

In some embodiments of the apparatus, the sequence comprises a vehicle turn sequence, and the controller is configured to: in response to determining the vehicle turn sequence, at least one light source located on the lateral end of the rail is caused to generate periodic/pulsed third light (e.g., yellow light).

In some embodiments of the device, the crossbar includes an accessory insertion port, the sequence includes an accessory insertion sequence, and the controller is configured to: in response to determining the accessory insertion sequence, a light source of the plurality of light sources associated with the accessory insertion port is caused to generate light.

In some embodiments, the sequence includes a chase sequence, and the controller is configured to: in response to determining the chase sequence, a first light source of the plurality of light sources is caused to generate a first light (e.g., white light), and second and third light sources of the plurality of light sources are caused to generate a second light (e.g., yellow, and red light), wherein the first light source is located between the second and third light sources.

In some embodiments, the sequence includes a vehicle unlock sequence, and the controller is configured to: in response to determining the vehicle unlock sequence, a first light source of the plurality of light sources is caused to generate a first light (e.g., white light), and then a second light source of the plurality of light sources and a third light source are caused to generate a second light (e.g., white light, and red light), wherein the first light source is located between the second light source and the third light source.

In some embodiments of the apparatus, the sequence comprises a follow-up sequence, and the controller is configured to: in response to determining the follow sequence, a first light source on the rear side of the rail is caused to generate a first light (e.g., yellow light), and second and third light sources on the rear side of the rail are caused to generate a second light (e.g., yellow, and red light), wherein the first light source is located between the second and third light sources.

In some embodiments of the device, the sequence comprises a locking sequence, and the controller is configured to: in response to determining the locking sequence, causing a light source on the rear side of the rail to generate light of a first intensity and subsequently causing the light source on the rear side of the rail to generate light of a second intensity, the first intensity being greater than the second intensity.

In some embodiments of the apparatus, the plurality of light sources includes a forward light source, a backward light source, a side end light source, and a bottom surface light source.

In some embodiments of the apparatus, the crossbar includes electrical connections. In some embodiments, the cross bar includes a mounting bracket for coupling the cross bar to a vehicle. In some embodiments, the rail includes an electrical connector and a mounting bracket for coupling the rail to the vehicle, wherein the electrical connector is located in the mounting bracket. In some embodiments, the cross bar comprises an aluminum extrusion.

In some embodiments, the device includes a user interface configured to receive a user-initiated sequence, and determining the sequence includes determining the user-initiated sequence.

In some embodiments of the apparatus, the controller is configured to: in response to determining the sequence, determining whether the sequence is restricted; in response to determining that the sequence is unrestricted, allowing the light source of the plurality of light sources to perform the action; in response to determining that the sequence is restricted and the restriction criteria are met, allowing the light source of the plurality of light sources to perform the action; and in response to determining that the sequence is restricted and the restriction criteria are not met, forgoing causing the light source of the plurality of light sources to perform the action.

In some embodiments, a computer-readable non-transitory storage medium containing software that includes instructions that are operable when executed to perform operations comprising: determining a sequence of vehicles; in response to determining the sequence, a signal is sent to cause the rail light source to perform an action.

In some embodiments of the medium, determining the sequence of the vehicle includes determining a user initiated sequence.

In some embodiments of the medium, the operations include: in response to determining the sequence, determining whether the sequence is restricted; allowing the rail light source to perform the action in response to determining that the sequence is unrestricted; in response to determining that the sequence is restricted and the restriction criteria are met, allowing the rail light source to perform the action; and in response to determining that the sequence is restricted and the restriction criteria are not met, forgoing causing the rail light source to perform the action.

In some embodiments, a vehicle comprises: a rail mounted to the vehicle, the rail comprising a plurality of light sources; and a control system comprising a processor and a memory, the memory comprising instructions executable by the processor, the processor operable to execute the instructions to perform operations comprising: determining a sequence of vehicles; and in response to determining the sequence, sending a signal to cause the rail light source to perform an action.

In some embodiments of the vehicle, the rail comprises a top surface and a bottom surface, wherein the plurality of light sources comprises light sources located in the bottom surface, and wherein the light sources located in the bottom surface are configured to illuminate non-vehicle areas.

In some embodiments of the vehicle, the cross bar is configured to support a load when mounted on the vehicle.

The embodiments disclosed above are merely examples, and the scope of the present disclosure is not limited to them. Particular embodiments may include all, a portion, or none of the features, elements, features, functions, operations, or steps of the embodiments disclosed above. Embodiments according to the invention are specifically disclosed in the appended claims directed to methods, storage media, devices, systems and/or computer program products, wherein any feature mentioned in one claim category (e.g., methods) may also be claimed in another claim category (e.g., systems). The dependencies or references in the appended claims are chosen solely for formal reasons. However, any subject matter resulting from the deliberate reference to any preceding claim (particularly to a plurality of dependencies) may also be claimed such that any combination of claims and their features are disclosed and may be claimed regardless of the dependencies selected in the appended claims. The subject matter which may be claimed includes not only the combination of features as set forth in the attached claims, but also any other combination of features in the claims, wherein each feature mentioned in the claims may be combined with any other feature or combination of features in the claims. Furthermore, any of the embodiments and features described or depicted herein may be protected in separate claims and/or in any combination with any of the embodiments or features described or depicted herein or with any of the features of the appended claims.

Drawings

Fig. 1 shows an exemplary truck with a cross bar.

FIG. 2 illustrates an exemplary SUV having a crossbar.

Fig. 3A illustrates an exemplary rail having a plurality of light sources.

Fig. 3B shows another view of the crossbar of fig. 3A.

FIG. 4 illustrates an exemplary user interface for controlling a rail having a plurality of light sources.

Fig. 5A-5C illustrate exemplary actions performed by a light source of a rail.

Fig. 6A-6C illustrate exemplary actions performed by the light source of the rail.

Fig. 7A-7C illustrate exemplary actions performed by the light source of the rail.

Fig. 8A-8G illustrate exemplary actions performed by the light source of the rail.

Fig. 9A-9G illustrate exemplary actions performed by a light source of a rail.

Fig. 10A and 10B illustrate an exemplary crossbar.

FIG. 11 illustrates an exemplary vehicle.

FIG. 12 is a flowchart showing steps of a method for controlling a vehicle cross bar.

FIG. 13A is a schematic diagram of an exemplary computer system.

Fig. 13B shows exemplary firmware for a vehicle Electronic Control Unit (ECU).

Detailed Description

Fig. 1 shows an exemplary truck 100 having a rail 110 and a rail 120. The rail 110 is mounted to the roof 102 of the truck 100 via mounts 114A and 114B, and the rail 120 is mounted to the bed side panel 104 of the truck 100 via mounts 124 (additional mounts, not shown) (the rail 120 may be mounted to an opposing bed side panel (not shown)). The rail 110 and rail 120 include a plurality of light sources (112 and 122, respectively). In some embodiments, the rails 110 and 120 are configured to support a load. As used herein, a rail is configured to support a load when the rail (alone or in combination with another rail) is rated to support 220 lbs. In some embodiments, offset light sources are integrated into the rail. In other embodiments, the offset light source is separate from the rail and connected to the rail (or vehicle), as further described herein.

The controller is configured to cause one of the plurality of light sources to perform an action. As used herein, a light source may be understood as performing an action when it changes state in response to a signal. For example, the actions may include generating light (e.g., white light, red light, yellow light, blue light, green light, etc.), ceasing to generate light (e.g., turning off the light source that is generating light prior to the action), and changing the color of the light (e.g., switching activated white light to red light, and activated yellow light to white light). In some embodiments, the controller is configured to control the light sources individually (e.g., activate/deactivate the light sources independently, change the colors of the light sources independently). In some embodiments, the controller causes the plurality of light sources to perform actions to coordinate the plurality of light sources when generating the illumination pattern (e.g., animation). The light generation includes, for example, continuous illumination and periodic illumination (such as flashing, blinking, or pulsing), monochromatic, color-changing, or combined color light, and constant or varying intensity light.

In some embodiments, the controller is configured to determine a vehicle sequence, and in response to determining the vehicle sequence, cause a light source of the plurality of light sources to perform an action. As used herein, a vehicle sequence may be understood to correspond to one or more steps in a vehicle process. In some embodiments, the vehicle sequence is initiated by a user activation instruction, such as a user depressing a brake pedal, a user activating a turn signal, a user locking/unlocking the vehicle with a key fob, and a user interacting with a user interface. In some embodiments, the vehicle sequence may be independent of the cross bar. For example, a vehicle ECU determines a sequence for vehicle braking (e.g., a regenerative braking system), whether or not the vehicle has an associated rail; when the rail disclosed herein is added to a vehicle, the controller determines (by monitoring the corresponding ECU and/or by receiving signals from the ECU) the vehicle braking sequence, and in response to determining the vehicle braking sequence, causes a light source of the plurality of light sources to perform a red light generating action (see, e.g., fig. 5A-5C). In some embodiments, the vehicle sequence relies on a cross bar. For example, the controller may determine that an accessory is inserted into an accessory insertion port of the crossbar and, in response, cause a light source associated with the insertion port to perform a light generating action (see, e.g., fig. 9A-9G). In an embodiment, the controller may cause the light source to perform more than one action in response to the vehicle sequence. For example, the controller determines that the autopilot system is to slow down and turn the vehicle, and in response to determining the sequence of vehicles, the rail controller causes the light source to perform a red light generating action (see, e.g., fig. 5A-5C) and causes the light source to perform a yellow light generating action (see, e.g., fig. 7A-7C). In some embodiments, determining the vehicle sequence includes determining that all steps in the vehicle sequence have been performed. In other embodiments, determining the vehicle sequence includes determining that fewer than all of the steps in the vehicle sequence have been performed. For example, determining the vehicle sequence may include determining a launch step for the executed vehicle sequence.

The controller may "cause" the light source to perform an action, either directly or indirectly. For example, the controller may be associated with a rail (e.g., mounted in the rail or added to the vehicle) and may be associated with a vehicle (e.g., mounted in the vehicle for non-rail functionality) (an exemplary vehicle controller is disclosed below with reference to fig. 11). In some embodiments, the controller determining the sequence of the vehicle may send a signal to another controller (e.g., a controller in direct communication with the rail light source) to cause the light source to perform an action. In such examples, the plurality of controllers work together to form a single controller that determines the sequence of vehicles and, in response to determining the sequence, causes the light source of the plurality of light sources to perform an action.

Fig. 2 shows an exemplary SUV having a crossbar 210 and a crossbar 220. Similar to the rails 110 and 120 shown in fig. 1, the rails 210 and 220 include a light source 212, a light source 222, a mounting bracket 214A, a mounting bracket 214B, and a mounting bracket 224. The rails 210 and 220 are mounted on the roof 202 of the SUV 200.

The vehicles in fig. 1 and 2 are exemplary. While the present patent application shows a rail on a truck and SUV, it should be understood that the rails described herein are not limited by the type of vehicle in which the rail is mounted. For example, the cross bar may be mounted to a passenger vehicle, transport vehicle, tractor, camper, or the like. Further, unless explicitly described, the crossbar herein is not limited by the location where it is mounted to the vehicle. For example, although fig. 1 and 2 illustrate a cross bar mounted to the roof and cabin of a vehicle, the cross bar may be mounted inside the vehicle, on the outer surface of a windshield or other glass, on the top of a driver side door frame, on the hood of the vehicle, and so forth.

Fig. 3A shows an exemplary rail 300 having a plurality of light sources 310, a top surface 320, and a mounting bracket 330. In some embodiments, rail 300 is rail 110, rail 120, rail 210, or rail 220 described above.

Light source 310 includes a plurality of light sources configured to illuminate non-vehicle areas around the vehicle. The light source 310 includes a front side light source 312 and a side end light source 314. In some embodiments, the rail 300 includes a rear light source (not shown in fig. 3) and a bottom surface light source (not shown in fig. 3). As used herein, "front" and "rear" of a crossbar refer to opposite sides of the crossbar. When mounted to a vehicle, the "front" side of the crossbar refers to the forward direction of the vehicle (i.e., the "travel" direction of the vehicle), and the "rear" side of the crossbar refers to the rearward direction of the vehicle (i.e., the "reverse" direction of the vehicle). In some embodiments, the crossbar is configured to be mounted in a particular orientation such that one side is pre-designated as the forward side of the crossbar and the other side is pre-designated as the rearward side of the crossbar. In some embodiments, the rail is not preconfigured to be installed in a specified orientation. In such embodiments, once installed, the crossbar may be programmed by the user to designate one side as "front" and the other side as "rear". In some embodiments, the crossbar may automatically detect its orientation relative to the vehicle and automatically designate one side as "front" and the other side as "rear".

In some embodiments, the forward light source comprises a bright white Light Emitting Diode (LED). In these embodiments, high brightness white illumination may enhance the light produced by low beam or high beam lights on the vehicle.

The rail 300 also includes side end light sources 314. As used herein, a light source located at a rail side end may be understood to include a light source located in the transition from a front side light source to a rear side light source. Additional side-end light sources are identified below with reference to fig. 6A-9G. The side light sources can enhance the turn signal and hazard signal of the vehicle. In some embodiments, the side light sources and nearby front side light sources may be used as turn signals to enhance light from the vehicle. In some embodiments, a light 334 (see fig. 3B) is used as the turn light. In such embodiments, the bottom surface light 334 is directed downward and forward of the vehicle. The lack of illumination of the front corners of conventional vehicles reduces visibility during cornering, particularly during low speed sharp cornering on uneven terrain. Side-end light sources (or bottom surface lamps 334), particularly high brightness light sources, may address these drawbacks. In some embodiments, the turn signal is activated by a controller. For example, the controller may monitor vehicle parameters (e.g., vehicle speed, steering angle, overall vehicle inclination, etc.), and in response to determining a vehicle steering or turning sequence, cause the light source at the rail side end (or on the bottom surface) to perform a light generating action. The light sources at either end of the rail may be activated to assist in steering on the respective sides of the vehicle.

In some embodiments, the plurality of light sources 310 are individually adjustable. To this end, the light source may be a separate light source, such as an LED. The individually adjustable light sources may also include a backlight panel (e.g., similar to a liquid crystal display) having individually controllable pixels. The rail 300 includes RGBW functionality visible from all sides of the vehicle. In embodiments where the individual light sources are controlled individually, 360 ° illumination advantageously allows for a large number of different illumination modes. Such animations may include, but are not limited to, welcome animations, side indicator extensions, follow-up functions, color recognition for tracking usage, or auxiliary car lighting.

In some embodiments, the circumferential surface with the light source continuously encircles the rail. The circumferential surface is located between a top surface configured to support cargo (e.g., top surface 320 of crossbar 300) and a bottom surface having a mounting bracket (e.g., mounting bracket 330 of crossbar 300) configured to be attached to a vehicle.

Some embodiments include task lighting in the bottom surface of the rail. An exemplary task light 334 is shown in fig. 3B. The bottom surface light source may be understood to include a light source located on a surface opposite a rail surface configured to support a load. In embodiments where the rail is mounted to the roof of the vehicle, the bottom surface is proximate the vehicle and the top surface is distal from the vehicle. For example, the bottom surface light source in the rail of fig. 1 and 2 would be on the same side of the rail as the mount. The bottom surface light source is positioned to illuminate a non-vehicle area beside the vehicle. In some embodiments, the controller causes the bottom surface light surface to perform an action in response to the controller determining a vehicle sequence. For example, when the controller determines a door opening sequence, in some embodiments, the controller may cause the bottom surface light source to perform a light generating action to illuminate an area of the vehicle adjacent the vehicle door. Similarly, if the controller determines a door closing sequence, the controller may cause the bottom surface light source to cease generating light. In some embodiments, the bottom surface light source provides a floodlight. These may assist in stationary activities such as campsite lighting, task lighting, or any other general lighting that assists the user on the vehicle side. In some embodiments, the location of the user is monitored by radar or Near Field Communication (NFC) of the vehicle, and a light source of the plurality of light sources is illuminated such that the task lighting follows the user. In some embodiments, bottom surface lights 334 are used for steering, as described herein.

The crossbar 300 includes a top surface 320 configured to support a load. The top surface 320 includes channels 322 for securing cargo to the rails. In some embodiments, the channel 322 provides power to the accessory. Top surface 320 also includes accessory insertion port 324. The accessory insertion port 324 may be used to attach gear cables (see, e.g., fig. 9A-9G) and other accessories, but may also provide an electrical outlet.

The crossbar 300 includes a mounting bracket 330 configured to be attached to a vehicle. The mounting is located on a surface of the rail opposite the top surface 320. As shown in fig. 1 and 2, the mounting bracket may be attached to the vehicle outside of the vehicle, such as to the roof of the vehicle (e.g., to the roof 102 of the vehicle 100 or the roof 202 of the vehicle 200) or to the cabin of the vehicle (e.g., to the cabin side panel 104 of the vehicle 100). In other embodiments, the crossbar is attached to the interior of the vehicle. The mounts may attach the cross bar to the vehicle using any suitable method, including mechanical (e.g., bolts, clamps), magnetic, suction, etc.

In some embodiments, the crossbar 300 includes electrical connectors that are coupled to the light sources. The electrical connection may receive power, data, and control signals from the vehicle; data transmission and control signals may be used to operate the rail light source or to operate other accessories. In the crossbar 300, the mounting bracket 330 includes an electrical connector 332 that is physically connected to the vehicle. In some embodiments, the electrical connector is not physically connected to the vehicle. For example, the crossbar 300 may be powered by a battery power source (e.g., a battery compartment in the crossbar) and the data transmission/control is via a wireless connection (e.g., bluetooth, wi-Fi, NEC, etc.). In some embodiments, a USB port is used for the electrical connection of the crossbar.

Fig. 4 illustrates an exemplary user interface 400 for controlling a rail including a plurality of light sources. The user interface 400 may be presented on a vehicle interface, a smart device, or any interface that provides the user with the functionality to control rail illumination. The user interface 400 includes a representation 402 of the crossbar when viewed from the front of the vehicle and a representation 404 of the crossbar when viewed from the rear of the vehicle. The user interface 400 provides the following functionality to the user: a light generating action is initiated in front of the rail (button 410), behind the rail (button 412), changing the color generated by the light sources of the rail (button 414, button 416 and button 418), and changing the intensity of the light generated by the light sources of the rail (button 420, button 422 and button 424). When a user selects to make a change to the crossbar at the user interface, a controller (e.g., an experience management module (XMM) ECU) determines a sequence of vehicles initiated by the user. In response to determining the vehicle sequence, the controller causes a light source of the plurality of light sources to perform an action.

In some embodiments, the crossbar is a single crossbar, such as shown in the user interface of fig. 4. In other embodiments, the cross bar may be a plurality of bars, for example, one bar at the front of the vehicle and one bar at the rear as shown in fig. 1 and 2. The light source actions of the cross bars can be coordinated by the cross bars. Taking the vehicle braking sequence (see fig. 5A-5C below) as an example, a first light source in the front side of the front rail may be controlled to perform a white light generating action and a second light source in the rear side of the rear rail may be controlled to perform a red light generating action.

In some embodiments, the controller is configured to limit the motion by a mode or state of the vehicle. For example, the user may be restricted from selecting a sequence of vehicles on the user interface 400 unless the vehicle is in a park mode. In some embodiments, the controller is further configured to determine whether the sequence is restricted in response to determining the sequence. The controller may determine the restricted sequence by accessing a stored restricted sequence list. In response to determining that the sequence is unrestricted, the controller is configured to allow the light source of the plurality of light sources to perform an action. In some embodiments, the controller is configured to allow the light sources of the plurality of light sources to perform an action in response to determining that the sequence is restricted and the restriction criteria are met. In some embodiments, the controller is configured to forgo causing the light source of the plurality of light sources to perform an action in response to determining that the sequence is restricted and the restriction criteria are not met. For example, the restricted sequence may include a light source action restricted to the vehicle being in a park mode or an off-road mode. For example, in some embodiments, the sequence (e.g., the following sequence discussed below) is limited to an "off-road" mode. When the controller determines the follow-up sequence, in some embodiments, the controller may determine whether a limit criterion is met (in this example, the limit criterion is that the vehicle is in an "off-road" mode), and if the vehicle is in an off-road mode, then the associated light generating action is allowed. If the vehicle is not in the off-road mode, the controller may forgo causing the associated light generating action.

The user interface 400 includes a "following vehicle" button 424. In the following vehicle mode, vehicles in the fleet may use crossbars to provide visual communication between the fleet and other members of the fleet. For example, the controller may cause the cross bar to perform a sequence of following vehicles when other vehicles in the fleet have fallen behind a fleet lead a set distance. In embodiments with a follow-up sequence, the controller may determine the follow-up sequence by identifying that the distance between the vehicles has exceeded a threshold. In other embodiments, when ambient light conditions limit visual communication between vehicles, the following vehicle may communicate with a lead of the fleet (e.g., via a Telematics Control Module (TCM) ECU) (in some such embodiments, the vehicle may communicate with other vehicles in the fleet using, for example, the TCM ECU). The controller may be configured to cause a first light source on the back side of the rail to perform a yellow light generating action in response to determining the follow-up sequence, and cause second and third light sources on the back side of the rail to subsequently perform a yellow light generating action, wherein the first light source is located between the second and third light sources.

In some embodiments, the vehicle sequence is a braking sequence and the action includes a white light generating action on the front side of the rail and a red light generating action on the rear side of the rail. In embodiments in which the sequence includes a vehicle braking sequence, the controller may be configured to cause a first light source on a rear side of the rail to perform a red light generating action and a second light source on a front side of the rail to perform a white light generating action in response to determining the vehicle braking sequence.

Fig. 5A-5C illustrate exemplary actions performed by a light source of a rail in response to a controller determining a vehicle braking sequence. Fig. 5A to 5C show a front side light source 502 and a rear side light source 504. As shown in fig. 5A, the front side light source 502 performs a white light generating action and the rear side light source 504 performs a red light generating action. In some implementations, the back side light source 504 performs a white light generating action or a flash light generating action. In such an arrangement, the vehicle may operate in a normal operating mode (e.g., no vehicle sequence is determined). Fig. 5B shows the front side light source 502 and the rear side light source 504 performing an action in response to a braking sequence. In fig. 5B, the front side light source 502 has not changed, but the back side light source 504 has performed a red light generating action, i.e. the intensity of the light has increased (compared to the intensity of the generated light depicted in fig. 5A). Fig. 5C shows the front side light source 502 and the rear side light source 504 after the braking sequence has ended. The braking sequence may have ended when, for example, a brake pedal in the vehicle is released. In the embodiment of fig. 5C, the front side light source 502 is likewise unchanged, but the back side light source 504 performs a red light generating action, i.e. the intensity of the light is reduced from that in fig. 5B.

In some embodiments, the controller determines the vehicle braking sequence by determining that a brake pedal is activated (e.g., by a Body Control Module (BCM) ECU), by determining that an autopilot system is decelerating the vehicle (e.g., by an Autonomous Control Module (ACM) ECU), by determining that a regenerative braking system is decelerating the vehicle (e.g., by a Vehicle Dynamics Module (VDM) ECU), or by determining that a brake light is activated (e.g., by a trailer brake light, a Rear Zone Control (RZC) ECU for a rear parking light, or by a BCM ECU for a rear parking light). The controller determines that the braking sequence has ended when, for example, the brake pedal is released, the autopilot system stops decelerating the vehicle, the regenerative braking system stops decelerating the vehicle, the brake lights are deactivated, a period of time has elapsed since the determination of the vehicle sequence, or the controller determines to return to the normal mode (e.g., by the VDM ECU, by the Central Gateway Module (CGM) ECU). In response to determining that the braking sequence has ended, the controller may, for example, stop causing the light source to perform an action, cause the light source to appropriately perform a light generating action before the controller determines the braking sequence, or cause the light source to perform a light generating action associated with a mode of the vehicle (e.g., the normal mode depicted in fig. 5A).

In some embodiments, the vehicle sequence is a vehicle unlock sequence, and the action includes a first light source of the plurality of light sources performing a white light generating action and a second light source and a third light source of the plurality of light sources subsequently performing a white light generating action, wherein the first light source is located between the second light source and the third light source. In embodiments in which the sequence includes a vehicle unlock sequence, the controller is configured to cause a first light source of the plurality of light sources to perform a white light generating action and subsequently cause a second light source and a third light source of the plurality of light sources to perform a white light generating action in response to determining the vehicle unlock sequence, wherein the first light source is located between the second light source and the third light source. In some embodiments, light sources adjacent to the second and third light sources of the plurality of light sources continue to perform white light generating actions. In some embodiments, the light sources continue to produce white light in this pattern until the rail is illuminated 360 degrees. In some embodiments, the light source at the rear side of the rail performs a red light generating action after the rear side performs a white light generating action.

Fig. 6A-6C illustrate exemplary actions performed by a light source of a rail in response to a controller determining a vehicle unlock sequence. Fig. 6A to 6C show a front side light source 602, a rear side light source 604, and a side light source 606.

As shown in fig. 6A, the light sources of the front side light source 602 perform a white light generation action, and then adjacent light sources in the front side light source 602 perform a white light generation action. In the example shown in fig. 6A, white light is generated from the middle of the front side of the cross bar, and then spread in two directions. The front side light sources in the directions of arrows 610 and 612 perform a white light generating action until the side light source 606 performs a white light generating action, and then the white light generating action continues to the light sources around the side ends in the direction of 614. Fig. 6B shows the rail, i.e., front side light source 602 and side light source 606, after the white light generating action continues around the rail. Next, as shown in FIG. 6C, the rear light source 604 performs a red light generating action.

In some embodiments, the vehicle sequence is a vehicle locking sequence and the action includes the light source on the rear side of the rail performing a light generating action at a first intensity, the light source on the rear side of the rail then performing the light generating action at a second intensity, the first intensity being greater than the second intensity. In embodiments in which the sequence includes a vehicle locking sequence, the controller is configured to cause the light source on the rear side of the rail to perform a light generating action at a first intensity and subsequently cause the light source on the rear side of the rail to perform a light generating action at a second intensity, the first intensity being greater than the second intensity, in response to determining the locking sequence.

In some embodiments, the unlock/lock sequence is initiated by a user operating a key (e.g., a button on a wireless key, a key turn in a vehicle lock), a user operating interface (e.g., a user interface on a smart device provides a lock/unlock button), and/or a user approaching a vehicle (e.g., a wireless key approaching/departing a vehicle, a paired smart device approaching/departing a vehicle). In such embodiments, the controller determines the vehicle unlock/lock sequence through a Vehicle Access System (VAS) ECU and/or a Door Control Module (DCM) ECU. The controller determines that the vehicle unlock/lock sequence has ended when, for example, the user has entered/exited the vehicle, a period of time has elapsed since the determination of the vehicle sequence, or the controller (e.g., VDM ECU, CGM ECU) determines to return to the normal mode. In response to determining that the vehicle unlock sequence has ended, the controller may, for example, stop causing the light source to perform an action, cause the light source to appropriately perform a light generating action before the controller determines the vehicle unlock sequence, or cause the light source to perform a light generating action associated with a mode of the vehicle (e.g., the normal mode depicted in fig. 5A).

In some embodiments, the vehicle sequence is a vehicle turn sequence, and the action includes a yellow light generating action performed by a light source at the rail side end. In embodiments where the sequence includes a vehicle turn sequence, the controller may be configured to cause the light source on the rail side end to perform a periodic/pulsed yellow light generating action in response to determining the vehicle turn sequence.

Fig. 7A-7C illustrate exemplary actions performed by the light source of the rail in response to the controller determining a vehicle turn sequence. Fig. 7A-7C illustrate a front side light source 702, a back side light source 704, and a side light source 706. As shown in fig. 7A, the front side light source 702 performs a white light generating action, and the rear side light source 704 performs a red light generating action. In such an arrangement, the vehicle may be operated in a driving mode (e.g., the vehicle is parked or driving and no vehicle sequence is determined). In fig. 7B, the light source of the side light source 706 performs a yellow light generating operation. In the example of fig. 7B, the intensity of yellow light is greater than the intensity of white light produced by the front side light source 702 and red light produced by the rear side light source 704. In this way, attention is drawn to the turning of the vehicle. In FIG. 7C, the side-end light source has stopped performing yellow light generating operations. In some embodiments, the side-end light source 706 may alternate between fig. 7B and fig. 7C in determining the vehicle turn sequence.

In some embodiments, determining the vehicle turn sequence includes detecting activation of a turn control (e.g., receiving user input on a steering column control, monitoring a VDM ECU for vehicle steering), detecting an autopilot-initiated turn (e.g., an ACM ECU), detecting an autopilot-initiated lane change, etc. (e.g., an ACM ECU). In some embodiments, determining the vehicle turn sequence includes detecting that a vehicle turn light has been activated (e.g., an RZC ECU or BCM ECU operating the turn light). When, for example, the vehicle turning signal is off, a period of time has elapsed since the determination of the vehicle sequence, or the controller (e.g., VDM ECU, CGM ECU) determines to return to the normal mode, the controller determines that the vehicle turning sequence has ended. In response to determining that the vehicle turn sequence has ended, the controller may, for example, stop causing the light source to perform an action, cause the light source to appropriately perform a light generating action before the controller determines the vehicle turn sequence, or cause the light source to perform a light generating action associated with a mode of the vehicle (e.g., the normal mode depicted in fig. 7A).

In some embodiments, the vehicle sequence is a chase sequence, and the action includes a first light source performing a white light generating action and a second light source and a third light source of the plurality of light sources performing a yellow light generating action, wherein the first light source is located between the second light source and the third light source. In some embodiments, the action performed in response to determining the chase sequence includes the fourth light source and the fifth light source performing a red light generation action. In some embodiments, the second light source and the third light source are located between the fourth light source and the fifth light source.

Fig. 8A-8G illustrate exemplary actions performed by the light source of the rail in response to the controller determining the chase sequence. Fig. 8A to 8G show a front side light source 802, a rear side light source 804, and a side light source 806. As shown in fig. 8A, the front side light source 802 performs a white light generating action, and the rear side light source 804 performs a red light generating action. In such an arrangement, the vehicle may operate in a normal operating mode (e.g., the vehicle is parked or driving and no vehicle sequence is determined). Fig. 8B shows the back side light source 804 no longer performing light generating actions. In fig. 8C, light source 804A in back side light source 804 performs a white light generating action, and light sources 804B and 804C in back side light source 804 perform a red light generating action. In fig. 8D, light source 804D and light source 804E (located on either side of light source 804A) in back side light source 804 perform a yellow light generating action. The intensity of the yellow light generating action of light source 804D and light source 804E is greater than the intensity of the white light generating action of 804A and the red light generating actions of 804B and 804C. In fig. 8E, light source 804D and light source 804E have stopped performing yellow light generating actions. In fig. 8F, light source 804E performs a yellow light generating action with a greater intensity than the white light generating action of 804A and the red light generating actions of 804B and 804C. In FIG. 8G, light source 804E has stopped performing the yellow light generating action, light source 804D performs the yellow light generating action with a greater intensity than the white light generating action of 804A and the red light generating actions of 804B and 804C. In some embodiments, the illumination pattern of fig. 8B-8G is repeated until it is determined that the chase sequence has ended.

In some embodiments, the controller determines the chase sequence by receiving a chase notification of a third party (e.g., a law enforcement agency has transmitted a chase instruction). In such embodiments, the TCM ECU may receive the notification and determine the chase sequence. The controller determines that the chase sequence has ended when, for example, a new notification is received, the vehicle is parked in the park, a period of time has elapsed since the determination of the vehicle sequence, or the controller (e.g., VDM ECU, CGM ECU) determines to return to the normal mode. In response to determining that the vehicle chase has ended, the controller may, for example, stop causing the light source to perform an action, cause the light source to appropriately perform a light generating action before the controller determines the chase sequence, or cause the light source to perform a light generating action associated with a mode of the vehicle (e.g., the normal mode depicted in fig. 8A).

In some embodiments, the vehicle sequence is an accessory insertion sequence, and the action includes a light generating action performed by a light source associated with the accessory insertion port.

Fig. 9A-9G illustrate exemplary actions performed by the light source of the rail in response to the controller determining the attachment insertion sequence. Fig. 9A to 9G show a front side light source 902, a rear side light source 904, and a side end light source 906. The crossbars shown in fig. 9A-9G illustrate light sources that perform light generating actions in response to insertion of accessory 910 and accessory 914 into accessory insertion port 912 and accessory insertion port 916, respectively. As shown in fig. 9A, the front side light source 902 performs a white light generating action, and the rear side light source 904 performs a red light generating action. In such an arrangement, the vehicle may operate in a normal operating mode (e.g., the vehicle is parked or driving and no vehicle sequence is determined).

As used herein, a light source is associated with an accessory insertion port if the position of the light source relative to the accessory insertion port distinguishes the accessory port from a different accessory port. For example, in fig. 9A-9G, front light source 904A on the left side of the rail is associated with left side accessory port 912, and front light source 904B on the right side of the rail is associated with right side accessory port 916. In the case of a rail having one port, any light source may be associated with the accessory insertion port.

In fig. 9A, accessory 910 is inserted into accessory port 912 in direction 920. As shown in fig. 9B, in response to determining that the accessory 910 is inserted into the port 912, the controller has caused all light sources in the rail to cease performing light generating actions. To notify the successful insertion of the accessory, the controller causes the light source 902A and the light source 904A associated with the insertion port 912 to perform a white light generating action. These actions are shown in fig. 9C. In fig. 9D, the accessory insertion sequence of accessory 910 has ended and the controller has caused the light source of the rail to return to the action shown before the controller determines the accessory insertion sequence (i.e., the light generating action depicted in fig. 9A). Insertion of the accessory 914 into the accessory port 916 in direction 922 is also shown in fig. 9D. The sequence for inserting an accessory into the insertion port 916 followed by fig. 9E to 9G is the same as the sequence for inserting an accessory into the insertion port 912 followed by fig. 9B to 9D: in fig. 9E, the controller causes all light sources to cease light generation actions; in fig. 9F, the controller is controlled such that light source 902B and light source 904B associated with the add port 916 perform a white light generating action; also, in fig. 9G, the accessory insertion sequence of accessory 914 has ended and the controller has caused the light source of the rail to return to the action shown before the controller determines the accessory insertion sequence (i.e., the light generating action depicted in fig. 9D).

In fig. 9A to 9G, the accessory shown is a gear protection cable. It should be appreciated that other accessories may be inserted into the accessory insertion port. The gear protection cable may include additional features such as integrated gear safety, automatic clasping/attachment, load sensing, autonomous driving sensors, and/or gear collision detection warnings. Regarding gear safety, the rail may include an integrated cable lock, camera, accelerometer, or other feature to secure items placed on the rail. The cable lock may be automatically retractable to accommodate any slack in the cable that may jump in the wind while traveling (additional length may be stored within the crossbar). With respect to automatic latching of the latch, a motor (not shown) within the crossbar may drive the latching mechanism. In embodiments with load sensing, strain gauges or other sensors in the rail can calculate the load, which is then fed to the vehicle to provide an alert of overload or range adjustment calculation. Such sensors may be paired with additional sensors to identify if the item is loose on the rail, again providing an alert to the user. In embodiments with autonomous driving sensors, sensors such as radar may be embedded into the rail to assist in autonomous driving features. In some embodiments, a camera or other sensor may be used to provide a gear collision warning to an object on the rail, and a warning may be issued when a basement, garage, or other underhung item is at risk of collision with the object.

In some embodiments, the controller determines the accessory insertion sequence by determining to communicate with the accessory (e.g., the CGM ECU communicates with the accessory). The controller determines that the accessory insertion sequence has ended when, for example, the accessory communication insertion process has ended, a period of time has elapsed since the determination of the vehicle sequence, or the controller (e.g., VDM ECU, CGM ECU) determines to return to the normal mode. In response to determining that accessory insertion has ended, the controller may, for example, stop causing the light source to perform an action, cause the light source to appropriately perform a light generating action before the controller determines the vehicle unlock sequence, or cause the light source to perform a light generating action associated with a mode of the vehicle (e.g., the normal mode depicted in fig. 5A).

In addition to the sequences shown above with respect to fig. 5A-9G, the controller may determine other vehicle sequences and cause the light sources to perform actions associated with the sequences. For example, a vehicle accident or vehicle damage (e.g., a VDM ECU monitoring a vehicle driveline or suspension) or an emergency event (e.g., a VDM ECU determining that an emergency brake has been activated while the vehicle is in a driving mode) may be determined, and the controller may cause the light source to perform a hazard light action (e.g., a flashing yellow light generating action at the side light source). In some embodiments, the controller determines a car usage sequence (e.g., the RZC ECU determines car drape activation, side car latch activation, tailgate latch activation, or cargo lamp activation) and controls the rear light source to perform a light generating action that illuminates the car. In some embodiments, the controller determines external light activation by a vehicle controller (e.g., BCM ECU that causes light action of headlights, side lights, tail lights, camping lights) and causes the light sources in the cross bar to perform light action that supplements the vehicle lighting. For example, a Winch Control Module (WCM) ECU may cause a vehicle light to perform an action that draws attention to the use of the winch by the vehicle; the controller may cause the light source on the rail to perform a light generating action that also draws attention to the vehicle's use winch in response to determining that the WCM ECU is drawing attention via the lights of the vehicle.

Fig. 10A and 10B illustrate an exemplary crossbar 1000 and an exemplary crossbar 1050. The crossbar 1000 and the crossbar 1050 may be crossbars as shown in fig. 1 through 3, may be controlled by the user interface shown in fig. 4, and may perform the actions shown in fig. 5A through 9G. Fig. 10A and 10B illustrate cross-sections of the rail 1000 and rail 1050 to illustrate an exemplary structural arrangement of the rails. The rails 1000 and 1050 include a top surface 1010 and a top surface 1050, respectively. The lamp strips 1020 and 1070 are inserted into the channels 1022 and 1072, respectively. The light strip generates light to perform the actions described herein. In light strips 1020 and 1070, the LEDs (visible in fig. 10A) are individually controllable. In each rail, a panel (not shown) is inserted into channel 1024 and channel 1074, respectively. In some embodiments, the panel is a diffuser panel that softens glare and reduces glare. In fig. 10A, the light strip 1020 of the rail 1000 directs light onto the panel. In fig. 10B, the light strip 1070 reflects light from the reflective surface 1076 onto the panel.

In some embodiments, the body of the rails 1000 and 1050 are fabricated from an aluminum extrusion. The aluminum extrusion may advantageously provide an effective heat sink for the lamp strip. This may be particularly advantageous when high power light sources are employed that generate more heat. Additional thermal management may be provided by the airflow over the rails as the vehicle travels. Aluminum extrusions may also reduce rail weight while providing sufficient strength to support cargo or equipment on the roof of a vehicle.

Fig. 11 illustrates an exemplary vehicle 1100 having a crossbar 1140 and a crossbar 1142. In some embodiments, the crossbars 1140 and 1142 include the features described herein with respect to crossbars 110, 120, 210, 220, 300, 1000, and 1050.

Vehicle 1100 may include a plurality of sensors 1110, a plurality of cameras 1120, and a control system 1130. In some implementations, the vehicle 1100 can be paired with a computing device 1150 (e.g., a smart phone 1150a, a tablet computing device 1150b, or a smart vehicle accessory). By way of example and not limitation, sensor 1110 may be an accelerometer, a gyroscope, a magnetometer, a Global Positioning Satellite (GPS) signal sensor, a vibration sensor (e.g., a piezoelectric accelerometer), a light detection and ranging (LiDAR) sensor, a radio detection and ranging (RADAR) sensor, an ultrasonic sensor, a temperature sensor, a pressure sensor, a humidity sensor, a chemical sensor, an electromagnetic proximity sensor, a current sensor, another suitable sensor, or a combination thereof. By way of example and not limitation, camera 1120 may be a still image camera, a video camera, a 3D scanning system (e.g., based on modulated light, laser triangulation, laser pulses, structured light, light detection and ranging (LiDAR)), an infrared camera, other suitable cameras, or a combination thereof. The vehicle 1100 may include various controllable components (e.g., doors, seats, windows, lights, HVAC, entertainment systems, security systems), instrumentation and information displays and/or interactive interfaces, functionality to pair a computing device 1150 with the vehicle (which may enable control of certain vehicle functions using the computing device 1150), and functionality to pair accessories with the vehicle, which can then be controlled through the interactive interface in the vehicle or through the paired computing device 1150.

The control system 1130 may enable control of various systems on the vehicle. As shown in fig. 11, the control system 1130 may include one or more ECUs, each dedicated to a particular set of functions. Each ECU may be a computer system (as further described in fig. 13), and each ECU may include functionality provided by one or more of the exemplary ECUs described below.

Features of embodiments as described herein may be controlled by a VDM ECU. The VDM ECU can control a number of different functions related to the driveline, regenerative braking, suspension, steering, traction control, mass distribution, aerodynamic characteristics, and driving modes of the vehicle. In some embodiments, by way of example and not limitation, the VDM ECU may control vehicle acceleration, control vehicle energy regeneration, calculate torque distribution, provide traction control, control drive mode, provide odometer functionality, control driveline disconnect, adjust damping, adjust roll stiffness, adjust chassis height, automatically level the vehicle while on a grade, and control emergency park brake actuators.

Features of embodiments as described herein may be controlled by one or more ECUs that provide the functionality of controlling access to and from a vehicle. The VAS ECU may provide a passive/active wireless sensor (e.g., bluetooth) that authorizes access (i.e., locking or unlocking) to the vehicle. The NFC ECU may support an NFC reader embedded in the vehicle (e.g., in the driver side outside door handle or in the inside armrest, driver side door panel) for user authentication.

Features of embodiments as described herein may be controlled by a TCM ECU. The TCM ECU may provide a wireless vehicle communication gateway to support functions such as, by way of example and not limitation, over The Air (OTA) software updates, communications between the vehicle and the internet, communications between the vehicle and the computing device 1150, in-vehicle navigation, workshop communications, communications between the vehicle and landscape features (e.g., automatic toll road sensors, automatic toll gates, power distributors at charging stations), or automatic call functions.

Features of embodiments as described herein may be controlled by one or more ECUs that provide functionality for controlling in-cabin components of a vehicle. The DCM ECU may provide functions that sense the external ambient temperature or control one or more components of the vehicle's door, such as (by way of example and not limitation) a window glass (e.g., move glass up or down), a door lock, a door handle (e.g., automatically move in or out to facilitate grasping a handle), a light, a side mirror (e.g., up, down, move in, out, fold, unfold), a mirror heater, an electrochromic mirror dimmer, a turn signal, an approach light, a spotlight, a blind spot monitor light, or a window switch light.

Features of embodiments as described herein may be controlled by the RZC ECU. The RZC ECU may provide functionality to control different body components based on body type, such as (by way of example and not limitation) license lamps. For vehicles with a cabin, the RZC ECU may provide the function of controlling the cabin cover, side cabin latch, tailgate latch, side cabin lights or cargo lights. For sport utility vehicles having a rear door, the RZC ECU may provide the function of controlling a lift-gate latch, lift-gate actuator, rear-view mirror foot light, or rear wiper blade. For vehicles with trailer hooks, the RZC ECU may provide the function of controlling the trailer brakes or the trailer brake parking lights. For a vehicle having a third row of seats, the RZC ECU may provide the function of controlling the movement of the internal components to facilitate access to the rear row of seats. For transportation vehicles, the RZC ECU may provide the function of controlling the movement of the bulkhead door motor and latch, the rollup door latch, various lights, rear stop lights, and turn lights.

Features of embodiments as described herein may be controlled by a BCM ECU. BCM ECU may provide electronic control for various components of the body of the vehicle such as (by way of example and not limitation): interior lighting (e.g., cabin lights, seat belt lights), exterior lighting (e.g., headlamps, side lights, tail lights, camping lights), power sockets, trunk switches, window wiper movement and glass water deployment devices, overhead center consoles, speakers, power ports, and wireless accessory charging and docking devices.

Features of embodiments as described herein may be controlled by the WCM ECU. The WCM ECU may provide the function of operating a winch mounted or coupled to the vehicle. The WCM ECU can control the reeling in and out of the winch cable, measure the force of the payload on the winch assembly, control the winch remote clutch, and provide a security feature associated with the winch.

Features of the embodiments as described herein may be controlled by a CGM ECU. The CGM ECU may be used as a communication backbone of a vehicle that connects and transmits data to and from various ECUs, sensors, cameras, motors and other vehicle components. The CGM ECU may include a network switch providing connectivity through a Controller Area Network (CAN) port, a Local Interconnect Network (LIN) port, and an ethernet port. The CGM ECU may also be used as a master control for different vehicle modes (e.g., road driving mode, park mode, off-road mode, traction mode, camping mode) to control certain vehicle components associated with placing the vehicle in one of these vehicle modes. In some embodiments, for electric vehicles, the CGM ECU may also control the vehicle charging port door and associated lights and sensors.

Features of embodiments as described herein may be controlled by one or more ECUs that may provide functions of an Automatic Driving System (ADS) and/or an Advanced Driver Assistance System (ADAS), which may be enabled by a driver of a vehicle to provide one or more functions that support driving assistance and/or automation. The ACM ECU may process the data captured by camera #20 and/or sensor # 10. In some embodiments, the ACM ECU may provide artificial intelligence functions to provide and/or refine functionality for supporting driving assistance and/or automation. An Autonomous Safety Module (ASM) ECU may provide a function for supporting driving safety by monitoring sensors supporting a self-driving function. A Driver Monitoring System (DMS) ECU may provide functionality for monitoring the driver's level of attention and informing the control system of the driver's level of attention (e.g., while relying on driving assistance and/or automation functions). The DMS may process data captured by a camera positioned to monitor the driver's gaze. A Park Assist Module (PAM) ECU may provide functionality to assist the driver during manual and/or automatic park operations. The PAM ECU may process the data captured by camera #20 and/or sensor #10 in order to determine the appropriate control commands.

Features of embodiments as described herein may be controlled by an XMM ECU that may generate a user interface that is displayed on a vehicle dashboard. The user interface may display information and provide audio output for the infotainment system, including various views of the surroundings and interior of the vehicle. XMM can provide interactive control for many different vehicle functions that can be controlled in connection with enabling a specified mode, such as (by way of example and not limitation): control interior and exterior lighting, vehicle displays (e.g., instrument cluster, central information display, and rear console display), audio output (e.g., audio processing, echo cancellation, beam focusing), music playing, heating, ventilation, and air conditioning (HVAC) controls, power settings, wi-Fi connectivity, bluetooth device connectivity, and vehicle leveling, and displaying information in a user interface (e.g., panoramic camera feed, distance to nearest charging station, and lowest range). In some embodiments, the interactive control provided by the XMM may enable interaction with other modules of the control system 1130.

The vehicle 1100 may include one or more additional ECUs, such as, by way of example and not limitation, a Seat Control Module (SCM) ECU, a Restraint Control Module (RCM) ECU, and/or an autonomous experience module (AXM) ECU. If the vehicle 1100 is an electric vehicle, one or more ECUs may provide functionality related to the battery pack of the vehicle, such as a Battery Management System (BMS) ECU, a Battery Power Isolation (BPI) ECU, a voltage-to-neutral temperature (BVT) ECU, and/or a Thermal Management Module (TMM) ECU.

Fig. 12 is a flowchart illustrating steps of a method 1200 for controlling a vehicle cross bar. Method 1200 may begin with step 1210, where a vehicle sequence is determined. Method 1200 may then continue with step 1220, where, in response to determining the vehicle sequence, a signal is sent to cause at least one rail light source to perform an action.

In some embodiments of the method, the sequence comprises a vehicle braking sequence, and the method further comprises: in response to determining the vehicle braking sequence, a first light source located on the rear side of the rail is caused to generate red light and a second light source located on the front side of the rail is caused to generate white light.

In some embodiments of the method, the sequence comprises a vehicle turn sequence, and the method further comprises: in response to determining the vehicle turn sequence, a light source located on a side end of the rail is caused to generate periodic/pulsed yellow light.

In some embodiments of the method, the crossbar includes an accessory insertion port and the sequence includes an accessory insertion sequence, and the method further comprises: in response to determining the accessory insertion sequence, a light source of the plurality of light sources is caused to generate light, wherein the light source is associated with the accessory insertion port.

In some embodiments, the sequence comprises a chase sequence, and the method further comprises: in response to determining the chase sequence, causing a first light source of the plurality of light sources to generate white light and causing a second light source and a third light source of the plurality of light sources to generate yellow light, wherein the first light source is located between the second light source and the third light source.

In some embodiments, the sequence includes a vehicle unlock sequence, and the method further comprises: in response to determining the vehicle unlock sequence, causing a first light source of the plurality of light sources to generate white light and subsequently causing a second light source and a third light source of the plurality of light sources to generate white light, wherein the first light source is located between the second light source and the third light source.

In some embodiments of the method, the sequence comprises a follower sequence, and the method further comprises: in response to determining the follow-up sequence, causing a first light source on the rear side of the rail to generate yellow light, and causing a second light source and a third light source on the rear side of the rail to generate yellow light, wherein the first light source is located between the second light source and the third light source.

In some embodiments of the method, the sequence comprises a locking sequence, and the method further comprises: in response to determining the locking sequence, causing a light source on the rear side of the rail to generate light of a first intensity, and subsequently causing the light source on the rear side of the rail to generate light of a second intensity, the first intensity being greater than the second intensity.

In some embodiments of the method, the plurality of light sources includes a forward light source, a backward light source, a side end light source, and a bottom surface light source.

In some embodiments of the method, the cross bar includes electrical connectors. In some embodiments, the cross bar includes a mounting bracket for coupling the cross bar to a vehicle. In some embodiments, the rail comprises an electrical connector and a mounting bracket, wherein the mounting bracket comprises the rail. In some embodiments, the cross bar comprises an aluminum extrusion.

In some embodiments, the method includes receiving a user-initiated sequence from a user interface, and determining the sequence includes determining the user-initiated sequence.

Some embodiments of the method include: in response to determining the sequence, determining whether the sequence is restricted; in response to determining that the sequence is unrestricted, allowing the light source of the plurality of light sources to perform the action; in response to determining that the sequence is restricted and the restriction criteria are met, allowing the light source of the plurality of light sources to perform the action; and in response to determining that the sequence is restricted and the restriction criteria are not met, forgoing causing the light source of the plurality of light sources to perform the action.

Particular embodiments may repeat one or more steps of the method of fig. 12, where appropriate. Although this disclosure describes and illustrates particular steps of the method of fig. 12 as occurring in a particular order, this disclosure contemplates any suitable steps of the method of fig. 12 occurring in any suitable order. Furthermore, although this disclosure describes and illustrates an example method 1200 for including particular steps of the method of fig. 12, this disclosure contemplates any suitable method 1200 for including any suitable steps, where appropriate, such methods may include all or a portion of the steps of the method of fig. 12 or none of such steps. Furthermore, although this disclosure describes and illustrates particular components, devices, or systems embodying particular steps of the method of fig. 12, this disclosure contemplates any suitable combination of any suitable components, devices, or systems embodying any suitable steps of the method of fig. 12.

Fig. 13A illustrates an exemplary computer system 1300. Computer system 1300 may include a processor 1302, memory 1304, storage 1306, an input/output (I/O) interface 1308, a communication interface 1310, and a bus 1312. Although this disclosure describes one exemplary computer system including the specified components in a particular arrangement, this disclosure contemplates any suitable computer system having any suitable number of any suitable components in any suitable arrangement. By way of example, and not limitation, computer system 1300 may be an Electronic Control Unit (ECU), an embedded computer system, a system on chip, a single board computer system, a desktop computer system, a laptop or notebook computer system, a mainframe, a computer system network, a mobile phone, a personal digital assistant, a server computing system, a tablet computer system, or a combination of two or more of these. Computer system 1300 may include one or more computer systems 1300 where appropriate; may be unitary or distributed, spanning multiple locations, machines, or data centers; or reside in a cloud, which may include one or more cloud components in one or more networks. Computer system 1300 may perform one or more steps of one or more methods described or illustrated herein at different times or at different locations, in real time, or in batch mode, where appropriate.

The processor 1302 may include hardware for executing instructions, such as instructions that make up a computer program. By way of example, and not limitation, to execute instructions, processor 1302 may retrieve (or fetch) instructions from an internal register, internal cache, memory 1304, or storage 1306; decoding and executing them; one or more results are then written to an internal register, internal cache, memory 1304, or storage 1306. The processor 1302 may include one or more internal caches for data, instructions, or addresses.

In a particular embodiment, the memory 1304 includes a main memory for storing instructions for execution by the processor 1302 or data for operation by the processor 1302. In a particular embodiment, one or more Memory Management Units (MMUs) reside between the processor 1302 and the memory 1304 and facilitate access to the memory 1304 requested by the processor 1302. In a particular embodiment, the memory 1304 includes Random Access Memory (RAM). The present disclosure contemplates any suitable RAM.

In a particular implementation, the storage 1306 includes a mass storage device for data or instructions. By way of example, and not limitation, storage 1306 may include a removable magnetic disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or two or more of these. The storage 1306 may include removable or fixed media and may be internal or external to the computer system 1300. The storage 1306 may include any suitable form of non-volatile solid-state memory or read-only memory (ROM).

In particular embodiments, I/O interface 1308 comprises hardware, software, or both, providing one or more interfaces for communication between computer system 1300 and one or more input and/or output (I/O) devices. Computer system 1300 may be communicatively connected to one or more of these I/O devices, which may be incorporated, plugged in, paired, or otherwise communicatively connected to vehicle 1100 (e.g., through a TCM ECU). The input devices may include any suitable device for converting user intent input into digital signals that can be processed by computer system 1300, such as, by way of example and not limitation, a steering wheel, touch screen, microphone, joystick, scroll wheel, button, toggle switch, dial, or pedal. The input device may include one or more sensors for capturing different types of information, such as (by way of example and not limitation) the sensor 1110 described above. The output devices may include devices designed to receive digital signals from computer system 1300 and convert them to an output format, such as, by way of example and not limitation, speakers, headphones, a display screen, a heads-up display, lights, intelligent vehicle accessories, other suitable output devices, or combinations thereof. The present disclosure contemplates any suitable I/O devices and any suitable I/O interfaces 1308 for such I/O devices. The I/O interface 1308 may include one or more I/O interfaces 1308, where appropriate.

In particular embodiments, communication interface 1310 includes hardware, software, or both, providing one or more interfaces for data communication between computer system 1300 and one or more other computer systems 1300 or one or more networks. Communication interface 1310 may include one or more interfaces to a Controller Area Network (CAN) or Local Interconnect Network (LIN). Communication interface 1310 may include one or more of a Serial Peripheral Interface (SPI) or an isolated serial peripheral interface (isoSPI). In some embodiments, communication interface 1310 may include a Network Interface Controller (NIC) or network adapter for communicating with an ethernet or other wired network, or a Wireless NIC (WNIC) or wireless adapter for communicating with a wireless network, such as a WI-FI network or cellular network.

In a particular embodiment, the bus 1312 includes hardware, software, or both that couple the components of the computer system 1300 to one another. Bus 1312 may include any suitable bus, and one or more buses 1312, where appropriate. Although this disclosure describes a particular bus, any suitable bus or interconnect is contemplated.

Here, one or more computer-readable non-transitory storage media may include one or more semiconductor-based integrated circuits or other Integrated Circuits (ICs) (such as, for example, field programmable gate arrays or application specific ICs), hard drives, hybrid hard drives, optical disks, optical disk drives, magneto-optical disks, magneto-optical disk drives, solid state drives, RAM drives, any other suitable computer-readable non-transitory storage media, or any suitable combination. The computer-readable non-transitory storage medium may be volatile, nonvolatile, or a combination of volatile and nonvolatile, where appropriate.

Fig. 13B shows an exemplary firmware 1350 of a vehicle ECU 1300 as described with respect to control system 1130. Firmware 1350 may include functionality 1352 for analyzing sensor data based on signals received from sensor 1110 or camera 1120 via communication interface 1310. Firmware 1350 may include functionality 1354 for processing user input received via I/O interface 1308 (e.g., provided directly by a driver or passenger of vehicle 1100, or provided via computing device 1150). Firmware 1350 may include functionality 1356 for recording detected events (which may be stored in storage 1306 or uploaded to the cloud) and functionality for reporting detected events (e.g., to a driver or passenger of the vehicle through an instrument display or interactive interface of the vehicle, or to a vehicle manufacturer, service provider, or third party through communication interface 1310). Firmware 1350 may include functionality 1358 for evaluating safety parameters (e.g., monitoring the temperature of a vehicle battery or the distance between vehicle 1100 and a nearby vehicle). Firmware 1350 may include functionality 1360 for transmitting control signals to components of vehicle 1100, including other vehicle ECUs 1300.

Herein, "or" is inclusive and not exclusive unless otherwise specified or indicated by context. Thus, herein, "a or B" refers to "A, B or both" unless otherwise specified explicitly or otherwise by context. Furthermore, "and" are both common and individual unless explicitly stated otherwise or indicated by context. Thus, herein, "a and B" refer to "a and B, collectively or individually," unless otherwise indicated explicitly or by context. It should also be understood that, as used in the specification herein and throughout the appended claims, the meaning of "a" and "the" includes "one" and "more than one" unless the context clearly dictates otherwise.

The scope of the present disclosure encompasses all changes, substitutions, variations, alterations, and modifications to the example embodiments described or illustrated herein that will be understood by those of ordinary skill in the art. The scope of the present disclosure is not limited to the exemplary embodiments described or illustrated herein. Furthermore, although the present disclosure describes and illustrates respective embodiments herein as including particular components, elements, features, functions, operations, or steps, any of these embodiments may include any combination or arrangement of any components, elements, features, functions, operations, or steps described or illustrated anywhere herein, as would be understood by one of ordinary skill in the art. Furthermore, references in the appended claims to a device or system or a component of a device or system that is adapted, arranged, capable, configured, enabled, operable, operative to perform a particular function encompass the device, system, component whether or not it or that particular function is activated, turned on, or unlocked, as long as the device, system, or component is so adapted, arranged, capable, configured, enabled, operative, or operative. Additionally, although the disclosure describes or illustrates particular embodiments as providing particular advantages, particular embodiments may not provide such advantages or provide some or all of such advantages.

Claims

1. An apparatus, the apparatus comprising:

a rail comprising a plurality of light sources; and

a controller configured to:

determining a sequence of vehicles; and

in response to determining the sequence, causing a light source of the plurality of light sources to perform an action.

2. The apparatus of claim 1, wherein,

the sequence includes a vehicle braking sequence, and wherein,

the controller is configured to:

in response to determining the vehicle braking sequence, a first light source located on a rear side of the rail is caused to produce red light and a second light source located on a front side of the rail is caused to produce white light.

3. The apparatus of claim 1, wherein,

the sequence includes a vehicle turn sequence, and wherein,

the controller is configured to:

in response to determining the vehicle turn sequence, a light source located on a side end of the rail is caused to generate periodic yellow light.

4. The apparatus of claim 1, wherein,

the crossbar has an accessory insertion port, wherein,

the sequence includes an attachment insertion sequence, and wherein,

the controller is configured to:

in response to determining the accessory insertion sequence, a light source of the plurality of light sources is caused to generate light, wherein the light source is associated with the accessory insertion port.

5. The apparatus of claim 1, wherein,

the sequence includes a chase sequence, and wherein,

the controller is configured to:

in response to determining the chase sequence, causing a first light source of the plurality of light sources to produce white light and causing a second light source and a third light source of the plurality of light sources to produce yellow light, wherein the first light source is located between the second light source and the third light source.

6. The apparatus of claim 1, wherein,

the sequence includes a vehicle unlock sequence, and wherein,

the controller is configured to:

in response to determining the vehicle unlock sequence, causing a first light source of the plurality of light sources to produce white light and subsequently causing a second light source and a third light source of the plurality of light sources to produce white light, wherein the first light source is located between the second light source and the third light source.

7. The apparatus of claim 1, wherein,

the sequence comprises a follower sequence, and wherein,

the controller is configured to:

in response to determining the follow sequence, causing a first light source on the rear side of the rail to generate yellow light and causing a second light source and a third light source on the rear side of the rail to generate yellow light, wherein the first light source is located between the second light source and the third light source.

8. The apparatus of claim 1, wherein,

the sequence comprises a locking sequence, and wherein,

the controller is configured to:

in response to determining the locking sequence, causing a light source on the rear side of the rail to generate light of a first intensity and subsequently causing a light source on the rear side of the rail to generate light of a second intensity, the first intensity being greater than the second intensity.

9. The apparatus of claim 1, wherein the plurality of light sources comprises a forward light source, a backward light source, a side end light source, and a bottom surface light source.

10. The apparatus of claim 1, the crossbar further comprising at least one of an electrical connector and a mount for coupling the crossbar to a vehicle.

11. The apparatus of claim 10, wherein the cross bar comprises the mounting bracket and the electrical connection, and wherein the mounting bracket comprises the electrical connection.

12. The device of claim 1, further comprising a user interface configured to receive a user-initiated sequence, wherein determining the sequence comprises determining the user-initiated sequence.

13. The device of claim 1, wherein the controller is configured to:

In response to determining the sequence, determining whether the sequence is restricted;

in response to determining that the sequence is unrestricted, allowing the light source of the plurality of light sources to perform the action;

in response to determining that the sequence is restricted and a restriction criterion is met, allowing the light source of the plurality of light sources to perform the action; and

in response to determining that the sequence is restricted and the restriction criteria are not met, relinquishing to cause the light source of the plurality of light sources to perform the action.

14. The apparatus of claim 1, wherein the cross bar comprises an aluminum extrusion.

15. A computer-readable non-transitory storage medium containing software that includes instructions operable when executed to perform operations comprising:

determining a sequence of vehicles;

in response to determining the sequence, a signal is sent to cause the rail light source to perform an action.

16. The medium of claim 15, wherein determining the sequence of the vehicle comprises determining a user initiated sequence.

17. The medium of claim 15, wherein the operations further comprise:

Allowing the rail light source to perform the action in response to determining that the sequence is unrestricted;

in response to determining that the sequence is restricted and a restriction criterion is met, allowing the rail light source to perform the action; and

in response to determining that the sequence is restricted and the restriction criteria are not met, the actions are abandoned to be performed by the rail light source.

18. A vehicle, the vehicle comprising:

a rail mounted to the vehicle, wherein the rail includes a plurality of light sources; and

a control system comprising a processor and a memory, the memory comprising instructions executable by the processor, the processor operable to execute the instructions to perform operations comprising:

determining a sequence of the vehicles; and

19. The vehicle of claim 18, wherein the rail comprises a top surface and a bottom surface, wherein the plurality of light sources comprises light sources located in the bottom surface, and wherein the light sources located in the bottom surface are configured to illuminate non-vehicle areas.

20. The vehicle of claim 18, wherein the cross bar is configured to support a load when mounted on the vehicle.