OEM information customization method and device

Abstract

The invention provides an OEM information customization method and device, and relates to the technical field of computers, and the technical scheme is characterized in that an actual hardware component list of a to-be-configured notebook computer is acquired; screening out a group of candidate hardware configuration packets from a plurality of predefined hardware configuration packets; analyzing metadata of each hardware configuration packet in the candidate hardware configuration packets, and determining a hardware configuration packet subset of a final application and an application sequence of each hardware configuration packet in the subset from the candidate hardware configuration packets; and executing the execution instruction embedded in the hardware configuration packet subset of the final application. The OEM information customization method and device provided by the invention have the advantages of adapting to the change of the actual hardware component list, selecting the configuration package based on the actual hardware component list, determining the application sequence of the configuration package according to the rule, completing the configuration matched with the actual hardware component list, reducing the mismatching of the configuration, supporting the processing of hardware combination, and improving the user experience. Automatic configuration selection and application are realized; and a configuration management structure is provided.

Description

Technical Field

[0001] The present application relates to the technical field of computer technology, and in particular to an OEM information customization method and device. Background Art

[0002] In the laptop manufacturing process, OEM (Original Equipment Manufacturer) information customization is a critical step before product delivery. Typically, after hardware assembly is completed on the production line, the laptop to be configured enters the OEM information customization station. This station is connected to the central OEM information management system via the network. Based on the product model information provided by the Manufacturing Execution System (MES), it obtains a preset OEM information package from the central system and then writes it to the laptop. These OEM information packages typically include an operating system image, pre-installed software, brand logos, firmware parameters, and drivers that match the standard configuration of a specific product model.

[0003] However, during the actual production process, due to fluctuations in the supply chain, temporary adjustments to material supplies, or specific customer order requirements, the actual hardware components installed in laptops of the same product model may differ from the standard configuration list of that model in different production batches or within the same batch. For example, a hardware component of a specific brand or model originally planned to be used (such as a solid-state drive, wireless network card, display, etc.) may be replaced by an alternative component that is functionally equivalent but comes from a different supplier or has slightly different specifications. Although these alternative components can meet basic functional requirements, their driver versions, internal firmware parameters, power management policies, or compatibility with other components may differ from those of the standard components.

[0004] Existing customization methods that rely on obtaining standard OEM information packages based on product models are unable to perceive and adapt to these real-time hardware component changes. If an OEM information package generated for a standard hardware configuration is directly applied to a laptop equipped with alternative hardware, the driver or firmware parameters contained therein may not fully match the actual hardware. This can lead to system instability, partial functional failure, performance degradation, and even compatibility issues, seriously affecting the quality of the final product and the user experience.

[0005] To address these issues, while production traceability systems typically record the material coding information of the hardware actually assembled, effectively bridging this real-time, specific hardware information into the OEM information customization process and ensuring that the customization system can automatically select and apply the correct configuration based on the actual hardware inventory remains a challenge. Centralized OEM information management systems typically organize and manage configuration data based on product models, lacking the ability to directly perceive and process the real-time hardware details of individual devices. Even if the system stores configuration snippets or patches for different alternative hardware, intelligently identifying the current device's alternative hardware combinations and accurately and efficiently filtering all necessary and compatible configuration items from the vast amount of configuration snippets for application remains a complex problem.

[0006] Furthermore, hardware component replacements are often not isolated; changes to one component may require coordinated adjustments to the configurations of multiple related components. For example, replacing a specific model of CPU or motherboard may require adjustments to power management or frequency settings in the BIOS; replacing a high-resolution display may require matching a specific display driver and color profile. This complex configuration adjustment involving multiple hardware components and their interactions makes simply selecting patches based on a single replacement hardware solution infeasible and error-prone. Relying on manual judgment and selection of these complex configuration differences is not only inefficient, but also requires extremely high technical skills from the operator, making it difficult to meet the efficiency, precision, and consistency requirements of modern automated production lines.

[0007] Furthermore, with multiple product models and the potential for multiple hardware alternatives for each model, the central OEM information management system must maintain a vast and complex library of configuration data and matching rules. Creating, validating, updating, and maintaining these rules is a massive undertaking and prone to errors. If the rule library is incomplete or contains errors, incorrect OEM information can be written in, leading to problems in subsequent product testing, increased rework, and increased production costs.

[0008] Therefore, in the field of consumer electronics manufacturing, dynamic changes in hardware materials are the norm. The existing OEM information customization method, which is based on pulling fixed information packages from fixed models, faces severe tests in terms of adaptability and accuracy when faced with such a dynamically changing production environment. How to implement an automated, high-precision, and efficient OEM information dynamic adaptation and writing mechanism that can handle complex hardware combinations, to ensure that every laptop computer off the production line can obtain system drivers, firmware parameters, and related configurations that fully match its unique, real-time hardware combination, thereby fundamentally avoiding compatibility issues, functional anomalies, or performance degradation caused by improper configuration, thereby improving the quality of the final product and meeting the high requirements of modern intelligent manufacturing for production efficiency and flexibility, is a technical problem that needs to be urgently addressed in this field.

[0009] In view of the above problems, the existing technology is in urgent need of improvement. Summary of the Invention

[0010] The purpose of this application is to provide an OEM information customization method and device, which can adapt to changes in the actual hardware component list, select configuration packages based on the actual hardware component list, determine the application order of configuration packages according to rules, complete the configuration that matches the actual hardware component list, reduce configuration mismatches, support processing hardware combinations, automate configuration selection and application, and provide a configuration management structure.

[0011] In the first aspect, this application provides an OEM information customization method, the technical solution is as follows:

[0012] Get the actual hardware component list of the laptop to be configured;

[0013] Based on the actual hardware component list, a group of candidate hardware configuration packages is screened from a plurality of predefined hardware configuration packages, wherein each of the hardware configuration packages corresponds to one or more hardware components or a combination of hardware components and includes execution instructions for deploying the corresponding OEM information configuration and metadata, wherein the metadata defines one or more target hardware identifiers compatible with the hardware configuration package and rule information characterizing the interaction between the hardware configuration package and other hardware configuration packages, wherein the rule information includes at least dependency relationships for determining the application order of the hardware configuration packages and conflict relationships for identifying incompatible combinations of hardware configuration packages;

[0014] Parsing metadata of each hardware configuration package in the candidate hardware configuration packages, and determining a subset of hardware configuration packages to be ultimately applied and an application order of the hardware configuration packages in the subset from the candidate hardware configuration packages based on the dependency relationships, the conflict relationships, and a preset decision logic defined in the metadata;

[0015] According to the determined application order, the execution instructions embedded in each hardware configuration package in the hardware configuration package subset of the final application are executed in sequence to complete the configuration of OEM information matching the actual hardware component list of the laptop computer.

[0016] Furthermore, in the present application, the step of parsing the metadata of each hardware configuration package in the candidate hardware configuration packages and determining a subset of hardware configuration packages to be finally applied and the order of applying each hardware configuration package in the subset from the candidate hardware configuration packages based on the dependency relationship, the conflict relationship, and the preset decision logic defined in the metadata further includes:

[0017] Collecting historical configuration data, including a subset of hardware configuration packages selected for historical configuration, an application sequence, an actual hardware combination, and configuration results;

[0018] Analyzing the execution efficiency of the preset decision logic in different configuration scenarios based on the historical configuration data;

[0019] Generating decision logic adjustment suggestions based on the execution efficiency obtained through analysis;

[0020] The preset decision logic is updated according to the decision logic adjustment suggestion to adjust the behavior of the preset decision logic when processing new hardware combinations, rare configuration scenarios, or changed production targets.

[0021] Furthermore, in this application, the step of obtaining a list of actual hardware components of the laptop computer to be configured further includes:

[0022] When it is identified that the laptop computer has hardware components connected via non-standard interfaces, or that information of some of the hardware components cannot be fully obtained via a standard scanning method due to firmware limitations, a supplementary hardware information acquisition process is activated;

[0023] The supplementary hardware information acquisition process includes: utilizing a pre-defined dedicated communication protocol or driver for the non-standard interface to interact with the hardware component connected to the non-standard interface to obtain its identification information; and / or querying a knowledge base containing known firmware limitations and corresponding information acquisition strategies, and using alternative detection methods or indirect information sources based on the query results to obtain information about the hardware components subject to the firmware limitations;

