Dot matrix tail light display data processing method and system based on mobile terminal

Abstract

The application provides a mobile terminal-based dot matrix tail light display data processing method and system, and relates to the technical field of automobile light control. The method comprises the following steps: receiving a tail light display configuration instruction transmitted by a mobile terminal, performing protocol analysis on the tail light display configuration instruction to extract a color parameter vector selected by a user and custom pattern bitmap data uploaded by the user; performing coordinate mapping based on the resolution of the custom pattern bitmap data and the physical pixel arrangement structure of a high-density LED dot matrix in the dot matrix tail light, to obtain mapped pixel coordinates; filling the color parameter vector into the mapped pixel coordinates, to obtain original dot matrix driving data containing information of each pixel point; and constructing a virtual elliptical boundary covering a light-emitting surface of the high-density LED dot matrix based on the physical pixel arrangement structure in the original dot matrix driving data. The application improves the display effect and compliance of intelligent tail lights.

Description

Technical Field

[0001] This invention relates to the field of automotive lighting control technology, and in particular to a data processing method and system for dot-matrix taillight displays based on a mobile terminal. Background Technology

[0002] In the field of intelligent connected vehicle lighting control technology, personalized display configuration of vehicle taillights based on mobile terminals has become a mainstream application scenario. Existing technologies typically send color parameters or custom pattern data to the vehicle controller via a mobile application. After parsing the instructions, the vehicle controller directly maps the data to the physical pixels of the high-density LED matrix for driving display.

[0003] In the process of mapping logical data to physical pixels, this type of technical solution simply corresponds coordinates based on resolution without fully considering the impact of the physical arrangement spacing of the high-density LED dot matrix and the light-guiding characteristics of the outer light-transmitting material on the light propagation path. This results in obvious brightness attenuation and uneven light intensity distribution at the gaps between physical pixels, creating a visual grainy appearance. Due to the lack of spatial sampling and pulse width modulation compensation mechanisms for the light intensity distribution of the emitting surface, it is difficult to meet the limits of overall brightness uniformity in motor vehicle lighting regulations while ensuring display effects, thus affecting the display quality and compliance of taillights. Summary of the Invention

[0004] This invention provides a method and system for processing dot-matrix taillight display data based on a mobile terminal, thereby improving the display effect and compliance of intelligent taillights.

[0005] To solve the above-mentioned technical problems, the technical solution of the present invention is as follows: Firstly, a data processing method for a dot-matrix taillight display based on a mobile terminal, the method comprising: Receive taillight display configuration instructions transmitted from the mobile terminal, and perform protocol parsing on the taillight display configuration instructions to extract the user-selected color parameter vector and the user-uploaded custom pattern bitmap data; Based on the resolution of the custom pattern bitmap data and the physical pixel arrangement structure of the high-density LED dot matrix in the dot matrix taillight, coordinate mapping is performed to obtain the mapped pixel coordinates; color parameter vectors are filled into the mapped pixel coordinates to obtain the original dot matrix driving data containing information of each pixel. Based on the physical pixel arrangement structure in the original dot matrix driving data, a virtual elliptical boundary covering the high-density LED dot matrix emitting surface is constructed; the angle parameters are iterated in the virtual elliptical boundary and the internal region through the elliptical parametric equation to obtain multiple discrete spatial sampling coordinates; the physical position of each discrete sampling coordinate point is mapped to the corresponding actual light intensity value, and the actual light intensity value is compared with the preset standard light intensity value to obtain the light intensity deviation vector. The pulse width modulation compensation coefficient matrix is ​​derived based on the light intensity deviation vector; the driving duty cycle of each pixel in the original dot matrix driving data is weighted and corrected by the pulse width modulation compensation coefficient matrix to obtain the corrected target dot matrix driving data. The corrected target dot matrix driving data is encapsulated into a control frame of the vehicle communication bus protocol and sent to the taillight controller through the vehicle communication gateway. The taillight controller then drives the high-density LED dot matrix to perform the corresponding color display.

[0006] Furthermore, the system receives taillight display configuration instructions transmitted from the mobile terminal, performs protocol parsing on the taillight display configuration instructions to extract the user-selected color parameter vector and the user-uploaded custom pattern bitmap data, including: The vehicle communication gateway receives the original communication data frames sent by the mobile terminal through its wireless communication interface, performs protocol header verification and frame decapsulation on the original communication data frames, and obtains the complete taillight display configuration instruction payload. Based on preset data field mapping rules, the color encoding field and image data field are separated from the complete taillight display configuration instruction payload. The color encoding field is decoded in color space to obtain the color parameter vector selected by the user; the image data field is compressed, decoded and reconstructed in pixel matrix to obtain the user-uploaded custom pattern bitmap data.

[0007] Furthermore, coordinate mapping is performed between the resolution of the custom pattern bitmap data and the physical pixel arrangement structure of the high-density LED dot matrix in the dot matrix taillight to obtain the mapped pixel coordinates; the color parameter vector is then filled into the mapped pixel coordinates to obtain the original dot matrix driving data containing information about each pixel, including: Parse custom pattern bitmap data to obtain image resolution parameters, and read the number of rows and columns in the physical pixel arrangement structure of the high-density LED dot matrix; The mapping ratio between logical pixel coordinates and physical pixel coordinates is calculated based on image resolution parameters and row and column number parameters to establish coordinate transformation relationships; By using coordinate transformation relationships, the logical pixel coordinates in the custom pattern bitmap data are mapped to the physical pixel coordinates in the high-density LED dot matrix, thus obtaining the mapped pixel coordinates. The color information in the color parameter vector is assigned to the driving channel corresponding to the mapped pixel coordinates to obtain the original dot matrix driving data containing information of each pixel.

[0008] Furthermore, based on the physical pixel arrangement structure in the original dot matrix driving data, a virtual elliptical boundary covering the high-density LED dot matrix emitting surface is constructed; multiple discrete spatial sampling coordinates are obtained by iterating the angle parameters in the virtual elliptical boundary and its internal region using the elliptical parametric equation, including: Analyze the physical pixel arrangement structure in the original dot matrix driving data and extract the set of edge pixel coordinates of the high-density LED dot matrix luminous surface; The geometric center point, major axis radius, and minor axis radius of the virtual elliptical boundary are determined by fitting the edge pixel coordinate set, and a virtual elliptical boundary covering the high-density LED dot matrix light-emitting surface is constructed. By using the geometric center point as a reference, iterating the angle parameters within a preset angle range according to a fixed angle step, and combining the major axis radius and minor axis radius, the discrete point coordinates of the virtual ellipse boundary and the internal region are obtained. The discrete point coordinates are mapped to discrete spatial sampling coordinates corresponding to the physical space of the high-density LED dot matrix.

[0009] Furthermore, the physical location of each discrete sampling coordinate point is mapped to the corresponding actual light intensity value. The actual light intensity value is then compared with a preset standard light intensity value to obtain a light intensity deviation vector, including: Each discrete spatial sampling coordinate is mapped to a physical pixel address index of a high-density LED dot matrix. Based on the physical pixel address index, a pre-stored light effect mapping relationship table is retrieved to obtain the actual light intensity value of each physical pixel unit under the preset light-transmitting material light guide path. The preset standard light intensity value corresponding to the physical pixel address index position is extracted by querying the pre-stored standard light intensity distribution curve through the physical pixel address index. A vector difference operation is performed between the actual light intensity value and the preset standard light intensity value to obtain the light intensity deviation vector that characterizes the difference in light intensity distribution.

[0010] Furthermore, a pulse width modulation (PWM) compensation coefficient matrix is ​​derived based on the light intensity deviation vector. The driving duty cycle of each pixel in the original dot matrix driving data is then weighted and corrected using this PWM compensation coefficient matrix to obtain the corrected target dot matrix driving data, including: The light intensity deviation vector is normalized and mapped to a preset duty cycle adjustment range to obtain the initial compensation coefficients corresponding to the physical pixel units of the high-density LED dot matrix. Based on the physical pixel arrangement structure of high-density LED dot matrix, the initial compensation coefficients are arranged in a matrix according to the physical pixel address index to construct the pulse width modulation compensation coefficient matrix. Extract the initial driving duty cycle of each pixel in the original dot matrix driving data, and perform a weighted multiplication operation on the initial driving duty cycle and the corresponding compensation coefficient in the pulse width modulation compensation coefficient matrix to obtain the corrected driving duty cycle. The corrected drive duty cycle is updated to the corresponding drive channel in the original dot matrix drive data to obtain the corrected target dot matrix drive data.

[0011] Furthermore, the corrected target dot matrix driving data is encapsulated into a control frame of the vehicle communication bus protocol and sent to the taillight controller via the vehicle communication gateway. The taillight controller then drives the high-density LED dot matrix to perform the corresponding color display, including: Based on the corrected target dot matrix driving data, the data frame is encapsulated according to the data frame structure of the vehicle communication bus protocol, and a frame identifier and cyclic redundancy check code are added to obtain the control frame of the vehicle communication bus protocol to be transmitted. The control frame of the vehicle communication bus protocol to be transmitted is sent to the taillight controller through the bus transmission interface of the vehicle communication gateway, and the control frame is stored in the data receiving buffer of the taillight controller. The taillight controller reads the control frame from the data receiving buffer and performs protocol parsing to restore the corrected target dot matrix driving data, thereby obtaining the pulse width modulation signal corresponding to the corrected driving duty cycle of each pixel, and driving the high-density LED dot matrix to perform the corresponding color display.

