Vehicle light control method, system and device and vehicle end control equipment

Abstract

The invention relates to a vehicle light control method, system and device and vehicle end control equipment, and relates to the technical field of vehicles. The method comprises the steps of determining a current lamp using scene of a vehicle based on state updating data under the condition that the state updating data of the vehicle is monitored to meet a target light triggering condition; determining target illumination coordinates for the interior of the vehicle based on the current light scene; acquiring a pre-matched light control instruction based on the target illumination coordinate, and controlling at least one light component of the vehicle based on the light control instruction to illuminate an area corresponding to the target illumination coordinate; in this way, different in-vehicle target areas in related vehicle usage scenes can be illuminated for the user based on different vehicle usage scenes of the user, and therefore the use experience of the user for in-vehicle light is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of vehicles, in particular to a vehicle light control method, system, device and vehicle end control equipment. BACKGROUND

[0002] In related technologies, the light control operation of the vehicle is mostly dependent on manual switching by the user or simple ambient light sensing. Although some technical solutions in related technologies provide differentiated light response solutions (such as adjusting color, brightness, flicker frequency or animation effect) according to different vehicle use scenarios, these solutions usually only focus on the switching of light display forms, and do not further combine the actual demand differences of users for key lighting areas in specific vehicle use scenarios. SUMMARY

[0003] Therefore, it is necessary to provide a vehicle light control method, system, device, vehicle end control equipment, computer readable storage medium and computer program product capable of uniformly and accurately controlling vehicle lights in different scenarios to solve the above technical problems.

[0004] In a first aspect, the present application provides a vehicle light control method, the method comprising:

[0005] In the case that the vehicle is monitored to be updated from a first state to a second state, and the related state update data meets a target light trigger condition, determining a current light use scenario of the vehicle based on the state update data;

[0006] Determining a target lighting coordinate for the interior of the vehicle based on the current light use scenario;

[0007] Obtaining a pre-matched light control instruction based on the target lighting coordinate, and controlling at least one light component of the vehicle based on the light control instruction to illuminate the area corresponding to the target lighting coordinate.

[0008] In a second aspect, the present application further provides a vehicle light control system comprising a cabin domain controller, a vehicle integrated control unit and a plurality of light controllers;

[0009] The cabin domain controller is communicatively connected to any vehicle integrated controller in the vehicle integrated control unit; each vehicle integrated controller is communicatively connected in series, and each vehicle integrated controller is communicatively connected to at least one light controller;

[0010] The cabin domain controller is configured to: in a case where it is monitored that the vehicle is updated from a first state to a second state, and relevant state update data meets a target light triggering condition, determine a current light use scene of the vehicle based on the state update data; determine a target illumination coordinate for an interior of the vehicle based on the current light use scene; obtain a pre-matched light control instruction based on the target illumination coordinate; and send the light control instruction to the vehicle integrated control unit, so that the vehicle integrated control unit sends the light control instruction to the relevant light controller, to control at least one light component in the vehicle pointed to by the light control instruction, to illuminate a region corresponding to the target illumination coordinate.

[0011] In a third aspect, the present application further provides a vehicle light control device, which comprises:

[0012] A data acquisition module is configured to: in a case where it is monitored that the vehicle is updated from a first state to a second state, and relevant state update data meets a target light triggering condition, determine a current light use scene of the vehicle based on the state update data.

[0013] A coordinate determination module is configured to: determine a target illumination coordinate for an interior of the vehicle based on the current light use scene.

[0014] A light control module is configured to: obtain a pre-matched light control instruction based on the target illumination coordinate, and control at least one light component of the vehicle based on the light control instruction, to illuminate a region corresponding to the target illumination coordinate.

[0015] In a fourth aspect, the present application further provides a vehicle end control device, which comprises a memory and a processor, the memory stores a computer program, and the processor implements the steps in the first aspect when executing the computer program.

[0016] In a fifth aspect, the present application further provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the steps in the first aspect.

[0017] In a sixth aspect, the present application further provides a computer program product, which comprises a computer program, and the computer program is executed by a processor to implement the steps in the first aspect.

[0018] In the vehicle light control method, system, device, vehicle end control equipment, computer readable storage medium and computer program product provided by the present application, the vehicle light control method is used to obtain and analyze the relevant state update data when it is monitored that the vehicle is updated from the first state to the second state. When it is determined that the state update data meets any target light triggering condition, the current light use scene of the vehicle is determined based on the state update data. Then, the target illumination coordinates in the vehicle are determined based on the determined current light use scene, so as to know the in-vehicle area that the user intends to illuminate in the current light use scene. Then, the pre-matched light control instruction is obtained based on the determined target illumination coordinates, so as to obtain the light control instruction that can be used to control the in-vehicle light and realize the illumination of the target illumination coordinates in the vehicle. Then, the light control instruction can be sent to the related light component to realize the opening control of the light component, so as to achieve the illumination effect of the area corresponding to the target illumination coordinates in the vehicle through the start of the light component, thereby realizing the effect that the opening of the in-vehicle light can meet the current needs of the in-vehicle user. Therefore, the human-computer interaction between the in-vehicle light and the in-vehicle user can be improved, and the light use effect that the in-vehicle user intends to achieve can be met. BRIEF DESCRIPTION OF DRAWINGS

[0019] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related art, the drawings needed to be used in the description of the embodiments of the present application or the related art will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other related drawings can be obtained by those skilled in the art without creative labor.

[0020] Figure 1 An application environment diagram of the vehicle light control method in an embodiment;

[0021] Figure 2 A flowchart of the vehicle light control method in an embodiment;

[0022] Figure 3 A sub-flowchart of the vehicle light control method in an embodiment;

[0023] Figure 4 An architecture diagram of the first vehicle integrated controller in an embodiment;

[0024] Figure 5 An architecture diagram of the second vehicle integrated controller in an embodiment;

[0025] Figure 6 An architecture diagram of the third vehicle integrated controller in an embodiment;

[0026] Figure 7This is a structural block diagram of a vehicle lighting control device in one embodiment;

[0027] Figure 8 This is an internal structural diagram of the vehicle-side control device in one embodiment. Detailed Implementation

[0028] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0029] It should be noted that the terms "first," "second," etc., used in this application can be used to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish the first element from the second element. The terms "comprising" and "having," and any variations thereof, used in this application, are intended to cover non-exclusive inclusion. The term "multiple" used in this application refers to two or more. The term "and / or" used in this application refers to one of the embodiments, or any combination of multiple embodiments.

[0030] The vehicle lighting control method provided in this application embodiment can be applied to, for example... Figure 1 In the application environment shown, the vehicle lighting control system includes a Cockpit Domain Controller (CDC), a Vehicle Intelligence Unit (VIU), and multiple lighting controllers. The Vehicle Intelligence Unit may include multiple vehicle integrated controllers, such as a first vehicle integrated controller VIU0, a second vehicle integrated controller VIU1, and a third vehicle integrated controller VIU2. The Cockpit Domain Controller can communicate with one vehicle integrated controller, and the vehicle integrated controllers can be connected in series. Each vehicle integrated controller can also communicate with several lighting controllers, and each lighting controller can be used to control the vehicle lights. Figure 1 (The relevant vehicle lights are not shown) are turned on or off, and the lighting parameters are displayed. The VIU0 can serve as the main control unit for the output control of the vehicle lighting control system, directly driving and controlling the output effect of the interior lights.

[0031] In this method, when the cockpit domain controller detects that the vehicle has changed from a first state to a second state, and the relevant state update data meets the target lighting triggering conditions, it determines the current lighting scenario of the vehicle based on the state update data; it determines the target illumination coordinates for the vehicle interior based on the current lighting scenario; it obtains a pre-matched lighting control command based on the target illumination coordinates, and controls at least one lighting component of the vehicle based on the lighting control command to illuminate the area corresponding to the target illumination coordinates. This method helps improve the human-machine interaction between in-vehicle lighting and in-vehicle users, and meets the lighting effects that in-vehicle users intend to achieve.

[0032] The cockpit domain controller can also communicate with a server via a network. The server can be a standalone physical server, a server cluster or distributed system consisting of multiple physical servers, or a cloud server that provides cloud computing services.

[0033] In one exemplary embodiment, such as Figure 3 As shown, a vehicle lighting control method is provided, which is applied to... Figure 1 The following steps, 201 to 203, are used as an example to illustrate the process:

[0034] Step 201: When it is detected that the vehicle has changed from the first state to the second state, and the relevant state update data meets the target light triggering conditions, the current lighting scenario of the vehicle is determined based on the state update data.

