Patent Description:
For vehicle manufacturers, enhancing the occupant experience by improving visual aesthetics within the interior of the vehicle is generally desirable and oftentimes the focus of vehicle interior designs. One technique for improving visual aesthetics within the vehicle interior is to provide aesthetic lighting at various locations within the vehicle. A current approach for providing such lighting within a vehicle interior involves implementing light sources that are connected to various light guides that are, in turn, routed throughout the vehicle interior to provide lighting at desired locations within the vehicle. However, this current approach is not terribly robust, is too complex, requires too much space, and is expensive. In particular, light guides (such as fiber optics) are typically quite fragile, and routing these light guides to the desired locations within the vehicle without interference from other vehicle components is typically a complex undertaking and requires substantial space within the vehicle interior.

Known vehicle lighting systems are disclosed in the documents <CIT> and <CIT>.

As the foregoing illustrates, what is needed in the art are more effective techniques for providing aesthetic lighting to locations within a vehicle interior.

The present invention provides a vehicle lighting system according to claim <NUM> and a computer-implemented method according to claim <NUM>.

At least one technical advantage of the disclosed techniques relative to the prior art is that the disclosed techniques enable varying lighting effects within the interior of a vehicle via a simple and robust light assembly. In that regard, the light assembly is constructed by forming a printed circuit board (PCB) layer in the shape of a vehicle component, mounting light sources on the PCB layer, and attaching the PCB layer with the mounted light sources onto the vehicle component. The light assembly is connected to a light controller that controls the mounted light sources. The light controller receives lighting routines from a lighting effects engine and controls the light sources of the light assembly to generate the desired lighting effects. In this manner, lighting effects within the interior of a vehicle are provided via a relatively simple, compact, and robust light assembly. These technical advantages represent one or more technological advancements over prior art approaches.

So that the manner in which the recited features of the one or more embodiments set forth above can be understood in detail, a more particular description of the one or more embodiments, briefly summarized above, may be had by reference to certain specific embodiments, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only typical embodiments and are therefore not to be considered limiting of its scope in any manner, for the scope of the various embodiments subsumes other embodiments as well.

In the following description, numerous specific details are set forth to provide a more thorough understanding of certain specific embodiments. However, it will be apparent to one of skill in the art that other embodiments may be practiced without one or more of these specific details or with additional specific details.

The embodiments are described in part below with reference to flowchart illustrations and/or block diagrams of methods, systems, and computer program products and data structures according to embodiments herein. It will be understood that each block of the illustrations, and combinations of blocks, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general-purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the block or blocks.

<FIG> is a block diagram of a vehicle lighting system <NUM> configured to implement one or more aspects of the various embodiments. The vehicle lighting system <NUM> includes vehicle sub-systems <NUM>, a head unit <NUM>, a set of light controllers <NUM>, and a set of light assemblies <NUM> interconnected via a bus, network, or any other feasible electrical connections. The vehicle sub-systems <NUM>, head unit <NUM>, set of light controllers <NUM>, and set of light assemblies <NUM> are each installed in a vehicle.

Each light controller <NUM> is connected with and controls a corresponding light assembly <NUM>. Each light controller <NUM> also includes a power supply (not shown) that provides power to the light controller <NUM> and the corresponding light assembly <NUM>. In some embodiments, the light controller <NUM> receives a lighting routine (corresponding to a particular lighting effect) and sends control signals to the light assembly <NUM> for controlling light sources of the light assembly <NUM> in accordance with the received lighting routine (thereby producing the corresponding lighting effect). The light controller <NUM> may include a memory for storing instructions and a processor for executing the instructions for controlling the light assembly <NUM> based on a received lighting routine. In general, a light controller <NUM> comprises any type of device suitable for controlling the light sources of the light assembly <NUM> to provide different colors, intensities (brightness levels), and/or lighting patterns for generating various lighting effects. For example, the light controller <NUM> may comprise a microcontroller, application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), programmable logic controller (PLC), or other programmable logic device.

The head unit <NUM> includes a lighting effects engine <NUM> that provides lighting effects to the interior of the vehicle via the set of one or more light controllers <NUM> (such as 170a-170n) and the set of light assemblies <NUM> (such as 180a-180n). In these embodiments, the logic of the lighting effects engine is located in the head unit <NUM>. In other embodiments, the logic of the lighting effects engine is external to the head unit <NUM>, for example, in a separate hardware unit. Each light assembly <NUM> includes a PCB layer that is formed to have a shape corresponding to a particular interior component of a vehicle (such as a speaker cover or mirrorsail). The PCB layer is attachable to the corresponding vehicle component. Each light assembly <NUM> is positioned within the interior of the vehicle at the location of the corresponding interior vehicle component. For example, a first light assembly 180a is formed to resemble the shape of a left-front speaker cover, and a second light assembly 180b is formed to resemble the shape of a right-front speaker cover. Therefore, the first light assembly 180a is placed at the location of the left-front speaker cover, and the second light assembly 180b is placed at the location of the right-front speaker cover. Each light assembly <NUM> includes light sources, such as light-emitting diodes (LEDs), mounted to the PCB layer. Each light assembly <NUM> further includes a light controller <NUM> connected to the PCB layer for controlling the light sources.