[0012] Secondly, the dot-matrix taillight display data processing system based on mobile terminals includes: The acquisition module is used to receive the taillight display configuration instruction transmitted by the mobile terminal, and to perform protocol parsing on the taillight display configuration instruction to extract the color parameter vector selected by the user and the custom pattern bitmap data uploaded by the user. The mapping module is used to perform coordinate mapping between the resolution of the custom pattern bitmap data and the physical pixel arrangement structure of the high-density LED dot matrix in the dot matrix taillight, so as to obtain the mapped pixel coordinates; the color parameter vector is filled into the mapped pixel coordinates to obtain the original dot matrix driving data containing the information of each pixel. The module is used to construct a virtual elliptical boundary covering the light-emitting surface of a high-density LED dot matrix based on the physical pixel arrangement structure in the original dot matrix driving data; iterates the angle parameters in the virtual elliptical boundary and the internal region through the elliptical parametric equation to obtain multiple discrete spatial sampling coordinates; maps the physical position of each discrete sampling coordinate point to the corresponding actual light intensity value, and compares the actual light intensity value with the preset standard light intensity value to obtain the light intensity deviation vector. The driving module is used to derive the pulse width modulation compensation coefficient matrix based on the light intensity deviation vector; and to perform weighted correction on the driving duty cycle of each pixel in the original dot matrix driving data through the pulse width modulation compensation coefficient matrix to obtain the corrected target dot matrix driving data. The processing module encapsulates the corrected target dot matrix driving data into a control frame of the vehicle communication bus protocol and sends it to the taillight controller through the vehicle communication gateway. The taillight controller then drives the high-density LED dot matrix to perform the corresponding color display.

[0013] Thirdly, a computing device, comprising: One or more processors; A storage device for storing one or more programs that, when executed by one or more processors, cause the one or more processors to implement the method.

[0014] Fourthly, a computer-readable storage medium storing a program that, when executed by a processor, implements the method.

[0015] The above-described solution of the present invention has at least the following beneficial effects: By employing technical methods such as receiving taillight display configuration commands transmitted from mobile terminals and performing protocol parsing, performing coordinate mapping based on custom pattern resolution and the physical pixel structure of LED dot matrix, constructing virtual elliptical boundaries for spatial light intensity sampling to obtain light intensity deviation vectors, deriving pulse width modulation compensation coefficient matrix to correct the driving duty cycle, and encapsulating control frames to send to the taillight controller, this technology overcomes the technical problems of traditional dot matrix taillights, which fail to consider the physical arrangement spacing of LED dot matrix and the light guiding characteristics of light-transmitting materials during data mapping, resulting in uneven light intensity distribution, obvious visual graininess, and difficulty in balancing display effects with the brightness requirements of vehicle lighting regulations. This achieves the technical effect of improving the brightness uniformity of the dot matrix taillight's luminous surface, eliminating visual graininess, meeting relevant vehicle lighting regulations, while retaining the user's ability to personalize color and pattern settings, thus enhancing the display quality and compliance of intelligent taillights. Attached Figure Description

[0016] Figure 1 This is a flowchart illustrating the data processing method for a dot-matrix taillight display based on a mobile terminal, provided by an embodiment of the present invention.

[0017] Figure 2 This is a schematic diagram of a dot-matrix taillight display data processing system based on a mobile terminal, provided by an embodiment of the present invention. Detailed Implementation

[0018] Exemplary embodiments of the present disclosure will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

[0019] like Figure 1 As shown, an embodiment of the present invention proposes a data processing method for a dot-matrix taillight display based on a mobile terminal, the method comprising the following steps: Step 1: Receive the taillight display configuration instruction transmitted by the mobile terminal, and perform protocol parsing on the taillight display configuration instruction to extract the user-selected color parameter vector and the user-uploaded custom pattern bitmap data; Step 2: Based on the resolution of the custom pattern bitmap data, coordinate mapping is performed between the resolution and the physical pixel arrangement structure of the high-density LED dot matrix in the dot matrix taillight to obtain the mapped pixel coordinates; the color parameter vector is filled into the mapped pixel coordinates to obtain the original dot matrix driving data containing information of each pixel. Step 3: Based on the physical pixel arrangement structure in the original dot matrix driving data, construct a virtual elliptical boundary covering the high-density LED dot matrix emitting surface; use the elliptical parameter equation to iterate the angle parameters in the virtual elliptical boundary and the internal region to obtain multiple discrete spatial sampling coordinates; map the physical position of each discrete sampling coordinate point to the corresponding actual light intensity value, and compare the actual light intensity value with the preset standard light intensity value to obtain the light intensity deviation vector. Step 4: Derive the pulse width modulation compensation coefficient matrix based on the light intensity deviation vector; use the pulse width modulation compensation coefficient matrix to perform weighted correction on the driving duty cycle of each pixel in the original dot matrix driving data to obtain the corrected target dot matrix driving data. Step 5: The corrected target dot matrix driving data is encapsulated into a control frame of the vehicle communication bus protocol and sent to the taillight controller through the vehicle communication gateway. The taillight controller then drives the high-density LED dot matrix to perform the corresponding color display.

[0020] In this embodiment of the invention, by employing the technical means of receiving taillight display configuration instructions transmitted from a mobile terminal and performing protocol parsing to extract color parameter vectors and custom pattern bitmap data, performing coordinate mapping based on pattern resolution and the physical pixel structure of high-density LED dot matrix to obtain original dot matrix driving data, constructing a virtual elliptical boundary covering the LED dot matrix emitting surface and obtaining discrete spatial sampling coordinates through elliptical parametric equations to obtain light intensity deviation vectors, deriving pulse width modulation compensation coefficient matrix based on light intensity deviation vectors and correcting driving duty cycle, and then encapsulating the corrected target driving data into an on-board communication bus control frame and sending it to the taillight controller, the invention overcomes the technical problems of traditional dot matrix taillight data mapping not fully considering the physical arrangement spacing of high-density LED dot matrix and the light guiding characteristics of the outer light-transmitting material, resulting in uneven light intensity distribution and visual graininess in the display screen, and difficulty in meeting the brightness requirements of motor vehicle lighting regulations while ensuring display effect. This achieves the technical effect of improving the brightness uniformity of the dot matrix taillight emitting surface, eliminating visual graininess, ensuring compliance with relevant vehicle lighting regulations, while retaining the user's personalized color and pattern setting function, and improving the display quality and compliance of intelligent dot matrix taillights.

[0021] In a preferred embodiment of the present invention, step 1 above may include: Step 1.1: Receive the original communication data frame sent by the mobile terminal through the wireless communication interface of the vehicle communication gateway. Perform protocol header verification and frame decapsulation processing on the original communication data frame to obtain the complete taillight display configuration instruction payload. Specifically, the Bluetooth or Wi-Fi wireless communication interface integrated inside the vehicle communication gateway is continuously in a data receiving and listening state. When the mobile terminal sends the original communication data frame related to taillight display configuration through the wireless communication link, the wireless communication interface will completely receive the original communication data frame and temporarily store it in the dedicated receiving data buffer area of ​​the vehicle communication gateway. Perform protocol header verification on the temporarily stored original communication data frame, extract the protocol header data at the front end of the original communication data frame, and verify whether the frame synchronization identifier in the protocol header completely matches the preset synchronization identifier of the vehicle wireless communication, and whether the theoretical total number of data bytes marked by the frame length identifier is equal to the actual number of data bytes received. At the same time, perform a successive summation operation on all byte values ​​in the protocol header except for the verification field, and compare the sum obtained by the summation with the verification value in the frame verification field. When the summation result is completely consistent with the verification value, the protocol header verification is deemed qualified.

[0022] After the protocol header verification passes, frame decapsulation processing is performed according to the preset vehicle wireless communication frame structure. This preset vehicle wireless communication frame structure is a standardized data encapsulation format predefined by the system and adapted to vehicle Bluetooth or Wi-Fi wireless transmission scenarios. It is specifically used for transmitting taillight display configuration instructions between mobile terminals and vehicle communication gateways. Its structure consists of five fixed parts from front to back: frame start symbol, protocol header, valid data payload, link layer padding redundant bytes, and frame end symbol. The number of bytes occupied by each part is pre-fixed in the system and will not change arbitrarily during transmission, ensuring that the sender and receiver have a completely consistent understanding of the data format. When performing frame decapsulation, the total number of bytes occupied by the frame start symbol, protocol header, frame end symbol, and link layer padding redundant bytes is subtracted from the total number of bytes in the original communication data frame. The effective byte length of the taillight display configuration instruction payload is determined by this subtraction operation. Based on the calculated effective length, all outer encapsulation and redundant data are stripped from the original communication data frame, and finally, a complete, uninterrupted, and interference-free taillight display configuration instruction payload is extracted.

[0023] Step 1.2: Based on preset data field mapping rules, the color encoding field and image data field are separated from the complete taillight display configuration instruction payload. The color encoding field is decoded in color space to obtain the user-selected color parameter vector; the image data field is compressed, decoded, and reconstructed using a pixel matrix to obtain the user-uploaded custom pattern bitmap data. Specifically, this includes: calling the pre-fixed data field mapping rules in the vehicle communication gateway storage unit, which clearly indicates the starting offset byte number and fixed occupied byte number of the color encoding field in the taillight display configuration instruction payload; and using the starting offset byte number of the taillight display configuration instruction payload to obtain the user-uploaded custom pattern bitmap data. Based on bytes, the starting byte position is added to the starting offset byte number of the color-coded field to determine the starting position of the color-coded field. This starting position is then added to a fixed number of bytes in the color-coded field to determine the ending position, thus completing the precise segmentation of the color-coded field. After the color-coded field segmentation is completed, the total number of bytes of the configuration instruction payload is subtracted from the number of bytes occupied by the color-coded field. This subtraction operation yields the byte length of the image data field. Based on this length, the complete image data field is separated from the remaining instruction payload data, achieving non-overlapping and non-missing separation of the two data fields.

[0024] The separated color encoding fields are processed according to the preset color space decoding logic. The preset color space is a dedicated color standard system that is pre-calibrated and stored. This color space comprehensively matches the differences in hardware luminous efficiency of the high-density LED dot matrix in vehicles, the attenuation and chromaticity shift characteristics of different colors of light by the outer light-transmitting material of the taillight, and simultaneously meets the mandatory requirements of the ECE R48 automotive lighting regulations for taillight chromaticity coordinates and luminous brightness. Unlike the general display color space of mobile terminals, it has pre-configured fixed color conversion coefficients corresponding to the red, green, and blue channels. The red, green, and blue channel encoding values ​​in the color encoding field are multiplied by the preset conversion coefficients of the corresponding color channels in the preset color space. Then, the three channels are processed... The results of the multiplication operation are linearly superimposed to complete the conversion from the general color encoding of the mobile terminal to the standard color values ​​adapted to the light emission characteristics of the taillight hardware. Finally, a color parameter vector adapted to the high-density LED dot matrix driver is obtained. For the separated image data fields, a preset lossless decoding algorithm is used to restore and decode the compressed image data. After decoding, the horizontal and vertical pixel count parameters built into the image data are extracted. The horizontal and vertical pixel counts are multiplied to obtain the total number of pixels of the custom pattern. According to the arrangement order from top to bottom and from left to right, the decoded single pixel data is sequentially filled into the corresponding arrangement positions according to the total number of pixels to complete the pixel matrix reconstruction of the custom pattern. Finally, the user-uploaded custom pattern bitmap data with complete pixels and a standard arrangement is obtained.

