Global Headlamp

Abstract

We provide global headlamps that can be used in countries around the world. A system and method for global headlamps includes: obtaining configuration information indicating a jurisdiction associated with a vehicle; accessing headlamp state information including a plurality of headlamp states; determining a current headlamp state from the plurality of headlamp states based on the configuration information; and outputting a propagation via a pixelated light source within the vehicle's headlamp, the propagation representing a particular beam pattern conforming to the jurisdiction.

Description

[Technical Field]

[0001] [CROSS-REFERENCE TO RELATED APPLICATIONS] This application claims priority to U.S. Provisional Patent Application No. 63 / 058,876, filed July 30, 2020, the contents of which are expressly incorporated by reference in their entirety.

[0002] FIELD OF THE DISCLOSURE The present disclosure relates to vehicle headlamps, and more particularly, to area-adjustable vehicle headlamps. [Background technology]

[0003] Headlamps, such as headlights at the front of a vehicle, are fundamental tools for enhancing safety for people inside and outside the vehicle. For example, light from a vehicle's headlamps can illuminate the world to increase the visibility of people inside the vehicle. As another example, the light can enable people outside the vehicle to identify the vehicle as it moves through the world. This dual purpose of headlamps (e.g., seeing and being seen) can inform the particular propagation (e.g., beam pattern or projection) of the light output by each headlight. As one example, a vehicle's headlamps can project asymmetric light to illuminate leading vehicles and pedestrians while substantially minimizing glare to oncoming traffic.

[0004] Different jurisdictions, such as countries or geographic regions, have different regulatory or standard-setting bodies that set regulations regarding these projections. As one example, vehicles in Europe have headlights that comply with regulations set forth by the Economic Commission for Europe (ECE). As another example, vehicles in the United States have headlights that comply with Federal Motor Vehicle Safety Standards set forth by the National Highway Traffic Safety Administration (NHTSA). In this example, U.S. vehicles may use headlamp propagation as defined by FMVSS 108.

[0005] Due to these jurisdictional differences, global vehicle operators manufacture different headlamps for different jurisdictions. For example, regulations in different jurisdictions may conflict with each other, such that different headlamps are required for different jurisdictions. Furthermore, within a single jurisdiction, there may be variations due to driver handedness. As an example, roads in certain countries within the European Union (e.g., the UK, Ireland) are left-handed, while roads in certain other countries within the European Union (e.g., Germany, France) are right-handed. Summary of the Invention

[0006] The systems, methods, and devices of this disclosure each have several innovative aspects, no single one of which is solely responsible for all of the desirable attributes disclosed herein.

[0007] While particular embodiments and examples are disclosed herein, the subject matter of the present invention extends beyond the specifically disclosed example embodiments to other alternative embodiments and / or uses, as well as modifications and equivalents thereof.

[0008] The details, including optional details, of one or more embodiments of the subject matter of this specification are set forth in the accompanying drawings and the description below. Other optional features, aspects, and advantages of the subject matter will become apparent from the description, drawings, and claims.

[0009] One embodiment is a computer-implemented method executed by a headlamp controller included in a vehicle that can be configured to control headlamps of the vehicle, the method including obtaining configuration information indicating a jurisdiction associated with the vehicle, accessing headlamp state information including a plurality of headlamp states, determining a current headlamp state from the plurality of headlamp states based on the configuration information, and outputting, via a pixelated light source in the headlamp, a propagation based on the current headlamp state, the propagation representing a particular beam pattern that conforms to the jurisdiction.

[0010] Another embodiment is a vehicle system for propagating light compliant with requirements of multiple jurisdictions, the system including a memory that stores headlamp status information for multiple jurisdictions and a selection of a current jurisdiction, a controller that reads the selected current jurisdiction and headlamp status information associated with the selected jurisdiction, and a plurality of light emitting elements configured to output a propagation compliant with the selected jurisdiction based on the headlamp status information.

[0011] Yet another embodiment is a headlamp controller included in a vehicle, the headlamp controller controlling headlamps of the vehicle, the headlamp controller comprising one or more processing elements configured to obtain configuration information indicative of a jurisdiction associated with the vehicle, determine a current headlamp state based on the configuration information, and cause a pixelated light source in the headlamp to output a propagation representative of a particular beam pattern that complies with the jurisdiction based on the current headlamp state. [Brief explanation of the drawings]

[0012] Throughout the drawings, reference numbers are reused to indicate correspondence between referenced elements. The drawings are provided to illustrate embodiments of the subject matter described herein, but not to limit its scope.

[0013] [Figure 1A] 1 illustrates a block diagram of an example vehicle that sets headlamp status based on configuration information indicative of a jurisdiction.

[0014] [Figure 1B] 1 shows a detailed view of an example of a pixelated light source for a headlamp.

[0015] [Figure 2] 1 illustrates an example process for setting headlamp status based on configuration information.