[0024] The hardware information obtained through the standard scanning method is combined and verified with the hardware information obtained through the supplementary hardware information acquisition process to form the actual hardware component list, thereby ensuring its completeness and accuracy.

[0025] Furthermore, in the present application, the step of parsing the metadata of each hardware configuration package in the candidate hardware configuration packages and determining a subset of hardware configuration packages to be finally applied and the order of applying each hardware configuration package in the subset from the candidate hardware configuration packages based on the dependency relationship, the conflict relationship, and the preset decision logic defined in the metadata includes:

[0026] When conflicting metadata declarations of multiple hardware configuration packages are identified and the preset decision logic cannot determine a unique choice based on a single priority value, or when conflict resolution requires specific goals of the current production task, obtaining external production goal parameters associated with the current production task;

[0027] Obtaining multi-dimensional priority information preset in metadata of each of the conflicting hardware configuration packages;

[0028] Calculating a comprehensive evaluation value for each conflicting hardware configuration package based on the external production target parameters and the multi-dimensional priority information in combination with predefined conflict resolution rules;

[0029] Based on the comprehensive evaluation value, one hardware configuration package is selected from the conflicting hardware configuration packages and included in the hardware configuration package subset of the final application, and the hardware configuration package subset of the final application and the application order of each hardware configuration package in the subset are further determined according to the dependency defined in the metadata and the preset decision logic.

[0030] Furthermore, in the present application, the steps of selecting one hardware configuration package from the conflicting hardware configuration packages based on the comprehensive evaluation value to be included in the hardware configuration package subset of the final application, and further determining the hardware configuration package subset of the final application and the application order of each hardware configuration package in the subset according to the dependency relationship defined in the metadata and the preset decision logic include:

[0031] After selecting one hardware configuration package from the conflicting hardware configuration packages based on the comprehensive evaluation value and incorporating it into the hardware configuration package subset of the final application, and before finally determining the application order, re-evaluating the dependencies between the hardware configuration package subset of the final application including the selected hardware configuration package and the remaining candidate hardware configuration packages, so as to identify new dependencies or potential secondary conflicts generated by the introduction of the selected hardware configuration package;

[0032] If it is identified that a newly added dependency is not satisfied or a secondary conflict exists, and the preset decision logic cannot resolve the newly added dependency or the secondary conflict, a preset adjustment strategy is triggered, which includes modifying the selection of other hardware configuration packages in the hardware configuration package subset of the final application, or adjusting the selection priority of subsequent candidate hardware configuration packages, so as to resolve the problem of the newly added dependency not being satisfied or the secondary conflict;

[0033] If the adjustment strategy cannot resolve the problem of unsatisfied newly added dependencies or the secondary conflict, the current configuration is marked as a high-risk configuration and a preset risk avoidance operation is performed, which includes falling back to selecting a suboptimal hardware configuration package among the conflicting hardware configuration packages or prompting manual intervention;

[0034] After the newly added dependency is satisfied and the secondary conflict is resolved, or after the risk avoidance operation has been performed, the application order of each hardware configuration package in the subset is finally determined based on the dependency defined in the updated hardware configuration package subset of the final application and its metadata and the preset decision logic.

[0035] Furthermore, in the present application, the step of screening out a group of candidate hardware configuration packages from a plurality of predefined hardware configuration packages based on the actual hardware component list includes:

[0036] Acquiring context parameters associated with the laptop to be configured, the context parameters including at least one of product series information, target market area information, or customer order specific requirement information;

[0037] Based on the actual hardware component list, screening out preliminary candidate hardware configuration packages from the predefined multiple hardware configuration packages, whose target hardware identifiers defined in their metadata match the hardware component identifiers in the actual hardware component list;

[0038] For each of the preliminary candidate hardware configuration packages, determining whether the hardware configuration package is applicable to the current configuration context based on the obtained context parameters and context applicability rules defined in the metadata of the hardware configuration package or a predefined context policy library;

[0039] The hardware configuration packages determined to be applicable are selected to form the set of candidate hardware configuration packages.

[0040] Furthermore, in the present application, the step of calculating a comprehensive evaluation value for each conflicting hardware configuration package based on the external production target parameters and the multi-dimensional priority information in combination with predefined conflict resolution rules includes:

[0041] For each of the conflicting hardware configuration packages, extract the multi-dimensional priority information from its metadata, where the multi-dimensional priority information includes the index values ​​or grade classifications of the hardware configuration package on multiple preset evaluation dimensions;

[0042] Based on the external production target parameter, a weight set or scoring rule corresponding to the external production target parameter is selected or generated from the predefined conflict resolution rule, wherein the weight set or scoring rule defines the importance of each evaluation dimension;

[0043] For each of the conflicting hardware configuration packages, the comprehensive evaluation value of the hardware configuration package under the external production target parameters is calculated by combining the weight set or scoring rules with the corresponding multi-dimensional priority information.

[0044] Furthermore, in this application, the OEM information includes at least one or more combinations of the following:

[0045] Preset desktop wallpapers, manufacturer support contact information displayed in system properties, and a set of preconfigured application shortcuts for specific regions.

[0046] Furthermore, in the present application, the external production target parameters include preset regional compliance requirements or cost control levels associated with the current notebook computer production batch.

[0047] In a second aspect, the present application further proposes an OEM information customization device, which includes:

[0048] The acquisition module is used to obtain the actual hardware component list of the laptop to be configured;

[0049] a screening module, configured to screen a group of candidate hardware configuration packages from a plurality of predefined hardware configuration packages based on the actual hardware component list, wherein each of the hardware configuration packages corresponds to one or more hardware components or a combination of hardware components and includes execution instructions for deploying its corresponding OEM information configuration and metadata, wherein the metadata defines one or more target hardware identifiers compatible with the hardware configuration package and rule information characterizing the interaction between the hardware configuration package and other hardware configuration packages, wherein the rule information includes at least dependency relationships for determining the application order between the hardware configuration packages and conflict relationships for identifying incompatible combinations of hardware configuration packages;

[0050] a decision module, configured to parse metadata of each hardware configuration package in the candidate hardware configuration packages, and determine a subset of hardware configuration packages to be ultimately applied and an application order of the hardware configuration packages in the subset from the candidate hardware configuration packages based on the dependency relationships and conflict relationships defined in the metadata and a preset decision logic;

[0051] An execution module is used to execute the execution instructions embedded in each hardware configuration package in the hardware configuration package subset of the final application in sequence according to the determined application order, so as to complete the configuration of OEM information matching the actual hardware component list of the laptop computer.

[0052] From the above, it can be seen that the OEM information customization method and device provided by this application obtains the actual hardware component list, filters the candidate configuration packages based on the list, parses the metadata and determines the final configuration package subset and application order based on rules and logic, and then executes the configuration instructions. It has the ability to adapt to changes in the actual hardware component list, select configuration packages based on the actual hardware component list, determine the application order of configuration packages based on rules, complete the configuration that matches the actual hardware component list, reduce configuration mismatches, support processing hardware combinations, automate configuration selection and application, and provide a configuration management structure. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] Figure 1 This is a flow chart of an OEM information customization method provided in this application.

[0054] Figure 2 This is a structural diagram of an OEM information customization device provided in this application.

[0055] In the figure: 210, acquisition module; 220, screening module; 230, decision module; 240, execution module. DETAILED DESCRIPTION

[0056] The technical solutions in this application will be clearly and completely described below in conjunction with the drawings in this application. Obviously, the described embodiments are only a part of the embodiments of this application, rather than all of the embodiments. The components of the present application generally described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application for which protection is claimed, but merely represents selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work are within the scope of protection of this application.

[0057] It should be noted that similar reference numerals and letters represent similar items in the following drawings. Therefore, once an item is defined in one drawing, it does not need to be further defined or explained in subsequent drawings. At the same time, in the description of this application, the terms "first", "second", etc. are only used to distinguish the description and should not be understood as indicating or implying relative importance.

[0058] In the traditional OEM information customization process of existing laptop production lines, faced with the normal situation that the actual assembled hardware components of the same model product are inconsistent with the standard configuration list, how to implement an automated, high-precision and efficient OEM information dynamic adaptation and writing mechanism that can handle complex hardware combinations to ensure that every laptop off the production line can obtain system drivers, firmware parameters and related configurations that fully match its unique, real-time hardware combination, thereby avoiding compatibility issues, functional abnormalities or performance degradation caused by improper configuration.