[0035] Among them, vehicles can be any passenger car, commercial vehicle, or special vehicle; passenger cars include sedans, SUVs, etc.; commercial vehicles include city buses, long-distance buses, trucks, etc.; special vehicles include fire trucks, ambulances, police cars, emergency rescue vehicles, etc.

[0036] The vehicle parameters related to the first state and the second state are somewhat different; the state update data corresponding to the second state updated from the first state may include change data of various state information of the vehicle, such as change data related to the state of the doors, change data related to the state of the occupants, change data related to the state of the central locking system, change data related to the state of the armrest box, change data related to the state of wireless charging, change data related to the state of the small table, change data related to the state of the curtain, etc.

[0037] The lighting triggering conditions can include changes in the status of the car doors, occupants, central locking, armrest, wireless charging, tray tables, and screens, among others. Different status update data can be pre-set with corresponding matching lighting triggering conditions. Specifically, a matching relationship can be pre-set between the status update data and the vehicle lighting scenario; or a matching relationship can be pre-set between the status update data, the lighting triggering conditions, and the vehicle lighting scenario.

[0038] For example, the cockpit domain controller monitors and acquires various control signals and status data in the vehicle in real time. When it detects that the vehicle has changed from a first state to a second state, it acquires the status update data related to the change from the first state to the second state, and then determines whether the status update data meets any preset target light triggering condition. If it does, it indicates that the state change of the vehicle can be used to trigger a preset type of follow spot scene. That is, in principle, the control of vehicle lights included in the relevant follow spot scene can be triggered based on the status change data. Therefore, the cockpit domain controller can determine the current lighting scene of the vehicle based on the status update data, or determine the current lighting scene of the vehicle based on the status update data and the corresponding target light triggering condition.

[0039] Step 202: Determine the target illumination coordinates for the interior of the vehicle based on the current lighting scenario.

[0040] Among them, a matching relationship can be pre-set between the vehicle lighting scene and the coordinates of the interior to be illuminated.

[0041] For example, when the cockpit domain controller determines the current lighting scenario of the vehicle, it can determine the target illumination coordinates corresponding to the current lighting scenario based on the preset correlation between the vehicle lighting scenario and the coordinates to be illuminated inside the vehicle.

[0042] Step 203: Obtain a pre-matched lighting control command based on the target illumination coordinates, and control at least one lighting component of the vehicle based on the lighting control command to illuminate the area corresponding to the target illumination coordinates.

[0043] The system can pre-set a matching relationship between the coordinates to be illuminated inside the vehicle and the lighting control commands. The target lighting components pointed to by the lighting control commands can include ambient lights and headlights inside the vehicle; if required, they can also include ambient lights, headlights, and signal lights outside the vehicle. The lighting components can include at least a light-emitting element and a light-emitting direction control element. The light-emitting element can be involved in controlling light emission parameters such as light emission brightness, light emission color, light emission effect, and light emission duration. The light-emitting direction control element can be used to control the light emission direction of the light-emitting element.

[0044] The lighting components controllable by this application can be any lighting component inside the vehicle or specially designed lighting components. For example, they can be lighting components specifically designed for locations inside the vehicle, such as the roof area or side areas. These lighting components can be evenly distributed throughout the vehicle or distributed according to requirements. Each light-emitting element in these lighting components can be equipped with a light emission direction control element. For example, for a passenger vehicle with two rows of seats, four, five, or six lighting components can be evenly distributed in the roof areas of the first and second rows, or five lighting components can be arranged corresponding to the seating arrangement. Furthermore, the number of rows and columns of interior lighting components can be determined based on the vehicle's length and width. This application does not limit the specific number or location of the lighting components controlled by the interior lighting control method provided in this application. For example, the lighting components may also include ambient lighting such as light strips.

[0045] For example, once the target illumination coordinates are determined, the cockpit domain controller can further obtain a pre-matched lighting control command based on the target illumination coordinates and send the lighting control command to the relevant lighting components to be controlled, so as to control the relevant lighting components inside the vehicle through the lighting control command, thereby achieving the effect of illuminating the area inside the vehicle corresponding to the target illumination coordinates.

[0046] The vehicle lighting control method provided in this application acquires and analyzes relevant state update data when the vehicle changes from a first state to a second state. If the state update data satisfies any target light triggering condition, the current lighting scenario of the vehicle is determined based on the state update data. Then, the target illumination coordinates inside the vehicle are determined based on the determined current lighting scenario to ascertain the area inside the vehicle that the user intends to illuminate under the current lighting scenario. Next, a pre-matched lighting control command is acquired based on the determined target illumination coordinates to obtain a lighting control command that can be used to control the interior lighting and illuminate the target illumination coordinates inside the vehicle. The lighting control command is then sent to the relevant lighting components to control their activation, achieving the effect of illuminating the area corresponding to the target illumination coordinates inside the vehicle through the activation of the lighting components. This ensures that the interior lighting meets the current needs of the user inside the vehicle. Therefore, this method improves the human-machine interaction between the interior lighting and the user inside the vehicle, satisfying the user's desired lighting effect.

[0047] In one exemplary embodiment, such as Figure 3As shown, a sub-process of a vehicle lighting control method is provided, including steps 301 to 302. Specifically: Step 301 involves obtaining the target prerequisite conditions for the target lighting trigger condition pre-matching, and the vehicle's current condition parameters; Step 302 involves obtaining a pre-matched lighting control command based on the target illumination coordinates, provided that the current vehicle condition parameters meet the target prerequisite conditions. Specifically, this can be executed as follows: obtaining the target general prerequisite conditions for the target lighting trigger condition pre-matching, and the vehicle's current condition parameters; obtaining the target scene prerequisite conditions for the target lighting trigger condition pre-matching, provided that the current vehicle condition parameters meet the target general prerequisite conditions; and obtaining the lighting control command pre-matched with the state update data, provided that the current vehicle condition parameters meet the target scene prerequisite conditions.

[0048] The target prerequisites can include general prerequisites and scenario-specific prerequisites. General prerequisites refer to the basic conditions necessary for activating the in-vehicle follow spot function. For example, general prerequisites may include: the vehicle's follow spot function setting switch is on; an optical sensor malfunction; and a light sensor that is functioning normally but detects insufficient ambient light, requiring supplemental lighting. The determination or identification of an "optical sensor malfunction" can be achieved by subscribing to the RSM (RadiantSensor Module or Rain and Sunlight Sensor Module) service. The determination or identification of "a light sensor that is functioning normally but detects insufficient ambient light, requiring supplemental lighting" can be achieved by subscribing to the RSM service for light sensor malfunctions. The vehicle's follow spot function setting switch being on (ON) indicates a user demand to enable the follow spot function; an optical sensor malfunction indicates that the lights are forcibly activated when the sensor malfunctions.

[0049] The vehicle's light sensor module can be used to detect at least the ambient light radiation intensity inside the vehicle. Furthermore, the lighting triggering conditions for the lighting components controlled by the vehicle lighting control method provided in this application can be pre-set with matching, identical, universal preconditions.

[0050] The acquired current vehicle condition parameters may include at least vehicle parameters matching pre-set general prerequisites; and may further include other vehicle parameters, such as vehicle parameters associated with the follow spot scene corresponding to the vehicle's status update data. For example, the current vehicle condition parameters may include parameters indicating the state of the vehicle's follow spot function setting switch, parameters indicating whether the optical sensor is malfunctioning, and parameters indicating whether the vehicle's light sensor is functioning normally and has detected insufficient ambient light, requiring supplemental lighting; in addition, they may include parameters indicating the overall vehicle usage mode, parameters indicating the door status, parameters indicating the user's intent inside the vehicle, and so on.

[0051] For example, in order to ensure the accuracy of vehicle lighting control and to avoid other factors that may be detrimental to vehicle use or operation caused by vehicle lighting control, the cockpit domain controller may further obtain the target lighting trigger conditions corresponding to the current vehicle status update data, pre-match the set target general preconditions, and obtain the current vehicle condition parameters. The current vehicle condition parameters obtained here include at least the vehicle parameters that correspond one-to-one with the data types included in the target general preconditions.

[0052] In other words, one possible implementation is that the cockpit domain controller can, based on the analysis of the data types included in the target general prerequisites, further obtain the vehicle's current vehicle condition parameters (the current vehicle condition parameters are the data corresponding to the general prerequisites) by comparing the analyzed data types one by one. The data types included in the current vehicle condition parameters obtained in this way are exactly the same as the data types included in the target general prerequisites. Another possible implementation is that, while obtaining the target general prerequisites, the cockpit domain controller obtains the vehicle's current vehicle condition parameters based on the vehicle condition parameters of all possible data types that are pre-set. In addition to the data that completely corresponds to the data types included in the target general prerequisites, the current vehicle condition parameters obtained in this way may also include other data.