[0016] [Figure 3]1 illustrates an example process for a headlamp controller to cause light output from a headlamp to match a particular jurisdiction.

[0017] [Figure 4A] 1 illustrates an example of a low beam condition produced by a pixelated light source compliant with a first jurisdiction. [Figure 4B] 1 illustrates an example of a low beam condition produced by a pixelated light source compliant with a first jurisdiction. [Figure 4C] 1 illustrates an example of a low beam condition produced by a pixelated light source compliant with a first jurisdiction.

[0018] [Figure 5A] 1 illustrates an example of a low beam condition produced by a pixelated light source compliant with a second jurisdiction. [Figure 5B] 1 illustrates an example of a low beam condition produced by a pixelated light source compliant with a second jurisdiction. [Figure 5C] 1 illustrates an example of a low beam condition produced by a pixelated light source compliant with a second jurisdiction.

[0019] [Figure 6A] 1 illustrates an example of a low beam condition produced by a pixelated light source compliant with a third jurisdiction. [Figure 6B] 1 illustrates an example of a low beam condition produced by a pixelated light source compliant with a third jurisdiction. [Figure 6C] 1 illustrates an example of a low beam condition produced by a pixelated light source compliant with a third jurisdiction.

[0020] [Figure 7] 1 illustrates an exemplary pixelated light source that outputs different low beam states.

[0021] Like reference numbers and designations in the various drawings indicate like elements. DETAILED DESCRIPTION OF THE INVENTION

[0022] overview This specification describes, among other things, a global headlamp usable in any or substantially any country in the world. As described below, the global headlamp can use a pixelated light source as its light source. In some embodiments, the pixelated light source can correspond to an array of light emitting elements. For example, the pixelated light source can have a threshold number of columns (e.g., three columns, four columns, five columns), each with a certain number of light emitting elements. In this example, the columns can have the same or different numbers of light emitting elements. An example of an embodiment of a pixelated light source described herein with reference to FIG. 1B has four columns, where the first and second columns have 28 light emitting elements (e.g., columns 116A and 116B), the third column has 24 light emitting elements (e.g., column 116C), and the fourth column has 22 light emitting elements (e.g., column 116D). In some embodiments, each light emitting element can be individually addressable or addressable in groups.

[0023] The aforementioned global headlamp may output light that complies with automotive beam pattern requirements established by regulatory bodies in different jurisdictions. Light that forms a particular beam pattern, beam shape, projection, etc. is referred to herein as a propagation. As one example, a global headlamp may be configured to output a first low beam propagation that is used by a vehicle in the United States and complies with U.S. automotive or other vehicle regulatory requirements. As another example, a global headlamp may be configured to output a second low beam propagation that is used by a vehicle in the European Union and complies with European Union vehicle regulatory requirements. Thus, it will be appreciated that jurisdictions may set requirements for one or more countries or regions associated with the jurisdiction.

[0024] The output of these different propagations, which comply with different regulatory agencies, can be satisfied through control of the light-emitting elements in the pixelated light source. For a first propagation, a first subset of light-emitting elements can be used to output light. Each light-emitting element in the first subset can output light with a particular intensity or intensity relative to each other. Intensity, in some embodiments, can represent luminous intensity. As can be appreciated, the particular intensity of an LED can be adjusted (e.g., the luminous intensity can be adjusted) according to the current through the LED. For a second propagation, a second subset of light-emitting elements can be used to output light. This second subset can include different light-emitting elements compared to the first subset. Optionally, the second subset can include the same light-emitting elements as the first subset and output light with a different intensity or relative intensity compared to the light-emitting elements in the first subset.

[0025] In one embodiment, a vehicle's headlamp controller can be used to update headlamp propagation in substantially real time. As referred to herein, the headlamp controller can update headlamp status to indicate the particular propagation to be used. For example, the headlamp controller can determine that the vehicle is in a first jurisdiction (e.g., the United Kingdom). In this example, the vehicle can move to a second jurisdiction (e.g., France). Optionally, the headlamp controller may obtain configuration information indicative of the headlamp status. An example of the configuration information can include the vehicle's location. Based on the configuration information, the vehicle can update the headlamp status to be associated with the second jurisdiction. While first and second jurisdictions are described above, in some embodiments, the same jurisdiction can have different requirements for the country or region associated with the jurisdiction. For example, a jurisdiction can have a first country requirement of driving on the left side of the road, which can differ from a second country requirement of driving on the right side of the road.

[0026] In this manner, the technology described herein enables global headlamps that can be used worldwide. Therefore, global headlamps can simplify vehicle manufacturing because the same headlamp can be used in any country. For example, the bill of materials can be reduced from three or more light source variations to a single light source (e.g., a pixelated light source). Furthermore, the headlamp controller can enable an improved user experience when using the vehicle. For example, the headlamp controller can enable seamless transitions between jurisdictions. As another example, the headlamp controller allows a manufacturer's employee to easily define headlamp status before delivery to a purchaser. In this manner, vehicles can be shipped worldwide without physically modifying the vehicle's headlamps.