The lighting effects engine <NUM> receives inputs from a user and/or vehicle sub-systems <NUM> and outputs a lighting effect/lighting pattern corresponding to the received input. For example, the lighting effects engine <NUM> may receive a particular user input, map the user input to a particular lighting effect, and retrieve a set of lighting routines that generate the lighting effect. Each lighting routine in the set of lighting routines is associated with a particular light controller <NUM> and light assembly <NUM> pair. The lighting effects engine <NUM> then transmits the set of lighting routines to the set of light controllers <NUM>. The set of light controllers <NUM> collectively generate the selected lighting effect/lighting pattern by executing the received lighting routines on the set of light assemblies <NUM>.

In other embodiments, the lighting effects engine <NUM> receives a particular input signal from a vehicle sub-system <NUM> and maps the received input signal to a particular lighting effect. For example, lighting effects engine <NUM> may receive an input signal comprising a "turn left" navigation direction from a navigation/GPS sub-system, and map the input signal to a "turn left" lighting effect that includes activating blue blinking lights located at a left-front position within the vehicle. The lighting effects engine <NUM> retrieves a set of lighting routines that generate the "turn left" lighting effect and transmits the set of lighting routines to the set of light controllers <NUM>.

Techniques for constructing the light assembly <NUM> are discussed in further detail in relation to <FIG>. Techniques for controlling the light assembly <NUM> via the lighting effects engine <NUM> are discussed in further detail in relation to <FIG>.

<FIG> illustrates an exemplary vehicle component <NUM> that can be implemented in the vehicle lighting system of <FIG>, according to various embodiments. In the example of <FIG>, the vehicle component <NUM> comprises a speaker cover for an audio speaker positioned in any location within the vehicle. Other, unclaimed examples of the vehicle component <NUM> include a mirrorsail (interior portion of a side mirror), a door panel, a dashboard panel, a ceiling panel, a pillar panel, and the like. In other embodiments, the vehicle component <NUM> may comprise any other type of interior component of a vehicle. A light assembly <NUM> is formed on top of the vehicle component <NUM>, and thus is positioned within the interior of the vehicle at the location of the vehicle component <NUM>. Therefore, the set of light assemblies <NUM> may be located at any of various locations within the interior of the vehicle.

<FIG> illustrates an exemplary PCB layer <NUM> constructed for the vehicle component <NUM> of <FIG>, according to various embodiments. As shown, the PCB layer <NUM> is constructed/formed to have a geometric shape that is based on a geometric shape of the corresponding vehicle component <NUM>. In some embodiments, the PCB layer <NUM> is constructed/formed to have a geometric shape that approximates, resembles, and/or is substantially similar to a geometric shape of the corresponding vehicle component <NUM>. The PCB layer <NUM> is attachable to the corresponding vehicle component <NUM>. In the example of <FIG>, the PCB layer <NUM> is constructed to have a pair of holes corresponding in size and location as the pair of holes in the corresponding vehicle component <NUM>. The PCB layer <NUM> is further perforated with smaller holes to allow sound from the speaker to penetrate through the PCB layer <NUM>. In other embodiments, the PCB layer <NUM> comprises multiple PCBs connected to each other to form desired shapes, such as a double curvature.

In some embodiments, the PCB layer <NUM> comprises any form of printed circuit, such as a rigid printed circuit board or a flexible printed circuit ("flex circuit"). A rigid printed circuit board may be formed from material such as fiberglass-filled epoxy, or other suitable material. A flexible printed circuit may be formed, for example, from one or more flexible sheets of polymer, such as polyimide, or other suitable material. In further embodiments, the PCB layer <NUM> may be formed from a combination of rigid and flexible layers ("rigid-flex" printed circuit). In other embodiments, the PCB layer <NUM> may comprise any type of substrate suitable for mounting light sources and forming electrical connections for the light sources.

As shown, the PCB layer <NUM> is further constructed/formed by mounting a set of light sources <NUM> onto the PCB layer <NUM> and forming a set of terminals <NUM> on the PCB layer <NUM>. The PCB layer <NUM> is further constructed by forming internal wiring/traces (not shown) that connects the terminals <NUM> to the light sources <NUM> for powering and sending control signals to the set of light sources <NUM>. The set of terminals <NUM> connects the PCB layer <NUM> to external wiring <NUM>. The external wiring <NUM> connects the set of terminals <NUM> to a corresponding light controller <NUM> (not shown) to supply power and control signals to the set of light sources <NUM>. As formed with the light sources <NUM>, internal wiring/traces, and terminals <NUM>, the PCB layer <NUM> may be referred to as a PCB Assembly (PCBA) that is populated with interconnected electronic components.

In some embodiments, the light sources <NUM> comprise light-emitting diodes (LEDs). In these embodiments, any type of LED may be used, such as individual red, green and blue LEDs, white LEDs, high-power LEDs (HP-LEDs), high-output LEDs, bi-color LEDs, tri- color LEDs, and the like. In general, any set of LEDs for providing different colors, intensities (brightness levels), and lighting patterns to generate desired lighting effects may be implemented herein. Each LED may be connected to a separate trace so that each LED can be controlled independently.