[0025] In this embodiment of the invention, by performing frame synchronization verification, length verification, and cumulative verification on the original communication data frames, and combining byte length subtraction operation to complete frame decapsulation, problems such as garbled characters, packet loss, and redundant data generated during wireless transmission can be completely eliminated. This ensures the integrity and transmission accuracy of the taillight display configuration instruction payload, and avoids subsequent light control failures due to abnormal transmission data. By accurately separating the color encoding field and image data field through byte offset addition and length subtraction operations, color decoding is completed in conjunction with channel coefficient multiplication and linear superposition operations, and pattern pixel matrix reconstruction is completed through pixel number multiplication operations. This fully restores the color parameters and custom patterns set by the user on the mobile terminal, eliminates color distortion and pattern incompleteness caused by data parsing deviations, and provides standard and reliable raw data for coordinate mapping, light intensity deviation calculation, and drive data correction. At the same time, it improves the stability of personalized configuration data interaction between the mobile terminal and the vehicle taillight, and lays a data foundation for improving the uneven distribution of dot matrix taillight light intensity and eliminating visual graininess.

[0026] In a preferred embodiment of the present invention, step 2 above may include: Step 2.1 involves parsing the custom pattern bitmap data to obtain image resolution parameters and reading the row and column quantity parameters in the physical pixel arrangement structure of the high-density LED dot matrix. Specifically, this includes performing a comprehensive data parsing operation on the custom pattern bitmap data that has been reconstructed from the pixel matrix. This parsing process proceeds step by step according to the standard data structure of the bitmap file, locating the header information area of ​​the bitmap data. This area is located at the beginning of the bitmap data and contains core parameters such as file identifier, size information, and pixel format. By reading a specified byte segment of the header information area byte by byte, two key parameters representing the size of the custom pattern, namely the number of horizontal pixels and the number of vertical pixels, are accurately extracted. After extraction, the validity of these two parameters is verified. The extracted values ​​are compared with the preset pattern size range. After confirming that the values ​​are within a reasonable range and without abnormal deviations, the number of horizontal pixels and the number of vertical pixels are determined as the image resolution parameters to ensure that the basic data for coordinate mapping is accurate.

[0027] A communication connection is established with the taillight controller via the vehicle communication bus. A parameter reading command is sent to the taillight controller. After the command is parsed by the taillight controller, it triggers a reading operation in its built-in storage unit. The built-in storage unit has all the specifications of the high-density LED dot matrix hardware pre-installed. The physical horizontal and vertical pixel counts of the high-density LED dot matrix are accurately read from it. These two values ​​together constitute the row and column count parameters of the dot matrix physical pixel arrangement structure. After reading, the read physical horizontal and vertical pixel counts are compared and verified with the preset standard specifications of the taillight hardware. If there is a discrepancy, the reading command is resent until the row and column count parameters that perfectly match the actual hardware pixel specifications of the taillight are obtained. This provides accurate hardware parameter support for the calculation of the coordinate mapping ratio and avoids mapping misalignment due to hardware parameter deviations.

[0028] Step 2.2: Calculate the mapping ratio between logical pixel coordinates and physical pixel coordinates based on image resolution and row / column number parameters to establish a coordinate transformation relationship. Specifically, this includes loading four valid parameters—the number of horizontal pixels in the custom pattern, the number of vertical pixels in the custom pattern, the number of physical horizontal pixels in the high-density LED dot matrix, and the number of physical vertical pixels in the high-density LED dot matrix—into the dedicated arithmetic register of the vehicle controller. Simultaneously, verify the validity of these four parameters, confirming that all parameters are positive integers greater than zero, excluding missing parameters, zero values, or abnormal values. After the parameter verification is passed, accurately calculate the horizontal and vertical coordinate mapping ratios. The horizontal coordinate mapping ratio is used to represent... The scaling correspondence between the horizontal logical pixels of the custom pattern and the horizontal physical pixels of the taillight dot matrix is ​​calculated as follows: the number of horizontal pixels of the custom pattern is used as the dividend, and the number of physical horizontal pixels of the high-density LED dot matrix is ​​used as the divisor. A division operation is performed on the two, and the quotient is the horizontal coordinate mapping ratio. This ratio directly reflects how many horizontal logical pixels a single physical horizontal pixel needs to correspond to. The calculation logic of the vertical coordinate mapping ratio is exactly the same as that of the horizontal coordinate mapping ratio. The number of vertical pixels of the custom pattern is used as the dividend, and the number of physical vertical pixels of the high-density LED dot matrix is ​​used as the divisor. The quotient is the vertical coordinate mapping ratio. This ratio is used to determine how many vertical logical pixels a single physical vertical pixel needs to correspond to.

[0029] After calculating the two sets of mapping ratios, the ratio values ​​are checked again for rationality to ensure that both the horizontal and vertical coordinate mapping ratios are real numbers greater than zero, avoiding the problem of invalid ratios causing coordinate mapping failure. After passing the check, the horizontal and vertical coordinate mapping ratios are synchronously stored in the temporary calculation cache area of ​​the vehicle controller. The coordinate origins of logical pixels and physical pixels are uniformly defined. The upper left corner vertex of the custom pattern and the upper left corner vertex of the high-density LED dot matrix light-emitting surface are set as the common coordinate origin. Based on this, the core conversion rule for coordinate transformation is determined: the horizontal coordinate value of any logical pixel is divided by the horizontal coordinate mapping ratio to obtain the corresponding dot matrix physical horizontal coordinate value. The vertical coordinate value of any logical pixel is divided by the vertical coordinate mapping ratio to obtain the corresponding physical vertical coordinate value of the dot matrix. By fixing the coordinate origin, clarifying the bidirectional conversion formula, and combining two sets of precisely calculated mapping ratios, a complete and unique coordinate transformation relationship that is fully adapted to the physical pixel arrangement structure of the high-density LED dot matrix is ​​established. This transformation relationship can ensure that the custom pattern is fully adapted to the physical display area of ​​the dot matrix according to the original length and width ratio, without the problem of proportional distortion due to horizontal stretching or vertical compression of the pattern, and without the pattern exceeding the dot matrix light emission range or being incompletely displayed. At the same time, it provides a standardized coordinate reference basis for constructing virtual elliptical boundaries based on the physical pixel arrangement structure and carrying out light intensity sampling.

[0030] Step 2.3: Map the logical pixel coordinates in the custom pattern bitmap data to the physical pixel coordinates in the high-density LED dot matrix using coordinate transformation relationships to obtain the mapped pixel coordinates. Specifically, this involves traversing each logical pixel coordinate in the custom pattern bitmap data one by one, from top to bottom and from left to right. During the traversal, horizontal and vertical coordinate transformation operations are performed on each logical pixel coordinate. For the horizontal coordinate of a logical pixel, the coordinate value is divided by the horizontal mapping ratio calculated in Step 2.2. After performing the division operation, the calculation result is rounded to the nearest integer to obtain the physical horizontal coordinate of the logical pixel on the high-density LED dot matrix. For the vertical coordinate of a logical pixel, the same processing method is used: the coordinate value is divided by the vertical mapping ratio, and the calculation result is rounded to the nearest integer to obtain the corresponding physical vertical coordinate. After each logical pixel coordinate transformation is completed, the transformed physical horizontal and vertical coordinates are associated and stored until all logical pixel coordinate transformations are completed. Finally, a set of mapped pixel coordinates with no deviation, no misalignment, and no omissions is obtained, ensuring that each logical pixel can accurately correspond to the physical pixel position of the LED dot matrix.

[0031] Step 2.4 assigns the color information in the color parameter vector to the driving channel corresponding to the mapped pixel coordinates to obtain the original dot matrix driving data containing information of each pixel. Specifically, this includes: sorting and organizing the mapped pixel coordinate set; sorting all mapped pixel coordinates one by one according to the physical pixel arrangement order of the high-density LED dot matrix from top to bottom and from left to right; and establishing the correspondence between pixel coordinates and hardware driving channels. Each physical pixel of the high-density LED dot matrix corresponds to an independent hardware driving channel. The encoding of the driving channel and the coordinates of the physical pixels are fixedly mapped using a linear coordinate encoding algorithm. This algorithm is a standardized mapping rule pre-embedded in the taillight controller, used to convert the physical pixel coordinates of the two-dimensional plane into a one-dimensional linear hardware driving channel code. The specific calculation rule is: driving channel code = physical vertical coordinate multiplied by the total number of physical horizontal pixels of the high-density LED dot matrix plus the physical horizontal coordinate.

[0032] The system performs calculations based on the encoding algorithm. It multiplies the physical vertical coordinate of each mapped pixel coordinate with the total physical horizontal pixel count of the dot matrix, then adds the product to the pixel's physical horizontal coordinate. This process calculates a unique hardware driver channel code, ensuring that each mapped pixel coordinate is matched with a unique hardware driver channel, guaranteeing no mismatches or duplicates. After matching, it calls the color parameter vector generated earlier using a preset color space. This vector contains three core parameters: red, green, and blue driver values. Following a corresponding principle, the system assigns these three color driver values ​​to the corresponding hardware driver channel for each mapped pixel coordinate. During the assignment process, the results are verified in real-time to ensure that each driver channel accurately receives the corresponding value. The color-driven values ​​are complete and error-free, ensuring that each physical pixel is precisely bound to the user-defined color display parameters. Once the driving channels corresponding to all mapped pixel coordinates have completed color assignment, the system begins to integrate the relevant information of all physical pixels. The integrated content includes the physical horizontal coordinates, physical vertical coordinates, corresponding driving channel codes, and bound red, green, and blue driving values ​​for each physical pixel. The information is arranged in an orderly manner according to a preset data format to form a unified dataset. At the same time, the dataset is checked for completeness to confirm that all physical pixel information is included, without omissions or errors. After confirming that the dataset contains the complete driving parameters of each pixel, it is identified as the original dot matrix driving data and stored in the driving data cache of the taillight controller, providing standard and reliable basic data support for light intensity deviation detection and driving duty cycle correction.