[0027] Block Diagram FIG. 1A shows a block diagram of an example vehicle 100 that sets headlamp states 112A-B of headlamps 110A-B based on configuration information 106 indicative of a jurisdiction. The headlamps 110A-B may use pixelated light sources as described in FIG. 1B. The vehicle 100 may include a vehicle processor 104 for controlling the functions or operation of the vehicle 100. For example, the processor 104 may provide information (e.g., via one or more data buses) to one or more other systems included in the vehicle 104. In this example, the other systems may relate to heating, ventilation, and air conditioning (HVAC) functions, autonomous driving functions, electric vehicle battery monitoring / control, etc. The processor 104 may further obtain information from one or more sensors (e.g., global navigation satellite system sensors, cameras), one or more antennas, etc.

[0028] In the illustrated embodiment, the vehicle 100 further includes headlamp controllers 102A-102B that control each of the headlamps 110A-110B on the vehicle 100. The headlamp controllers 102A-102B may correspond to a processing element (e.g., a processor, an FPGA, an ASIC, etc.). The headlamp controllers 102A-102B may also correspond to an electronic control unit (ECU) as described in U.S. Provisional Application No. 63 / 043467 and International Application No. PCT / US2021 / 038658, which are incorporated by reference herein in their entireties. In some embodiments, a single headlamp controller may be used to control the headlamps 110A-110B.

[0029] The headlamp controllers 102A-102B can set the current headlamp states 112A-112B of the headlamps 110A-110B. As previously described, a headlamp state can cause the headlamp to output a particular propagation. For example, a headlamp state can cause the headlamp to output light that projects a particular beam pattern. The headlamp controllers 102A-102B can define the headlamp states 112A-112B from a plurality of states. The headlamp states can represent permutations that cause the headlamp to output propagations that comply with the regulatory rules of a particular jurisdiction. Thus, multiple states can represent all headlamp states that comply with the regulatory rules of any jurisdiction. For example, the headlamp controller 102A can cause the headlamp 110A to output a low beam propagation that complies with U.S. regulatory rules. As another example, the headlamp controller 102A can cause the headlamp 110A to output a high beam propagation that complies with those same rules.

[0030] To define the headlamp states 112A-112B, in some embodiments, the headlamp controllers 102A-102B can use configuration information 106. The configuration information 106 can indicate a jurisdiction so that the headlamp states 112A-112B are compliant with the jurisdiction. An example of the configuration information 106 can include the current location of the vehicle 100 (e.g., based on GNSS information received from the vehicle processor 104 and / or a GNSS sensor). With this example of configuration information 106, the headlamp controllers 102A-102B can select a headlamp state 112A-112B that is compliant with the jurisdiction that regulates the location. Additionally, the headlamp states 112A-112B can be specific to low beam or high beam states.

[0031] The configuration information 106 may also include a homology region associated with the vehicle 100. For example, the homology region may outline countries that implement a particular regulation (e.g., countries within the same jurisdiction). The homology region may be based on a country variable (also called a country code) for logically selecting applicable states. In some embodiments, the homology region may be set during manufacture of the vehicle 100. For example, the country variable may be set with respect to the vehicle or other identifier indicating the jurisdiction. Thus, the headlamp controllers 102A-102B may select headlamp states 112A-112B that conform to the homology region. In this manner, manufacturing of the vehicle 100 may be simplified. For example, the same headlamp controllers 102A-102B and headlamps 110A-110B may be used to manufacture vehicles regardless of region.

[0032] During manufacture, these homology regions may be defined to bring the vehicle into compliance with regulations in one of the regions. In some embodiments, the homology regions may be stored in a protected portion of memory or in read-only memory of the vehicle processor 104. Optionally, a specific password, authentication key, secret key, etc. may be required to adjust the homology regions (e.g., as described in FIG. 3).

[0033] In some embodiments, vehicle 100 may determine that its current location is outside a defined homology region. For example, the driver of vehicle 100 may have driven or otherwise transported vehicle 100 to a country in a different homology region. In this example, vehicle 100 may obtain location information via a Global Navigation Satellite System (GNSS) position. Based on the GNSS position, vehicle 100 may determine that vehicle 100 is in a different homology region. In some embodiments, vehicle 100 may provide its location to an external system over a network (e.g., via a cellular network or Wi-Fi). In response, the external system may indicate the homology region relative to the location of vehicle 100.