<FIG> illustrates an exemplary light assembly <NUM> that can be implemented in the vehicle lighting system of <FIG>, according to various embodiments. As shown, the light assembly <NUM> comprises a formed PCB layer <NUM> (having mounted light sources <NUM>) that is fixed/attached to a corresponding vehicle component <NUM>. In some embodiments, the PCB layer <NUM> is fixed/attached to the corresponding vehicle component <NUM>, for example, via an adhesive layer (not shown) placed between the PCB layer <NUM> and the vehicle component <NUM>. In other embodiments, the PCB layer <NUM> is fixed/attached to the corresponding vehicle component <NUM> via other feasible techniques, such as via mechanical-based connectors and fasteners. Since the PCB layer <NUM> is formed to have a geometric shape resembling the geometric shape of the corresponding vehicle component <NUM>, the PCB layer <NUM> easily attaches to the corresponding vehicle component <NUM> with no portions of the PCB layer <NUM> protruding beyond the physical boundaries of the corresponding vehicle component <NUM>.

<FIG> illustrates an activated light assembly <NUM> that can be implemented in the vehicle lighting system of <FIG>, according to various embodiments. In the example of <FIG>, the light assembly <NUM> includes the light assembly <NUM> of <FIG> and further includes a fabric layer <NUM>. In these embodiments, the fabric layer <NUM> covers the PCB layer <NUM> and mounted light sources <NUM>. The fabric layer <NUM> comprises any suitable fabric that allows the light from the light sources <NUM> to be seen/visible through the fabric. For example, the fabric layer <NUM> may comprise synthetic fibers (such as polyester), natural fibers (such as cotton), or a combination thereof (such as cotton-polyester blends). In other embodiments, the fabric layer <NUM> comprises any type of fabric with a weaving that allows light to penetrate and be visible through the fabric. In the example of <FIG>, the light sources <NUM> are activated/turned on, whereby the resulting lighting effect can be seen through the fabric layer <NUM>. In the example of <FIG>, the light assembly <NUM> is generating the "starry night" lighting effect.

<FIG> illustrates a non-activated light assembly <NUM> that can be implemented in the vehicle lighting system of <FIG>, according to various embodiments. In the example of <FIG>, the light assembly <NUM> includes the light assembly <NUM> of <FIG>, whereby the light sources <NUM> are de-activated/turned off. As shown, when the light sources <NUM> are de-activated, the light sources <NUM> and the PCB layer <NUM> are not visible through the fabric layer <NUM>. In this manner, when the light sources <NUM> are de-activated/turned off, the light assembly <NUM> has the typical appearance of the corresponding vehicle component <NUM>.

<FIG> is a block diagram of an exemplary light assembly <NUM> that can be implemented in the vehicle lighting system of <FIG>, according to various embodiments. As shown, the light assembly <NUM> comprises external wiring <NUM>, an adhesive layer <NUM>, a PCB layer <NUM> with mounted light sources <NUM>, a protective layer <NUM>, and a fabric layer <NUM>. The adhesive layer <NUM> attaches/fixes the PCB layer <NUM> to a corresponding vehicle component <NUM>. The external wiring <NUM> may be configured to pass through the vehicle component <NUM> and the adhesive layer <NUM> to connect the PCB layer <NUM> to a corresponding light controller <NUM> (not shown). In some embodiments, the adhesive layer <NUM> comprises a double-sided adhesive layer, glue, or any other suitable type of adhesive. The protective layer <NUM> may comprise a protective cover that protects the PCB layer <NUM> and light sources <NUM>. In some embodiments, the protective layer <NUM> comprises a plastic cover, a silicone cover, or other suitable cover that is protective and see-through. In some embodiments, the protective layer <NUM> is molded onto the surface of the PCB layer <NUM>.

<FIG> is a flow diagram of method steps for constructing a light assembly <NUM> that can be implemented in the vehicle lighting system of <FIG>, according to various embodiments. Although the method steps are described in conjunction with the systems of <FIG>, persons skilled in the art will understand that the method steps can be performed in any order by any system.

The method <NUM> begins by forming (at step <NUM>) a PCB layer <NUM> to have a geometric shape that is based on a geometric shape of a corresponding vehicle component <NUM>. In some embodiments, the PCB layer <NUM> is constructed to have a geometric shape that approximates, resembles, and/or is substantially similar to a geometric shape of the corresponding vehicle component <NUM>. The method <NUM> also includes mounting (at step <NUM>) a set of one or more light sources <NUM> (such as LEDs) onto the PCB layer <NUM> and forming a set of terminals <NUM> on the PCB layer <NUM>. Internal wiring/traces are also formed on the PCB layer <NUM> to connect the set of terminals <NUM> to the set of light sources <NUM> for supplying power and control signals to the set of light sources <NUM>. The formed PCB layer <NUM> with the mounted light sources <NUM>, terminals <NUM>, and internal wiring/traces may be referred to as a PCB Assembly (PCBA).

The method <NUM> further includes forming (at <NUM>) a protective layer <NUM> over the PCB layer <NUM> (such as a hard plastic cover) and forming a fabric layer <NUM> over the protective layer <NUM>. The method <NUM> further includes attaching (at step <NUM>) external wiring <NUM> to the terminals <NUM> on the PCB layer <NUM>. The external wiring <NUM> is connected to a corresponding light controller <NUM> for supplying power and control signals to the set of light sources <NUM> for generating desired lighting effects. The method <NUM> further includes attaching/fixing (at step <NUM>) the formed PCB layer <NUM> to a corresponding vehicle component <NUM>, for example, via an adhesive layer <NUM>. The method <NUM> then ends.