[0059] In this regard, refer to Figure 1 , this application proposes an OEM information customization method, the method comprising:

[0060] S110, obtaining a list of actual hardware components of the laptop computer to be configured;

[0061] S120. Based on the actual hardware component list, select a group of candidate hardware configuration packages from a plurality of predefined hardware configuration packages, wherein each hardware configuration package corresponds to one or more hardware components or a combination of hardware components and includes execution instructions for deploying its corresponding OEM information configuration and metadata, wherein the metadata defines one or more target hardware identifiers compatible with the hardware configuration package and rule information characterizing the interaction between the hardware configuration package and other hardware configuration packages, wherein the rule information includes at least dependency relationships for determining the application order of the hardware configuration packages and conflict relationships for identifying incompatible combinations of hardware configuration packages;

[0062] S130: Parse metadata of each hardware configuration package in the candidate hardware configuration packages, and determine a subset of hardware configuration packages to be ultimately applied and an application order of the hardware configuration packages in the subset based on dependencies and conflicts defined in the metadata and a preset decision logic.

[0063] S140 . Execute the execution instructions embedded in each hardware configuration package in the hardware configuration package subset of the final application in sequence according to the determined application order, so as to complete the configuration of OEM information matching the actual hardware component list of the notebook computer on the notebook computer.

[0064] The actual hardware component list refers to the hardware list actually assembled in the laptop to be configured, which can be obtained by scanning or querying. Its function is to provide the real hardware composition information of the device.

[0065] The predefined multiple hardware configuration packages refer to a library containing multiple hardware configuration solutions, which can be stored in a data structure and whose function is to provide optional configuration units.

[0066] The metadata of a hardware configuration package refers to the additional information in the hardware configuration package that describes its own properties and relationships. Specifically, it can be stored in a structured data format. Its function is to define the hardware to which the configuration package applies and the rules for interaction with other configuration packages.

[0067] Among them, the target hardware identification refers to one or more hardware identification information defined in the metadata that is compatible with the hardware configuration package. It can be specifically represented by a hardware ID or material code. Its function is to screen candidate configuration packages that match the actual hardware.

[0068] Among them, rule information refers to the information in the metadata that characterizes the interaction between hardware configuration packages. It can be specifically expressed by dependency and conflict relationships. Its role is to guide the selection and sorting of configuration packages.

[0069] The dependency relationship refers to the information in the rule information used to determine the application order between hardware configuration packages. Specifically, it can be represented by a pointing relationship, which ensures that the dependent configuration package is applied before the dependent configuration package.

[0070] The conflict relationship refers to information in the rule information used to identify incompatible hardware configuration package combinations, and can be specifically represented by a mutually exclusive relationship, which is used to avoid selecting incompatible configuration packages at the same time.

[0071] The preset decision logic refers to the rules or algorithms used to parse metadata and determine the final configuration plan. Specifically, it can be implemented using an algorithm or rule set, and its function is to intelligently select subsets from candidate packages and determine the application order.

[0072] The hardware configuration package subset finally applied refers to a set of configuration packages selected from the candidate hardware configuration packages and ultimately executed on the device. Specifically, the subset can be represented by a list, and its function is to determine the configuration scheme that matches the actual hardware.

[0073] The application order of each hardware configuration package in the subset refers to the execution order of each configuration package in the hardware configuration package subset of the final application, which can be specifically represented by an ordered list, and its function is to ensure that the dependency relationship is satisfied.

[0074] The execution instruction refers to the executable code or script contained in the hardware configuration package for deploying the OEM information configuration, which can be implemented by a script or program, and its function is to actually complete the configuration operation on the device.

[0075] The core innovation of this application lies in obtaining the actual hardware inventory of the device, and based on the hardware configuration package containing interaction rules, automatically selecting a subset of configuration packages that matches the actual hardware and determining their application order according to metadata and preset decision logic, and finally executing the configuration in sequence to achieve dynamic adaptation of OEM information.

[0076] The working process and principle of this application are as follows: first, a list of the actual hardware components of the laptop to be configured is obtained. This list contains the identification information of the various hardware components currently installed on the device. This provides the system with the basic data for accurate configuration, no longer relying solely on preset product model information.

[0077] Furthermore, based on the actual hardware component list obtained, a group of candidate hardware configuration packages are screened out from multiple pre-defined hardware configuration packages. Each hardware configuration package is designed to configure one or more specific hardware components or a combination thereof. These configuration packages contain execution instructions for actually deploying the OEM information configuration, as well as key metadata. The metadata defines the target hardware identifier to which the configuration package is adapted, ensuring that the screened candidate packages are associated with the actual hardware. In addition, the metadata also contains rule information that characterizes the interactions between configuration packages, such as dependencies for determining the order of application and conflict relationships for identifying incompatible combinations.

[0078] Next, the system parses the metadata for each of the candidate hardware configuration packages. Based on the dependencies and conflicts defined in the metadata and the pre-set decision logic, the system determines a subset of hardware configuration packages from the candidate hardware configuration packages for final application and the order in which the packages within this subset should be applied. This step is central to achieving automated and high-precision customization. By parsing metadata, the system can identify the constraints between configuration packages. Combined with the pre-set decision logic, the system can intelligently select an optimal combination of configuration packages and plan their correct application order, thus handling complex hardware combinations and interactions.

[0079] Finally, the instructions embedded in each hardware configuration package within the final application's hardware configuration package subset are executed sequentially, following the specified application order. These instructions complete the configuration of the laptop with OEM information that matches its actual hardware components. Strictly following the specified order ensures that dependencies are met and avoids configuration issues caused by incorrect execution order. Ultimately, the OEM configuration on the device precisely matches its actual hardware.

[0080] As a preferred embodiment, the solution of this application is specifically implemented as follows:

[0081] A laptop to be configured is connected to the custom system. The system first scans the laptop to obtain a list of its actual hardware components. For example, the list shows that the device is equipped with a specific CPU model, an SSD from a specific vendor, and a non-standard wireless network card.

[0082] Based on the actual hardware component list, the system filters through a predefined hardware configuration package library. The library contains configuration packages for different CPUs, different SSDs, different wireless network cards, etc. The screening process identifies a set of candidate configuration packages that match the hardware identifiers in the list. For example, the performance optimization package for the CPU, the firmware configuration package for the SSD, and the driver and firmware configuration package for the wireless network card are screened out. Each screened configuration package contains an execution script and metadata. For example, the metadata of the wireless network card driver package declares that it depends on the wireless network card firmware package, and the SSD firmware package conflicts with another general SSD optimization package.

[0083] The system parses the metadata of these candidate configuration packages. Based on the dependencies defined in the metadata (driver depends on firmware), conflict relationships (two SSD packages conflict), and preset decision logic (for example, giving priority to SSD firmware packages from specific vendors rather than general optimization packages), the system determines the subset of configuration packages that will be ultimately applied. For example, the subset is determined to include a CPU performance package, a specific SSD firmware package, a wireless network card firmware package, and a wireless network card driver package. At the same time, the order in which these packages are applied is determined, for example, the CPU package is applied first, then the SSD firmware package, then the wireless network card firmware package, and finally the wireless network card driver package.

[0084] Finally, the system executes the instructions embedded in each configuration package in the subset, following the predetermined application order. For example, the CPU performance optimization script executes first, followed by the SSD firmware update or configuration script, followed by the wireless network card firmware write instruction, and finally the wireless network card driver installation or configuration instruction. This completes the OEM configuration on the laptop, precisely matching its actual hardware component list.

[0085] Through the above solution, this application solves the problem of mismatch between OEM information and actual hardware in the OEM information customization link of the notebook computer production line, when the actual assembled hardware components are inconsistent with the standard configuration list, which is a normal situation. By obtaining the actual hardware component list of the device and performing intelligent screening, decision-making and orderly execution based on the hardware configuration package containing interaction rules, the dynamic adaptation and writing of OEM information is achieved. This ensures that every laptop computer off the production line can obtain system drivers, firmware parameters and related configurations that fully match its unique and real-time hardware combination. This avoids compatibility issues, functional failures or performance degradation caused by improper configuration, and improves the accuracy and reliability of the configuration. The solution can automatically handle complex hardware combination changes and dependency conflicts between configuration packages, improve production efficiency, and reduce reliance on manual intervention.