[0033] In this embodiment of the invention, by accurately parsing the header information of the custom pattern bitmap data and validating the extracted resolution parameters, the physical row and column parameters of the high-density LED dot matrix are read and verified. This ensures the accuracy of the basic data required for coordinate mapping and avoids problems such as deviations in subsequent mapping ratio calculations and misalignment of pattern display due to parameter errors. By accurately calculating the horizontal and vertical mapping ratios and establishing a unique coordinate transformation relationship, a deviation-free mapping from logical pixels to physical pixels is achieved. This ensures that the display ratio of the custom pattern on the LED dot matrix is ​​consistent with the user design, without compression or incomplete display. The pixel coordinates are matched with the data using an encoding algorithm. The hardware driver channel, combined with precise color parameter assignment and data integration, ensures that each physical pixel can be accurately bound to the user-defined color parameters. The generated raw dot matrix driver data is complete and standardized, providing reliable pre-data support for light intensity deviation detection, pulse width modulation compensation coefficient matrix derivation, and driver data correction. It effectively solves the problems of chaotic taillight display colors and misaligned patterns caused by coordinate mapping chaos and color assignment deviation in traditional technologies. At the same time, it lays a solid data foundation for improving the uneven distribution of taillight intensity and eliminating visual graininess, further improving the display accuracy and personalized configuration effect of dot matrix taillights, and taking into account both display effect and hardware compatibility.

[0034] In a preferred embodiment of the present invention, step 3 above may include: Step 3.1 involves parsing the physical pixel arrangement structure in the original dot matrix driving data and extracting the set of edge pixel coordinates for the high-density LED dot matrix emitting surface. Specifically, this includes: traversing all valid physical pixel coordinates sequentially from top to bottom and left to right, filtering out the extreme values ​​of the horizontal and vertical coordinates, traversing the physical horizontal coordinates of all physical pixels, and recording the smallest physical horizontal coordinate (the horizontal coordinate of the leftmost pixel on the emitting surface) and the largest physical horizontal coordinate (the horizontal coordinate of the rightmost pixel on the emitting surface). Then, traversing the physical vertical coordinates of all physical pixels, and recording the smallest physical vertical coordinate (the vertical coordinate of the topmost pixel on the emitting surface) and the largest physical vertical coordinate (the vertical coordinate of the bottommost pixel on the emitting surface). All physical pixels that satisfy any one of the following four conditions are selected: physical horizontal coordinate equal to the minimum horizontal coordinate, physical horizontal coordinate equal to the maximum horizontal coordinate, physical vertical coordinate equal to the minimum vertical coordinate, and physical vertical coordinate equal to the maximum vertical coordinate. The coordinates of all physical pixels are collected to form an initial set of edge pixel coordinates. After collection, the set is deduplicated to remove duplicate coordinate data. At the same time, the continuity of edge pixels is checked to ensure that the leftmost, rightmost, topmost, and bottommost edge pixels can continuously cover the edge of the entire light-emitting surface without breaks or missing points. Finally, a complete and continuous set of edge pixel coordinates of the high-density LED dot matrix light-emitting surface is determined, providing an accurate boundary reference for fitting the virtual ellipse boundary.

[0035] Step 3.2: Based on the edge pixel coordinate set fitting, determine the geometric center point, major axis radius, and minor axis radius of the virtual elliptical boundary, constructing a virtual elliptical boundary covering the high-density LED dot matrix emitting surface. Specifically, this includes: after obtaining the edge pixel coordinate set, starting the virtual elliptical boundary fitting process; calculating and determining the geometric center point, major axis radius, and minor axis radius of the virtual elliptical boundary using the edge pixel coordinates; and defining the calculation parameters: Let the edge pixel coordinate set contain... The set of coordinates of the nth pixel, where the nth pixel is the nth pixel. The physical horizontal coordinates of each edge pixel are The physical vertical coordinate is The lateral coordinates of the geometric center point of the ellipse are: The vertical axis is The maximum physical horizontal coordinate of the edge pixels is The minimum physical horizontal coordinate is The maximum physical vertical coordinate is The minimum physical vertical coordinate is The radius of the major axis of the virtual ellipse is The minor axis radius is .

[0036] The geometric center point is calculated using the arithmetic mean method, with the following formula: In the formula: It is the sum of all physical horizontal coordinates in the set of edge pixel coordinates. The total number of edge pixels is calculated. Here are the horizontal coordinates of the geometric center point of the virtual ellipse boundary. The formula for calculating the vertical coordinates of the geometric center point is: In the formula: It is the sum of all physical vertical coordinates in the set of edge pixel coordinates. The total number of edge pixels is calculated. The vertical coordinates of the geometric center point of the virtual ellipse boundary are given. and Combined, determine the coordinates of the geometric center point of the virtual ellipse boundary. Calculate the major axis radius and minor axis radius. The major axis radius represents the lateral extension dimension of the ellipse, and the calculation formula is: In the formula: The actual lateral width of the high-density LED dot matrix emitting surface is given by dividing the lateral width by 2. The resulting value is the major axis radius *a* of the virtual ellipse boundary. The minor axis radius characterizes the longitudinal extension dimension of the ellipse, and its calculation formula is: In the formula: The actual vertical height of the high-density LED dot matrix emitting surface is given by dividing the vertical height by 2. The resulting value is the minor axis radius of the virtual ellipse boundary. After the parameters are calculated, the system is based on the geometric center point. Major axis radius 'a', minor axis radius Following the standard geometric structure of an ellipse, a virtual elliptical boundary is constructed that covers the entire high-density LED dot matrix light-emitting surface. This ensures that the elliptical boundary encloses all edge pixels, and that the edge of the ellipse basically matches the edge contour of the light-emitting surface, without any cases of exceeding the range of the light-emitting surface or failing to completely cover the light-emitting surface. After the construction is completed, the system verifies the virtual elliptical boundary by substituting the coordinates of the edge pixels into the elliptical parametric equation to confirm that all edge pixels are within the elliptical boundary and its internal region. After the verification is passed, the virtual elliptical boundary is determined as the reference boundary for spatial sampling.

[0037] Step 3.3 involves iterating the angle parameters within a preset angle range using the geometric center point as a reference, and combining the major axis radius and minor axis radius to obtain the discrete point coordinates of the virtual ellipse boundary and its internal region. Specifically, this includes determining the geometric center point, major axis radius, and minor axis radius of the virtual ellipse boundary, and then iterating the angle parameters to obtain the discrete point coordinates of the virtual ellipse boundary and its internal region. First, a preset angle range and a fixed angle step size are established. The preset angle range is set to 0 degrees to 360 degrees to ensure that the entire circumference of the virtual ellipse is covered. The fixed angle step size is set to 1 degree. The value of the angle step size is pre-fixed in the system and does not require real-time adjustment. The iteration process uses the geometric center point of the virtual ellipse boundary as the reference, starting from 0 degrees and increasing the angle parameter successively according to the fixed angle step size until it reaches 360 degrees, completing one complete angle iteration. For each iteration angle parameter, the coordinates of the corresponding ellipse boundary point are calculated using the ellipse parametric equation. The specific calculation process is as follows: the horizontal coordinate of the ellipse boundary point = the horizontal coordinate of the geometric center point plus the radius of the major axis multiplied by the cosine value of the angle parameter; the vertical coordinate of the ellipse boundary point = the vertical coordinate of the geometric center point plus the radius of the minor axis multiplied by the sine value of the angle parameter. Through this calculation method, the coordinates of the virtual ellipse boundary point corresponding to each angle are obtained.

[0038] While acquiring the boundary point coordinates, the discrete point coordinates of the internal region of the ellipse are simultaneously acquired. Specifically, for each iteration angle, starting from 0, the sampling radius is increased step by step according to a fixed radius until the sampling radius equals the radius of the ellipse boundary corresponding to that angle. For each sampling radius, the corresponding point coordinates are calculated according to the above ellipse parametric equation, i.e., the horizontal coordinate of the internal discrete point = the horizontal coordinate of the geometric center point plus the sampling radius multiplied by the cosine value corresponding to the angle parameter, and the vertical coordinate of the internal discrete point = the vertical coordinate of the geometric center point plus the sampling radius multiplied by the sine value corresponding to the angle parameter. After completing the iteration and internal sampling of one angle, the system associates and stores the boundary point coordinates and internal discrete point coordinates corresponding to that angle until the iteration sampling of all angles from 0 degrees to 360 degrees is completed. Finally, all discrete point coordinates of the virtual ellipse boundary and internal region are collected, resulting in a complete set of discrete point coordinates. This ensures that the sampling points uniformly cover the entire high-density LED dot matrix light-emitting surface, providing comprehensive point support for light intensity sampling.

[0039] Step 3.4 maps the discrete point coordinates to discrete spatial sampling coordinates corresponding to the physical space of the high-density LED dot matrix. Specifically, after obtaining the set of discrete point coordinates, the theoretical discrete point coordinates are mapped to discrete spatial sampling coordinates corresponding to the physical space of the high-density LED dot matrix. This ensures that the sampling coordinates accurately correspond to the actual physical pixels of the dot matrix, facilitating the acquisition of actual light intensity values. The specific mapping process is as follows: Each discrete point coordinate in the set of discrete point coordinates is traversed sequentially, and the horizontal and vertical coordinates of that point are processed respectively. First, it is determined whether the horizontal coordinate of the discrete point is within the range of the physical horizontal coordinates of the high-density LED dot matrix, and whether the vertical coordinate is within the range of the physical vertical coordinates. Discrete point coordinates outside the range are directly discarded to avoid invalid sampling. For discrete point coordinates within the range, the system performs rounding on both the horizontal and vertical coordinates. The rounded horizontal coordinate is used as the physical horizontal sampling coordinate corresponding to the discrete point, and the rounded vertical coordinate is used as the corresponding physical vertical sampling coordinate. The two are combined to form the discrete spatial sampling coordinates corresponding to the discrete point. For example, if the horizontal coordinate of a discrete point is 10.3 and the vertical coordinate is 25.6, after rounding, the corresponding physical horizontal sampling coordinate is 10 and the physical vertical sampling coordinate is 26, which are the discrete spatial sampling coordinates after the point is mapped.