[0053] This application does not specify the method by which the cockpit domain controller obtains the target general preconditions for obtaining the target light triggering conditions and the current vehicle condition parameters of the vehicle. It can choose between the two implementation methods mentioned above based on the requirements.

[0054] Among them, scene prerequisites are relative to general prerequisites. General prerequisites are the basic conditions that must be met to activate the in-vehicle follow spot function, while scene prerequisites are specific conditions that must be met to activate the follow spot function based on the different follow spot scenarios corresponding to the vehicle's status update data, and are adapted to the pre-set matching relevant follow spot scenarios. Different light triggering conditions can be pre-set with matching scene prerequisites.

[0055] In one embodiment, when the follow spot scene is activated and the vehicle is unlocked for follow spotting, the preconditions for the pre-matched target scene may include the vehicle's UsageMode state being either "non-driving" (not in a driving state) or "remote driving" (remote driving), and all four doors being closed. "Non-driving" refers to a state where the vehicle is not actively in motion, such as the vehicle being off (OFF), in park (P) but not started, powered but stationary (e.g., charging, waiting for someone, using cabin functions), or the user being inside the vehicle but not controlling it. "Remote driving" refers to a remote operator controlling the vehicle in real-time via a communication network, performing driving actions such as starting, steering, accelerating, and braking; for example, if automatic parking fails, the user can remotely control the vehicle via a mobile app.

[0056] For example, after obtaining the target general preconditions and current vehicle condition parameters, the cockpit domain controller can further compare the current vehicle condition parameters with the target general preconditions to determine whether the current vehicle condition parameters meet the preset target general preconditions. Only if they do meet the preset target general preconditions will subsequent steps be executed. If the current vehicle condition parameters do not meet the preset target general preconditions, it means that the vehicle is not suitable for triggering the follow-up function of the follow-up light scene corresponding to the vehicle's state update data. In this case, there is no need to execute subsequent steps. This can avoid invalid or redundant execution of subsequent steps, thereby improving the data processing efficiency of the vehicle cockpit domain controller and also helping to ensure the execution efficiency of the cockpit domain controller for other vehicle-side control processes.

[0057] Correspondingly, if the current vehicle condition parameters meet the preset target general prerequisites, it means that the vehicle meets the basic requirements for enabling the follow light function in the follow light scene corresponding to the vehicle's status update data. Then, the cockpit domain controller can further obtain the target scene prerequisites that are pre-matched to the target light triggering conditions, so as to further determine whether the current vehicle condition parameters meet the preset target scene prerequisites.

[0058] As described above, in one implementation, the cockpit domain controller acquires current vehicle condition parameters that only include the data types included in the general preconditions. The cockpit domain controller can then further acquire the vehicle's current vehicle condition parameters (the current vehicle condition parameters being the data corresponding to the scene preconditions) by comparing the analyzed data types one by one based on the analysis of the data types included in the target scene preconditions. In another implementation, the cockpit domain controller acquires current vehicle condition parameters that already include data related to the target scene preconditions. Therefore, the cockpit domain controller can subsequently acquire only the target scene preconditions that are pre-matched to the target light triggering conditions.

[0059] The lighting control command pre-matched with the status update data can be the lighting control command pre-matched with the follow spot scene corresponding to the status update data; different follow spot scenes may have certain differences in the control parameters and methods for different lights in the vehicle. The lighting control command can be sent by the cockpit domain controller to the lighting controller corresponding to the light to be controlled in the vehicle through at least one vehicle integrated controller, so that the lighting controller can control the vehicle light pointed to by the lighting control command.

[0060] For example, after the cockpit domain controller obtains the target scene prerequisites for the target light triggering condition, it can further determine whether the current vehicle condition parameters meet the target scene prerequisites for the target light triggering condition. Only if the determination result is met will subsequent steps be executed. If the current vehicle condition parameters do not meet the preset target scene prerequisites, it means that the vehicle is not suitable for triggering the follow light function of the follow light scene corresponding to the vehicle's state update data. In this case, there is no need to execute subsequent steps. This can avoid invalid or redundant execution of subsequent steps, thereby improving the data processing efficiency of the vehicle cockpit domain controller and also helping to ensure the execution efficiency of the cockpit domain controller for other vehicle-side control processes.

[0061] Correspondingly, if the current vehicle condition parameters meet the pre-set target scenario prerequisites, it means that the vehicle meets the specific requirements for enabling the follow-up lighting function of the follow-up lighting scenario corresponding to the vehicle's status update data (compared to the basic requirements mentioned above). Furthermore, the cockpit domain controller can further obtain the lighting control command pre-matched to the vehicle's status update data to enable the follow-up lighting function of the follow-up lighting scenario corresponding to the vehicle's status update data.

[0062] For example, if the cockpit domain controller obtains a lighting control command that is pre-matched to the vehicle's status update data, it means that the vehicle is suitable for the follow-up lighting function in the scenario corresponding to the status update data. Then, the cockpit domain controller can control the target lighting component pointed to by the lighting control command based on the lighting control command.

[0063] It should be noted that "control of the target lighting components" may include control of turning on some lights or control of turning off some lights. That is, "activation of the follow spot function in the follow spot scene" is not limited to turning on some lights in the vehicle, but may also involve turning off some lights in the vehicle.

[0064] In particular, the activation of the follow spot function in the follow spot scene, in order to meet the lighting effect of illuminating the coordinates of the target intended to be illuminated by the relevant lighting components, may involve adjusting the light emission angle of the relevant number and position of the target lighting components, as well as adjusting parameters such as the light emission color, brightness, frequency, animation effect, and light emission duration of the target lighting components.

[0065] In the above embodiment, the target general preconditions for the target light triggering condition prematch and the vehicle's current vehicle condition parameters are obtained. This allows for a determination of whether the vehicle's current vehicle condition parameters meet the target general preconditions for the target light triggering condition prematch. If the current vehicle condition parameters meet the target general preconditions, it indicates that the vehicle's current state meets the basic preconditions for the vehicle's lights to be controlled. Then, the target scene preconditions for the target light triggering condition prematch can be further obtained to determine whether the current vehicle condition parameters meet the target scene preconditions. If the current vehicle condition parameters meet the target scene preconditions, it indicates that the vehicle's current state meets the specific preconditions required for the vehicle lights to be controlled according to the state update data. Conditionally, the target illumination coordinates corresponding to the updated state data can be directly obtained to pre-match the light control command, and the target light component pointed to by the light control command can be controlled based on the light control command. This vehicle light control method is beneficial to improving the control accuracy of vehicle lights in different scenarios, avoiding or reducing the situation of false triggering or missed triggering of related lights. Moreover, by judging whether the current vehicle condition parameters meet the target general preconditions and the target scenario preconditions in sequence, it is beneficial to end the execution of subsequent steps when the target general preconditions are not met, which helps to avoid redundant execution of related steps in the vehicle light control method. This can improve the data processing efficiency of the vehicle cockpit domain controller and also help to ensure the execution efficiency of the cockpit domain controller for other vehicle-side control processes.

[0066] In an exemplary embodiment, after controlling at least one lighting component of the vehicle based on the lighting control command performed in the above steps, the vehicle lighting control method provided in this application further includes: when it is detected that the state update data corresponding to the vehicle's state update data does not meet the target lighting triggering condition, obtaining a lighting scene shutdown command pre-matched by the lighting control command; implementing reset control of at least one of the lighting components based on the lighting scene shutdown command; and the reset control indicating that the relevant lighting component is controlled to return to a preset initial position.

[0067] The status update data refers to the status update data that has already been monitored by the cockpit domain controller. The cockpit domain controller continuously monitors whether the vehicle's status data has been updated. The update of the status data here mainly refers to the update of data related to the activation of the follow spot function in the preset scene. The preset initial position includes, for example, the target light component being in the off state and the relevant light surface being parallel to the corresponding vehicle surface. In addition, the preset initial position may also include other related parameters, which are not limited to this application.