[0034] Thus, the vehicle 100 can identify that different headlamp states 112A-112B should be selected so that the vehicle complies with regulations in different homologous regions (e.g., different jurisdictions). The vehicle 100 can automatically update the headlamp states 112A-112B and optionally present information indicating the update to the user. Optionally, the vehicle 100 can request that the driver confirm that the headlamp states 112A-112B should be updated. For example, the vehicle 100 can include a display responsive to user input. In this example, the vehicle processor 104 can cause the presentation of a user interface via the display. The user interface can request that the driver confirm that the headlamps 110A-110B are configured to output different propagations. In some embodiments, the user interface can present a graphical depiction of the different propagations (e.g., compared to current propagation). As an example, the user interface can present the exemplary diagrams of FIGS. 4A-4C as opposed to FIGS. 5A-5C. In this manner, the driver can see the difference in low beam propagation between, for example, the United States and Europe.

[0035] Thus, headlamp states 112A-112B can cause headlamps 110A-110B to output a propagation that meets the regulations for a particular jurisdiction. Additionally, headlamp states 112A-112B can cause the propagation to be either low beam propagation or high beam propagation. For example, the driver of vehicle 100 can provide an input to vehicle 100 to indicate that either high beams or low beams should be utilized. As another example, vehicle processor 104 can identify when high beams or low beams should be used (e.g., processor 104 can implement automatic high beams). For example, if there is no oncoming traffic, vehicle processor 104 can select high beams. In this example, low beams can be selected if oncoming traffic is detected by vehicle processor 104 (e.g., via radar or camera).

[0036] In addition to triggering specific propagation outputs, the headlamp controllers 102A-102B can enforce secondary requirements. Examples of secondary requirements can include fault conditions defined by a regulatory agency associated with a jurisdiction. Thus, the headlamp controllers 102A-102B can ensure that the headlamps comply with such defined fault conditions.

[0037] For example, for certain jurisdictions (e.g., Europe), if a headlamp's light source experiences a failure, the headlamp can still potentially output light. As an example, a headlamp can still operate (e.g., stop outputting light or reduce light) if some of the light-emitting elements in a pixelated light source experience a failure. In this example, the headlamp controllers 102A-102B can determine whether the remaining functional light-emitting elements still meet the requirements associated with the jurisdiction. If the requirements are met, the headlamp controllers 102A-102B can output a headlamp status 112A-112B that causes the headlamp 110A-110B to output light. Optionally, the vehicle processor 104 can update the display to indicate that the headlamp 110A-110B is experiencing a failure or error. However, if the headlamp controllers 102A-102B determine that the remaining light-emitting elements cannot meet the requirements, the controllers 102A-102B can turn off the headlamp. Similarly, vehicle processor 104 can update the display to indicate that headlamps 110A-110B are not functioning and that the driver should call for assistance.

[0038] As another example of a secondary requirement, the headlamp controllers 102A-102B may implement a combination of lighting. For example, in a first jurisdiction (e.g., the United States), high beams and fog beams cannot be activated simultaneously. Thus, in this example, the headlamp controllers 102A-102B may prohibit fog beams when high beams are activated. In contrast, in a second jurisdiction (e.g., Europe), this combination may be permitted. Thus, the headlamp controllers 102A-102B may ensure that such secondary requirements are met regardless of jurisdiction around the world. In contrast, prior art techniques have relied on hard-coded rules that enforce the secondary requirements of a single jurisdiction.

[0039] FIG. 1B shows a detailed view of an example pixelated light source 120A for a headlamp 110A. The illustrated pixelated light source 120A includes an array of light emitting elements (e.g., rows 116A-116D). These light emitting elements may be included on a printed circuit board (PCB), and light from the light emitting elements may be provided to one or more optical elements for routing to a real-world environment. The illustrated headlamp may correspond to the left-hand side (LHS) headlamp 110A of FIG. 1A. The pixelated light source 120A can be utilized for either the left or right headlamp of a vehicle without modification. In this manner, manufacturing may be simplified because the pixelated light source can be used in both headlamps of a vehicle to operate collectively. A headlamp controller can cause the pixelated light source to output a particular transmission depending on which side of the vehicle the pixelated light source is located on. In some embodiments, a particular pixelated light source may be specific to a side of the vehicle.

[0040] As previously described, headlamp state 112A can cause headlamp 110A to output a propagation compliant with a particular jurisdiction. State 112A can also cause headlamp 110A to output either a low beam or a high beam propagation. Based on state 112A, pixelated light source 120A can cause activation of specific light-emitting elements to generate a propagation. Examples of activation of light-emitting elements for different propagations are shown in FIGS. 4A-4C. Light-emitting elements can include light-emitting diodes (LEDs), micro-LEDs, organic LEDs, etc. In some embodiments, a pixel (e.g., as described below) can be associated with each light-emitting element. In some embodiments, a pixel can be associated with multiple light-emitting elements (e.g., multiple micro-LEDs can form a pixel).