As discussed above in relation to <FIG>, the vehicle lighting system <NUM> includes vehicle sub-systems <NUM> and a head unit <NUM> that executes a lighting effects engine <NUM>. Based on received inputs, the lighting effects engine <NUM> provides lighting effects to the interior of the vehicle via the set of one or more light controllers <NUM> (such as 170a-170n) and the set of light assemblies <NUM> (such as 180a-180n). <FIG> illustrates an exemplary head unit <NUM> that can be implemented in the vehicle lighting system of <FIG>, according to various embodiments. As shown, the head unit <NUM> comprises at least one processor <NUM>, input/output (I/O) devices <NUM>, and a memory unit <NUM>, coupled together.

In general, a processor <NUM> may be any technically feasible processing device or hardware unit capable of processing data and executing software applications and program code. The processor <NUM> of the head unit <NUM> allows on-board processing of instructions, commands, and lighting routines, particularly as part of an application layer and/or API of the head unit <NUM>. The processor <NUM> executes the software and performs the functions and operations set forth in the embodiments described herein. For example, a processor <NUM> may comprise a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination of different processing units, such as a CPU configured to operate in conjunction with a GPU, or many CPUs configured to work together through cloud computing.

The memory unit <NUM> may include a hard disk, a random access memory (RAM) module, a flash memory unit, or any other type of memory unit or combination thereof. Processor and I/O devices read data from and write data to memory <NUM>. The memory unit <NUM> is configured to store software application(s) and data. Instructions from the software constructs within the memory unit <NUM> are executed by processors to enable the operations and functions described herein. In various embodiments, the memory unit <NUM> is configured to store a lighting effects engine <NUM>, lighting mapping table <NUM>, and lighting routines <NUM> for performing embodiments herein. The head unit <NUM> may be connected to a storage device <NUM> comprising a persistent storage device, such as a hard disk drive (HDD) or flash memory. The storage device <NUM> stores, for example, the lighting effects engine <NUM>, lighting mapping table <NUM>, and lighting routines <NUM>.

The processor <NUM> is configured to execute the lighting effects engine <NUM> to provide an underlying functionality of a vehicle lighting system as described in various embodiments herein. In other embodiments, the lighting effects engine <NUM> is executed within a stand-alone lighting effects unit that is connected with the head unit <NUM>. In these embodiments, the lighting effects unit comprises a memory unit and processor for executing the lighting effects engine <NUM> to provide an underlying functionality of a vehicle lighting system as described in various embodiments herein. The lighting effects engine <NUM> may comprise an add-on feature, part of the original equipment manufacturer (OEM) controls of the vehicle, or a combination of both.

The I/O devices <NUM> are also coupled to memory <NUM> and comprise as a front end interface located in the vehicle that allows the user to interact with the head unit <NUM> and vehicle sub-systems <NUM> via user inputs, such as voice commands and touch inputs. The I/O devices <NUM> include devices capable of receiving user inputs, such as a microphone (for receiving voice commands), a keyboard, a mouse, a control stick, a trackball, and so forth, as well as devices capable of providing output, such as a display, speaker, and so forth. Additionally, I/O devices may include devices capable of both receiving input and providing output, such as a touchscreen, a universal serial bus (USB) port, and so forth.

The head unit <NUM> is coupled to one or more vehicle sub-systems <NUM>, such as a navigation/GPS sub-system <NUM>, safety/autonomous sub-system <NUM>, fundamental sub-systems <NUM>, and entertainment sub-system <NUM>. In some embodiments, the lighting effects engine <NUM> receives inputs from a user (via the I/O devices <NUM> of the head unit <NUM>) and/or one or more vehicle sub-systems <NUM>, and outputs a lighting effect corresponding to the received input. In particular, the lighting effects engine <NUM> maps a received input to a particular lighting effect via the lighting mapping table <NUM> and retrieves a set of lighting routines associated with the lighting effect. The lighting effects engine <NUM> then outputs/transmits the set of lighting routines to the set of light controllers <NUM>, which in turn, apply/execute the set of lighting routines on the set of light assemblies <NUM> to collectively produce the desired lighting effect.

A lighting routine <NUM> comprises a set of instructions, set of commands, data signals, and/or control signals. A lighting effect comprises a dynamic lighting effect or a static lighting effect. For a dynamic lighting effect, a corresponding lighting routine <NUM> specifies an ordered sequence of activated light sources <NUM> on a light assembly <NUM> to generate the dynamic lighting effect. The lighting routine <NUM> for a dynamic lighting effect may further specify the colors, brightness, and timing of the activated light sources <NUM>. For a static lighting effect, a corresponding lighting routine <NUM> specifies activation of particular light sources <NUM> on a light assembly <NUM> to generate the static lighting effect. The lighting routine <NUM> for a static lighting effect may further specify the colors and brightness of the activated light sources <NUM>.

Each lighting routine <NUM> in the set of lighting routines is associated with a particular light controller <NUM> and light assembly <NUM> pair. The lighting routines <NUM> in the set of lighting routines may differ from one another depending on the lighting effect to be achieved. For example, to achieve a first lighting effect, a first lighting routine transmitted to a first light controller <NUM> may be different than a second lighting routine transmitted to a second light controller <NUM>. The set of light controllers <NUM> collectively generate the desired lighting effect by executing the received lighting routines on the set of light assemblies <NUM>. Each light controller <NUM> applies/executes the received lighting routine <NUM> on the corresponding light assembly <NUM> by controlling the light sources <NUM> of the light assembly <NUM> in accordance with the received lighting routine. In particular, each light controller <NUM> controls the light sources <NUM> of the light assembly <NUM> by sending control signals to the light sources <NUM> for controlling the light sources <NUM> in accordance with the received lighting routine.