[0068] For example, when the cockpit domain controller detects a re-update of the status data corresponding to the previously detected status update data, it analyzes and judges whether the re-update data meets the preset target light triggering conditions. If the judgment result is that the re-update data meets any target light triggering condition, the execution steps 201-203 above can be further executed. If the judgment result is that the re-update data does not meet any target light triggering condition, it means that the vehicle does not need to activate any follow spot scene at this time. It is only necessary to end (turn off) the follow spot scene that was activated corresponding to the previously detected status update data. Therefore, at this time, the cockpit domain controller can obtain the light scene shutdown command related to the preset light control command corresponding to the activated follow spot scene. Then, by sending the obtained light scene shutdown command to the relevant light controller, the reset control of at least some of the target lights pointed to by the light scene shutdown command can be realized.

[0069] It should be noted that within the same lighting scene (follow spot scene), the target lighting components pointed to by the pre-set lighting control commands and lighting scene shutdown commands will always involve control over some of the same lighting components (at least the same lighting component), but there can also be differences in the specific lighting components. For example, a lighting control command might be used to turn on target lighting components 1, 2, 3, 4, 5, and 6, while a related lighting scene shutdown command might be used to turn off target lighting components 1, 2, 3, and 4, but without controlling target lighting components 5 and 6, which can remain on. As another example, a lighting control command might be used to turn on target lighting components 1, 2, 3, and 4, and turn off target lighting component 5, while a related lighting scene shutdown command might be used to turn off target lighting components 1, 2, 3, and 4, but without controlling target lighting component 5.

[0070] In this embodiment, when the vehicle's status update data is detected, it is determined whether the status update data meets the target light triggering conditions. If the determination result indicates that the conditions are not met, a light scene shutdown command pre-matched with the light control command corresponding to the previously acquired status update data is used to achieve reset control of at least one of the vehicle's target light components. This achieves the end (shutdown) of the follow spot scene corresponding to the previously acquired status update data. This method helps to ensure accurate control of the end of the follow spot scene corresponding to the previously acquired status update data and avoids redundant control of individual light states by other control methods (such as shutdown control for all vehicle lights).

[0071] For example, the "lighting scene shutdown command pre-matched with the lighting control command" here is essentially a partial shutdown command. Compared to a global shutdown command, it avoids disrupting the other lighting needs of the vehicle occupants and helps prevent functional conflicts and logical confusion. For instance, the lighting control command corresponding to a certain spotlighting scenario is used to: turn on the driver's side dome light, turn on the front passenger side dome light, turn on the left second-row dome light, and turn on the right second-row dome light; while the lighting scene shutdown command corresponding to the same spotlighting scenario can achieve: turn off the left second-row dome light and turn off the right second-row dome light; and the front driver and passenger side dome lights are not controlled until the vehicle status changes to, for example, a spotlighting scenario, at which point the front driver and passenger side dome lights are turned off and the interior ambient lights are turned on.

[0072] In an exemplary embodiment, after controlling at least one lighting component of the vehicle based on the lighting control command performed in the above steps, the vehicle lighting control method provided in this application further includes: when the state update data corresponding to the vehicle's state update data is detected and the light scene shutdown condition pre-matched by the target lighting trigger condition is met, obtaining the light scene shutdown command pre-matched by the lighting control command; implementing reset control of at least one of the lighting components based on the light scene shutdown command; and the reset control indicates that the relevant lighting component is controlled to return to a preset initial position.

[0073] Among them, the light scene closing condition pre-matched by the target light triggering condition can be a condition used to control the exit of the follow spot scene pre-matched by the state update data corresponding to the target light triggering condition; the light scene closing condition may include, for example, the vehicle changing from a stationary state to a moving state, or a certain light in the current follow spot scene being turned on having been continuously lit for a preset time, etc.

[0074] For example, when the cockpit domain controller detects a re-update of the status data corresponding to the previously detected status update data, it will determine whether the re-update of the status data meets the pre-matched lighting scene shutdown condition of the target lighting trigger condition. If the determination result is that the re-update of the status data meets the pre-matched lighting scene shutdown condition of the target lighting trigger condition, it means that the vehicle does not need to activate any follow spot scene at this time. It is only necessary to end (shut down) the follow spot scene that was already activated corresponding to the previously detected status update data. Therefore, at this time, the cockpit domain controller can obtain the lighting scene shutdown command related to the pre-set lighting control command corresponding to the activated follow spot scene. Then, by sending the obtained lighting scene shutdown command to the relevant lighting controller, the reset control of at least some of the target lighting components pointed to by the lighting scene shutdown command can be realized.

[0075] In this embodiment, when the vehicle's status update data is detected, it is determined whether the status update data meets the target light trigger condition pre-matched light scene shutdown condition. If the determination result indicates that the condition is not met, the light scene shutdown command pre-matched based on the light control command corresponding to the previously acquired status update data is used to achieve the reset control of at least one of the vehicle's target lights. This achieves the end (shutdown) of the follow spot scene corresponding to the previously acquired status update data. This method helps to ensure accurate control of the end of the follow spot scene corresponding to the previously acquired status update data and avoids redundant control of individual light states by other control methods (such as shutdown control for all vehicle lights).

[0076] It should be noted that "whether the target light triggering condition is met" and "whether the light scene shutdown condition pre-matched for the target light triggering condition is met" in the two embodiments mentioned above are two completely different comparison concepts. Taking the requirement that a target light triggering condition needs to meet conditions A, B, and C as an example, "whether the target light triggering condition is met" refers to judging whether conditions A, B, and C are met; while in "whether the light scene shutdown condition pre-matched for the target light triggering condition is met", the "light scene shutdown condition" here does not judge whether conditions A, B, and C are met, but can be, for example, judging whether conditions D and E are met; conditions D and E are pre-set light scene shutdown conditions pre-matched for the target light triggering condition.

[0077] For example, in the unlocked follow light scenario, the target light triggering condition may include: the central locking state changes to the unlocked state; and the light scene closing condition pre-matched to the target light triggering condition may include: the central locking state changes to the locked state, or the unlocked follow light scenario is interrupted by other functions, or the unlocked follow light function lasts for 30 seconds.

[0078] In an exemplary embodiment, the vehicle lighting control method provided in this application further includes: after obtaining a lighting scene shutdown command, and after detecting that the relevant lighting component pointed to by the lighting scene shutdown command changes from an on state to a off state, obtaining the light emission parameters of the relevant lighting component in the on state; the light emission parameters include one or more of brightness parameters, color parameters, light flow parameters, and light emission direction; and when a lighting control command matching the lighting scene shutdown command is detected again, implementing light emission control of the relevant lighting component based on the lighting control command and the light emission parameters.

[0079] The phrase "obtain the light output parameters of the relevant lighting components in the on state" aims to obtain the light output parameters of each lighting component in the on state under the follow spot scene related to the light scene's shutdown command. In other words, "lighting component" refers to the lighting component to be controlled under the relevant follow spot scene (a specific follow spot scene), "on state" can refer to the light-on state of the lighting component in the relevant follow spot scene, and "light output parameters" can refer to the light output parameters involved in the entire light-on state of the lighting component in the relevant follow spot scene.

[0080] For example, after receiving a lighting scene shutdown command, the cockpit domain controller can transmit the command to the relevant lighting controller while simultaneously monitoring whether the lighting controller has successfully controlled the target light (lighting component) indicated by the shutdown command. If the cockpit domain controller detects that the target light indicated by the shutdown command has changed from an on state to an off state, it indicates that the target light has been successfully controlled. At this point, the light output parameters of each target light in the on state can be acquired and saved. This allows for the control of the target light in the same follow spot scene to be performed based on the control command and the saved light output parameters when a similar lighting scene control command is subsequently detected.

[0081] For example, if the cockpit domain controller receives a lighting control command for a certain follow spot scene for the first time, it will control the light output according to the preset light output parameters of the relevant target light for that follow spot scene. However, during the continuous process of the follow spot scene, the adjustment operations of the vehicle user on the relevant target light can be recorded so that the saved "light output parameters" include the personalized adjustment of the relevant target light by the vehicle user in the follow spot scene. This allows the cockpit domain controller to control the light output of the relevant target light in the way that the vehicle user prefers in subsequent follow spot scenes. This is beneficial to improving the lighting experience of the vehicle user in different follow spot scenes in the vehicle, thereby improving the overall user experience.

[0082] In this embodiment, by acquiring and saving the light output parameters of the relevant lighting components in each follow spot scene when it is enabled, and controlling the light output of the relevant lighting components by using the saved light output parameters when the follow spot scene is restarted, the light output of the relevant lighting components can be controlled in a way that vehicle users prefer, which helps to improve the lighting experience of vehicle users for different follow spot scenes in the vehicle.