[0041] In some embodiments, headlamp status 112A can indicate pixel information 114A. Headlamp status 112A may optionally be provided via one or more messages on a bus, such as a controller area network (CAN) bus. For example, headlamp controller 102A may store information indicating pixels to be used for propagation in a given jurisdiction. Thus, in this example, controller 102A can define pixels for high beam or low beam propagation consistent with a particular jurisdiction. The stored information may optionally be stored in a lookup table (e.g., in volatile or non-volatile memory of the headlamp controller or processor, etc.). The lookup table can store values ​​for each pixel used for propagation. The values ​​can indicate intensities or relative intensities for the pixel (e.g., luminous intensity). For example, the lookup table can indicate light-emitting element values ​​(e.g., luminous intensity values) for a given headlamp state. Thus, pixel information 114A can reflect values ​​for the light-emitting elements of pixelated light source 120A.

[0042] The pixel information 114A may also be specific to a particular side of the pixelated light source. In the illustrated embodiment, the pixel information 114A may reflect pixel values ​​for a left-side pixelated light source. As an example, a left-side headlamp may output a propagation specific to the left side, and a right-side headlamp may output a propagation specific to the right side. Examples of propagations for left and right-side headlamps are shown in Figures 4A-4B.

[0043] The headlamp status 112A may be provided periodically, such as every threshold number of microseconds or milliseconds. The headlamp status 112A may optionally set values ​​in registers associated with the light-emitting elements. Based on these values, a particular shunt utilized by the LED driver may be selected. In this manner, a subset of the light-emitting elements may be selected. The light intensity, such as luminous intensity, output by the light-emitting elements in the subset may be defined, for example, by the respective duty cycles associated with the LED driver. The luminous intensity may also be defined, for example, based on measurements of the continuous current supplied to each light-emitting element. Information regarding shunts and output intensities is included in U.S. Provisional Application No. 63 / 043467 and International Application No. PCT / US2021 / 038658, which are incorporated herein by reference in their entireties.

[0044] The headlamp state 112A may also be provided as information for the pixelated light source 120A to implement. For example, the pixel information 114A may be analyzed by a processing element included in the pixelated light source 120A. The light source 120A may then activate a subset of the light-emitting elements. The headlamp state 112A may then be updated, and the light source 120A may implement the update. For example, the driver or vehicle may select low beams from a previous high beam state. As another example, the vehicle may be transported to a new jurisdiction.

[0045] Shown are example columns 116A-116D of pixelated light source 120A. In some embodiments, the first two columns 116A-116B can be used for low beam propagation. Optionally, the third and fourth columns 116C-116D may be activated for high beam propagation.

[0046] In some embodiments, there may be additional rows of light emitting elements. Optionally, there may be rows with light emitting elements that output light of different spectrums. For example, one row or a portion thereof may include light emitting elements that output infrared light or ultraviolet light. In this example, a vehicle processor (e.g., processor 104) may activate the infrared light based on the self-driving or autonomous mode that is activated. In some embodiments, these invisible or substantially invisible light emitting elements may be located above the visible light emitting elements. For example, row 116A may correspond to the visible light emitting elements, and above that may include a similarly sized row with invisible light emitting elements.

[0047] As previously described, pixel information 114A may correspond to luminous intensity values ​​of pixels of pixelated light source 120A. In some embodiments, these pixel values ​​may be modified by a scaling factor. For example, vehicle 100 may detect that external ambient light is above a threshold measure. In this example, pixel information 114A may be uniformly increased in intensity by the scaling factor. The scaling factor may optionally be jurisdiction dependent. For example, a first jurisdiction may allow scaling (e.g., Europe as defined in ECE R123). The intensity values ​​may further be updated based on turning of vehicle 100. For example, the intensity of certain light emitting elements may be increased while the intensity of other light emitting elements remains the same or is decreased.

[0048] Flowchart example FIG. 2 illustrates an example process 200 for setting headlamp states based on configuration information. The headlamp controller can obtain configuration information 106 and use the information 106 to define headlamp states. For example, the configuration information 106 can include homology regions (e.g., jurisdictions) as described in FIG. 1A. The configuration information 106 can also include vehicle driving sides. As can be appreciated, certain jurisdictions may allow driving on both sides of the road depending on the location within the particular jurisdiction. The configuration information 106 can further include the current location of the vehicle from an antenna or GNSS sensor. The configuration information 106 can further include vehicle models and variants. For example, the headlamp controller may be configured for use with multiple vehicle models.

[0049] Based on the configuration information 106, the headlamp controller can select a region configuration based on stored information about all global headlamp states. As an example, the headlamp controller can identify that the vehicle should use European regulations for left-hand traffic. The headlamp controller can receive a headlamp state request and select a headlamp state as described in FIGS. 1A-1B.

[0050] As previously described, headlamp conditions can cause headlamps to output specific propagations. For example, a headlamp condition can cause a headlamp to output a jurisdiction-compliant low beam propagation. In this example, a vehicle driver may have selected to use low beams, or the vehicle may have low beams automatically selected. Additionally, the headlamp controller can implement secondary requirements, such as fault conditions, as previously described.

[0051] With respect to propagation, the headlamp state can make use of specific light emitting elements of the pixelated light source. A specific intensity, such as luminous intensity, for the light emitting elements can also be set. In this way, the pixelated light source may be configured to output multiple propagations to enable global use.