[0086] Specifically, the OEM information in this application includes at least one or a combination of the following: a preset desktop wallpaper, manufacturer support contact information displayed in system properties, or a set of preconfigured application shortcuts for a specific region.

[0087] The core purpose of the OEM information defined in this application, such as preset desktop wallpapers, manufacturer support contact information integrated into system properties, and pre-configured application shortcuts for specific regions, is to provide end users with an immediately visible branding experience, convenient after-sales support channels, and optimize the accessibility of regionalized applications, so that users can experience personalization and convenience when using the device for the first time, effectively improving overall user satisfaction.

[0088] In some of the above-mentioned solutions of the present application, a method is proposed for determining a subset of hardware configuration packages to be finally applied and their application order from candidate hardware configuration packages based on a preset decision logic. However, this preset decision logic is relatively fixed. When faced with ever-changing hardware combinations in actual production, rare configuration scenarios that may arise, or the need to adjust configuration strategies according to changing production goals (such as efficiency, cost, quality, etc.), the fixed decision logic may not be able to make the best or most reliable decision, resulting in the determined configuration scheme may not fully match the actual hardware, or perform poorly in certain complex conflict scenarios, thereby affecting the accuracy of the OEM information configuration and the quality of the final product.

[0089] In this regard, the present application further proposes the steps of parsing metadata of each hardware configuration package in the candidate hardware configuration packages, and determining a subset of hardware configuration packages to be ultimately applied and the order in which the hardware configuration packages in the subset are applied based on the dependencies, conflicts, and preset decision logic defined in the metadata, further comprising:

[0090] Collect historical configuration data, including the hardware configuration package subset selected for historical configuration, application order, actual hardware combination, and configuration results;

[0091] Analyze the execution efficiency of preset decision logic in different configuration scenarios based on historical configuration data;

[0092] Generate decision logic adjustment suggestions based on the execution efficiency obtained through analysis;

[0093] Update the preset decision logic based on the decision logic adjustment suggestions to adjust the behavior of the preset decision logic when handling new hardware combinations, rare configuration scenarios, or changing production goals.

[0094] Among them, by introducing a mechanism based on historical data feedback, the preset decision logic used to determine the final hardware configuration package subset and application order is dynamically optimized. First, historical configuration data is collected. This data includes the hardware configuration package subsets used in past actual configuration processes, the application order of these packages, the actual hardware combination of the device to be configured at that time, and the final configuration results. This historical data provides an empirical basis for evaluating and improving decision logic. For example, the input (actual hardware combination, candidate packages), decision process (selected subset, order), and output (configuration success / failure, error code, time consumption, etc.) of each configuration attempt can be recorded. This data can be stored in a database or log file.

[0095] Furthermore, based on this collected historical configuration data, the execution performance of the currently preset decision logic in different configuration scenarios is analyzed. This analysis process can identify the performance of the decision logic when handling specific hardware combinations, resolving conflicts, or determining orders, thereby discovering where it performs well and where it has shortcomings or can be improved. For example, the analysis can identify that in scenarios containing specific alternative hardware combinations, the subset of configuration packages selected by the decision logic leads to a high failure rate, or when handling a certain dependency conflict, the determined application order always leads to errors in subsequent steps. The analysis can use statistical methods or pattern recognition techniques.

[0096] Based on the analysis of execution performance, we generate recommendations for adjusting the decision logic. These recommendations are based on practical experience and are intended to optimize the behavior of the decision logic, enabling it to make better decisions in the future. For example, if the analysis reveals that a conflict resolution rule performs poorly in a specific scenario, recommendations might include modifying the priority weight of that rule or adding a new, more refined rule for that specific scenario. Recommendations can be generated automatically by the analysis system or by human experts based on the analysis report.

[0097] Finally, based on these generated decision logic adjustment suggestions, the preset decision logic is updated. In this way, the decision logic is no longer static, but can learn and evolve based on historical experience. This dynamically updated decision logic, combined with steps such as obtaining the actual hardware component list, screening candidate hardware configuration packages, and parsing metadata, enables the entire OEM information customization method to more accurately identify the hardware characteristics of the current device. Based on the continuously optimized decision logic, it selects the most matching subset from the candidate packages and determines the optimal application order. This combination enables the method to better adapt to new hardware combinations, handle rare configuration scenarios, and flexibly adjust its decision-making behavior based on changing production goals, improving the intelligence level of the entire OEM information customization method and its adaptability and reliability in complex and changing environments.

[0098] In some of the above-mentioned solutions of this application, it is proposed to obtain a list of actual hardware components of the laptop computer to be configured as the basis for subsequent screening of hardware configuration packages and determining the application order. However, in an actual production environment, some hardware components may be connected through non-standard interfaces, or their information may not be fully obtained through standard scanning methods due to firmware limitations, resulting in the inability to obtain a complete and accurate list of actual hardware components, which in turn affects the accuracy of subsequent OEM information configuration and may cause the configuration to not match the actual hardware.

[0099] In this regard, the present application further proposes that the step of obtaining a list of actual hardware components of the laptop to be configured further includes:

[0100] When it is identified that the laptop contains hardware components connected via non-standard interfaces, or that information about some hardware components cannot be fully obtained through standard scanning due to firmware limitations, a supplementary hardware information acquisition process is activated;

[0101] The supplemental hardware information acquisition process includes: utilizing a pre-defined dedicated communication protocol or driver for the non-standard interface to interact with the hardware component connected to the non-standard interface to obtain its identification information; and / or querying a knowledge base containing known firmware limitations and corresponding information acquisition strategies, and using alternative detection methods or indirect information sources based on the query results to obtain information about hardware components subject to firmware limitations;

[0102] The hardware information obtained through standard scanning methods is combined and verified with the hardware information obtained through the supplemental hardware information acquisition process to form an actual hardware component list to ensure its completeness and accuracy.

[0103] This solution refines and enhances the step of obtaining the actual hardware component list of the laptop to be configured. This aims to address the problem that standard scanning methods cannot obtain complete and accurate information when dealing with hardware connected via non-standard interfaces or hardware whose information is restricted by firmware.

[0104] By introducing a supplementary hardware information acquisition process and activating it when necessary, we ensure a complete and accurate list of actual hardware components, even in complex hardware environments. This provides a reliable foundation for subsequent hardware configuration package screening, application sequence determination, and ultimately OEM information customization based on this list.

[0105] Specifically, when the system attempts to obtain laptop hardware component information through standard hardware scanning methods (e.g., the device manager interface provided by the operating system, PCI scanning, USB enumeration, etc.), some hardware components may not be identified, or the identification information may be incomplete or inaccurate. This may be because these hardware components use non-standard physical interfaces or communication protocols, or their firmware design limits the exposure of complete identification or configuration information through standard methods.

[0106] When the system identifies the existence of such hardware components connected via non-standard interfaces, or when the information of some hardware components cannot be fully obtained through standard scanning methods, for example, the information of a specific model of embedded controller or customized sensor cannot be obtained through standard methods, the system will trigger and activate a supplementary hardware information acquisition process. Identification can be done by checking the return results of standard scans, such as whether there are unknown devices, device information fields that are empty or contain common identifiers, etc., or by using a pre-established hardware feature library to identify specific hardware types that are known to have acquisition problems.

[0107] This supplementary hardware information acquisition process provides a targeted solution. For hardware connected through non-standard interfaces, such as sensors, controllers, or security chips connected through I2C, SPI, or other custom buses, the system will use preset, dedicated communication protocols or drivers for these non-standard interfaces. These dedicated protocols or drivers can interact with hardware components connected to non-standard interfaces at a low level, send specific query commands, or read registers to obtain identification information of these hardware, such as vendor ID, device ID, model, serial number, or firmware version. For example, for a custom touchpad controller connected through the I2C bus, a specific I2C driver can be loaded, and commands can be sent through the driver to read the device ID and firmware version of the controller.