[0083] For example, when the cockpit domain controller obtains the light emission parameters of the relevant target light (light component) in a certain follow spot scene when it is enabled, it can further compare them with the previously saved light emission parameters of the same follow spot scene. If there is no difference in the comparison result, the light emission parameters obtained this time can be left unsaved. If there is a difference in the comparison result, the previously saved light emission parameters can be replaced based on the saved light emission parameters obtained this time, or only the data with differences can be updated and stored.

[0084] In an exemplary embodiment, the target general preconditions include the vehicle follow-beam mode being turned on and the vehicle light sensor module service being subscribed to; the vehicle lighting control method provided in this application further includes: when it is determined that the current vehicle condition parameters indicate that the vehicle follow-beam mode is not turned on and / or the vehicle light sensor module service is not being subscribed to, reacquiring the vehicle's status update data until the status update data satisfies any target lighting triggering condition.

[0085] Among them, "Vehicle follow-up light mode is on" can correspond to the aforementioned "Vehicle follow-up light function setting switch is on", and "Vehicle light sensor module service subscription in progress" can specifically include at least one of the aforementioned "subscribing to RSM service" and "subscribing to RSM service light sensor failure", corresponding to "optical sensor failure" and "line sensor is normal, but detects insufficient ambient light and needs to supplement light".

[0086] For example, after acquiring the target general prerequisites and current vehicle condition parameters, the cockpit domain controller compares these two data points. The result indicates that the current vehicle condition parameters do not meet the target general prerequisites. A specific embodiment corresponds to this: based on the comparison result, the cockpit domain controller learns that the current vehicle condition parameters indicate that the vehicle is not in the vehicle follow headlight mode, and / or is not subscribing to the RSM service, and / or is not experiencing a light sensor malfunction while subscribing to the RSM service. Based on this result, the cockpit domain controller can further execute the step of reacquiring the vehicle's status update data until the status update data meets any target light triggering condition.

[0087] In this embodiment, if it is determined that the current vehicle condition parameters do not meet the target general preconditions (specifically, if it is determined that the current vehicle condition parameters do not meet any of the conditions included in the target general preconditions), then the execution step 201 is returned. This is beneficial because the execution of subsequent steps can be terminated when the target general preconditions are not met, which helps to avoid redundant execution of related steps in the vehicle lighting control method. This can improve the data processing efficiency of the vehicle cockpit domain controller and also help to ensure the execution efficiency of the cockpit domain controller for other vehicle-side control processes.

[0088] In an exemplary embodiment, the vehicle lighting control method provided in this application further includes: when it is determined that the current vehicle condition parameters do not meet the target scenario prerequisites in the target prerequisites, re-acquiring the vehicle's state update data until the state update data meets any target lighting triggering condition.

[0089] For example, after the cockpit domain controller obtains the target scene prerequisites and the current vehicle condition parameters, the comparison between these two data indicates that the current vehicle condition parameters do not meet the target scene prerequisites. The cockpit domain controller can then further execute the step of re-acquiring the vehicle's state update data until the state update data meets any target light triggering condition.

[0090] In this embodiment, if it is determined that the current vehicle condition parameters do not meet the preconditions of the target scenario (specifically, if it is determined that the current vehicle condition parameters do not meet any of the preconditions of the target scenario), then the execution step 201 is returned. This is beneficial because the execution of subsequent steps can be terminated when the preconditions of the target scenario are not met, which helps to avoid redundant execution of related steps in the vehicle lighting control method. This can improve the data processing efficiency of the vehicle cockpit domain controller and also help to ensure the execution efficiency of the cockpit domain controller for other vehicle-side control processes.

[0091] In addition, it should be added that, regarding the determination of "target illumination coordinates", the sound data and motion data of the vehicle occupants can be obtained when the working mode of the lighting components inside the vehicle is in the singing atmosphere mode; based on the sound data and motion data, the target illumination coordinates of the lighting components can be determined.

[0092] For example, acquiring motion data of vehicle occupants includes: acquiring skeletal tracking information and lip tracking information of each vehicle occupant; determining skeletal keypoint data of each vehicle occupant based on the skeletal tracking information, and determining lip keypoint data of each vehicle occupant based on the lip tracking information; and determining motion data of the vehicle occupants based on the skeletal keypoint data and the lip keypoint data.

[0093] For example, the target illumination coordinates of the lighting component can also be determined based on at least one of the audio characteristics of the accompaniment of the song currently playing inside the vehicle, the sound characteristics of the sound data, and the motion characteristics of the motion data. Specifically, this involves acquiring the instrument type, beat type, and spectral characteristics included in the accompaniment of the song currently playing inside the vehicle; and determining the audio characteristics of the accompaniment based on at least one of these factors. Alternatively, the audio energy of the accompaniment of the song currently playing inside the vehicle can be acquired; and the audio characteristics of the accompaniment can be determined based on the energy proportion of each preset frequency band within the audio energy.

[0094] For example, based on the skeletal keypoint data and lip keypoint data included in the motion data of each vehicle occupant, the target occupant for outputting the singing content is determined; based on the sound data and motion data of each target occupant, the target illumination coordinates of the lighting component are determined.

[0095] For example, upon receiving a voice command to control the vehicle's lights, lip images of each user inside the vehicle are acquired; based on the voice command and each lip image, the identifier of the user who initiated the voice command is determined; based on the user identifier, the target illumination coordinates corresponding to the voice command are determined.

[0096] For example, determining the target illumination coordinates corresponding to the light control voice based on the user identifier includes: determining at least one of pre-adapted light control preference information, light control permission information, and light control operation range based on the user identifier; and determining the target illumination coordinates corresponding to the light control voice based on at least one of the light control preference information, light control permission information, and light control operation range.

[0097] For example, the lighting area information included in the lighting control voice is obtained, and the target lighting coordinates for the vehicle are determined based on the lighting area information.

[0098] For example, determining the target lighting coordinates for a vehicle based on lighting area information includes: obtaining lighting reference text and lighting position text included in the lighting area information; and determining the target lighting coordinates for the vehicle based on the lighting reference text, the lighting position text, and a preset vehicle coordinate system.

[0099] For example, determining the target lighting coordinates for a vehicle based on lighting area information includes: determining the target lighting coordinates for a vehicle based on lighting area information and a preset lighting angle quantization strategy.

[0100] For example, the lighting needs focus of the vehicle occupants inside the vehicle and the heat center of the vehicle occupant distribution are obtained; based on the lighting needs focus and the heat center, the target lighting coordinates of the vehicle occupants are determined.

[0101] For example, obtaining the lighting focus of a vehicle occupant inside the vehicle includes: obtaining the user gesture and gaze focus of the vehicle occupant inside the vehicle; determining a first candidate coordinate based on the user gesture and determining a second candidate coordinate based on the gaze focus; and determining the lighting focus of the vehicle occupant based on at least one of the first candidate coordinate and the second candidate coordinate.

[0102] For example, determining the target lighting coordinates of vehicle occupants based on the lighting demand focus and the heat center includes: obtaining the identity identifier of each vehicle occupant and determining the control weight of each vehicle occupant for the vehicle interior lighting components based on the identity identifier; adjusting at least one of the lighting demand focus and the heat center based on each control weight to obtain the adjusted target lighting demand focus and target heat center; and determining the target lighting coordinates of the vehicle occupants based on the target lighting demand focus and the target heat center.

[0103] For example, obtaining the user gestures and gaze focus of vehicle occupants inside the vehicle includes: obtaining the identity identifiers of each vehicle occupant inside the vehicle; and, when a target occupant belonging to a preset object is determined based on the identity identifiers, obtaining the user gestures and gaze focus of the target occupant.

[0104] For example, acquiring user gestures of vehicle occupants inside a vehicle includes: acquiring wrist tracking information and finger tracking information of the hands of each vehicle occupant inside the vehicle; determining key hand data of each vehicle occupant based on the wrist tracking information and finger tracking information; and determining user gestures of the vehicle occupants based on the key hand data.

[0105] For example, the target lighting coordinates of vehicle occupants are determined based on the lighting demand focus and the center of the heat point, including obtaining a first weight for a first candidate coordinate preset for the vehicle, a second weight for a second candidate coordinate preset for the vehicle, and a third weight for the center of the heat point preset for the vehicle; the first weight is greater than the second weight and the first weight is greater than the third weight; the target lighting coordinates of vehicle occupants are determined based on the product of the first candidate coordinate and the first weight, the product of the second candidate coordinate and the second weight, and the product of the center of the heat point and the third weight.

[0106] The vehicle lighting control method provided in this application is essentially a vehicle interior follow spot control method, specifically for interior follow spot settings, and may include:

[0107] (1) Switch triggering conditions: When the CDC (Cockpit Domain Controller) cross-domain call is received, the interface for setting the follow light switch is set. The internal lighting parameters are set through the setInnerLightPara interface (interface for setting internal lighting parameters) of the service BCM_InnerLight_AppSrv (BCM internal lighting application service). AppSrv_CallerId=0x8001 (an example of an application service caller identifier); the parameter innerLightTrackEnableCfg (configuration for enabling the interior light tracking function) controls the enabling status of the light tracking function: 0x1→APPSRV_ONOFFCMD_OFF: disable light tracking, 0x2→APPSRV_ONOFFCMD_ON: enable light tracking;

[0108] (2) Execution action: Based on the CDC's call memory switch and report status, call the innerLightCfgSts interface (internal light configuration status interface) of the BCM_InnerLight_AppSrv service to obtain the configuration status of the internal light, and actively push updates (Notification Even) when the light status changes.

[0109] (3) The VIU stores the follow spot status in EEPROM (Electrically Erasable Programmable Read-Only Memory), which is enabled by default at the factory. When it receives the getter call (value retrieval method call) BCM_InnerLight_AppSrv.innerLightCfgSts (internal light configuration status in BCM internal light application service <e.g.: AppSrv_InnerLightCfgSts, Getter>) from the CDC, the VIU returns the reported value to the caller.

[0110] One embodiment for unlocking a spotlight scene includes the following implementation methods:

[0111] (1) Lighting control, prerequisites (A&B(D||C)&E): A. The vehicle's UsageMode is set to non-driving and non-remote driving; B. The follow headlight switch is on; C. The RSM (Light Sensor Module) service is subscribed to: BCM_RLS_Info.notifyRLSBeamLampCtrlReq.RLSLowBeamWorkModeReq=0x1:ON (one example); that is, the optical sensor is faulty; D. The RSM service is subscribed to: BCM_RLS_Info.notifyRLSFltSt.RLSFltSt.RLSOpticalSnsrFltFlag=0x1:TRUE (one example); that is, the light sensor is normal, but it detects that the ambient light is insufficient and supplemental lighting is required; E. All four doors are closed.

[0112] (2) Triggering condition: The central locking status is obtained by BCM_Door_CS.DoorStatusInfo.CentralLockStatus (the central locking status under the door status information in the BCM door control service) and jumps to 0x1:CS_LockStatus_UNLOCK, which is the unlocked state. (Interface name: DoorStatusInfo.CentralLockStatus, service name: cross-domain service BCM_Door_CS, interface description: central locking status, server: VIU, client: VIU).

[0113] (3) Action: The follow-up light function is unlocked and turned on. The dome light in the front driver's seat is turned on, the dome light in the front passenger seat is turned on, the left dome light in the second row is turned on, and the right dome light in the second row is turned on.

[0114] (4) Exit conditions (A|B|C|D): A. The preconditions are not met; B. BCM_Door_CS.DoorStatusInfo.CentralLockStatus obtains the central locking status and jumps to 0x0:CS_LockStatus_LOCKED (locked state); C. It is interrupted by other functions; D. The tracking light function lasts for 30 seconds.

[0115] (5) Exit action: A. If you exit using exit conditions A, B, or D, the control unlock follow light function will be turned off, and the ceiling light that was turned on by the unlock follow light will be turned off; B. If you exit using exit condition C, the control unlock follow light function will be turned off, and the ceiling light will perform according to the interrupted function; the brightness will be turned on according to the memorized brightness.

[0116] One embodiment is provided: second-row left angle control, and the related implementation methods may include:

[0117] (1) Prerequisite: The motor of the second row left reading light is in good working order;

[0118] (2) Triggering condition: The second row left reading light is currently in the unlocked follow-light control state;

[0119] (3) Action: The angle of the second-row left reading light motor is adjusted to the position of the second-row left seat.

[0120] One embodiment provides a scenario for controlling the right angle of the second row, and the related implementation methods may include:

[0121] (1) Prerequisite: The motor of the second row right reading light is in good working order;

[0122] (2) Triggering condition: The second row right reading light is currently in the unlocked follow-light control state;

[0123] (3) Action: Adjust the angle of the second-row right reading light motor to the position of the second-row right seat.

[0124] One embodiment is provided for a door opening follow spot control scenario (outward opening door), and the related implementation methods may include:

[0125] (1) Preconditions (A&(B|C)&D):

[0126] A. Follow spot light switch is set to ON; B. Subscribe to RSM service BCM_RLS_Info.notifyRLSBeamLampCtrlReq.RLSLowBeamWorkModeReq=0x1:ON; C. Subscribe to RSM service for light sensor fault BCM_RLS_Info.notifyRLSFltSt.RLSFltSt.RLSOpticalSnsrFltFlag=0x1:TRUE; D. Power saving output is effective (Power saving output: prerequisite is no fault in indoor power saving, trigger condition is that the vehicle user mode UsageMode is Convenience / Driving / Remote Driving / OTA / Remote, and the action is indoor light power saving + set to high level); where Convenience / Driving / Remote Driving / OTA / Remote correspond to convenience function / driving status / remote driving / remote upgrade / remote respectively;

[0127] (2) Triggering conditions: Any of the four doors is changed from closed to open (not closed), and the corresponding seat is unoccupied;

[0128] (3) Actions: The door opening follow-up light function is turned on, the front wireless charging position dome light is turned on, the second row left dome light is turned on, the second row right dome light is turned on, the driver's dome light is turned off, and the passenger dome light is turned off.

[0129] (4) Exit conditions (A|B|C): A. The prerequisite conditions are not met; B. All four doors are closed for 10 seconds or the vehicle speed is greater than 3km / h; C. The exit is interrupted by other functions.

[0130] One embodiment is provided for a door opening follow spot control scenario (inward opening door). The differences between the implementation method and the previously mentioned outward opening door may include:

[0131] (1) Triggering conditions: Any of the four doors is changed from closed to open (not closed), and there is someone in the corresponding seat;

[0132] (2) Execution of actions (A&B): A. If the door that is opened is either the driver's side or the passenger side door, the front row spotlight function will be activated, the driver's side dome light will be turned on, and the passenger side dome light will be turned on. B. If the door that is opened is either the left or right door of the second row, the rear row spotlight function will be activated, the left dome light of the second row will be turned on and the angle will be adjusted to the aisle position, and the right dome light of the second row will be turned on and the angle will be adjusted to the aisle position.

[0133] One embodiment is provided for a follow spot scene on an armrest box, and the related implementation methods may include:

[0134] (1) Prerequisites: The internal light energy saving is on, and A. The follow spot setting switch is on; B. RSM service is subscribed; C. The light sensor of the RSM service is faulty;

[0135] (2) Triggering condition: Open the armrest box;

[0136] (3) Execute action: VIU_CommonLight_FirstMiddleSet=0x1:ON; / / Turn on (the top light in the front armrest box position);

[0137] (4) Exit conditions: the internal light is turned off for power saving, the follow spot is turned off, and the armrest box is turned off.

[0138] One embodiment is provided for a wireless charging light-tracking scenario, and the related implementation methods may include:

[0139] (1) Preconditions (A&B&C&(D|E)):

[0140] A. Internal light power saving is on; B. Follow spot switch is on; C. Wireless charging service BCM_WirlessCharging_AppSrv.notifyStatus.WCGChargingSt=0x1: Charging in progress or 0x2: WCGChargingSt_CHARGE_FINISHED: Charging finished; D. RSM service subscription BCM_RLS_Info.notifyRLSBeamLampCtrlReq.RLSLowBeamWorkModeReq=0x1: ON; E. RSM service subscription light sensor failure BCM_RLS_Info.notifyRLSFltSt.RLSFltSt.RLSOpticalSnsrFltFlag=0x1: TRUE;

[0141] (2) Triggering conditions (A|B): A. The driver's door is changed from closed to open and there should be someone in the driver's seat; B. The passenger door is changed from closed to open and there should be someone in the passenger seat.

[0142] (3) Action: The wireless charging follow-up function is turned on, and the overhead light at the front wireless charging position is lit;

[0143] (4) Exit conditions (A|B): A. The preconditions are not met; B. The exit is interrupted by other functions.

[0144] (5) Exit Action (A&B): A. If exiting through exit condition A, the control unlocking follow-up light function will be turned off, and the dome light at the front wireless charging position will be turned on. B. If exiting through exit condition B, the control unlocking follow-up light function will be turned off, and the dome light will perform the function after interruption.

