Customer demand function and production line function bidirectional decoupling efficient production line software integration method suitable for laser radar

By decoupling customer requirements from production line functions in the LiDAR production line software integration, generating independent modules and separating their communication addresses, the problem of tight coupling between LiDAR production line functions and customer requirements is solved. This achieves efficient and portable LiDAR production line software integration, shortens delivery cycles, and reduces costs.

CN121785567APending Publication Date: 2026-04-03TIANMU XINWANG (SUZHOU) TECHNOLOGY CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-12-30
Publication Date
2026-04-03

AI Technical Summary

Technical Problem

When faced with small-batch, multi-variety, and customized orders, the existing technology's LiDAR production line functions are tightly coupled with customer needs, resulting in poor portability. When migrating across projects, it is necessary to re-examine the coupling process and adjust parameters, which cannot achieve "plug and play", thus extending the delivery cycle and increasing maintenance costs.

Method used

We adopt an efficient production line software integration method that decouples customer-demand functions from production line functions. By developing independently on both the customer business demand side and the production line demand side, we generate independent production line function modules and implement two-level cryptography and physical separation at the communication address level to ensure the independence and portability of production line functions.

Benefits of technology

It enables plug-and-play functionality for LiDAR production lines, significantly shortening delivery cycles, reducing maintenance costs, improving production line utilization, and ensuring that commercial-side functions remain unaffected.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121785567A_ABST
    Figure CN121785567A_ABST
Patent Text Reader

Abstract

The invention provides a customer demand function and production line function bidirectional decoupling-oriented efficient production line software integration method suitable for a laser radar. The method mainly comprises the following steps of customer business demand analysis and development, customer production line function demand confirmation, business demand side and production line side combination, small-batch verification, customer evaluation and mass production software generation. According to the method, the production efficiency can be improved to the greatest extent while the business demand side and the production line demand side of a customer are developed in a combined manner, intersection point type integration is adopted during production, production line functions are associated with communication addresses after leaving a factory, and secondary password + physical separation is performed, so that the functions of the business side are not influenced, and the production efficiency is improved. And the subsequent self-upgrading of a business demand side and a production line side is not influenced.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of intelligent manufacturing software integration, and in particular to a highly efficient production line software integration method that bidirectionally decouples customer-demand-oriented functions and production line functions for lidar. Background Technology

[0002] With small-batch, multi-variety, and customized orders becoming mainstream, production line software needs to frequently respond to new customer needs. Traditional approaches employ a "project-based" integration: for each new customer, both "demand-side logic" and "production line-side logic" must be developed simultaneously. Existing technologies abstract "LiDAR production line equipment capabilities" into single-station services (such as atomic interfaces for dispensing, lens coupling, and functional testing), but this remains at the communication protocol level. The "LiDAR production line functions" themselves (such as the complete process chain of "automatic lens coupling → UV curing → optical axis adjustment → functional testing → final testing") are not encapsulated at the business level, leading to poor portability. Cross-project migration requires re-evaluating coupling paths, optical calibration parameters, and test thresholds. Furthermore, customer needs are tightly coupled with LiDAR production line functions: even minor adjustments to the demand side can have far-reaching consequences, making it impossible to "develop only customer needs without modifying the LiDAR production line functional modules."

[0003] Therefore, there is an urgent need for a method that can pre-package "production line functions" as independent, portable modules. This would allow for the development of customer-side functional logic when facing different customer needs, enabling existing production line functions to be "plug-and-play" and deployed through standardized interfaces. This would reduce the integration workload from "two heads" to "one head," significantly shortening the delivery cycle, reducing maintenance costs, and improving production line utilization.

[0004] Based on the above requirements, this invention provides an efficient production line software integration method that bidirectionally decouples customer-oriented functions and production line functions for LiDAR. Summary of the Invention

[0005] To meet the above requirements, this invention provides a highly efficient production line software integration method for LiDAR, which bidirectionally decouples customer-demand-oriented functions from production line functions. This invention maximizes production efficiency while simultaneously developing customer business needs and production line needs in parallel. During production, it employs a point-of-sale integration approach. After leaving the factory, the production line functions are associated with communication addresses and separated using a "two-level encryption + physical separation" method, without affecting the business-side functions or subsequent self-upgrades on both the business-side and production line sides. This invention mainly includes the following steps:

[0006] S1: Customer business needs analysis and development;

[0007] S2: Confirmation of customer production line functional requirements;

[0008] S3: Combining business demand with production line;

[0009] S4: Small batch validation;

[0010] S5: Customer Assessment;

[0011] S6: Generate mass production software.

[0012] In S1, the R&D personnel analyze and extract customer input to begin customized development based on business requirements:

[0013] S101: Customer requirements input, R&D breaks down the requirements into new requirements and existing requirements;

[0014] S102: For existing requirements, the software testing end verifies the compatibility of the requirements;

[0015] S103: R&D personnel conduct development and verification in response to new requirements.

[0016] In S2, in sync with S1, the existing production line function set is displayed to the customer, and the existing functions are expanded for the customer to select. The customer inputs the production line test function requirements as needed.

[0017] S201: Based on the customer's production line testing requirements, encapsulate the selected production line functions into portable functional functions;

[0018] S202: For functions that customers add to their production lines that are not yet included, inform the customers in advance, and the production line R&D personnel will develop the functions. Once the functions are developed, they will be integrated into the existing production line function set.

[0019] In step S3, steps S1 and S2 are integrated to generate a test version of the mass production software.

[0020] S301: Before integration, the R&D personnel check the consistency of the communication framework. The development of S1 and S2 above must be under the same framework.

[0021] S302: During integration, based on the needs of the business side, the functions of the production line side are migrated as a whole, the communication address is modified to the dedicated communication address of the production line side, and the intervention function of the production line side is enabled.

[0022] S303: After integration, the commercial demand side R&D personnel and the production line side R&D personnel jointly verify and confirm that the test version of the mass production software has no problems, and output the gold sample LiDAR.

[0023] In step S4, small-batch production verification is performed based on the test version of the mass production software;

[0024] S401: Verify the smoothness of the test version of the mass production software and record the production time of each workstation;

[0025] S402: Collect data from each workstation and compare it with the gold sample module to verify the consistency of the lidar;

[0026] S403: After verification, permanently disable the production line intervention function.

[0027] In step S5, the sample produced in step S4 is delivered to the customer for evaluation.

[0028] S501: Conduct a safety assessment, wake up the production line function when the production line intervention is shut down, and assess the reliability of separating the module production line from commercial needs.

[0029] S502: Business requirement functional assessment. The client verifies whether all business requirements have been met. If not, return to S1.

[0030] In S6, after the evaluation in S5 is passed, a formal version of the mass production software is generated and used as the baseline version of the production line software. Mass production is carried out according to small batch specifications, thus completing an efficient production line software integration method that decouples customer-demand functions from production line functions.

[0031] Furthermore, when performing self-upgrades on the commercial side, it is not necessary to re-integrate production line functions, and when performing self-upgrades on the production line side, it is not necessary to re-integrate commercial side requirements. Development is based on the production line side software baseline version, achieving bidirectional decoupling.

[0032] Furthermore, since the baseline version of the production line software integrates the requirements of the business side, the risk of deviating from business requirements is avoided in subsequent production line software development. Attached Figure Description

[0033] Figure 1 This is the overall flowchart of the present invention.

[0034] Figure 2 This is the feature set of the baseline version of the integrated production line software.

[0035] Figure 3 This is a diagram showing the two-way decoupling between the production line side and the commercial side. Detailed Implementation

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

[0037] This invention provides a highly efficient production line software integration method for LiDAR, which bidirectionally decouples customer-demand-oriented functions from production line functions. This invention maximizes production efficiency while simultaneously developing solutions for customer business needs and production line needs. During production, it employs a point-to-point integration approach. After leaving the factory, production line functions are associated with communication addresses and separated using a "two-level password + physical separation" method. This does not affect the business-side functions or subsequent self-upgrades for both the business-side and production line sides. (See attached...) Figure 1 The present invention mainly includes the following steps:

[0038] S1: Customer business needs analysis and development;

[0039] S2: Confirmation of customer production line functional requirements;

[0040] S3: Combining business demand with production line;

[0041] S4: Small batch validation;

[0042] S5: Customer Assessment;

[0043] S6: Generate mass production software;

[0044] In S1, the R&D personnel analyze and extract customer input to begin customized development based on business requirements:

[0045] S101: Customer requirements input, R&D separates the requirements into new requirements and existing requirements.

[0046] S102: For existing requirements, the software testing end verifies the compatibility of the requirements;

[0047] S103: R&D personnel conduct development and verification in response to new requirements.

[0048] In S2, in sync with S1, the existing production line function set is displayed to the customer, and the existing functions are expanded for the customer to select. The customer inputs the production line test function requirements as needed.

[0049] S201: Based on the customer's production line testing requirements, encapsulate the selected production line functions into portable functional functions;

[0050] S202: For functions that customers add to their production lines that are not yet included, inform the customers in advance, and the production line R&D personnel will develop the functions. Once the functions are developed, they will be integrated into the existing production line function set.

[0051] In step S3, steps S1 and S2 are integrated to generate a test version of the mass production software, as shown in the attached figure. Figure 2 As shown;

[0052] S301: Before integration, the R&D personnel check the consistency of the communication framework. The development of S1 and S2 above must be under the same framework.

[0053] S302: During integration, based on the needs of the business side, the functions of the production line side are migrated as a whole, the communication address is modified to the dedicated communication address of the production line side, and the intervention function of the production line side is enabled.

[0054] S303: After integration, the commercial demand side R&D personnel and the production line side R&D personnel jointly verify and confirm that the test version of the mass production software has no problems, and output the gold sample LiDAR.

[0055] In step S4, small-batch production verification is performed based on the test version of the mass production software;

[0056] S401: Verify the smoothness of the test version of the mass production software and record the production time of each workstation;

[0057] S402: Collect data from each workstation and compare it with the gold sample module to verify the consistency of the lidar;

[0058] S403: After verification, the hardware password area is erased by setting the software password on the host computer, and a one-time programming area flag is set to permanently disable the production line intervention function.

[0059] In step S5, the sample produced in step S4 is delivered to the customer for evaluation.

[0060] S501: Conduct a safety assessment, wake up the production line function when the production line intervention is shut down, and assess the reliability of separating the module production line from commercial needs.

[0061] S502: Business requirement functional assessment. The customer verifies whether all business requirements have been met. If not, return to S1.

[0062] In S6, after the evaluation in S5 is passed, a formal version of the mass production software is generated and used as the baseline version of the production line software. Mass production is carried out according to small batch specifications, thus completing an efficient production line software integration method that decouples customer-demand functions from production line functions.

[0063] Furthermore, in conjunction with the appendix Figure 3 When performing self-upgrades on the commercial side, it is not necessary to re-integrate production line functions, and when performing self-upgrades on the production line side, it is not necessary to re-integrate commercial side requirements. Development is based on the production line side software baseline version, achieving bidirectional decoupling.

[0064] Furthermore, in conjunction with the appendix Figure 3 Because the baseline version of the production line software integrates the requirements of the commercial side, the risk of deviating from commercial requirements is avoided in subsequent production line software development.

[0065] The preferred embodiments of the present application have been described above with reference to the accompanying drawings, but this does not limit the scope of the claims of the present application. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and substance of the embodiments of the present application shall be within the scope of the claims of the present application.

Claims

1. A highly efficient production line software integration method for LiDAR, characterized by bidirectional decoupling of customer-oriented functions and production line functions, wherein... This invention maximizes production efficiency while simultaneously developing solutions for customer business needs and production line needs. During production testing, it employs a point-of-sale integration approach. After delivery, production line functions are associated with communication addresses and separated using a "two-level password + physical separation" mechanism. This ensures that subsequent self-upgrades for both the business and production line sides are not affected, achieving bidirectional decoupling between the production line and business sides. The invention mainly includes the following steps: S1: Customer business needs analysis and development; S2: Confirmation of customer production line functional requirements; S3: Combining business demand with production line; S4: Small batch validation; S5: Customer Assessment; S6: Generate mass production software.

2. The efficient production line software integration method for LiDAR with bidirectional decoupling of customer-oriented functions and production line functions as described in claim 1, characterized in that, When performing a self-upgrade on the commercial side, production line functions are no longer integrated. When performing a self-upgrade on the production line side, commercial side requirements are not integrated again. Development is based on the production line side software baseline version, achieving two-way decoupling. Since the production line side software baseline version integrates commercial side requirements, the risk of deviating from commercial requirements is avoided in subsequent production line side software development.