[0108] Furthermore, for hardware whose information cannot be fully retrieved through standard scanning methods due to firmware limitations—for example, the firmware of certain network adapters or storage devices may restrict access to detailed model or feature information through standard APIs—the system queries a knowledge base containing known firmware limitations and corresponding information retrieval strategies. This knowledge base pre-stores known information retrieval limitations for specific hardware models and firmware versions, and provides corresponding alternative detection methods or indirect information sources. Based on the query results, the system applies the strategies specified in the knowledge base to retrieve information. Alternative detection methods may include using vendor-specific tools, reading specific memory areas, or querying other system components associated with the hardware (such as the BIOS or management engine) to obtain indirect information. Indirect information sources include consulting manufacturing data associated with the hardware, serial number databases, or querying known information through the network. For example, the knowledge base may record that complete model information for a specific solid-state drive model cannot be obtained through standard interfaces, but can be obtained by reading its specific SMART attributes or using vendor-provided command-line tools.

[0109] Finally, the basic hardware information acquired through the standard scan is combined with the specialized hardware information obtained through the supplemental hardware information acquisition process. This combined information forms a more comprehensive and accurate list of actual hardware components. This combined list is then verified, for example, to check for duplicate entries, information consistency, and the completeness of key component information, to further ensure its completeness and accuracy. This supplemented and verified list of actual hardware components contains accurate information for all identifiable key hardware components in the laptop, including those difficult to obtain through standard methods. This accurate list serves as the foundation for subsequent steps, such as selecting candidate packages from predefined hardware configuration packages that match the actual hardware and determining the final application subset and order based on the metadata of these packages. By providing a complete and accurate hardware list, this solution enables the subsequent configuration process to precisely match the device's actual hardware configuration, thereby avoiding configuration errors caused by incomplete or inaccurate hardware information, improving the success rate of OEM information customization and the quality of the final product.

[0110] In some of the above-mentioned schemes of the present application, a method is proposed for parsing the metadata of candidate hardware configuration packages, and determining a subset of hardware configuration packages for final application and the application order of each hardware configuration package in the subset from the candidate hardware configuration packages based on the dependencies, conflict relationships and preset decision logic defined in the metadata. However, in this process, when the metadata declarations of multiple hardware configuration packages conflict with each other, if the preset decision logic only relies on a single priority value, it may not be possible to determine a selection; or, in some production scenarios, the resolution of the conflict needs to consider the specific goals or external factors of the current production task, and the existing preset decision logic lacks the ability to adjust and optimize according to the external context, resulting in a deviation between the configuration selection and the production goal in complex or specific scenarios.

[0111] In this regard, the present application further proposes parsing the metadata of each hardware configuration package in the candidate hardware configuration package, and determining a subset of hardware configuration packages for final application and the application order of each hardware configuration package in the subset from the candidate hardware configuration packages based on the dependency relationship, conflict relationship and preset decision logic defined in the metadata, including the following steps: when it is identified that the metadata declarations of multiple hardware configuration packages conflict with each other and the preset decision logic cannot determine a selection based on a single priority value, or when the conflict resolution needs to be based on the specific goal of the current production task, obtaining the external production target parameters associated with the current production task; obtaining the multi-dimensional priority information preset in the metadata of each conflicting hardware configuration package; calculating a comprehensive evaluation value for each conflicting hardware configuration package based on the external production target parameters and the multi-dimensional priority information, combined with the predefined conflict resolution rules; based on the comprehensive evaluation value, selecting a hardware configuration package from the conflicting hardware configuration packages to be included in the subset of hardware configuration packages for final application, and continuing to determine the subset of hardware configuration packages for final application and the application order of each hardware configuration package in the subset based on the dependency relationship defined in the metadata and the preset decision logic.

[0112] Among them, when a specific conflict scenario is identified, that is, when the metadata declarations of multiple hardware configuration packages conflict with each other, and the preset decision logic relies only on a single priority value and cannot determine a choice, or when the resolution of the conflict requires considering the specific goals of the current production task, a higher-level decision process is triggered. For example, on a production line, if two hardware configuration packages are found to be applicable to a hardware component, but they have the same single priority value, or if the current production task requires prioritizing cost over performance, this process will be initiated.

[0113] The process further retrieves external production target parameters associated with the current production task. These parameters can come from the Manufacturing Execution System (MES) or order information. For example, the production target for the current batch could be minimizing cost, maximizing performance, maximizing the activation rate of specific functions, or prioritizing the use of components from specific suppliers. For example, an external production target parameter could be a flag indicating "prioritize cost" or a list indicating "specific functional modules must be enabled."

[0114] At the same time, the process will obtain the multi-dimensional priority information preset in the metadata of each conflicting hardware configuration package. Unlike a single priority, multi-dimensional priority information provides a more detailed evaluation basis. For example, the metadata of a hardware configuration package may contain its priority values ​​or levels (such as high, medium, and low) in multiple dimensions such as "performance", "cost", "compatibility", and "stability". For example, a configuration package may have a priority of 90 in the performance dimension, a priority of 30 in the cost dimension, and a priority of 95 in the compatibility dimension.

[0115] Based on the acquired external production target parameters and multi-dimensional priority information, combined with predefined conflict resolution rules, a comprehensive evaluation value is calculated for each conflicting hardware configuration package. This calculation process combines the external target with the multi-dimensional priority information. For example, if the external production target is "prioritizing cost," the priority of the cost dimension will be given a higher weight when calculating the comprehensive evaluation value; if the external target is "maximizing performance," the priority weight of the performance dimension will be increased. The predefined conflict resolution rules can be a set of weight coefficients, a scoring function, or a decision matrix. For example, the comprehensive evaluation value can be calculated as: `Comprehensive evaluation value = weight_performance * priority_performance + weight_cost * priority_cost + ...`, where the weight values ​​are determined based on the external production target parameters.

[0116] Based on the calculated comprehensive evaluation values, select the hardware configuration package with the highest comprehensive evaluation value from the conflicting hardware configuration packages and include it in the final hardware configuration package subset for application. For example, if the calculation results show that the comprehensive evaluation value of configuration package A is 85 and the comprehensive evaluation value of configuration package B is 70, configuration package A is selected.

[0117] After selecting a hardware configuration package, the solution continues to determine the subset of hardware configuration packages for the final application and sort the order of application of each hardware configuration package in the subset based on the dependencies defined in the metadata and the preset decision logic. This part of the process is similar to the basic solution, but introduces more refined decision-making basis in the conflict resolution link. In this way, based on the basic solution's screening of candidate packages and identification of conflicts, the solution provides a mechanism for handling complex conflicts, so that when a single priority is not enough to make a decision or external factors need to be considered, a choice that better meets actual needs can be made. This decision-making process that combines external context and multi-dimensional information enhances the adaptability of configuration selection and solves the problem of deviation in configuration selection when the basic solution handles complex or specific scenarios.

[0118] In some of the above-mentioned solutions of this application, it is proposed to resolve hardware configuration package conflicts based on external production target parameters and multi-dimensional priority information and select one hardware configuration package to be included in the hardware configuration package subset for the final application, and then continue to determine the hardware configuration package subset for the final application and the application order of each hardware configuration package in the subset based on the dependencies defined in the metadata and the preset decision logic. However, after selecting one hardware configuration package from the conflicting hardware configuration packages based on the comprehensive evaluation value to be included in the hardware configuration package subset for the final application, the selected hardware configuration package may introduce new dependencies or generate potential secondary conflicts with the remaining candidate hardware configuration packages or other selected hardware configuration packages. The original preset decision logic may not fully consider or effectively resolve these new dependencies or secondary conflicts that only appear after the conflicts are resolved, resulting in an incomplete hardware configuration package subset, unsatisfied dependencies, or unresolved conflicts, which in turn affects the correctness and stability of the OEM information configuration.