In some embodiments, the communications/interactions between the vehicle sub-systems <NUM>, the lighting effects engine <NUM>, and the set of light controllers <NUM> are implemented via Controller Area Network (CAN), and/or LIN Local Interconnect Network (LIN), MOST (Media Oriented Systems Transport), IEEE <NUM>, or other suitable technologies. In other embodiments, the communications/interactions between the vehicle sub-systems <NUM>, the lighting effects engine <NUM>, and the set of light controllers <NUM> are implemented via other protocols and/or bus standards configured to allow vehicle components to communicate with each other.

In some embodiments, the lighting effects engine <NUM> receives inputs from a user/occupant via the I/O devices <NUM> of the head unit <NUM>. For example, the user inputs may select turning on or turning off the lighting effects function of the vehicle lighting system <NUM>, or select a particular lighting effect. The lighting effects engine <NUM> then maps the user input to a corresponding lighting effect. For example, the user may select a "starry night" lighting effect which illuminates the vehicle interior with points of white light, simulating a night sky with stars. In response, the lighting effects engine <NUM> maps the "starry night" lighting effect to a corresponding set of lighting routines, and transmits the set of lighting routines to the set of light controllers <NUM> for generating the "starry night" lighting effect. Examples of other user-selectable lighting effects include a "tranquil" light effect that illuminates the vehicle interior with a light-blue light, and a "red-flash" light effect that illuminates the vehicle interior with a flashing red light. In other embodiments, the user-selectable lighting effects include other lighting effects.

In some embodiments, the lighting effects engine <NUM> receives input signals from one or more vehicle sub-systems <NUM>, and outputs a lighting effect corresponding to the received input signals. The input signals received from the vehicle sub-systems <NUM> may comprise data signals, control signals, and/or audio signals. The one or more vehicle sub-systems <NUM> may include a navigation/GPS sub-system <NUM>, a safety/autonomous sub-system <NUM>, fundamental sub-systems <NUM>, and an entertainment sub-system <NUM>. In other embodiments, the one or more vehicle sub-systems <NUM> include other vehicle sub-systems.

The lighting effects engine <NUM> may receive input signals from the navigation/GPS sub-system <NUM> that specify navigation information (such as navigation directions). For example, the input signals may specify a "turn left" navigation direction. The lighting effects engine <NUM> may then map the input signal to a "turn left" lighting effect that includes activating blue blinking lights at a light assembly <NUM> located at the left-front position within the vehicle. The lighting effects engine <NUM> retrieves a set of lighting routines corresponding to the "turn left" lighting effect and transmits the set of lighting routines to the set of light controllers <NUM> for generating the "turn left" lighting effect. In this example, a first light assembly 180a is located at the left-front speaker cover, and therefore a lighting routine is sent to the corresponding first light controller 170a that causes the first light assembly 180a to generate blue blinking lights. In this example, the remaining light controllers <NUM> may receive no lighting routine, or a lighting routine that specifies activation/illumination of none of the light sources.

The lighting effects engine <NUM> may receive input signals from the safety/autonomous sub-system <NUM>, which provides safety and self-drive (autonomous) functions for the vehicle. For example, the input signals may specify that another vehicle is detected in the right blind-spot. The lighting effects engine <NUM> then maps the input signal to a "right blind-spot" lighting effect that includes activating red flashing lights at a light assembly <NUM> located at the right-front position within the vehicle. The lighting effects engine <NUM> retrieves a set of lighting routines corresponding to the "right blind-spot" lighting effect and transmits the set of lighting routines to the set of light controllers <NUM> for generating the "right blind-spot" lighting effect. In this example, a second light assembly 180b is located at the right-front speaker cover, and therefore a lighting routine is sent to the corresponding second light controller 170b that causes the second light assembly 180b to generate red flashing lights. In this example, the remaining light controllers <NUM> may receive no lighting routine, or a lighting routine that specifies activation/illumination of none of the light sources.

The lighting effects engine <NUM> may receive input signals from the fundamental sub-systems <NUM> of the vehicle, which provides fundamental/basic functions for the vehicle such as braking, acceleration, turn signals, and the like. For example, the fundamental sub-systems <NUM> includes vehicle components such as an engine control unit (ECU) to control engine parameters or monitor the vehicle's engine, a powertrain control module (PCM), and a series of sensor systems (such as tire pressure monitoring system, a temperature sensor, and the like), among other vehicle components. For example, the input signals may specify that braking of the vehicle is detected. The lighting effects engine <NUM> then maps the input signal to a "braking" lighting effect that includes activating steady red lights at a light assembly <NUM> located at the front dashboard within the vehicle. The lighting effects engine <NUM> retrieves a set of lighting routines corresponding to the "braking" lighting effect and transmits the set of lighting routines to the set of light controllers <NUM> for generating the "braking" lighting effect. In this example, a third light assembly 180c is located at the front dashboard, and therefore a lighting routine is sent to the corresponding third light controller 170c that causes the third light assembly 180c to illuminate steady red lights. In this example, the remaining light controllers <NUM> may receive no lighting routine, or a lighting routine that specifies activation/illumination of none of the light sources.