[0145] One embodiment provides a scenario for follow spot lighting on the second-row seats, and the related implementation methods may include:

[0146] (1) Preconditions (A&B&(C|D)): A. Power saving output is effective, B. Follow spot setting switch is on, C. RSM service is subscribed, D. RSM service light sensor is faulty;

[0147] (2) Triggering conditions (A|B): A. The second-row left door is changed from open to closed, and the second-row left dome light is on; B. The second-row right door is changed from open to closed, and the second-row right dome light is on.

[0148] (3) Execution of actions (A&B): A. If triggered by triggering condition A, the second row left seat will be adjusted to the aisle position; B. If triggered by triggering condition B, the second row right seat will be adjusted to the aisle position.

[0149] One embodiment provides a scenario where the small table on the back of the front seat is used for follow lighting. Related implementation methods may include:

[0150] (1) Preconditions (A&B&(C|D)): A. Power saving output is effective, B. Follow spot setting switch is on, C. RSM service is subscribed, D. RSM service light sensor is faulty;

[0151] (2) Triggering conditions (A|B): A. The driver's seat back tray table is turned from closed to unfolded; B. The passenger seat back tray table is turned from closed to unfolded.

[0152] (3) Execution of actions (A&B): A. If triggered by A, the left reading light in the second row will be turned on, with the brightness value set to the memorized brightness value, and the angle will be adjusted to the seat back position; B. If triggered by B, the right reading light in the second row will be turned on, with the brightness value set to the memorized brightness value, and the angle will be adjusted to the seat back position.

[0153] (4) Exit conditions (A|B|C): A. Preconditions are not met; B. Driver's seat tray table is retracted; C. Passenger seat tray table is retracted.

[0154] (5) Exit Action (A&B&C): A. If you exit via A, the left and right reading lights of the second row will be turned off. B. If you exit via B, the left reading light of the second row will be turned off. C. If you exit via C, the right reading light of the second row will be turned off.

[0155] One example provided is a screen-linked follow spot (enhancing the viewing atmosphere) scenario, and related implementation methods may include:

[0156] (1) Preconditions (A&B&(C|D)): A. Power saving output is effective, B. Follow spot setting switch is on, C. RSM service is subscribed, D. RSM service light sensor is faulty;

[0157] (2) Triggering condition: Obtain the screen status through (projection screen unfolding status in BCM projection screen control service) BCM_ProjectorScreen_CS.ProjectorScreenStatusInfo.OpenStatus;

[0158] (3) Execution action: If the screen status changes from other to 0x1:CS_DoorOpenStatus_OPENING, the screen follow light is turned on, the second row left top light is turned on and the illumination position is the seat back position, the second row right top light is turned on and the illumination position is the seat back position.

[0159] (4) Exit conditions (A|B|C): A. Internal lights are off for power saving, B. Follow spot is set to off, C. The curtain status is 0x0:CS_DoorOpenStatus_CLOSING (closing in progress) or the status is 0xFF:CS_DoorOpenStatus_UNKNOWN (unknown status) for 5 seconds or the status is 0x2:CS_DoorOpenStatus_CLOSED (closed) or 0x3:CS_DoorOpenStatus_OPENED (opened).

[0160] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps. It is understood that the steps in different embodiments can be freely combined as needed, and all non-contradictory solutions formed by such combinations are within the scope of protection of this application.

[0161] Based on the same inventive concept, this application also provides a vehicle lighting control system for implementing the vehicle lighting control method described above. The solution provided by this system is similar to the implementation described in the above method; therefore, the specific limitations of one or more vehicle lighting control system embodiments provided below can be found in the limitations of the vehicle lighting control method described above, and will not be repeated here.

[0162] In one exemplary embodiment, please refer to Figure 1 Reference Figure 4-6 , Figure 1 This provides a vehicle lighting control system, including a cockpit domain controller, a vehicle integrated control unit, and multiple lighting controllers. The cockpit domain controller is communicatively connected to any of the vehicle integrated controllers within the vehicle integrated control unit. For example, the cockpit domain controller CDC can be connected to the first vehicle integrated controller via Ethernet (ETH) wiring. The vehicle integrated controllers communicate in series, specifically via Ethernet wiring, and each vehicle integrated controller is communicatively connected to at least one lighting controller. The cockpit domain controller, upon detecting a change in the vehicle's state from a first state to a second state, and provided that the relevant state update data meets the target lighting triggering conditions, determines the vehicle's current lighting scenario based on the state update data; determines the target illumination coordinates for the vehicle's interior based on the current lighting scenario; obtains a pre-matched lighting control command based on the target illumination coordinates; and sends the lighting control command to the vehicle integrated control unit, which then transmits the lighting control command to the relevant lighting controllers, thereby controlling at least one lighting component pointed to by the lighting control command in the vehicle to illuminate the area corresponding to the target illumination coordinates.

[0163] In one exemplary embodiment, please refer to Figure 1 and Figure 4 The first vehicle integrated controller (VIU0) in the vehicle lighting control system can be connected to the cockpit domain controller (CDC) via ETH wiring, and also to the MDC (Modular Domain Controller) via ETH wiring. The MDC can be a modular domain controller, or the MDC (Mobile Data Center) can be the vehicle's mobile data center; the actual functions of the MDC can be configured based on requirements. The first vehicle integrated controller (VIU0) can be electrically connected to target lights via multiple lighting controllers (e.g., HSD, High Side Driver) to control the relevant target lights. For example, the target lights connected to the first vehicle integrated controller (VIU0) via the lighting controllers may include: driver's seatbelt buckle light, passenger's seatbelt buckle light, left puddle light, left backlight, front trunk light, second-row right-side lock buckle light, second-row center lock buckle light, etc.

[0164] In one exemplary embodiment, please refer to Figure 1 and Figure 5 The second vehicle integrated controller VIU1 in the vehicle lighting control system can be directly connected to the following target lights through the lighting controller: switch backlight - right, hazard warning backlight, left puddle light, right puddle light, left vanity mirror light, right vanity mirror light, front dome light, second row left dome light, second row right dome light, third row left dome light, and third row right dome light. The second vehicle integrated controller VIU1 is also connected to the front dome light through one LIN (Local Interconnect Network) bus, and to the second row left dome light, second row right dome light, third row left dome light, and third row right dome light through another LIN bus. The second vehicle integrated controller VIU1 is also connected to the MFW (Multi-Function Wheel) via a CAN (Controller Area Network) bus. The second vehicle integrated controller VIU1 is also connected to two DIUs via another CAN bus. DIUs are Domain Interface Units or Data Interface Units. For example, DIU_FR (Domain Interface Unit – Front Right) can be further electrically connected to target lights via multiple lighting controllers to control the relevant target lights. The target lights connected to DIU_FR via the lighting controllers may include: the right blind spot indicator, the right front indicator light, and the right front door handle light. DIU_RR (Domain Interface Unit – Rear Right) can also be further electrically connected to target lights via multiple lighting controllers to control the relevant target lights. The target lights connected to DIU_RR via the lighting controllers may include: the right rear door light and the right rear door handle light.

[0165] In one exemplary embodiment, please refer to Figure 1 and Figure 6The third vehicle integrated controller (VIU2) in the vehicle lighting control system can directly connect to the following target lights via the lighting controller: trunk light, rear backlight, second-row left latch light, third-row left latch light, third-row right latch light, and n ambient light heads. The lighting controller can also include HSD PWM (High Side Driver Pulse Width Modulation), and can be configured to connect three HSD PWMs to the RGB (Red, Green, and Blue) indicator lights used to form the charging port cover indicator. The third vehicle integrated controller (VIU2) can also connect to the ALC (Adaptive Light Control) via the CANFD (Controller Area Network with Flexible Data-rate) bus. The ALC can also connect to the ambient light heads. In addition, the third vehicle integrated controller VIU2 can also be connected to DIU_FL (Domain Interface Unit – Front Left) and DIU_RL (Domain Interface Unit – Rear Left) via CAN bus. The target lights that DIU_FL can be directly connected to through the lighting controller can include: left blind spot indicator, left front door light, left front door handle light, and backlight; the target lights that DIU_RL can be directly connected to through the lighting controller can include: left rear door light and left rear door handle light.

[0166] Based on the same inventive concept, this application also provides a vehicle lighting control device for implementing the vehicle lighting control method described above. The solution provided by this device is similar to the solution described in the above method; therefore, the specific limitations in one or more vehicle lighting control device embodiments provided below can be found in the limitations of the vehicle lighting control method described above, and will not be repeated here.