[0040] After each discrete point is mapped, the mapped discrete spatial sampling coordinates are stored. At the same time, it is verified whether the sampling coordinates correspond to a valid physical pixel in the high-density LED dot matrix. If not, the discrete point coordinates are readjusted until they are mapped to a valid physical pixel coordinate. After all discrete point coordinates have been mapped and verified, a complete set of discrete spatial sampling coordinates is formed. Each sampling coordinate in this set corresponds precisely to a physical pixel in the high-density LED dot matrix, providing accurate physical coordinate support for obtaining the actual light intensity value of each sampling point and calculating the light intensity deviation vector.

[0041] In this embodiment of the invention, by parsing the original dot matrix driving data, accurately extracting the edge pixel coordinates, and verifying continuity, the accuracy of the basic data for fitting the virtual ellipse boundary is ensured, avoiding the incomplete coverage of the luminous surface by the ellipse boundary due to missing edge pixels or breakpoints. By scientifically calculating the geometric center point, major axis radius, and minor axis radius, a virtual ellipse boundary that fits the contour of the luminous surface is fitted, providing a reasonable reference range for spatial light intensity sampling. This solves the problems of inaccurate light intensity sampling range and incomplete coverage in traditional technologies. Through iterative sampling with fixed angle step size and radius step size, uniform sampling of the virtual ellipse boundary and its internal region is achieved, ensuring the accuracy of the sampling data. The sampling points can fully cover the entire high-density LED dot matrix light-emitting surface, avoiding blind spots in light intensity sampling. By mapping the coordinates of discrete points to physical space sampling coordinates, the precise correspondence between sampling points and actual physical pixels is achieved. This provides a reliable coordinate reference for obtaining actual light intensity values ​​and calculating light intensity deviation vectors, solving the problems of light intensity sampling being disconnected from physical pixels and inaccurate light intensity deviation calculations in traditional technologies. It lays a solid foundation for the derivation of the pulse width modulation compensation coefficient matrix and the correction of driving data, providing precise light intensity sampling support for improving uneven taillight intensity distribution and eliminating visual graininess, while balancing sampling accuracy and computational efficiency.

[0042] In a preferred embodiment of the present invention, step 3 above may include: Step 3.5: Map each discrete spatial sampling coordinate to a physical pixel address index of the high-density LED dot matrix. Based on the physical pixel address index, retrieve the pre-stored light effect mapping table to obtain the actual light intensity value of each physical pixel unit under the preset light-guiding path of the light-transmitting material. Specifically, this includes: calling the obtained physical horizontal total pixel count parameter of the high-density LED dot matrix, and combining it with each discrete spatial sampling coordinate to calculate the physical pixel address index corresponding to each discrete spatial sampling coordinate. The calculation of the physical pixel address index adopts a linear encoding algorithm. The specific calculation process is: physical pixel address index = physical vertical sampling coordinate multiplied by the physical horizontal total pixel count of the high-density LED dot matrix plus the physical horizontal sampling coordinate. Through this calculation method, the two-dimensional discrete spatial sampling coordinates are converted into a one-dimensional physical pixel address index, ensuring that each discrete spatial sampling coordinate can correspond to a unique physical pixel address index, without duplication or mismatch.

[0043] After the calculation is completed, the validity of each physical pixel address index is checked to confirm that the address index is within the valid address range of the high-density LED dot matrix. For address indexes that are out of range, the corresponding discrete spatial sampling coordinates are directly removed to avoid invalid light intensity retrieval. After successful verification, the system retrieves the pre-stored light effect mapping table in the taillight controller's built-in storage unit using the physical pixel address index. This table was calibrated and solidified through extensive real-vehicle light effect tests before the system leaves the factory. The table clearly records the actual light intensity value of each physical pixel address index and the corresponding physical pixel unit under the preset light-transmitting material light guide path. The preset light-transmitting material light guide path is a standard light propagation path preset by combining the light scattering and light attenuation characteristics of the outer PMMA diffusion film and the light guide layer, ensuring that the actual light intensity value in the table is consistent with the actual light emission effect of the physical pixel. The corresponding entry in the light effect mapping table is accurately located using the physical pixel address index, and the actual light intensity value of each physical pixel unit is extracted one by one. After extraction, the actual light intensity value is associated and stored with the corresponding physical pixel address index and discrete spatial sampling coordinates to form an actual light intensity value set, ensuring that each valid sampling point has corresponding actual light intensity data support.

[0044] Step 3.6: Query the pre-stored standard light intensity distribution curve using the physical pixel address index, and extract the preset standard light intensity value corresponding to the physical pixel address index position. Specifically, this includes: while obtaining the actual light intensity value of each physical pixel unit, simultaneously querying the pre-stored standard light intensity distribution curve in the taillight controller's built-in storage unit using the physical pixel address index. This standard light intensity distribution curve is pre-calibrated based on the ECE R48 automotive lighting regulations and the ideal light-emitting characteristics of the high-density LED matrix. The horizontal axis of the curve represents the physical pixel address index, and the vertical axis represents the preset standard light intensity value of the physical pixel unit at the corresponding address index. The curve trend closely matches the ideal light intensity distribution of the high-density LED matrix's light-emitting surface, ensuring that the preset standard light intensity values ​​of all physical pixels meet the regulatory limits for taillight brightness uniformity. During the query process, each verified physical pixel address index is mapped to the horizontal axis of the standard light intensity distribution curve. Through curve interpolation, the preset standard light intensity value corresponding to that address index is accurately extracted. The specific interpolation process is as follows: if the physical pixel address index exactly corresponds to a standard coordinate point on the horizontal axis of the curve, the vertical axis value corresponding to that coordinate point is directly extracted as the preset standard light intensity value; if the physical pixel address index is located between two standard coordinate points, the difference between the standard light intensity values ​​corresponding to the two standard coordinate points is calculated. This difference is multiplied by the distance ratio between the address index and the left standard coordinate point, and then added to the standard light intensity value of the left standard coordinate point to obtain the preset standard light intensity value corresponding to that address index. This ensures that the extracted standard light intensity value accurately matches the curve trend without deviation.

[0045] After extraction, the preset standard light intensity value is associated with and stored with the corresponding physical pixel address index and the actual light intensity value to form a set of standard light intensity values. At the same time, the extracted preset standard light intensity values ​​are verified for compliance to confirm that the values ​​are within the brightness range specified by the ECE R48 standard. If any abnormal values ​​are found, the system will query and extract again to ensure the compliance and accuracy of the preset standard light intensity values ​​and provide reliable benchmark data for light intensity deviation calculation.

[0046] Step 3.7: Perform vector difference operation on the actual light intensity value and the preset standard light intensity value to obtain the light intensity deviation vector representing the difference in light intensity distribution. Specifically, after extracting and storing the actual light intensity value and the preset standard light intensity value, start the calculation process of the light intensity deviation vector. The core is to perform vector difference operation on the actual light intensity value and the preset standard light intensity value of each physical pixel unit, and finally form the light intensity deviation vector representing the difference in light intensity distribution of the entire high-density LED dot matrix. Sort and organize the set of actual light intensity values ​​and the set of standard light intensity values ​​to ensure that the values ​​in both sets are arranged in ascending order of physical pixel address index. To ensure that the actual light intensity value of each physical pixel unit corresponds to the preset standard light intensity value and avoid numerical misalignment during calculation, after sorting, a difference operation is performed on the light intensity value of each physical pixel unit one by one. The specific calculation process is as follows: the light intensity deviation value of a single physical pixel is equal to the actual light intensity value of that pixel and the preset standard light intensity value of that pixel. Through this subtraction operation, the light intensity deviation value of each physical pixel unit is obtained. If the deviation value is positive, it means that the actual light intensity of the pixel is higher than the standard light intensity; if the deviation value is negative, it means that the actual light intensity of the pixel is lower than the standard light intensity; if the deviation value is 0, it means that the actual light intensity of the pixel is the same as the standard light intensity.

[0047] After calculating the deviation value for each physical pixel, the deviation value is associated with and stored with the corresponding physical pixel address index. This process continues until the deviation values ​​for all valid physical pixels are calculated. All light intensity deviation values ​​are then arranged in ascending order of their physical pixel address indices to form a one-dimensional vector. This vector represents the light intensity deviation vector, which characterizes the differences in light intensity distribution across the high-density LED dot matrix. After calculation, the light intensity deviation vector is validated, and abnormal data with deviation values ​​exceeding a preset reasonable range are removed. For the physical pixels corresponding to the abnormal data, the calculation is re-executed to ensure that the light intensity deviation vector can truly and accurately reflect the uneven light intensity distribution across the entire high-density LED dot matrix, providing precise deviation data support for deriving the pulse width modulation compensation coefficient matrix and correcting the driving duty cycle.

[0048] In this embodiment of the invention, discrete spatial sampling coordinates are converted into physical pixel address indices using a linear encoding algorithm. Combined with a pre-stored light effect mapping table, the actual light intensity value of each physical pixel under the preset light-transmitting material light guide path is accurately obtained. This solves the problems of light intensity sampling being disconnected from physical pixels and inaccurate actual light intensity acquisition in traditional technologies. It ensures that light intensity sampling can match the actual characteristics of the taillight hardware and the light-transmitting material. The preset standard light intensity value is extracted through a standard light intensity distribution curve and interpolation calculation. This ensures that the standard light intensity meets the requirements of ECE R48 regulations and that the standard light intensity corresponds accurately to the physical pixel address index, providing a reliable benchmark for light intensity deviation calculation. The light intensity deviation vector is obtained through vector difference operation, which can accurately characterize the light intensity deviation of each physical pixel and clearly reflect the problem of uneven light intensity distribution across the entire emitting surface. This provides accurate and comprehensive deviation data for the derivation of the pulse width modulation compensation coefficient matrix, effectively solving the problems of ambiguous light intensity deviation judgment and weak compensation targeting in traditional technologies. This provides core data support for subsequent correction of driving data, improvement of uneven light intensity distribution, and elimination of visual graininess, further improving the display quality and compliance of the dot matrix taillight.