The lighting effects engine <NUM> may receive input signals from the entertainment sub-system <NUM>, which provides audio/video functions that provide, for example, audio and/or video output to a set of audio speakers and/or a video display (not shown). The entertainment sub-system <NUM> include entertainment components comprising speaker amplifiers, components controlling a volume of the amplifiers, an analog or digital radio, CD/DVD player, or other media sources/players. For example, the input signals may specify that the volume of the amplifier is being increased. The lighting effects engine <NUM> then maps the input signal to a "volume increase" lighting effect that includes illuminating green lights in sequence from left to right at a light assembly <NUM> located at the front dashboard within the vehicle. The lighting effects engine <NUM> retrieves a set of lighting routines corresponding to the "volume increase" lighting effect and transmits the set of lighting routines to the set of light controllers <NUM> for generating the "volume increase" lighting effect. In this example, a third light assembly 180c is located at the front dashboard, and therefore a lighting routine is sent to the corresponding third light controller 170c that causes the third light assembly 180c to illuminate green lights in sequence from left to right. In this example, the remaining light controllers <NUM> may receive no lighting routine, or a lighting routine that specifies activation/illumination of none of the light sources. In other embodiments, the lighting effects engine <NUM> receives audio signals from the entertainment sub-system <NUM> and provides lighting effects based on the audio signals, such as the frequencies or volume of the audio signals.

<FIG> is a conceptual diagram of the lighting mapping table <NUM> of <FIG>, according to various embodiments. For each received input (e.g., from the user or a vehicle sub-system <NUM>), the lighting effects engine <NUM> determines a corresponding lighting effect via the lighting mapping table <NUM>. As shown, the lighting mapping table <NUM> comprises a plurality of sections <NUM> (such as 950a, 950b, 950c, etc.), each section <NUM> comprises a plurality of mapping entries <NUM> (such as 901a, 901b, 901c, etc.).

Each section <NUM> corresponds to a particular source or type of input received by the lighting effects engine <NUM>. For example, a first section 950a includes mapping entries <NUM> for various inputs received from a user/occupant via the I/O devices <NUM> (represented as "UI" inputs in <FIG>), a second section 950b includes mapping entries <NUM> for various inputs received from the navigation/GPS sub-system <NUM> (represented as "Navi" inputs in <FIG>), a third section 950c includes mapping entries <NUM> for various inputs received from the safety/autonomous sub-system <NUM> (represented as "SA" inputs in <FIG>), a fourth section 950d includes mapping entries <NUM> for various inputs received from the fundamental sub-systems <NUM> (represented as "Fund" inputs in <FIG>), and a fifth section 950e includes mapping entries <NUM> for various inputs received from the entertainment sub-system <NUM> (represented as "ENT" inputs in <FIG>).

Each mapping entry <NUM> comprises a mapping from a particular input <NUM> to a particular lighting effect <NUM> corresponding to the input <NUM>. Each input <NUM> is identified by a unique identifier and each lighting effect <NUM> is also identified by a unique identifier. Each mapping entry <NUM> may further specify the lighting effect <NUM> by specifying a set of lighting routines associated with the lighting effect <NUM>. Each lighting routine in the set of lighting routines is identified by a unique identifier (such as "LR_1," "LR_2," "LR_3," etc.). Each lighting routine in the set of lighting routines may be retrieved from the storage device <NUM> using the unique identifier of the lighting routine. The mapping entry <NUM> may specify the set of lighting routines in a predetermined sequence/order to indicate the light controller <NUM> and light assembly <NUM> pair that is associated with each lighting routine in the set of lighting routines.

Thus, each mapping entry <NUM> may specify the set of lighting routines as a sequence of lighting routines. For example, a first lighting routine in the sequence may be associated with a first light assembly 180a located at the left-front speaker cover, a second lighting routine in the sequence may be associated with a second light assembly 180b located at the right-front speaker cover, a third lighting routine in the sequence may be associated with a third light assembly 180c located at the front dashboard, a fourth lighting routine in the sequence may be associated with a fourth light assembly 180d located at the left-rear speaker cover, and a fifth lighting routine in the sequence may be associated with a fifth light assembly 180e located at the right-rear speaker cover. For example, a mapping entry <NUM> specifying a sequence of lighting routines as "LR_3; LR_3; LR_8; LR_2; LR_2" indicates a first lighting routine LR_3 that is associated with a first light controller 170a and first light assembly 180a pair, a second lighting routine LR_3 that is associated with a second light controller 170b and second light assembly 180b pair, a third lighting routine LR_8 that is associated with a third light controller 170c and third light assembly 180c pair, a fourth lighting routine LR_2 that is associated with a fourth light controller 170d and fourth light assembly 180d pair, and a fifth lighting routine LR_2 that is associated with a fifth light controller 170e and fifth light assembly 180e pair.