[0119] In this regard, the present application further proposes that after selecting one hardware configuration package from the conflicting hardware configuration packages based on the comprehensive evaluation value and incorporating it into the hardware configuration package subset of the final application, and before finally determining the application order, the hardware configuration package subset of the final application containing the selected hardware configuration package and the remaining candidate hardware configuration packages are re-evaluated for dependencies, so as to identify new dependencies or potential secondary conflicts caused by the introduction of the selected hardware configuration package; if it is identified that the new dependencies are not satisfied or there are secondary conflicts, and the preset decision logic cannot resolve the new dependencies or secondary conflicts, the preset adjustment strategy is triggered, which includes modifying other hardware configuration packages in the hardware configuration package subset of the final application or adjust the selection priority of subsequent candidate hardware configuration packages to resolve the problem of unsatisfied new dependencies or secondary conflicts; if the adjustment strategy cannot resolve the problem of unsatisfied new dependencies or secondary conflicts, the current configuration is marked as a high-risk configuration, and a preset risk avoidance operation is performed, which includes falling back to the suboptimal hardware configuration package in the conflicting hardware configuration package or prompting manual intervention; after the new dependencies are satisfied and the secondary conflicts are resolved, or after the risk avoidance operation has been performed, the application order of each hardware configuration package in the subset is finally determined based on the updated final application hardware configuration package subset and the dependencies defined in its metadata and the preset decision logic.

[0120] After selecting a package from the conflicting hardware configuration packages based on a comprehensive evaluation and preliminarily including it in the final application subset, and before the final application order of these packages is determined, the solution performs a comprehensive dependency reassessment on the currently selected subset and any candidate packages that have not yet been selected. The purpose of this dependency reassessment is to proactively identify new dependencies or potential secondary conflicts that may arise from the addition of the newly selected hardware configuration package. New dependencies refer to packages that require support from other packages that may not have been selected or whose dependencies have not been considered. Potential secondary conflicts refer to new incompatibilities between the package and other packages in the subset or with the remaining candidate packages. This reassessment, performed before the final application order is determined, allows for the timely identification of global or subsequent issues that may arise from local conflict resolution decisions. For example, selected package A may depend on package X, which is not yet in the subset, or package A may have a version conflict with selected package B. The reassessment process traverses the packages in the subset and their metadata, checking whether their dependencies are in the subset or candidate set, and checking for conflict declarations between packages within the subset and between packages in the subset and candidate packages.

[0121] Furthermore, if the re-evaluation process identifies new unmet dependencies or secondary conflicts, and the existing pre-set decision logic is insufficient to automatically handle these emerging issues, the system triggers a pre-set adjustment strategy. This adjustment strategy is triggered because the standard logic cannot handle such complex situations, requiring a more flexible or specialized approach. The adjustment strategy involves modifying the selection of other hardware configuration packages in the initially selected subset. For example, it may select a package to satisfy the newly added dependency or replace or remove a package to avoid secondary conflicts. The adjustment strategy may also adjust the selection priority of the remaining candidate hardware configuration packages, for example, by increasing the priority of packages that can satisfy the newly added dependency or decreasing the priority of packages that conflict with the selected packages. These adjustments are intended to attempt to remediate issues introduced by the initial selection within the automated framework, ensuring the validity and compatibility of the final subset. For example, if selected package A is found to depend on package X, the adjustment strategy may attempt to add package X to the subset. Alternatively, if package A conflicts with package B, the adjustment strategy may attempt to remove package B or replace it with a compatible package C.

[0122] Furthermore, if the aforementioned adjustment strategy still fails to resolve unmet dependencies or secondary conflicts, this indicates a complex situation or deep-seated incompatibilities, making automated processing incapable of finding an effective solution. In this case, the system will mark the current configuration as high-risk and initiate a pre-defined risk mitigation action. This high-risk designation serves as a warning of potential issues. Risk mitigation is designed to prevent the deployment of a known problematic or uncertain configuration to a laptop. Risk mitigation actions include reverting to the suboptimal hardware configuration package selected during the initial conflict resolution, attempting another conflict resolution to see if this resolves further issues. Risk mitigation actions can also prompt manual intervention, referring the issue to a technician for manual analysis and decision-making, leveraging human experience to resolve complex or unusual situations. These risk mitigation measures ensure that safe and reliable exit or intervention mechanisms are available in the event of automated failure, preventing misconfiguration. For example, if the adjustment strategy fails to find a subset that satisfies package A's dependencies without introducing new conflicts, the system can either revert to the suboptimal package D selected during the initial conflict resolution and restart the subset determination process, or simply pause and prompt an operator for review.

[0123] Finally, only when the newly added dependencies are satisfied and the secondary conflicts are resolved and successfully handled through the adjustment strategy, or the risk avoidance operation has been executed, indicating that the problem has been handled through rollback or manual intervention, the system will finally determine the application order of each hardware configuration package in the subset based on the updated hardware configuration package subset of the final application and the dependencies and preset decision logic defined in its metadata. The order is determined based on the updated subset and metadata because the subset may have changed during the adjustment process, and the correct application sequence needs to be constructed based on the current valid package set. This step ensures that the final configuration application order is based on a verified set of hardware configuration packages with satisfied dependencies and resolved conflicts or avoidance measures.

[0124] In some of the above-mentioned schemes of the present application, it is proposed to screen candidate hardware configuration packages based on the actual hardware component list to preliminarily narrow the scope of configuration packages. However, screening based solely on hardware matching fails to consider the specific production context of the current laptop to be configured (such as product series, target market, customer order requirements, etc.). This may result in the screened candidate hardware configuration package set containing a large number of configuration packages that are hardware matched but are actually not suitable for the current production task, increasing the processing burden of subsequent analysis and decision-making, and reducing the matching degree and processing speed of the screening.

[0125] In this regard, the present application further proposes the steps of screening a set of candidate hardware configuration packages from a plurality of predefined hardware configuration packages based on the actual hardware component list, including:

[0126] Obtaining context parameters associated with the laptop to be configured, the context parameters including at least one of product series information, target market region information, or customer order specific requirement information;

[0127] Based on the actual hardware component list, screening out preliminary candidate hardware configuration packages from a plurality of predefined hardware configuration packages, wherein the target hardware identifier defined in the metadata thereof matches the hardware component identifier in the actual hardware component list;

[0128] For each of the preliminary candidate hardware configuration packages, determine whether the hardware configuration package is applicable to the current configuration context based on the obtained context parameters and the context applicability rules defined in the metadata of the hardware configuration package or a predefined context policy library;

[0129] The hardware configuration packages determined to be applicable are selected to form a group of candidate hardware configuration packages.

[0130] Among them, this solution is a further refinement and improvement of the step of screening candidate hardware configuration packages based on the actual hardware component list. Its basis is to introduce production context information as an additional basis for screening to improve the matching degree and processing speed of screening.

[0131] The solution first captures the specific OEM information requirements of the current production task by obtaining contextual parameters associated with the laptop to be configured, such as the product series, target market region, or customer order-specific requirements. These contextual parameters are non-hardware factors that affect the applicability of the configuration package. For example, product series information can be a string identifier such as "Latitude 7000 series"; target market region information can be a region code such as "EMEA"; and customer order-specific requirements information can be a Boolean flag or a specific configuration code. These parameters can be obtained from the Manufacturing Execution System (MES) or an associated production database.

[0132] Furthermore, based on the actual hardware component list, a preliminary screening is performed from multiple pre-defined hardware configuration packages to select hardware configuration packages whose target hardware identifiers defined in their metadata match the hardware component identifiers in the actual hardware component list, forming a preliminary set of candidate hardware configuration packages. This step ensures that the configuration packages selected in the preliminary screening are compatible at the hardware level and is a reflection of the basic screening logic. For example, if the actual hardware list contains a specific wireless network card module identifier, the preliminary screening will find all hardware configuration packages whose metadata contains this wireless network card module identifier.

[0133] Then, for each hardware configuration package in the preliminary candidate hardware configuration packages, it is determined whether the configuration package is actually applicable to the current configuration context based on the previously obtained context parameters and the context applicability rules defined in the metadata of the hardware configuration package or a predefined context policy library. The context applicability rules can be embedded in the metadata of each configuration package, such as a simple conditional expression. As a preferred embodiment, a predefined context policy library can be used, which centrally manages more complex applicability logic, such as a set of rules that make judgments based on a combination of multiple context parameters. The judgment process matches the context parameters with the rules or policy library to determine whether the configuration package is allowed to be applied in the current production environment. For example, a configuration package may be hardware-matched, but its rules state "not applicable to the EMEA market" or "only applicable to specific customer orders."