[0052] 3 illustrates an example of a headlamp controller process 300 for causing headlamp light output to match a particular jurisdiction. For convenience, this process 300 is described as being performed by a headlamp controller (e.g., controller 110A). In some embodiments, vehicle processor 104 can provide information to the pixelated light source such that controller 110A is not utilized or required. Thus, in some embodiments, vehicle processor 104 can perform some or all of the blocks included in process 300.

[0053] In block 302, the headlamp controller obtains configuration information. As previously described, the configuration information may be provided by one or more vehicle processors. In some embodiments, specific configuration information may be defined during manufacture of the vehicle. For example, a homology region may be established for the vehicle. As another example, the vehicle model, vehicle variant, and optionally the vehicle driver side may be established during manufacture. Other configuration information, such as real-time location, may be determined while the vehicle is in use (e.g., by the vehicle processor 104 or the headlamp controller).

[0054] Thus, the homologous region and / or driving side may be updated based on the real-time location. For example, if the vehicle is driven or transported to a different jurisdiction, the real-time location will reflect the different jurisdiction (e.g., as determined by the processor 104 or the headlamp controller). The vehicle can then prompt the driver to confirm that the headlamp is updated accordingly. For example, the prompt may be provided via a user interface presented on a display included in the vehicle, or the prompt may be provided via audio (e.g., the driver can respond affirmatively to the audio). Once updated, the vehicle can update the homologous region and / or driving side.

[0055] In block 304, the headlamp controller accesses headlamp status information. The headlamp controller may access the headlamp status information in a stored memory. For example, a lookup table may be used to define pixel values ​​for multiple propagations that comply with different jurisdictions.

[0056] In block 306, the headlamp controller determines the current headlamp state. The headlamp controller may determine the particular jurisdiction in which the headlamps should comply. For example, the headlamp controller may determine the current location of the vehicle based on configuration information (e.g., processor 104 may provide information to the headlamp controller that can be used to determine the location and select the jurisdiction). Additionally, the headlamp controller may determine whether low beams or high beams are activated. Based on this information, the headlamp controller may select a headlamp state that results in the output of low beam or high beam propagation that is jurisdiction-compliant and compliant.

[0057] In block 308, the headlamp controller triggers the output of headlamp propagations based on the headlamp status. The headlamp controller can trigger activation of specific light emitting elements within the pixelated light source to generate specific propagations. In this manner, the headlamp controller can enable left-hand traffic low beam propagation in a first jurisdiction to be output through the same headlamp as right-hand traffic high beam propagation in a second jurisdiction.

[0058] As another example, a headlamp controller or vehicle processor can determine a beam shape corresponding to a headlamp state for a homologous region and / or driver's side. The beam shape may be translated by the processor or headlamp controller to a particular pixel (e.g., pixel luminous intensity value). In some embodiments, the state information can be updated via an over-the-air (OTA) update.

[0059] The headlamp controller may optionally be specific to a side of the vehicle, just as the headlamp state is specific to a side of the vehicle (e.g., left side, right side). Optionally, the headlamp state may indicate a propagation for the left and right side, and the headlamp controller may use the propagation for the corresponding side. Propagation Examples

[0060] 4A-4C illustrate an example of a low beam condition produced by a pixelated light source compliant with a first jurisdiction. In the illustrated embodiment, the example jurisdiction is the United States (e.g., FMVSS). 4A-4C illustrate an example of a road with vehicles traveling on the right side.

[0061] 4A shows a first headlamp using a pixelated light source that outputs light 402A from a subset of light-emitting elements. In FIG. 4A, the light source outputs a low beam propagation in the left headlamp. The illustrated cutoff 404 can represent a transition in the illuminated region to the non-illuminated region. For example, the cutoff 404 may extend along the upper length of the propagation separating the illuminated and non-illuminated regions.

[0062] Figure 4B shows a second headlamp that uses a pixelated light source that outputs light 402B from a subset of light emitting elements. In Figure 4B, the light source outputs low beam propagation in the right headlamp.

[0063] Figure 4C illustrates the combination of the first and second headlamps of Figures 4A-4B, including propagation 402C associated with a low beam condition in a first jurisdiction.

[0064] 5A-5C show an example of a low beam condition produced by a pixelated light source that complies with a second jurisdiction. In the illustrated embodiment, the example jurisdiction is Europe for driving on the right side of the road. Thus, FIGS. 5A-5C show an example of a road where vehicles are driving on the right side.

[0065] 5A shows a first headlamp using a pixelated light source that outputs light 502A from a subset of light-emitting elements. In FIG. 5A, the light source outputs a low beam propagation in the left headlamp. The illustrated cutoff 504 can represent a transition in the illuminated region to the non-illuminated region. For example, the cutoff 504 may extend along the upper length of the propagation separating the illuminated and non-illuminated regions.