[0049] In a preferred embodiment of the present invention, step 4 above may include: Step 4.1: Normalize the light intensity deviation vector and map it to a preset duty cycle adjustment range to obtain the initial compensation coefficients corresponding to the physical pixel units of the high-density LED dot matrix. Specifically, this includes: retrieving the verified light intensity deviation vector from the computation cache area. This vector consists of light intensity deviation values ​​corresponding to all physical pixel units arranged in ascending order of physical pixel address index. Each deviation value represents the difference between the actual light intensity of the corresponding physical pixel and the preset standard light intensity. To eliminate the dimensional differences and numerical range of the light intensity deviation values, and to make the deviation values ​​adapt to the pulse width modulation adjustment range of the taillight LED driver chip, while meeting the ECE R48 regulations' limit requirements for vehicle headlight brightness, a full-domain numerical traversal operation is performed on the light intensity deviation vector, checking each light intensity deviation value in the vector one by one. The difference values ​​are compared and filtered. By comparing the values ​​of adjacent deviation values ​​one by one, the maximum and minimum light intensity deviation values ​​in the entire light intensity deviation vector are filtered and recorded to complete the extreme value calibration of the deviation values. After the extreme value calibration is completed, a normalization operation is performed on each independent light intensity deviation value in the light intensity deviation vector. The specific calculation process is as follows: the light intensity deviation value of the current single physical pixel is subtracted from the minimum light intensity deviation value to obtain the first-level operation difference; then the maximum light intensity deviation value is subtracted from the minimum light intensity deviation value to obtain the second-level operation difference; finally, the first-level operation difference is divided by the second-level operation difference to complete the normalization process. After this operation, all light intensity deviation values ​​are uniformly converted to the standard value range of 0 to 1, eliminating the compensation adjustment imbalance problem caused by the large range of different pixel deviation values.

[0050] After normalization, the system maps the normalized deviation value to a preset duty cycle adjustment range. This duty cycle adjustment range is a fixed range pre-calibrated by the system in combination with the working performance of the taillight driver IC, the light emission threshold of the high-density LED dot matrix, and the brightness requirements of the ECE R48 automotive lighting regulations. The lower limit of the range is the minimum duty cycle threshold to ensure normal LED lighting, and the upper limit of the range is the maximum duty cycle threshold to avoid excessive LED brightness. The specific process of the mapping operation is as follows: multiply the normalized deviation value by the difference between the upper and lower limits of the duty cycle adjustment interval, and then add the product result to the lower limit of the duty cycle adjustment interval. Through this linear mapping operation, the normalized deviation value in the 0 to 1 interval is converted into an effective coefficient value for pulse width modulation adjustment. This value is the initial compensation coefficient of the corresponding physical pixel unit. After the operation is completed, the validity of each initial compensation coefficient is checked. The initial compensation coefficient is checked one by one to see if it is within the preset duty cycle adjustment interval. Abnormal coefficients that exceed the interval range are eliminated and recalculated to ensure that all initial compensation coefficients meet the hardware driver and regulatory requirements. Finally, a set of initial compensation coefficients corresponding to the physical pixel address index is formed.

[0051] Step 4.2: Based on the physical pixel arrangement structure of the high-density LED dot matrix, the initial compensation coefficients are arranged in a matrix according to the physical pixel address index to construct the pulse width modulation compensation coefficient matrix. Specifically, this includes: reading the number of physical horizontal pixels and physical vertical pixels of the high-density LED dot matrix from the hardware parameter storage unit of the taillight controller, and simultaneously retrieving the total number of pixels in the dot matrix. Based on the number of physical horizontal pixels and physical vertical pixels, the dimension of the pulse width modulation compensation coefficient matrix to be constructed is determined, that is, the number of rows in the matrix is ​​consistent with the number of physical vertical pixels in the dot matrix, and the number of columns in the matrix is ​​consistent with the number of physical horizontal pixels in the dot matrix. To ensure that the matrix structure perfectly matches the physical pixel arrangement of the LED dot matrix, the physical pixel address index encoding rule is used to establish the correspondence between the initial compensation coefficients and the matrix row and column coordinates. The specific conversion calculation process is as follows: divide the physical pixel address index by the number of physical horizontal pixels in the dot matrix, and take the integer part of the calculation result as the row coordinate of the compensation coefficient matrix; divide the physical pixel address index by the number of physical horizontal pixels in the dot matrix, and take the remainder of the calculation result as the column coordinate of the compensation coefficient matrix. Through this calculation method, the one-dimensional physical pixel address index is accurately converted into two-dimensional matrix row and column coordinates, realizing the correspondence between the coefficients and the matrix positions.

[0052] After establishing the correspondence, the system iterates through each coefficient in the initial compensation coefficient set in ascending order of physical pixel address index. Based on the converted matrix row and column coordinates, the initial compensation coefficients are filled into the corresponding positions of the pulse width modulation compensation coefficient matrix one by one. The filling order strictly follows the arrangement rule of the physical pixels of the dot matrix from top to bottom and from left to right. After filling all columns of a row, the system moves to the next row to fill the coefficients, until all initial compensation coefficients are arranged in the matrix. After the matrix is ​​filled, the integrity of the pulse width modulation compensation coefficient matrix is ​​checked. The total number of coefficients in the matrix is ​​counted and compared with the total number of pixels in the high-density LED dot matrix to confirm that the two values ​​are completely equal and there are no missing coefficients, duplicate fillings, or misaligned positions. At the same time, it is verified that each coefficient in the matrix is ​​a valid initial compensation coefficient with no abnormal values. After passing the verification, the final pulse width modulation compensation coefficient matrix is ​​obtained, which is completely adapted to the physical pixel arrangement of the high-density LED dot matrix and can be directly used to drive duty cycle correction.

[0053] Step 4.3: Extract the initial driving duty cycle of each pixel in the original dot matrix driving data. Perform a weighted multiplication operation on the initial driving duty cycle and the corresponding compensation coefficient in the pulse width modulation compensation coefficient matrix to obtain the corrected driving duty cycle. Specifically, this includes: retrieving the original dot matrix driving data from the driving data cache area of ​​the taillight controller. This data contains the physical coordinates, driving channel code, color driving value, and initial driving duty cycle without light intensity compensation correction for each physical pixel. Following the physical pixel arrangement order from top to bottom and left to right, perform a full domain traversal of the original dot matrix driving data row by row and column by column. During the traversal, parse the driving parameter segment in the driving channel corresponding to each physical pixel one by one, and accurately extract the initial driving duty cycle value used by that pixel to control the LED brightness. After extraction, the system performs a validity check on each initial driving duty cycle value to verify whether the value is within the working duty cycle range allowed by the taillight driver chip. Simultaneously, the system verifies whether the value meets the minimum requirement of the ECE R48 regulation for the basic brightness of the taillight. Abnormal initial duty cycles with values ​​of zero, values ​​exceeding the driving range, or not meeting the lower limit of the regulation are eliminated. For abnormal values, the effective initial duty cycles of adjacent pixels are used for smooth replacement to ensure that the initial driving duty cycles involved in the calculation are all legal and valid basic driving parameters. After the initial driving duty cycle extraction and verification are completed, the system locates and matches the compensation coefficient corresponding to the same address index in the constructed pulse width modulation compensation coefficient matrix according to the physical pixel address index corresponding to each physical pixel, ensuring that the pixel and the compensation coefficient correspond and there is no misalignment or mismatch. A weighted multiplication operation is performed on each group of corresponding initial driving duty cycles and compensation coefficients. The specific calculation process is as follows: the initial driving duty cycle of a single physical pixel is used as the multiplicand, and the compensation coefficient at the corresponding position in the pulse width modulation compensation coefficient matrix is ​​used as the multiplier. The product obtained by directly multiplying the two is the corrected driving duty cycle of that physical pixel.

[0054] This weighted multiplication operation can adaptively adjust according to the actual deviation state of the light intensity deviation vector. When the actual light intensity of a physical pixel is lower than the preset standard light intensity, the compensation coefficient is greater than one, and the corrected driving duty cycle after multiplication is higher than the initial duty cycle, thereby increasing the brightness of the pixel to compensate for the light intensity attenuation. When the actual light intensity of a physical pixel is higher than the preset standard light intensity, the compensation coefficient is less than one, and the corrected driving duty cycle after multiplication is lower than the initial duty cycle, thereby reducing the brightness of the pixel to avoid exceeding the brightness limit. When the actual light intensity is consistent with the standard light intensity, the compensation coefficient is equal to one, and the corrected driving duty cycle remains unchanged from the initial duty cycle. After completing the weighted multiplication operation pixel by pixel, the system performs double verification on the corrected driving duty cycle again to verify whether the corrected value is still within the safe operating range of the driver chip and whether the value meets the constraints on the upper limit and uniformity of the taillight brightness. The corrected duty cycle that exceeds the limit is truncated by a threshold to limit it to a legal and compliant value range, and finally the effective corrected driving duty cycle corresponding to all physical pixels is obtained.

[0055] Step 4.4 updates the corrected drive duty cycle to the corresponding drive channel in the original dot matrix drive data to obtain the corrected target dot matrix drive data. Specifically, this includes: based on the physical pixel address index corresponding to each physical pixel, combined with the fixed pixel coordinates and the encoding correspondence rule of the hardware drive channel, locating the target hardware drive channel corresponding to each corrected drive duty cycle in the original dot matrix drive data one by one. The encoding rule still uses the method of multiplying the physical vertical coordinate by the total number of physical horizontal pixels of the high-density LED dot matrix and adding the physical horizontal coordinate to accurately lock the drive channel position to be written for each corrected drive duty cycle, ensuring that the update operation is without deviation and without crosstalk. After the location is completed, the initial drive duty cycle stored in the corresponding drive channel in the original dot matrix drive data is replaced one by one with the corrected drive duty cycle after weighted multiplication and verification. The replacement process uses an overwrite mode, directly updating the brightness control parameters within the driver channel while preserving the original red, green, and blue color driver values. Only the duty cycle parameters related to brightness adjustment are corrected to ensure that the user's personalized color display settings are not affected by light intensity compensation operations. After updating the duty cycle parameters of all hardware driver channels, all valid information in the original dot matrix driver data is integrated and reconstructed. The integrated content strictly follows the preset driver data format specifications, including the physical horizontal coordinates, physical vertical coordinates, corresponding hardware driver channel encoding, color driver values ​​decoded by the preset color space, and the corrected driver duty cycle after this correction. All parameters are arranged in ascending order according to the physical pixel address index, forming a dataset with a unified structure and complete fields.