[0134] As a result, the hardware configuration packages that are determined to be applicable based on contextual applicability are selected to form a final set of candidate hardware configuration packages. This step further narrows the set of hardware-compatible configuration packages that were initially screened, removing those that should not be applied due to hardware mismatches. By introducing contextual filtering immediately after the initial screening, this solution allows the subsequent parsing and decision-making process to only process a smaller set of configuration packages that are highly relevant to the current production task. Compared to performing only hardware matching screening, this reduces the number of configuration packages that enter the subsequent complex processing steps, reduces the processing burden, and improves the processing speed and matching level of the entire OEM information customization process.

[0135] Furthermore, the present application proposes the steps of calculating a comprehensive evaluation value for each conflicting hardware configuration package based on external production target parameters and multi-dimensional priority information, combined with predefined conflict resolution rules, including: for each conflicting hardware configuration package, extracting multi-dimensional priority information from its metadata, the multi-dimensional priority information including the index value or grade division of the hardware configuration package in multiple preset evaluation dimensions; based on the external production target parameters, selecting or generating a weight set or scoring criteria corresponding to the external production target parameters from the predefined conflict resolution rules, the weight set or scoring criteria defining the importance of each evaluation dimension; for each conflicting hardware configuration package, combining the weight set or scoring criteria with its corresponding multi-dimensional priority information, calculating the comprehensive evaluation value of the hardware configuration package under the external production target parameters.

[0136] Among them, for each conflicting hardware configuration package, multi-dimensional priority information is extracted from its metadata. This information contains the index values ​​or grade divisions of the hardware configuration package on multiple preset evaluation dimensions. This process ensures that when evaluating the hardware configuration package, its characteristic data in multiple key aspects, such as cost, performance, compatibility, deployment complexity, etc., can be obtained. This multi-dimensional information can be stored in the metadata of the hardware configuration package in numerical form (such as performance score, cost amount) or grade form (such as compatibility level: high, medium, low). Extracting this information is the basis for comprehensive evaluation and provides data input for comprehensively measuring the applicability of the hardware package.

[0137] Furthermore, based on the external production target parameters, a weight set or scoring criteria corresponding to the external production target parameters is selected or generated from the predefined conflict resolution rules. The external production target parameters reflect the current production task requirements, such as whether to pursue the lowest cost, the best performance, or rapid deployment. The predefined conflict resolution rule base stores the relative importance of each evaluation dimension under different production goals. For example, when the external goal is "cost optimization", the rule may specify that the cost dimension has a higher weight; when the goal is "performance priority", the performance dimension weight increases. The weight set can be a set of numerical values ​​that represent the contribution ratio of each dimension in the total evaluation. The scoring criteria can define the scores corresponding to different levels (such as compatibility levels). The process of selecting or generating weight sets or scoring criteria enables the evaluation criteria to dynamically adapt to the current production goals, ensuring that the final evaluation results are closely related to actual needs.

[0138] Therefore, for each conflicting hardware configuration package, the comprehensive evaluation value of the hardware configuration package under the external production target parameters is calculated by combining the weight set or scoring rules with the corresponding multi-dimensional priority information. The calculation method can be to multiply the indicator value of each dimension (or convert the grade into a score) by its corresponding weight, and then add up the weighted scores of all dimensions to obtain the total evaluation value. For example, if the quantitative values ​​of a hardware package in the three dimensions of cost, performance, and compatibility are V_c, V_p, and V_comp respectively, and the weights under the current production target are W_c, W_p, and W_comp respectively, then the comprehensive evaluation value can be calculated as V_c*W_c+V_p*W_p+V_comp*W_comp. This calculation method combines the characteristics of the hardware package itself with the importance preference of the external production target, and the resulting comprehensive evaluation value quantifies the pros and cons of the hardware package in the current specific scenario.

[0139] This step of calculating the comprehensive evaluation value is combined with the overall method of identifying conflicts and determining the application subset and order based on the decision logic. This calculation step is triggered when multiple hardware configuration package conflicts are identified and the preset decision logic cannot determine a unique choice based on a single priority, or when a decision needs to be made based on the specific goals of the current production task. By calculating the comprehensive evaluation value of each conflicting package, the system can make a comparison based on these quantitative results to select the optimal hardware configuration package under the current external production goals to be included in the final application subset. This combination enables the entire OEM information customization method to make more flexible and more realistic decisions when dealing with complex conflicts and dynamic production needs, thereby improving the accuracy and efficiency of configuration.

[0140] Specifically, the external production target parameters of the present application include preset regional compliance requirements or cost control levels associated with the current notebook computer production batch.

[0141] In the OEM information customization method of this application, external production target parameters provide critical production and business-level guidance for automated configuration decisions (especially when resolving configuration conflicts), ensuring that the final configuration is precisely aligned with the current production task. Specifically, these parameters can include specific regional compliance requirements closely associated with a particular laptop production batch, such as the configuration standards that must be followed to meet the laws and regulations of the target sales region (such as specific software pre-installation specifications and environmental certification standards), thereby ensuring product market access and avoiding potential risks. At the same time, they can also include the specific cost control level of the production batch, such as "economical," "balanced," or "high-value experience," to guide the system in effectively balancing cost input and expected benefits when screening or combining OEM information configurations (such as selecting pre-installed software versions and whether to include certain value-added services), thereby meeting profit targets and competitive strategies under different market positioning. These external parameters associated with specific production batches enable this customization method to flexibly adapt to changing regulatory environments, market demands, and business objectives.

[0142] Secondly, refer to Figure 2 , this application also proposes an OEM information customization device, which includes:

[0143] An acquisition module 210 is used to obtain a list of actual hardware components of the notebook computer to be configured;

[0144] a screening module 220 configured to screen a group of candidate hardware configuration packages from a plurality of predefined hardware configuration packages based on the actual hardware component list, wherein each of the hardware configuration packages corresponds to one or more hardware components or a combination of hardware components and includes execution instructions for deploying the corresponding OEM information configuration and metadata, wherein the metadata defines one or more target hardware identifiers compatible with the hardware configuration package and rule information characterizing the interaction between the hardware configuration package and other hardware configuration packages, wherein the rule information includes at least dependency relationships for determining the application order between hardware configuration packages and conflict relationships for identifying incompatible combinations of hardware configuration packages;

[0145] A decision module 230 is configured to parse metadata of each hardware configuration package in the candidate hardware configuration packages and determine a subset of hardware configuration packages to be ultimately applied from the candidate hardware configuration packages and an application order of the hardware configuration packages in the subset based on the dependency relationships and conflict relationships defined in the metadata and a preset decision logic;

[0146] The execution module 240 is used to execute the execution instructions embedded in each hardware configuration package in the hardware configuration package subset of the final application in sequence according to the determined application order, so as to complete the configuration of OEM information matching the actual hardware component list of the laptop computer.

[0147] By obtaining the actual hardware component list, screening candidate configuration packages based on the list, parsing metadata and determining the final configuration package subset and application order based on rules and logic, and then executing configuration instructions, it has the ability to adapt to changes in the actual hardware component list, select configuration packages based on the actual hardware component list, determine the application order of configuration packages based on rules, complete the configuration that matches the actual hardware component list, reduce configuration mismatches, support processing hardware combinations, automate configuration selection and application, and provide a configuration management structure.

[0148] In addition, in some preferred embodiments, an OEM information customization device proposed in this application can perform any one of the steps in the above method.

[0149] The above description is merely an embodiment of the present application and is not intended to limit the scope of protection of the present application. For those skilled in the art, various modifications and variations of the present application are possible. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A method for customizing OEM information, characterized in that: The method comprises: Get the actual hardware component list of the laptop to be configured; Based on the actual hardware component list, a group of candidate hardware configuration packages is screened from a plurality of predefined hardware configuration packages, wherein each of the hardware configuration packages corresponds to one or more hardware components or a combination of hardware components and includes execution instructions for deploying the corresponding OEM information configuration and metadata, wherein the metadata defines one or more target hardware identifiers compatible with the hardware configuration package and rule information characterizing the interaction between the hardware configuration package and other hardware configuration packages, wherein the rule information includes at least dependency relationships for determining the application order between the hardware configuration packages and conflict relationships for identifying incompatible combinations of hardware configuration packages; Parsing metadata of each hardware configuration package in the candidate hardware configuration packages, and determining a subset of hardware configuration packages to be ultimately applied and an application order of the hardware configuration packages in the subset from the candidate hardware configuration packages based on the dependency relationships, the conflict relationships, and a preset decision logic defined in the metadata; According to the determined application order, the execution instructions embedded in each hardware configuration package in the hardware configuration package subset of the final application are executed in sequence to complete the configuration of OEM information matching the actual hardware component list of the laptop computer.