[0167] In one exemplary embodiment, such as Figure 7 As shown, a vehicle lighting control device 400 is provided, including: a data acquisition module 41, a coordinate determination module 42, and a lighting control module 43, wherein:

[0168] The data acquisition module 41 is used to determine the current lighting scenario of the vehicle based on the status update data when the vehicle is detected to have changed from a first state to a second state and the relevant status update data meets the target light triggering conditions.

[0169] The coordinate determination module 42 is used to determine the target illumination coordinates for the interior of the vehicle based on the current lighting scenario.

[0170] The lighting control module 43 is used to obtain a pre-matched lighting control command based on the target illumination coordinates, and control at least one lighting component of the vehicle based on the lighting control command to illuminate the area corresponding to the target illumination coordinates.

[0171] In an exemplary embodiment, the lighting control module 43 is used to obtain a pre-matched lighting control command based on the target illumination coordinates. Specifically, it is used to: obtain the target prerequisite conditions for the target lighting triggering condition and the current vehicle condition parameters of the vehicle; and, if it is determined that the current vehicle condition parameters meet the target prerequisite conditions, obtain the pre-matched lighting control command based on the target illumination coordinates.

[0172] In an exemplary embodiment, after the lighting control module 43 controls at least one lighting component of the vehicle based on the lighting control command, if the state update data corresponding to the vehicle's state update data does not meet the target lighting triggering condition, a lighting scene shutdown command pre-matched with the lighting control command is obtained; a reset control of at least one of the lighting components is implemented based on the lighting scene shutdown command; the reset control indicates that the relevant lighting component is controlled to return to a preset initial position.

[0173] In an exemplary embodiment, after the lighting control module 43 controls at least one lighting component of the vehicle based on the lighting control command, if the state update data corresponding to the vehicle's state update data is detected and the light scene shutdown condition pre-matched by the target lighting trigger condition is met, the lighting scene shutdown command pre-matched by the lighting control command is obtained; the reset control of at least one of the lighting components is implemented based on the light scene shutdown command; the reset control indicates that the relevant lighting component is controlled to return to a preset initial position.

[0174] In an exemplary embodiment, the data acquisition module 41 is further configured to: after acquiring a light scene shutdown command and detecting that the relevant light component pointed to by the light scene shutdown command has changed from an on state to a off state, acquire the light output parameters of the relevant light component in the on state; the light output parameters include one or more of brightness parameters, color parameters, light flow parameters, and light output direction; the light control module 43 is further configured to: when acquiring a light control command matching the light scene shutdown command again, implement light output control of the relevant target light based on the light control command and the light output parameters.

[0175] In an exemplary embodiment, the data acquisition module 41 is further configured to: if it is determined that the current vehicle condition parameters indicate that the vehicle is not in the vehicle follow light mode and / or is not in the vehicle light sensor module service subscription, reacquire the vehicle status update data until the status update data meets any target light triggering condition.

[0176] In an exemplary embodiment, the data acquisition module 41 is further configured to: if it is determined that the current vehicle condition parameters do not meet the target scenario prerequisites in the target prerequisites, reacquire the vehicle's state update data until the state update data meets any target light triggering condition.

[0177] Each module in the aforementioned vehicle lighting control device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device (specifically, a vehicle-side control device), or stored in the memory of the computer device as software, so that the processor can call and execute the corresponding operations of each module.

[0178] In one exemplary embodiment, such as Figure 8 The illustration shows a vehicle-side control device including a processor and a memory. The processor provides computational and control capabilities. The memory includes a non-volatile storage medium storing a computer program. When executed by the processor, the computer program implements a vehicle lighting control method.

[0179] Those skilled in the art will understand that Figure 8 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer equipment (specifically, vehicle-side control equipment) on which the present application is applied. The specific computer equipment may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0180] In one exemplary embodiment, a vehicle-side control device is provided, including a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement steps related to a vehicle lighting control method.

[0181] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements steps related to a vehicle lighting control method.

[0182] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements steps related to a vehicle lighting control method.

[0183] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0184] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0185] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0186] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A vehicle lighting control method, characterized in that, The method includes: If the vehicle is detected to have changed from a first state to a second state, and the relevant state update data meets the target light triggering conditions, the current lighting scenario of the vehicle is determined based on the state update data. Determine the target illumination coordinates for the interior of the vehicle based on the current lighting scenario; Based on the target illumination coordinates, a pre-matched lighting control command is obtained, and based on the lighting control command, at least one lighting component of the vehicle is controlled to illuminate the area corresponding to the target illumination coordinates.

2. The method according to claim 1, characterized in that, The step of obtaining the pre-matched lighting control command based on the target illumination coordinates includes: Obtain the target prerequisite conditions for the target light triggering condition pre-matching, and the current vehicle condition parameters of the vehicle; If the current vehicle condition parameters are determined to meet the target prerequisites, a pre-matched lighting control command is obtained based on the target illumination coordinates.

3. The method according to claim 1, characterized in that, After controlling at least one lighting component of the vehicle based on the lighting control command, the method further includes: If the status update data corresponding to the status update data of the vehicle is detected and does not meet the target light triggering condition, the light scene turn-off command pre-matched by the light control command is obtained. The lighting scene shutdown command enables reset control of at least one of the lighting components; the reset control indicates that the relevant lighting component is returned to a preset initial position.

4. The method according to claim 1, characterized in that, After controlling at least one lighting component of the vehicle based on the lighting control command, the method further includes: If the status update data corresponding to the status update data of the vehicle is detected and the light scene shutdown condition pre-matched by the target light trigger condition is met, the light scene shutdown instruction pre-matched by the light control instruction is obtained. The lighting scene shutdown command enables reset control of at least one of the lighting components; the reset control indicates that the relevant lighting component is returned to a preset initial position.

5. The method according to claim 1, characterized in that, The method further includes: After receiving a light scene shutdown command, and detecting that the relevant light component pointed to by the light scene shutdown command changes from an on state to a off state, the light emission parameters of the relevant light component in the on state are obtained; the light emission parameters include one or more of brightness parameters, color parameters, light flow parameters, and light emission direction. Upon receiving a light control command that matches the light scene shutdown command again, the light output of the relevant light components is controlled based on the light control command and the light output parameters.

6. The method according to claim 1, characterized in that, The prerequisites for achieving this goal include having the vehicle's follow headlights enabled and the vehicle's light sensor module service subscribed. The method further includes: Obtain the target prerequisite conditions for the target light triggering condition pre-matching, and the current vehicle condition parameters of the vehicle; If the current vehicle condition parameters indicate that the vehicle is not in the follow headlight mode and / or is not in the vehicle light sensor module service subscription, the vehicle's status update data is reacquired until the status update data meets any of the target light triggering conditions.

7. The method according to claim 1, characterized in that, The method further includes: Obtain the target prerequisite conditions for the target light triggering condition pre-matching, and the current vehicle condition parameters of the vehicle; If it is determined that the current vehicle condition parameters do not meet the target scenario prerequisites in the target prerequisites, the vehicle's status update data is reacquired until the status update data meets any of the target light triggering conditions.

8. A vehicle lighting control system, characterized in that, This includes a cockpit domain controller, a vehicle integrated control unit, and multiple lighting controllers; The cockpit domain controller is communicatively connected to any one of the vehicle integrated controllers in the vehicle integrated control unit; the vehicle integrated controllers communicate in series, and each vehicle integrated controller is communicatively connected to at least one of the lighting controllers; The cockpit domain controller is configured to, upon detecting a change in vehicle status from a first state to a second state and the relevant status update data meeting the target lighting triggering conditions, determine the current lighting scenario of the vehicle based on the status update data; determine the target illumination coordinates for the vehicle interior based on the current lighting scenario; obtain a pre-matched lighting control command based on the target illumination coordinates; and send the lighting control command to the vehicle integrated control unit, which in turn sends the lighting control command to the relevant lighting controller, thereby controlling at least one lighting component in the vehicle pointed to by the lighting control command to illuminate the area corresponding to the target illumination coordinates.

9. A vehicle lighting control device, characterized in that, The device includes: The data acquisition module is used to determine the current lighting scenario of the vehicle based on the status update data when the vehicle is detected to have changed from a first state to a second state and the relevant status update data meets the target light triggering conditions. The coordinate determination module is used to determine the target illumination coordinates for the interior of the vehicle based on the current lighting scenario. The lighting control module is used to obtain a pre-matched lighting control command based on the target illumination coordinates, and control at least one lighting component of the vehicle based on the lighting control command to illuminate the area corresponding to the target illumination coordinates.

10. A vehicle-end control device, comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 7.

Images