[0056] After reconstruction, the system performs three levels of verification on the integrated dataset. The first level is integrity verification, which checks that the number of pixel entries in the dataset matches the total number of pixels in the high-density LED dot matrix, with no missing pixel parameters or duplicate entries. The second level is consistency verification, which checks that the coordinates, drive channel codes, and duty cycle parameters of each pixel match, with no data errors. The third level is compliance verification, which verifies the brightness output corresponding to all corrected drive duty cycles in the dataset, ensuring that they meet the requirements of the ECE R48 standard for taillight brightness uniformity and brightness limits. After all three levels of verification are passed, the integrated and verified dataset is determined as the final corrected target dot matrix drive data and stored in the dedicated drive execution cache area of ​​the taillight controller, awaiting subsequent vehicle bus encapsulation and drive execution instructions. This data can be directly used to control the high-density LED dot matrix to achieve uniform, compliant, and personalized color pattern light emission display.

[0057] In this embodiment of the invention, by normalizing the light intensity deviation vector and mapping it to a reasonable duty cycle adjustment range, an initial compensation coefficient adapted to the hardware driving capability can be obtained, avoiding abnormal lighting caused by compensation parameters exceeding the working range of the driver chip. A pulse width modulation compensation coefficient matrix is ​​constructed according to the dot matrix physical structure to ensure that the compensation parameters correspond precisely to the physical pixels, improving the targeting of compensation. By correcting the driving parameters through weighted calculation of the initial driving duty cycle and the compensation coefficient, the light intensity attenuation problem caused by the light-transmitting material and pixel spacing can be accurately compensated, improving the uneven brightness distribution of the light-emitting surface and eliminating the display graininess. The corrected parameters are updated to the original driving data to obtain compliant and uniform target driving data. While retaining the user's personalized color and pattern settings, the taillight brightness meets the requirements of motor vehicle lighting regulations, improving the display quality and safety of the dot matrix taillight.

[0058] In a preferred embodiment of the present invention, step 5 above may include: Step 5.1: Based on the corrected target dot matrix drive data, encapsulate the data according to the data frame structure of the vehicle communication bus protocol, add a frame identifier and a cyclic redundancy check code to obtain the control frame of the vehicle communication bus protocol to be transmitted. Specifically, this includes: retrieving the corrected target dot matrix drive data that has passed multi-level verification; calculating the total byte length of the data by multiplying the parameter byte length corresponding to a single physical pixel by the total number of pixels in the high-density LED dot matrix; encapsulating the data according to the standard data frame structure of the vehicle CAN communication bus protocol. This protocol frame structure sequentially includes a frame start segment, arbitration segment, control segment, data segment, cyclic redundancy check segment, and frame end segment; assigning a dedicated frame identifier to the control frame; this identifier is a pre-set taillight dot matrix drive-specific identifier used to distinguish it from other control commands on the vehicle bus, ensuring that the taillight controller can accurately identify the command type; and transmitting the target dot matrix drive data according to the vehicle bus protocol. The data is divided into segments according to the specified maximum data length per frame. If the total number of bytes does not exceed the single frame carrying limit, the data segment is filled directly and completely. If it exceeds the limit, the data is split sequentially from front to back, with each segment having a length equal to the maximum data length per frame. The last segment is filled with the remaining bytes. At the same time, a continuously increasing frame sequence number is assigned to the control frame corresponding to each segment. The frame sequence number is calculated by adding one to the previous frame sequence number to ensure orderly data transmission across multiple frames. Cyclic redundancy check (CRC) is calculated for all bytes in the frame start segment, arbitration segment, control segment, and data segment. The calculation process involves converting all the above byte data into a binary sequence, performing shift and XOR operations on the binary sequence sequentially based on a preset generator polynomial, and traversing all data bits to obtain the final check result, which is the CRC. This result is filled into the CRC segment, and finally, the frame end segment is added to complete the encapsulation. All encapsulated data units constitute the vehicle communication bus protocol control frame to be transmitted.

[0059] Step 5.2: The control frames of the vehicle communication bus protocol to be transmitted are sent to the taillight controller through the bus transmission interface of the vehicle communication gateway, and the control frames are stored in the data receiving buffer of the taillight controller. Specifically, the vehicle communication gateway first detects the transmission status of the vehicle CAN bus in real time, and determines whether the bus is idle by reading the bus level signal. When the bus is idle, the data transmission process is started. The gateway sends the control frames to be transmitted to the vehicle bus one by one in ascending order of the control frame sequence number through its own CAN bus transmission interface. During the transmission process, the transmission status is monitored in real time. If a transmission failure occurs, the current frame is immediately retransmitted until the frame is successfully transmitted. After the taillight controller listens to the exclusive frame identifier through the vehicle bus receiving interface, it starts the data receiving process, first receiving the control frame. The frame is subjected to cyclic redundancy check (CRC) verification. The CRC check code in the received frame is compared with the recalculated CRC result. If they match, the data reception is considered valid. If they do not match, the frame is discarded and a retransmission is requested. After the verification is passed, the taillight controller calculates the storage address of the data in the receiving buffer according to the frame sequence number of the control frame. The calculation method is to multiply the frame sequence number by the length of a single frame data and add the offset address of the data in the current frame to obtain the precise storage location. The data receiving buffer is a dedicated storage area pre-divided by the taillight controller. The size of the area is equal to the total number of bytes of the target dot matrix drive data. According to the calculated storage address, the drive data in the control frame data segment is written to the corresponding storage location in sequence until all control frames are received and stored in an orderly manner, ensuring that the target dot matrix drive data in the buffer is complete, continuous, and without errors or omissions.

[0060] Step 5.3: The taillight controller reads the control frame from the data receiving buffer and performs protocol parsing to restore the corrected target dot matrix driving data, obtaining the pulse width modulation signal corresponding to the corrected driving duty cycle of each pixel, and driving the high-density LED dot matrix to perform the corresponding color display. Specifically, the taillight controller reads the stored control frame data segment by segment from the data receiving buffer in ascending order of frame number. After reading, the control frame is parsed according to the protocol, and the frame start segment, arbitration segment, frame identifier, cyclic redundancy check code and frame end segment are stripped in sequence, retaining only the core data segment content. Then, the multiple frame data segments are spliced ​​and integrated according to the frame number to completely restore the corrected target dot matrix driving data.

[0061] The controller iterates through the target dot matrix driving data, extracts the hardware driving channel code, color driving value, and corrected driving duty cycle corresponding to each physical pixel, and generates a corresponding pulse width modulation signal based on the driving duty cycle. The high-level duration of the pulse width modulation signal is calculated by multiplying the fixed total signal period by the corrected driving duty cycle, and the low-level duration is the total signal period minus the high-level duration. This yields a pulse width modulation signal that meets the light intensity compensation requirements of each pixel. The controller synchronously transmits the generated pulse width modulation signal and RGB color driving value to the LED driver IC. The driver IC distributes the signal to the corresponding physical pixel unit according to the hardware driving channel code, controlling each pixel in the high-density LED dot matrix to emit light according to the set color and corrected brightness. The controller drives all physical pixels row by row in a top-to-bottom and left-to-right order, ultimately completing the display of user-defined patterns and colors, ensuring uniform brightness across the entire luminous surface and meeting automotive lighting regulations.

[0062] In this embodiment of the invention, by encapsulating data according to the vehicle communication bus protocol specification and adding frame identifiers and cyclic redundancy check codes, the stability and accuracy of the target dot matrix driving data transmission in the complex electromagnetic environment of the vehicle are ensured, avoiding data packet loss, corruption, or interference, and ensuring the complete and reliable transmission of driving data. Through bus idle detection, orderly sending and receiving verification and storage, the orderly transmission and accurate storage of control frames can be achieved, eliminating data transmission misalignment problems and providing a complete data foundation for driving data restoration. By restoring driving data through protocol parsing, calculating and generating pulse width modulation signals according to duty cycle, and accurately driving LED pixels, the effect of previous light intensity compensation is fully implemented. While retaining the user's personalized color and pattern settings, the dot matrix taillight light intensity is uniformly displayed, eliminating graininess and meeting vehicle lighting regulations, ensuring the unity of the personalized display function of the dot matrix taillight and driving safety compliance.

[0063] like Figure 2 As shown, embodiments of the present invention also provide a dot-matrix taillight display data processing system based on a mobile terminal, including: The acquisition module is used to receive the taillight display configuration instruction transmitted by the mobile terminal, and to perform protocol parsing on the taillight display configuration instruction to extract the color parameter vector selected by the user and the custom pattern bitmap data uploaded by the user. The mapping module is used to perform coordinate mapping between the resolution of the custom pattern bitmap data and the physical pixel arrangement structure of the high-density LED dot matrix in the dot matrix taillight, so as to obtain the mapped pixel coordinates; the color parameter vector is filled into the mapped pixel coordinates to obtain the original dot matrix driving data containing the information of each pixel. The module is used to construct a virtual elliptical boundary covering the light-emitting surface of a high-density LED dot matrix based on the physical pixel arrangement structure in the original dot matrix driving data; iterates the angle parameters in the virtual elliptical boundary and the internal region through the elliptical parametric equation to obtain multiple discrete spatial sampling coordinates; maps the physical position of each discrete sampling coordinate point to the corresponding actual light intensity value, and compares the actual light intensity value with the preset standard light intensity value to obtain the light intensity deviation vector. The driving module is used to derive the pulse width modulation compensation coefficient matrix based on the light intensity deviation vector; and to perform weighted correction on the driving duty cycle of each pixel in the original dot matrix driving data through the pulse width modulation compensation coefficient matrix to obtain the corrected target dot matrix driving data. The processing module encapsulates the corrected target dot matrix driving data into a control frame of the vehicle communication bus protocol and sends it to the taillight controller through the vehicle communication gateway. The taillight controller then drives the high-density LED dot matrix to perform the corresponding color display.