[0066] Figure 5B shows a second headlamp that uses a pixelated light source that outputs light 502B from a subset of light emitting elements. In Figure 5B, the light source outputs low beam propagation in the right headlamp.

[0067] Figure 5C illustrates the combination of the first and second headlamps of Figures 5A-5B, including propagation 502C associated with a low beam condition in the second jurisdiction.

[0068] 6A-6C show an example of a low beam condition produced by a pixelated light source that complies with a third jurisdiction. In the illustrated embodiment, the example jurisdiction is Europe (e.g., the same as the second jurisdiction described above), but for driving on the left side of the road. Thus, FIGS. 6A-6C show an example of a road with vehicles driving on the left side.

[0069] 6A shows a first headlamp using a pixelated light source that outputs light 602A from a subset of light-emitting elements. In FIG. 6A, the light source outputs a low beam propagation in the left headlamp. The illustrated cutoff 604 can represent a transition in the illuminated region to the non-illuminated region. For example, the cutoff 604 may extend along the upper length of the propagation separating the illuminated and non-illuminated regions.

[0070] Figure 6B shows a second headlamp that uses a pixelated light source that outputs light 602B from a subset of light emitting elements. In Figure 6B, the light source outputs low beam propagation in the right headlamp.

[0071] Figure 6C illustrates a combination of the first and second headlamps of Figures 6A-6B, including propagation 602C associated with a low beam condition in a third jurisdiction.

[0072] 7 shows an example of a pixelated light source that outputs different low beam states 702A-702C. As shown, the low beam state 702A for the United States can include activation of light emitting elements on a first row. The low beam states 702B-702C for Europe can include activation of light emitting elements on both the first and second rows.

[0073] While Figures 4A-4C, 5A-5C, and 6A-6C show examples of low beam conditions, it is understood that high beam conditions may be produced by the pixelated light source in different jurisdictions. The high beam condition may include, by way of example, activation of the third and / or fourth rows of light emitting elements above the pixelated light source.

[0074] Furthermore, in some embodiments, a global headlamp as described herein may correspond to a single headlamp located at the front of a vehicle. The single headlamp may include a light emitting element that extends substantially across (across) the front of the vehicle. Thus, the single headlamp may output light that forms a propagation on both the left and right sides of the vehicle.

[0075] Further embodiments All of the processes described herein may be embodied and fully automated via software code modules executed by a computing system including one or more computers or processors. The code modules may be stored on any type of non-transitory computer-readable medium or other computer storage device. Some or all of the methods may be embodied in dedicated computer hardware.

[0076] Many other variations beyond those described herein will be apparent from this disclosure. For example, depending on the embodiment, certain operations, events, or functions of any of the algorithms described herein may be performed in a different order, or may be added, combined, or entirely omitted (e.g., not all described operations or events may be required to implement an algorithm). Furthermore, in certain embodiments, operations or events may be performed simultaneously rather than sequentially, for example, via multithreading, interrupt processing, or multiple processors or processor cores, or in other parallel architectures. Furthermore, different tasks or processes may be performed by different machines and / or computing systems that can function together.

[0077] The various illustrative logic blocks and modules described in connection with the embodiments disclosed herein may be implemented or performed by a machine, such as a processing unit or processor, 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 thereof, designed to perform the functions described herein. The processor may be a microprocessor, but in alternative examples, the processor may be a controller, microcontroller, or state machine, combinations thereof, etc. The processor may include electrical circuitry configured to process computer-executable instructions. In other embodiments, the processor includes an FPGA or other programmable device that performs logical operations without processing computer-executable instructions. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration. While described herein primarily with reference to digital technology, a processor may also include primarily analog components. For example, some or all of the signal processing algorithms described herein may be implemented in analog circuitry or mixed analog and digital circuitry. The computing environment may include any type of computer system, including, but not limited to, a computer system based on a computational engine within a microprocessor, mainframe computer, digital signal processor, portable computing device, device controller, or appliance, to name a few.

[0078] In particular, conditional language such as "can," "could," "might," or "may" is understood within the context in which it is generally used to convey that certain embodiments include certain features, elements, and / or steps, while other embodiments do not, unless expressly stated otherwise. Thus, such conditional language does not generally imply that the features, elements, and / or steps are somehow required in one or more embodiments, or that one or more embodiments necessarily include logic for determining whether those features, elements, and / or steps should be included in or performed in any particular embodiment, with or without user input or prompting.

[0079] Disjunctive language such as the phrase "at least one of X, Y, or Z" is understood in the context of common usage to indicate that an item, term, etc. can be either X, Y, or Z, or any combination thereof (e.g., X, Y, and / or Z), unless specifically stated otherwise. Thus, such disjunctive language generally does not and should not imply that a particular embodiment requires at least one of X, at least one of Y, or at least one of Z, respectively, to be present.