The first section 950a of the mapping table <NUM> includes mapping entries <NUM> for inputs received from a user/occupant (represented as "UI" inputs in <FIG>). An example of a mapping entry <NUM> in the first section 950a includes a user input selecting the "starry night" lighting effect that maps to the "starry night" lighting effect specified by a same lighting routine (e.g., LR_11) that is sent to each light controller <NUM> in the set of light controllers <NUM>. For example, the sequence of lighting routines may comprise LR_11; LR_11; LR_11; LR_11; LR_11. Another example of a mapping entry <NUM> in the first section 950a includes a user input selecting the turning off of the lighting effects that maps to the "off" lighting effect specified by a same lighting routine (e.g., LR_0) that is sent to each light controller <NUM> in the set of light controllers <NUM>. For example, the sequence of lighting routines may comprise LR_0; LR_0; LR_0; LR_0; LR_0. In this example, the lighting routine (e.g., LR_0) specifies activation/illumination of none of the light sources of the light assembly <NUM>. In other embodiments, the first section 950a of the mapping table <NUM> includes other types of mapping entries <NUM>.

The second section 950b includes mapping entries <NUM> for inputs received from the navigation/GPS sub-system <NUM> (represented as "Navi" inputs in <FIG>). An example of a mapping entry <NUM> in the second section 950b includes an input comprising a "turn left" navigation direction that maps to the "turn left" lighting effect specified by a lighting routine (e.g., LR_3) that is sent only to the light controller <NUM> corresponding to the light assembly <NUM> located at the left-front speaker cover. For example, the sequence of lighting routines may comprise LR_3; LR_0; LR_0; LR_0; LR_0. Another example of a mapping entry <NUM> in the second section 950b includes an input comprising a "turn right" navigation direction that maps to the "turn right" lighting effect specified by a lighting routine (e.g., LR_3) that is sent only to the light controller <NUM> corresponding to the light assembly <NUM> located at the right-front speaker cover. For example, the sequence of lighting routines may comprise LR_0; LR_3; LR_0; LR_0; LR_0.

The third section 950c includes mapping entries <NUM> for inputs received from the safety/autonomous sub-system <NUM> (represented as "SA" inputs in <FIG>). An example of a mapping entry <NUM> in the third section 950c includes an input comprising detection of another vehicle in the left blind-spot that maps to the "left blind-spot" lighting effect specified by a lighting routine (e.g., LR_8) that is sent only to the light controller <NUM> corresponding to the light assembly <NUM> located at the left-front speaker cover. For example, the sequence of lighting routines may comprise LR_8; LR_0; LR_0; LR_0; LR_0. Another example of a mapping entry <NUM> in the third section 950c includes an input comprising a detection of another vehicle in the right blind-spot that maps to the "right blind-spot" lighting effect specified by a lighting routine (e.g., LR_8) that is sent only to the light controller <NUM> corresponding to the light assembly <NUM> located at the right-front speaker cover. For example, the sequence of lighting routines may comprise LR_0; LR_8; LR_0; LR_0; LR_0. Another example of a mapping entry <NUM> in the third section 950c includes an input comprising a detection of another vehicle in front that maps to the "front vehicle" lighting effect specified by a lighting routine (e.g., LR_8) that is sent only to the light controllers <NUM> corresponding to the light assemblies <NUM> located at the left-front speaker cover, right-front speaker cover, and front dash. For example, the sequence of lighting routines may comprise LR_8; LR_8; LR_8; LR_0; LR_0.

The fourth section 950d includes mapping entries <NUM> for inputs received from the fundamental sub-systems <NUM> (represented as "Fund" inputs in <FIG>). An example of a mapping entry <NUM> in the fourth section 950d includes an input comprising detection of a left turn signal that maps to the "left turn signal" lighting effect specified by a lighting routine (e.g., LR_13) that is sent only to the light controller <NUM> corresponding to the light assembly <NUM> located at the left-front speaker cover. For example, the sequence of lighting routines may comprise LR_13; LR_0; LR_0; LR_0; LR_0. Another example of a mapping entry <NUM> in the fourth section 950d includes an input comprising detection of a right turn signal that maps to the "right turn signal" lighting effect specified by a lighting routine (e.g., LR_13) that is sent only to the light controller <NUM> corresponding to the light assembly <NUM> located at the right-front speaker cover. For example, the sequence of lighting routines may comprise LR_0; LR_13; LR_0; LR_0; LR_0. Another example of a mapping entry <NUM> in the fourth section 950d includes an input comprising detection of braking of the vehicle that maps to the "braking" lighting effect specified by a lighting routine (e.g., LR_12) that is sent only to the light controllers <NUM> corresponding to the light assemblies <NUM> located at the left-front speaker cover, right-front speaker cover, and front dash. For example, the sequence of lighting routines may comprise LR_12; LR_12; LR_12; LR_0; LR_0.