2. The OEM information customization method according to claim 1, characterized in that: The step of parsing metadata of each hardware configuration package in the candidate hardware configuration packages and determining a subset of hardware configuration packages to be finally applied and an application order of each hardware configuration package in the subset from the candidate hardware configuration packages based on the dependency relationship, the conflict relationship, and a preset decision logic defined in the metadata further includes: Collecting historical configuration data, including a subset of hardware configuration packages selected for historical configuration, an application sequence, an actual hardware combination, and configuration results; Analyzing the execution efficiency of the preset decision logic in different configuration scenarios based on the historical configuration data; Generating decision logic adjustment suggestions based on the execution efficiency obtained through analysis; The preset decision logic is updated according to the decision logic adjustment suggestion to adjust the behavior of the preset decision logic when processing new hardware combinations, rare configuration scenarios, or changed production targets.

3. The OEM information customization method according to claim 1, characterized in that: The step of obtaining a list of actual hardware components of the laptop to be configured further includes: When it is identified that the laptop computer has hardware components connected via non-standard interfaces, or that information of some of the hardware components cannot be fully obtained via a standard scanning method due to firmware limitations, a supplementary hardware information acquisition process is activated; The supplementary hardware information acquisition process includes: utilizing a pre-defined dedicated communication protocol or driver for the non-standard interface to interact with the hardware component connected to the non-standard interface to obtain its identification information; and / or querying a knowledge base containing known firmware limitations and corresponding information acquisition strategies, and using alternative detection methods or indirect information sources based on the query results to obtain information about the hardware components subject to firmware limitations; The hardware information obtained through the standard scanning method is combined and verified with the hardware information obtained through the supplementary hardware information acquisition process to form the actual hardware component list, thereby ensuring its completeness and accuracy.

4. The OEM information customization method according to claim 1, characterized in that: The step of parsing metadata of each hardware configuration package in the candidate hardware configuration packages and determining a subset of hardware configuration packages to be finally applied and an application order of each hardware configuration package in the subset from the candidate hardware configuration packages based on the dependency relationship, the conflict relationship, and a preset decision logic defined in the metadata includes: When conflicting metadata declarations of multiple hardware configuration packages are identified and the preset decision logic cannot determine a unique choice based on a single priority value, or when conflict resolution requires specific goals of the current production task, obtaining external production goal parameters associated with the current production task; Obtaining multi-dimensional priority information preset in metadata of each of the conflicting hardware configuration packages; Calculating a comprehensive evaluation value for each conflicting hardware configuration package based on the external production target parameters and the multi-dimensional priority information in combination with predefined conflict resolution rules; Based on the comprehensive evaluation value, one hardware configuration package is selected from the conflicting hardware configuration packages and included in the hardware configuration package subset of the final application, and the hardware configuration package subset of the final application and the application order of each hardware configuration package in the subset are further determined according to the dependency defined in the metadata and the preset decision logic.

5. The OEM information customization method according to claim 4, characterized in that: The steps of selecting, based on the comprehensive evaluation value, one hardware configuration package from the conflicting hardware configuration packages to be incorporated into the hardware configuration package subset of the final application, and further determining the hardware configuration package subset of the final application and the application order of each hardware configuration package in the subset according to the dependency relationship defined in the metadata and the preset decision logic include: After selecting one hardware configuration package from the conflicting hardware configuration packages based on the comprehensive evaluation value and incorporating it into the hardware configuration package subset of the final application, and before finally determining the application order, re-evaluating the dependencies between the hardware configuration package subset of the final application including the selected hardware configuration package and the remaining candidate hardware configuration packages, so as to identify new dependencies or potential secondary conflicts generated by the introduction of the selected hardware configuration package; If it is identified that a newly added dependency is not satisfied or a secondary conflict exists, and the preset decision logic cannot resolve the newly added dependency or the secondary conflict, a preset adjustment strategy is triggered, which includes modifying the selection of other hardware configuration packages in the hardware configuration package subset of the final application, or adjusting the selection priority of subsequent candidate hardware configuration packages, so as to resolve the problem of the newly added dependency not being satisfied or the secondary conflict; If the adjustment strategy cannot resolve the problem of unsatisfied newly added dependencies or the secondary conflict, the current configuration is marked as a high-risk configuration and a preset risk avoidance operation is performed, which includes falling back to selecting a suboptimal hardware configuration package among the conflicting hardware configuration packages or prompting manual intervention; After the newly added dependency is satisfied and the secondary conflict is resolved, or after the risk avoidance operation has been performed, the application order of each hardware configuration package in the subset is finally determined based on the dependency defined in the updated hardware configuration package subset of the final application and its metadata and the preset decision logic.

6. The OEM information customization method according to claim 1, characterized in that: The step of selecting a group of candidate hardware configuration packages from a plurality of predefined hardware configuration packages based on the actual hardware component list includes: Acquiring context parameters associated with the laptop to be configured, the context parameters including at least one of product series information, target market area information, or customer order specific requirement information; Based on the actual hardware component list, screening out preliminary candidate hardware configuration packages from the predefined multiple hardware configuration packages, whose target hardware identifiers defined in their metadata match the hardware component identifiers in the actual hardware component list; For each of the preliminary candidate hardware configuration packages, determining whether the hardware configuration package is applicable to the current configuration context based on the obtained context parameters and context applicability rules defined in the metadata of the hardware configuration package or a predefined context policy library; The hardware configuration packages determined to be applicable are selected to form the set of candidate hardware configuration packages.

7. The OEM information customization method according to claim 4, characterized in that: The step of calculating a comprehensive evaluation value for each conflicting hardware configuration package based on the external production target parameters and the multi-dimensional priority information in combination with predefined conflict resolution rules includes: For each of the conflicting hardware configuration packages, extract the multi-dimensional priority information from its metadata, where the multi-dimensional priority information includes the index values ​​or grade classifications of the hardware configuration package on multiple preset evaluation dimensions; Based on the external production target parameter, a weight set or scoring rule corresponding to the external production target parameter is selected or generated from the predefined conflict resolution rule, wherein the weight set or scoring rule defines the importance of each evaluation dimension; For each of the conflicting hardware configuration packages, the comprehensive evaluation value of the hardware configuration package under the external production target parameters is calculated by combining the weight set or scoring rules with the corresponding multi-dimensional priority information.

8. The OEM information customization method according to claim 1, characterized in that: The OEM information includes at least one or more of the following: Preset desktop wallpapers, manufacturer support contact information displayed in system properties, and a set of preconfigured application shortcuts for specific regions.

9. The OEM information customization method according to claim 4, characterized in that: The external production target parameters include preset region-specific compliance requirements or cost control levels associated with the current notebook computer production batch.

10. An OEM information customization device, characterized in that: The device includes: The acquisition module is used to obtain the actual hardware component list of the laptop to be configured; a screening module, configured to screen a group of candidate hardware configuration packages from a plurality of predefined hardware configuration packages based on the actual hardware component list, wherein each of the hardware configuration packages corresponds to one or more hardware components or a combination of hardware components and includes execution instructions for deploying its corresponding OEM information configuration and metadata, wherein the metadata defines one or more target hardware identifiers compatible with the hardware configuration package and rule information characterizing the interaction between the hardware configuration package and other hardware configuration packages, wherein the rule information includes at least dependency relationships for determining the application order between the hardware configuration packages and conflict relationships for identifying incompatible combinations of hardware configuration packages; a decision module, configured to parse metadata of each hardware configuration package in the candidate hardware configuration packages, and determine a subset of hardware configuration packages to be ultimately applied and an application order of the hardware configuration packages in the subset from the candidate hardware configuration packages based on the dependency relationships and conflict relationships defined in the metadata and a preset decision logic; An execution module is used to execute the execution instructions embedded in each hardware configuration package in the hardware configuration package subset of the final application in sequence according to the determined application order, so as to complete the configuration of OEM information matching the actual hardware component list of the laptop computer.

Images