[0064] It should be noted that this system is a system corresponding to the above method. All implementation methods in the above method embodiments are applicable to this embodiment and can achieve the same technical effect.

[0065] Embodiments of the present invention also provide a computing device, including: a processor and a memory storing a computer program, wherein the computer program, when executed by the processor, performs the method described above. All implementations in the above method embodiments are applicable to this embodiment and can achieve the same technical effects.

[0066] Embodiments of the present invention also provide a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the method described above. All implementations in the above method embodiments are applicable to this embodiment and can achieve the same technical effects.

[0067] The above description represents the preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A data processing method for dot-matrix taillight display based on a mobile terminal, characterized in that, The method includes: Receive taillight display configuration instructions transmitted from the mobile terminal, and perform protocol parsing on the taillight display configuration instructions to extract the user-selected color parameter vector and the user-uploaded custom pattern bitmap data; Based on the resolution of the custom pattern bitmap data and the physical pixel arrangement structure of the high-density LED dot matrix in the dot matrix taillight, coordinate mapping is performed to obtain the mapped pixel coordinates; color parameter vectors are filled into the mapped pixel coordinates to obtain the original dot matrix driving data containing information of each pixel. Based on the physical pixel arrangement structure in the original dot matrix driving data, a virtual elliptical boundary covering the high-density LED dot matrix emitting surface is constructed; the angle parameters are iterated in the virtual elliptical boundary and the internal region through the elliptical parametric equation to obtain multiple discrete spatial sampling coordinates; the physical position of each discrete sampling coordinate point is mapped to the corresponding actual light intensity value, and the actual light intensity value is compared with the preset standard light intensity value to obtain the light intensity deviation vector. The pulse width modulation compensation coefficient matrix is ​​derived based on the light intensity deviation vector; the driving duty cycle of each pixel in the original dot matrix driving data is weighted and corrected by the pulse width modulation compensation coefficient matrix to obtain the corrected target dot matrix driving data. The corrected target dot matrix driving data is encapsulated into a control frame of the vehicle communication bus protocol and sent to the taillight controller through the vehicle communication gateway. The taillight controller then drives the high-density LED dot matrix to perform the corresponding color display.

2. The data processing method for dot-matrix taillight display based on a mobile terminal according to claim 1, characterized in that, The system receives taillight display configuration instructions transmitted from a mobile terminal, performs protocol parsing on the instructions to extract the user-selected color parameter vector and the user-uploaded custom pattern bitmap data, including: The vehicle communication gateway receives the original communication data frames sent by the mobile terminal through its wireless communication interface, performs protocol header verification and frame decapsulation on the original communication data frames, and obtains the complete taillight display configuration instruction payload. Based on preset data field mapping rules, the color encoding field and image data field are separated from the complete taillight display configuration instruction payload. The color encoding field is decoded in color space to obtain the color parameter vector selected by the user; the image data field is compressed, decoded and reconstructed in pixel matrix to obtain the user-uploaded custom pattern bitmap data.

3. The data processing method for dot-matrix taillight display based on a mobile terminal according to claim 2, characterized in that, Based on the resolution of the custom pattern bitmap data and the physical pixel arrangement structure of the high-density LED dot matrix in the dot matrix taillight, coordinate mapping is performed to obtain the mapped pixel coordinates. The color parameter vectors are filled into the mapped pixel coordinates to obtain the original bitmap driving data containing information about each pixel, including: Parse custom pattern bitmap data to obtain image resolution parameters, and read the number of rows and columns in the physical pixel arrangement structure of the high-density LED dot matrix; The mapping ratio between logical pixel coordinates and physical pixel coordinates is calculated based on image resolution parameters and row and column number parameters to establish coordinate transformation relationships; By using coordinate transformation relationships, the logical pixel coordinates in the custom pattern bitmap data are mapped to the physical pixel coordinates in the high-density LED dot matrix, thus obtaining the mapped pixel coordinates. The color information in the color parameter vector is assigned to the driving channel corresponding to the mapped pixel coordinates to obtain the original dot matrix driving data containing information of each pixel.

4. The data processing method for dot-matrix taillight display based on a mobile terminal according to claim 3, characterized in that, Based on the physical pixel arrangement structure in the original dot matrix driving data, a virtual elliptical boundary is constructed to cover the light-emitting surface of the high-density LED dot matrix. Multiple discrete spatial sample coordinates are obtained by iterating the angle parameters in the virtual ellipse boundary and interior region using the ellipse parametric equation, including: Analyze the physical pixel arrangement structure in the original dot matrix driving data and extract the set of edge pixel coordinates of the high-density LED dot matrix luminous surface; The geometric center point, major axis radius, and minor axis radius of the virtual elliptical boundary are determined by fitting the edge pixel coordinate set, and a virtual elliptical boundary covering the high-density LED dot matrix light-emitting surface is constructed. By using the geometric center point as a reference, iterating the angle parameters within a preset angle range according to a fixed angle step, and combining the major axis radius and minor axis radius, the discrete point coordinates of the virtual ellipse boundary and the internal region are obtained. The discrete point coordinates are mapped to discrete spatial sampling coordinates corresponding to the physical space of the high-density LED dot matrix.

5. The data processing method for dot-matrix taillight display based on a mobile terminal according to claim 4, characterized in that, The physical location of each discrete sampling coordinate point is mapped to the corresponding actual light intensity value. The actual light intensity value is compared with the preset standard light intensity value to obtain the light intensity deviation vector, including: Each discrete spatial sampling coordinate is mapped to a physical pixel address index of a high-density LED dot matrix. Based on the physical pixel address index, a pre-stored light effect mapping relationship table is retrieved to obtain the actual light intensity value of each physical pixel unit under the preset light-transmitting material light guide path. The preset standard light intensity value corresponding to the physical pixel address index position is extracted by querying the pre-stored standard light intensity distribution curve through the physical pixel address index. A vector difference operation is performed between the actual light intensity value and the preset standard light intensity value to obtain the light intensity deviation vector that characterizes the difference in light intensity distribution.

6. The data processing method for dot-matrix taillight display based on a mobile terminal according to claim 5, characterized in that, The pulse width modulation compensation coefficient matrix is ​​derived based on the light intensity deviation vector; The driving duty cycle of each pixel in the original dot matrix driving data is weighted and corrected using a pulse width modulation compensation coefficient matrix to obtain the corrected target dot matrix driving data, including: The light intensity deviation vector is normalized and mapped to a preset duty cycle adjustment range to obtain the initial compensation coefficients corresponding to the physical pixel units of the high-density LED dot matrix. Based on the physical pixel arrangement structure of high-density LED dot matrix, the initial compensation coefficients are arranged in a matrix according to the physical pixel address index to construct the pulse width modulation compensation coefficient matrix. Extract the initial driving duty cycle of each pixel in the original dot matrix driving data, and perform a weighted multiplication operation on the initial driving duty cycle and the corresponding compensation coefficient in the pulse width modulation compensation coefficient matrix to obtain the corrected driving duty cycle. The corrected drive duty cycle is updated to the corresponding drive channel in the original dot matrix drive data to obtain the corrected target dot matrix drive data.

7. The data processing method for dot-matrix taillight display based on a mobile terminal according to claim 6, characterized in that, The corrected target dot matrix driving data is encapsulated into a control frame of the vehicle communication bus protocol and sent to the taillight controller through the vehicle communication gateway. The taillight controller then drives the high-density LED dot matrix to perform the corresponding color display, including: Based on the corrected target dot matrix driving data, the data frame is encapsulated according to the data frame structure of the vehicle communication bus protocol, and a frame identifier and cyclic redundancy check code are added to obtain the control frame of the vehicle communication bus protocol to be transmitted. The control frame of the vehicle communication bus protocol to be transmitted is sent to the taillight controller through the bus transmission interface of the vehicle communication gateway, and the control frame is stored in the data receiving buffer of the taillight controller. The taillight controller reads the control frame from the data receiving buffer and performs protocol parsing to restore the corrected target dot matrix driving data, thereby obtaining the pulse width modulation signal corresponding to the corrected driving duty cycle of each pixel, and driving the high-density LED dot matrix to perform the corresponding color display.

8. A dot-matrix taillight display data processing system based on a mobile terminal, the system implementing the method as described in any one of claims 1 to 7, characterized in that, include: The acquisition module is used to receive the taillight display configuration instruction transmitted by the mobile terminal, and to perform protocol parsing on the taillight display configuration instruction to extract the color parameter vector selected by the user and the custom pattern bitmap data uploaded by the user. The mapping module is used to perform coordinate mapping between the resolution of the custom pattern bitmap data and the physical pixel arrangement structure of the high-density LED dot matrix in the dot matrix taillight, so as to obtain the mapped pixel coordinates. Fill the color parameter vector into the mapped pixel coordinates to obtain the original dot matrix driving data containing information about each pixel. The building module is used to construct a virtual elliptical boundary covering the light-emitting surface of a high-density LED dot matrix based on the physical pixel arrangement structure in the original dot matrix driving data. Multiple discrete spatial sampling coordinates are obtained by iterating the angle parameters in the boundary and interior region of the virtual ellipse through the elliptic parametric equation; the physical position of each discrete sampling coordinate point is mapped to the corresponding actual light intensity value, and the actual light intensity value is compared with the preset standard light intensity value to obtain the light intensity deviation vector. The driving module is used to derive the pulse width modulation compensation coefficient matrix based on the light intensity deviation vector; The driving duty cycle of each pixel in the original dot matrix driving data is weighted and corrected by the pulse width modulation compensation coefficient matrix to obtain the corrected target dot matrix driving data. The processing module encapsulates the corrected target dot matrix driving data into a control frame of the vehicle communication bus protocol and sends it to the taillight controller through the vehicle communication gateway. The taillight controller then drives the high-density LED dot matrix to perform the corresponding color display.

9. A computing device, characterized in that, include: One or more processors; A storage device for storing one or more programs, which, when executed by one or more processors, cause the one or more processors to implement the method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a program that, when executed by a processor, implements the method as described in any one of claims 1 to 7.

Images