The fifth section 950e includes mapping entries <NUM> for inputs received from the entertainment sub-system <NUM> (represented as "ENT" inputs in <FIG>). An example of a mapping entry <NUM> in the fifth section 950e includes an input comprising increasing of the amplifier volume that maps to the "volume increase" lighting effect specified by a lighting routine (e.g., LR_15) that is sent only to the light controller <NUM> corresponding to the light assembly <NUM> located at the front dashboard. For example, the sequence of lighting routines may comprise LR_0; LR_0; LR_15; LR_0; LR_0. Another example of a mapping entry <NUM> in the fifth section 950e includes an input comprising decreasing of the amplifier volume that maps to the "volume decrease" lighting effect specified by a lighting routine (e.g., LR_16) that is sent only to the light controller <NUM> corresponding to the light assembly <NUM> located at the front dashboard. For example, the sequence of lighting routines may comprise LR_0; LR_0; LR_16; LR_0; LR_0. For example, the lighting routine (e.g., LR_16) causes the light assembly <NUM> to illuminate green lights in sequence from right to left. Another example of a mapping entry <NUM> in the fifth section 950e includes an input comprising increasing of the amplifier volume to maximum that maps to the "volume maximum" lighting effect specified by a lighting routine (e.g., LR _19) that is sent to all light controllers <NUM> in the set of light controllers <NUM>. For example, the sequence of lighting routines may comprise LR_19; LR_19; LR_19; LR_19; LR_19. For example, the lighting routine (e.g., LR_19) causes the light assembly <NUM> to briefly illuminate red lights.

<FIG> is a flow diagram of method steps for controlling a set of light assemblies <NUM> that can be implemented in the vehicle lighting system of <FIG>, according to various embodiments. Although the method steps are described in conjunction with the systems of <FIG> and <FIG>, persons skilled in the art will understand that the method steps can be performed in any order by any system. In some embodiments, the method <NUM> may be performed by the lighting effects engine <NUM> in conjunction with the vehicle sub-systems <NUM>, the set of light controllers <NUM>, and the set of light assemblies <NUM>.

The method <NUM> begins by receiving (at step <NUM>) an input at the lighting effects engine <NUM>. For example, the received input may comprise a user input received via the I/O devices <NUM>, or an input signal received from a vehicle sub-system <NUM>, such as the navigation/GPS sub-system <NUM>, safety/autonomous sub-system <NUM>, fundamental sub-systems <NUM>, or entertainment sub-system <NUM>. The lighting effects engine <NUM> identifies (at step <NUM>) a lighting effect corresponding to the received input, for example, via a lighting mapping table <NUM>. The lighting effects engine <NUM> determines a mapping entry <NUM> in the lighting mapping table <NUM> that is associated with the received input, the mapping entry <NUM> specifying a set of lighting routines corresponding to the identified lighting effect. The mapping entry <NUM> further specifies a particular light controller <NUM> and light assembly <NUM> pair associated with each lighting routine <NUM> in the set of lighting routines.

The lighting effects engine <NUM> retrieves (at step <NUM>) the set of lighting routines from a storage device <NUM> and transmits the set of lighting routines to the set of light controllers <NUM> for execution. Each lighting routine <NUM> in the set of lighting routines is transmitted to the particular light controller <NUM> associated with the lighting routine <NUM>. The set of light controllers <NUM> receive (at step <NUM>) the set of lighting routines, and each light controller <NUM> applies/executes the received lighting routine <NUM> on the corresponding light assembly <NUM> by controlling the light sources <NUM> of the light assembly <NUM> in accordance with the received lighting routine. In particular, each light controller <NUM> controls the light sources <NUM> of the light assembly <NUM> by sending control signals to the light sources <NUM> for controlling the light sources <NUM> in accordance with the received lighting routine. The method <NUM> then continues at step <NUM> whereby the lighting effects engine <NUM> receives a next input.

In sum, a system and method is disclosed for constructing and controlling one or more light assemblies in an interior of a vehicle. In some embodiments, a light assembly is constructed by forming a PCB layer to have a geometric shape that is based on a geometric shape of a corresponding vehicle component. A set of light sources (such as LEDs) are mounted onto the PCB layer, and terminals and internal wiring are formed on the PCB layer. A protective layer is formed over the PCB layer and a fabric layer is formed over the protective layer. External wiring is attached to the terminals, the external wiring <NUM> being connected to a corresponding light controller for supplying power and control signals to the set of light sources. The formed PCB layer <NUM> is attached to the corresponding vehicle component, for example, via an adhesive layer. In some embodiments, a lighting effects engine receives an input from a user or a vehicle sub-system, determines a lighting effect corresponding to the received input, retrieves a set of lighting routines associated with the lighting effect, and transmits the set of lighting routines to the set of light controllers. The set of light controllers collectively generate the lighting effect by applying/executing the received lighting routines on the set of light assemblies.

Aspects of the present embodiments may be embodied as a system, method or computer program product. Accordingly, aspects of the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a "module" or "system. " In addition, any hardware and/or software technique, process, function, component, engine, module, or system described in the present disclosure may be implemented as a circuit or set of circuits. Furthermore, aspects of the present disclosure may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.

Claim 1:
A vehicle lighting system, comprising:
a light assembly (<NUM>; <NUM>; <NUM>; <NUM>) having:
a printed circuit board, PCB, layer (<NUM>) that is attachable to a vehicle component (<NUM>), wherein the vehicle component (<NUM>) comprises a speaker cover for an audio speaker positioned in any location within a vehicle, wherein a shape of the PCB layer (<NUM>) is based on a shape of the vehicle component (<NUM>), and wherein the PCB layer (<NUM>) is perforated with a plurality of holes to allow sound to penetrate through the PCB layer (<NUM>); and
a set of light sources (<NUM>) mounted on the PCB layer (<NUM>); and
a light controller (<NUM>) that is coupled to the light assembly (<NUM>; <NUM>; <NUM>; <NUM>) and is configured, when in operation, to cause the set of light sources (<NUM>) to generate a lighting effect within an interior of a vehicle.