[0080] Any process descriptions, elements, or blocks in the flow diagrams described herein and / or shown in the accompanying figures should be understood as potentially representing modules, segments, or portions of code that comprise one or more executable instructions for implementing a particular logical function or element in the process. As will be appreciated by those skilled in the art, alternative implementations in which elements or functions may be omitted, performed, or described in a different order than that shown or described, including substantially simultaneously or in reverse order, depending on the functionality involved, are included within the scope of the embodiments described herein.

[0081] Unless otherwise specified, articles such as "a" or "an" should generally be construed to include one or more listed items. Thus, phrases such as "an apparatus configured to" are intended to include one or more of the listed apparatuses. Also, such one or more listed apparatuses may be collectively configured to perform the stated enumeration. For example, "a processor configured to perform enumerations A, B, and C" may include a first processor configured to perform enumeration A working in conjunction with a second processor configured to perform enumerations B and C.

[0082] It should be emphasized that many variations and modifications can be made to the above-described embodiments, and that the elements thereof are to be understood as being among other acceptable examples, and all such modifications and variations are intended to be included within the scope of the present disclosure.

Claims

1. 1. A computer-implemented method executed by a headlamp controller included in a vehicle, the headlamp controller configured to control headlamps of the vehicle, the computer-implemented method comprising: obtaining configuration information indicating a jurisdiction associated with the vehicle; accessing headlamp status information comprising a plurality of headlamp statuses; determining a current headlamp state of the plurality of headlamp states based on the configuration information; and outputting a propagation based on the current headlamp state via a pixelated light source within the headlamp, the propagation representing a particular beam pattern compliant with the jurisdiction.

2. The method of claim 1 , wherein the configuration information includes one or more of a homologous region, a vehicle driver side, a current position of the vehicle, a vehicle model, or a vehicle variant.

3. The method of claim 1 , wherein the headlamp state information includes the plurality of headlamp states stored in respective lookup tables, the lookup tables defining values ​​for pixels of the pixelated light source.

4. The method of claim 3 , wherein the headlamp status information is specific to the side of the vehicle on which the headlamp is located.

5. The method of claim 1 , wherein the current headlamp conditions are selected to be compliant with the jurisdiction.

6. The method of claim 1 , wherein the current headlamp state is associated with high beam or low beam propagation.

7. The method of claim 1 , wherein the headlamp controller implements a secondary requirement of the jurisdiction.

8. The method of claim 1 , wherein the pixelated light source comprises a plurality of light emitting elements, and the propagation is provided by light output from a subset of the light emitting elements.

9. The method of claim 1 , wherein the pixelated light source is configured to output multi-jurisdiction compliant propagation.

10. 1. A vehicle system for propagating light that complies with requirements of multiple jurisdictions, comprising: a memory for storing headlamp status information for a plurality of jurisdictions and a current jurisdiction selection; a controller that reads the selected current jurisdiction and the headlamp status information associated with the selected jurisdiction; a plurality of light emitting elements configured to output a propagation compliant with the selected jurisdiction based on the headlamp status information.

11. The vehicle system of claim 10 , wherein the memory stores luminous intensity values ​​for each subset of the light emitting elements for each jurisdiction.

12. The vehicle system of claim 11 , wherein the memory stores the luminous intensity values ​​in a look-up table.

13. The vehicle system of claim 10 , wherein the headlamp status information indicates a low beam status or a high beam status.

14. The vehicle system of claim 10 , wherein the selection of the current jurisdiction is based on a current location of the vehicle system.

15. The vehicle system of claim 10 , wherein the plurality of light emitting elements are formed in a plurality of columns, and the power propagation causes activation of respective subsets of the light emitting elements.

16. 16. The vehicle system of claim 15, wherein a first power propagation associated with a low beam state in the selected current jurisdiction causes activation of a first light-emitting element included in a first threshold number column, and a second power propagation associated with a high beam state in the selected current jurisdiction causes activation of a second light-emitting element included in a second threshold number column, the second threshold being greater than the first threshold.

17. A headlamp controller included in a vehicle, the headlamp controller controlling a headlamp of the vehicle, the headlamp controller comprising: obtaining configuration information indicating a jurisdiction associated with the vehicle; determining a current headlamp status based on the configuration information; a headlamp controller comprising one or more processing elements configured to cause a pixelated light source within the headlamp to output a propagation representative of a particular beam pattern compliant with the jurisdiction based on the current headlamp conditions;

18. The headlamp controller of claim 17 , wherein the configuration information includes one or more of a homology region, a vehicle driver side, a current position of the vehicle, a vehicle model, or a vehicle variant.

19. 18. The headlamp controller of claim 17, wherein the processing element accesses headlamp state information including a plurality of headlamp states stored in respective lookup tables, the current headlamp state being selected from the plurality of headlamp states, and the lookup tables defining values ​​for pixels of the pixelated light source.

20. 20. The headlamp controller of claim 17, further comprising a memory configured to store a plurality of headlamp states.

Images