Data packet generation method, apparatus, device, and product

Abstract

The application discloses a data packet generation method, device, equipment and product. The method comprises the following steps: analyzing a configuration snapshot to obtain a configuration object; obtaining a complete configuration data object based on an option identifier in the configuration object; structurally assembling the complete configuration data object according to a preset data architecture template to generate a structured description document; extracting a resource reference in the structured description document to obtain a corresponding physical file, so as to generate a structured data packet based on the structured description document and the physical file. The application reduces the labor cost.

Description

Technical Field

[0001] This application relates to the field of computer technology, and more specifically, to a data packet generation method, apparatus, device, and product. Background Technology

[0002] After a user interacts with an online product configuration system, the output is usually just a simple list of option IDs or unstructured form data. While this data reflects the user's final choice, it lacks machine-readable semantic information, complete attribute descriptions, and precise association with underlying digital assets (such as CAD models, process documents, material codes, etc.).

[0003] Currently, to generate PDF or Excel reports for human readers, the system fills in the predefined template with the configuration options submitted by the user along with basic descriptive information, and outputs documents that focus on presentation.

[0004] However, the data generated by the above methods lacks correlation and relies on manual interpretation, resulting in low efficiency. Summary of the Invention

[0005] The main purpose of this application is to provide a data packet generation method, apparatus, device, or product that reduces labor costs and improves the efficiency and effectiveness of data packet generation.

[0006] To achieve the above objectives, firstly, this application provides a data packet generation method, comprising: Parse the configuration snapshot to obtain the configuration object; Retrieve the complete configuration data object based on the option identifier in the configuration object; The complete configuration data object is structurally assembled according to the preset data architecture template to generate a structured description document; Extract resource references from the structured description document and obtain the corresponding physical files to generate structured data packages based on the structured description document and the physical files.

[0007] In one embodiment, the configuration snapshot is parsed to obtain a configuration object, including: Perform data integrity verification on the configuration snapshot; If the verification passes, the configuration snapshot will be parsed to extract the field content from the configuration snapshot. The extracted field content is instantiated according to the preset internal data structure to generate a configuration object.

[0008] In one embodiment, obtaining a complete configuration data object based on option identifiers in the configuration object includes: Using the option identifier in the configuration object as an index, retrieve the corresponding complete digital definition unit in the product digital master data; By associating the complete digital definition unit with the option identifier, a complete configuration data object is obtained.

[0009] In one embodiment, using the option identifier in the configuration object as an index, the corresponding complete digital definition unit in the product digital master data is obtained, including: Iterate through each option identifier in the configuration object, use each option identifier as a unique matching key to perform a matching query in the product digital master data, extract all field data that match each option identifier, and obtain the complete digital definition record corresponding to each option identifier; The complete digital definition record is extracted as an independent data unit, and each option identifier is used as the associated primary key of the independent data unit to obtain the complete digital definition unit corresponding to each option identifier.

[0010] In one embodiment, a complete digital definition unit is associated with an option identifier to obtain a complete configuration data object, including: Using the option identifier as the primary key, the field content in the complete digital definition unit is merged with the corresponding option entry in the configuration object to generate a complete configuration data item corresponding to each option identifier; The complete configuration data items corresponding to each option identifier are summarized to obtain a complete configuration data object.

[0011] In one embodiment, the complete configuration data object is structurally assembled according to a preset data architecture template to generate a structured description document, including: Load the preset data architecture template, which defines the field structure, data types, hierarchical relationships, and grouping logic of the output document; According to the preset data architecture template, the complete configuration data items in the complete configuration data object are filled into the corresponding field positions in the preset data architecture template, and the filled data items are classified and organized according to the grouping logic defined in the preset data architecture template to obtain the classified and organized data items. Based on the hierarchical relationship defined by the preset data architecture template, the categorized and organized data items are processed into a structured serialization process to generate a machine-readable structured description document.

[0012] In one embodiment, resource references are extracted from the structured description document to obtain the corresponding physical file, and a structured data packet is generated based on the structured description document and the physical file, including: Parse the structured description document and extract all resource paths that point to the physical file from the structured description document; The paths in all resource paths are deduplicated, and the physical files corresponding to the deduplicated resource paths are obtained from the file storage system. The structured description document is packaged with the physical file to generate a structured data package.

[0013] Secondly, embodiments of this application provide a data packet generation apparatus, including: The parsing module is used to parse the configuration snapshot to obtain the configuration object; The data object acquisition module is used to obtain the complete configuration data object based on the option identifier in the configuration object; The assembly module is used to structurally assemble complete configuration data objects according to a preset data architecture template and generate a structured description document. The data packet generation module is used to extract resource references from the structured description document, obtain the corresponding physical files, and generate structured data packets based on the structured description document and the physical files.

[0014] Thirdly, embodiments of this application provide a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of any of the methods described above.

[0015] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of any of the methods described above.

[0016] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the steps of any of the methods described above.

[0017] This application provides a data packet generation method, apparatus, device, and product, including: parsing a configuration snapshot to obtain a configuration object; obtaining a complete configuration data object based on option identifiers in the configuration object; assembling the complete configuration data object in a structured manner according to a preset data architecture template to generate a structured description document; extracting resource references from the structured description document to obtain the corresponding physical file, and generating a structured data packet based on the structured description document and the physical file. This application parses configuration snapshots into intermediate configuration objects and automatically associates them with backend digital master data using option identifiers as indexes. This yields a complete configuration data object containing full technical attributes, relationships, and version information, fundamentally bridging the semantic gap between simple option records and engineering data requirements, ensuring the depth and accuracy of output information. Subsequently, it performs structured assembly according to a pre-defined standardized data architecture template, resulting in a highly consistent, predictable, and machine-readable structured description document that can be directly parsed and consumed without manual secondary processing or interpretation. Simultaneously, by automatically extracting resource references from this description document and accurately collecting corresponding physical files, it integrates structured metadata with entity resources, effectively avoiding the persistent problems of scattered storage, omissions, or version mismatches of resource files. Finally, this method automatically and faithfully converts simple user configuration selections into a self-contained, self-describing structured data package that can directly drive downstream CAD, ERP, PLM, and other systems, significantly reducing manual conversion costs and error risks. Attached Figure Description

[0018] The accompanying drawings, which form part of this application, are used to provide a further understanding of the application and to make other features, objects, and advantages of the application more apparent. The illustrative embodiments and descriptions of this application are used to explain the application and do not constitute an undue limitation of the application. In the drawings: Figure 1 This is a flowchart illustrating a data packet generation method provided in an embodiment of this application; Figure 2 This is a flowchart illustrating another data packet generation method provided in an embodiment of this application; Figure 3 This is a schematic diagram of the structure of a data packet generation device provided in an embodiment of this application; Figure 4 This is a schematic diagram of the computer device provided in the embodiments of this application. Detailed Implementation

[0019] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0020] The terms "first," "second," "third," "fourth," etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein.

[0021] In the embodiments of this application, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0022] It should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0023] It should be understood that in this application, "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to such process, method, product or device.

[0024] It should be understood that in this application, "multiple" refers to two or more. "And / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, "and / or B" can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "Contains A, B, and C", "Contains A, B, and C" means that all three A, B, and C are contained; "Contains A, B, or C" means that one of A, B, and C is contained; "Contains A, B, and / or C" means that any one, two, or three of A, B, and C are contained.

[0025] It should be understood that in this application, "B corresponding to A", "B corresponding to A", "A corresponds to B", or "B corresponds to A" means that B is associated with A, and B can be determined based on A. Determining B based on A does not mean determining B solely based on A; B can also be determined based on A and / or other information. Matching A and B is defined as a similarity between A and B that is greater than or equal to a preset threshold.

[0026] Depending on the context, "if" as used here can be interpreted as "when," "when," "in response to determination," or "in response to detection."

[0027] The data involved in this application may be data authorized by the tester or fully authorized by all parties. The collection, dissemination, and use of the data shall comply with the relevant laws, regulations and standards of the relevant countries and regions. The implementation methods / executives of this application may be combined with each other.

[0028] It is understood that in the specific embodiments of this application, data such as user information are involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0029] The technical solutions of this application will be described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments.

[0030] After user interaction, online product configuration systems typically output only a simple list of option IDs or unstructured form data. While this data reflects the user's final choice, it lacks machine-readable semantic information, complete attribute descriptions, and precise correlation with underlying digital assets (such as CAD models, process documents, and material codes). In modern manufacturing, product configuration results need to be directly parsed and automatically used by multiple downstream business systems, including design, production, procurement, and cost. This gap between lightweight output and the demands of engineering data prevents configuration systems from truly driving backend processes, creating a "dead end" in the product data chain at the configuration stage. Therefore, a technological means is urgently needed to automatically transform configuration records generated by user interaction into high-value, executable data assets.

[0031] The most readily available solutions fall into two main categories: one generates human-readable PDF or Excel reports, where the system populates user-submitted configuration options along with basic descriptive information into a predefined template, outputting a presentation-focused document; the other returns simple JSON objects via a REST API, typically just wrapping a list of configuration item IDs or a small number of queried names and returning them directly to the front end. Both methods are designed for human-readable presentation or minimal data exchange, relying on a flattened, superficial data presentation of the configuration results. They do not consider the backend system's needs for data integrity, semantic depth, and resource relevance during automatic processing, essentially remaining a continuation of traditional report generation or lightweight interface responses.

[0032] The aforementioned existing technologies suffer from three fundamental flaws: First, the output results lack deep semantics and correlation, containing only surface text or ID information, and lacking standard codes, complete technical attributes, version numbers, and precise mapping relationships with digital resources (models, drawings, process documents) for configuration items. This prevents downstream systems from automatically retrieving or calling relevant resources, requiring manual interpretation and creating "data silos." Second, the data model is flat and incomplete, only presenting a simple list structure, unable to express the complex logic of hierarchy, combination, and dependency between configuration items. It also lacks a large number of non-display parameters crucial to production, forcing downstream applications to manually supplement, map, and restructure the data after receiving it, resulting in low efficiency and easy introduction of biases. Third, resource files and configuration data are stored separately. Existing methods cannot automatically and accurately associate physical files with configuration items and perform version verification when generating output, leading to scattered, missing, or mismatched deliverables. This prevents the formation of a self-contained, offline-transferable complete product definition, fundamentally hindering the automation of configuration results in design, manufacturing, and procurement processes.

[0033] To address the aforementioned problems, this application proposes a data packet generation method.

[0034] Please see Figure 1 , Figure 1 This is a flowchart illustrating a data packet generation method provided in an embodiment of this application. Figure 1 As shown, it includes the following steps: Step S101: Parse the configuration snapshot to obtain the configuration object.

[0035] In one embodiment, parsing a configuration snapshot to obtain a configuration object includes: performing data integrity verification on the configuration snapshot; if the verification passes, parsing the format of the configuration snapshot and extracting the field content from the configuration snapshot; and instantiating the extracted field content according to a preset internal data structure to generate a configuration object.

[0036] Specifically, after the front-end user completes the product configuration and triggers the submit operation, the front-end application serializes the current configuration state object into a JSON string and sends it to the back-end data packet generation interface via an HTTPS POST request. This JSON string is the configuration snapshot.

[0037] Upon receiving the request, the backend interface first performs a data integrity check on the configuration snapshot. This verifies whether the snapshot contains necessary fields, such as the product basic identifier and option selection list, whether the data types of each field meet expectations, and whether the option identifier contains any empty or invalid values. Simultaneously, it performs a permission check on the caller sending the request, verifying whether it has the authority to generate the data packet.

[0038] After successful verification, the configuration snapshot is parsed to extract its field content, including the product basic identifier and an option selection list containing option identifiers and category information. The extracted field content is instantiated according to a preset internal data structure to generate an in-memory configuration object. This configuration object includes a first field for storing the product basic identifier, a second field for storing the option identifier list, and a third field for storing the mapping relationship between option categories and option identifiers, for subsequent processing. This embodiment ensures the legality and integrity of the input configuration snapshot data through multiple verification mechanisms, including integrity verification, permission verification, and format parsing, thereby improving the accuracy and security of data processing.

[0039] Step S102: Obtain the complete configuration data object based on the option identifier in the configuration object.

[0040] In one embodiment, obtaining a complete configuration data object based on the option identifier in the configuration object includes: using the option identifier in the configuration object as an index to obtain the corresponding complete digital definition unit in the product digital master data; associating the complete digital definition unit with the option identifier to obtain the complete configuration data object.

[0041] The process of retrieving the corresponding complete digital definition unit in the product digital master data, using the option identifier in the configuration object as an index, includes: traversing each option identifier in the configuration object, performing a matching query in the product digital master data with each option identifier as a unique matching key, extracting all field data that match each option identifier, and obtaining the complete digital definition record corresponding to each option identifier; extracting the complete digital definition record as an independent data unit, and using each option identifier as the association primary key of the independent data unit, to obtain the complete digital definition unit corresponding to each option identifier.

[0042] The process of associating complete digital definition units with option identifiers to obtain complete configuration data objects includes: using the option identifier as the association primary key, merging the field contents in the complete digital definition unit with the corresponding option entries in the configuration object to generate a complete configuration data item corresponding to each option identifier; and summarizing the complete configuration data items corresponding to each option identifier to obtain a complete configuration data object.

[0043] Specifically, after obtaining the configuration object, the operation of retrieving the corresponding complete digital definition unit in the product digital master data is first performed, using the option identifier in the configuration object as an index.

[0044] Specifically, each option identifier in the configuration object is traversed, and each currently traversed option identifier is used as a unique matching key to perform an exact match query in the product digital master data. This product digital master data is stored in a centralized master data management system, and each option identifier and its corresponding complete digital definition record are associated and stored through a unified resource identifier or key-value pair method. During the query, using the option identifier as the unique matching key, all field data matching the option identifier is extracted to obtain the complete digital definition record corresponding to that option identifier. This complete digital definition record includes at least a globally unique code, a set of technical attributes (including display attributes and non-display attributes, such as weight, power consumption, and interface specifications), a version number, a lifecycle status (effective date, approval status), associated resource paths (including 3D model file paths and 2D drawing paths), material codes, process node numbers, and cost center information, as well as metadata such as the creator and update time.

[0045] Then, the complete digital definition records obtained from the query are extracted as independent data units, and the option identifier is used as the associated primary key of the data unit to obtain complete digital definition units that correspond one-to-one with each option identifier.

[0046] After obtaining the complete digital definition unit, it is associated with the option identifier in the configuration object to generate a complete configuration data object. Specifically, using the option identifier as the association primary key, the field contents of each field in the complete digital definition unit are merged with the corresponding option entries in the configuration object. The field values ​​of each field in the complete digital definition unit are then filled into the corresponding extended field positions of the option entries, generating complete configuration data items that correspond one-to-one with each option identifier. This complete configuration data item includes the option identifier, all field contents of the complete digital definition unit corresponding to the option identifier (globally unique code, technical attribute set, version number, lifecycle status, associated resource path, material code, process node number, etc.), and the original selection information corresponding to the option identifier in the configuration object. The complete configuration data items corresponding to each option identifier are summarized and arranged according to the original arrangement order in the configuration object or according to the preset grouping rules in the complete digital definition unit to generate a combined data structure containing all complete configuration data items, resulting in the complete configuration data object. During the traversal and merging process, the relationships and dependencies between each complete configuration data item are reconstructed or verified based on the logical relationships between options defined in the complete digital definition unit (e.g., "Option A depends on Option B") to ensure the logical consistency between configuration data, thereby transforming and expanding simple user selection records into complete configuration data objects containing complete engineering, material, and manufacturing semantics.

[0047] Step S103: Assemble the complete configuration data object in a structured manner according to the preset data architecture template to generate a structured description document.

[0048] In one embodiment, the complete configuration data object is structurally assembled according to a preset data architecture template to generate a structured description document, including: Load the preset data architecture template, which defines the field structure, data types, hierarchical relationships, and grouping logic of the output document; According to the preset data architecture template, the complete configuration data items in the complete configuration data object are filled into the corresponding field positions in the preset data architecture template, and the filled data items are classified and organized according to the grouping logic defined in the preset data architecture template to obtain the classified and organized data items. Based on the hierarchical relationship defined by the preset data architecture template, the categorized and organized data items are processed into a structured serialization process to generate a machine-readable structured description document.

[0049] Specifically, the process begins by loading a pre-defined data architecture template. This template is a definition file in JSON Schema, XML Schema, or Domain-Specific Language (DSL) format, pre-defining the field structure, data types, hierarchical relationships, and grouping logic of the final structured description document. After loading this template, the structured assembly engine populates the corresponding field positions in the template with each complete configuration data item from the complete configuration data object, according to the template's definition. During the population process, the populated data items are categorized and organized according to the grouping logic defined in the data architecture template. For example, they may be grouped by "space," and each group may be further subdivided by "profession." Each configuration item includes fields such as identifier, code, attribute set, and model file path, as required by the template.

[0050] After the data items are categorized and organized, they are processed into a structured serialization based on the hierarchical relationship defined in the data architecture template, generating a machine-readable structured description document (such as configuration_spec.json). This structured description document contains product composition information, specification parameters of each component, and logical relationships between components. It precisely describes "what products are composed of which specific parts, what the detailed specifications of each part are, and how they are related." It is an unambiguous digital definition of product configuration that can be parsed by any downstream system, serving as the "brain" and "directory" of the entire data package.

[0051] Step S104: Extract resource references from the structured description document and obtain the corresponding physical files to generate a structured data package based on the structured description document and the physical files.

[0052] In one embodiment, extracting resource references from a structured description document and obtaining the corresponding physical file to generate a structured data packet based on the structured description document and the physical file includes: parsing the structured description document and extracting all resource paths in the structured description document that point to the physical file; deduplicating the paths in all resource paths and obtaining the physical file corresponding to the deduplicated resource path from the file storage system; and packaging the structured description document and the physical file to generate a structured data packet.

[0053] Specifically, after obtaining the structured description document, the resource file collector first parses the document to extract all resource paths pointing to physical files (such as model file paths and drawing file paths). All extracted resource paths are deduplicated to prevent the same file from being collected repeatedly. Version verification and permission checks can also be performed on the resource paths to ensure that the correct version of the physical file is obtained and that the user has the necessary access permissions.

[0054] Then, based on the deduplicated resource paths, the corresponding physical file entities are retrieved from distributed file storage systems (such as Object Storage Service (OSS) and Network Attached Storage (NAS)) and pulled to a temporary packaging workspace. After the files are retrieved, the structured description document and all the retrieved physical files are placed in a temporary folder, and packaged into a single structured data package file (such as ProjectX_Config_20231027.zip) using a standard compression library (such as ZIP), thus achieving integrated packaging of "description document + physical resources". The generated structured data package can be stored in a specified location, and an index record is created in the database to record the metadata of the data package (including project identifier, generation time, user information, and storage path). At the same time, the download link or storage information of the data package can be returned to the front-end caller or directly pushed to the preset downstream business system interface.

[0055] In an alternative embodiment, instead of packaging physical files, an online data package index containing structured description documents and secure access links to all resource files can be generated for downstream systems to retrieve files on demand, adapting to large file or cloud collaboration scenarios.

[0056] The final delivered structured data package is a complete, self-contained, offline-transferable digital product package. Once any downstream system obtains this package, it can decompress it and read the structured description documents within to obtain a complete digital definition of the product, and access all related design and process resources as needed, achieving "out-of-the-box" data access.

[0057] Please see Figure 2 , Figure 2 This is a flowchart illustrating another data packet generation method provided in an embodiment of this application. Figure 2 As shown, it includes: like Figure 2 As shown, the method is divided into three stages: input and parsing, data enrichment and association, and structured assembly and packaging. Each stage is connected sequentially to form a data conversion pipeline from lightweight configuration snapshots to complete structured data packages.

[0058] During the input and parsing phase, the system first receives the final configuration snapshot submitted by the front end. This snapshot is structured data in JSON format, containing a list of option IDs and basic product identification information. Subsequently, the configuration snapshot parser parses and performs basic validation (including data integrity and permission checks) on the received JSON data, converting the parsed data into a configuration object in memory for use in subsequent processing steps.

[0059] During the data enrichment and association phase, the configuration snapshot parser passes the parsed configuration objects to the data enrichment processing flow. The system iterates through each option ID in the configuration snapshot, using the currently accessed option ID as the query key to query the product digital master database. The product digital master database stores complete digital definition records for each configurable option, containing far more fields than required for front-end display. The system performs an exact match query using the option ID as the unique matching key to obtain the complete digital definition unit of that option. This unit includes standard codes, full attributes, version information, associated file resource paths, material codes, process node numbers, and other complete information. The system merges the retrieved complete digital definition records with the corresponding option entries in the configuration snapshot, using the option ID as the association primary key to form a list of "enriched configuration item" objects that correspond one-to-one with each option ID. This transforms simple user selection records into rich data objects containing complete engineering, material, and manufacturing semantics.

[0060] During the structured assembly and packaging phase, the structured assembly engine receives the aforementioned list of enriched configuration item objects. Following a predefined architecture template (such as JSON Schema), it structurally assembles each data item in the list. Based on the template's defined field structure, data type, hierarchical relationships, and grouping logic (such as spatial grouping or professional subdivision), it fills each data item into the corresponding position in the template and performs serialization processing, generating a machine-readable structured description document (such as config.json). This structured description document serves as the "brain" and "directory" of the entire data package, precisely describing the product's composition structure, the detailed specifications of each component, and the logical relationships between them. Subsequently, the resource file collector parses the structured description document, extracts all resource paths pointing to physical files, collects the corresponding physical file entities (including 3D model files, 2D drawing files, etc.) from the file repository based on these resource paths, and packages the structured description document and all collected physical files to generate the final structured data package (such as a ZIP format compressed package). This delivers a complete, self-contained, offline-transferable digital product package for direct parsing and use by downstream systems.

[0061] This application provides a data packet generation method, including: parsing a configuration snapshot to obtain a configuration object; obtaining a complete configuration data object based on the option identifier in the configuration object; assembling the complete configuration data object in a structured manner according to a preset data architecture template to generate a structured description document; extracting resource references from the structured description document to obtain the corresponding physical file, and generating a structured data packet based on the structured description document and the physical file. This application parses configuration snapshots into intermediate configuration objects and automatically associates them with backend digital master data using option identifiers as indexes. This yields a complete configuration data object containing full technical attributes, relationships, and version information, fundamentally bridging the semantic gap between simple option records and engineering data requirements, ensuring the depth and accuracy of output information. Subsequently, it performs structured assembly according to a pre-defined standardized data architecture template, resulting in a highly consistent, predictable, and machine-readable structured description document that can be directly parsed and consumed without manual secondary processing or interpretation. Simultaneously, by automatically extracting resource references from this description document and accurately collecting corresponding physical files, it integrates structured metadata with entity resources, effectively avoiding the persistent problems of scattered storage, omissions, or version mismatches of resource files. Finally, this method automatically and faithfully converts simple user configuration selections into a self-contained, self-describing structured data package that can directly drive downstream CAD, ERP, PLM, and other systems, significantly reducing manual conversion costs and error risks.

[0062] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0063] The following are device embodiments of this application. For details not described in detail, please refer to the corresponding method embodiments described above.

[0064] Figure 3 This diagram illustrates a data packet generation apparatus according to an embodiment of this application. For ease of explanation, only the parts relevant to the embodiment of this application are shown. The data packet generation apparatus includes: Parsing module 301 is used to parse the configuration snapshot to obtain the configuration object; The data object acquisition module 302 is used to acquire the complete configuration data object based on the option identifier in the configuration object; Assembly module 303 is used to perform structured assembly of complete configuration data objects according to a preset data architecture template, and generate a structured description document; The data packet generation module 304 is used to extract resource references from the structured description document, obtain the corresponding physical file, and generate a structured data packet based on the structured description document and the physical file.

[0065] In one embodiment, the parsing module 301 is further configured to perform data integrity verification on the configuration snapshot; If the verification passes, the configuration snapshot will be parsed to extract the field content from the configuration snapshot. The extracted field content is instantiated according to the preset internal data structure to generate a configuration object.

[0066] In one embodiment, the data object acquisition module 302 is further configured to acquire the corresponding complete digital definition unit in the product digital master data by using the option identifier in the configuration object as an index; By associating the complete digital definition unit with the option identifier, a complete configuration data object is obtained.

[0067] In one embodiment, the data object acquisition module 302 is further configured to traverse each option identifier in the configuration object, use each option identifier as a unique matching key to perform a matching query in the product digital master data, extract all field data that match each option identifier, and obtain the complete digital definition record corresponding to each option identifier. The complete digital definition record is extracted as an independent data unit, and each option identifier is used as the associated primary key of the independent data unit to obtain the complete digital definition unit corresponding to each option identifier.

[0068] In one embodiment, the data object acquisition module 302 is further configured to use the option identifier as the association primary key to merge the field content in the complete digital definition unit with the corresponding option entry in the configuration object to generate a complete configuration data item corresponding to each option identifier; The complete configuration data items corresponding to each option identifier are summarized to obtain a complete configuration data object.

[0069] In one embodiment, the assembly module 303 is further configured to load a preset data architecture template, wherein the data architecture template defines the field structure, data type, hierarchical relationship and grouping logic of the output document; According to the preset data architecture template, the complete configuration data items in the complete configuration data object are filled into the corresponding field positions in the preset data architecture template, and the filled data items are classified and organized according to the grouping logic defined in the preset data architecture template to obtain the classified and organized data items. Based on the hierarchical relationship defined by the preset data architecture template, the categorized and organized data items are processed into a structured serialization process to generate a machine-readable structured description document.

[0070] In one embodiment, the data packet generation module 304 is further configured to parse the structured description document and extract all resource paths pointing to physical files in the structured description document; The paths in all resource paths are deduplicated, and the physical files corresponding to the deduplicated resource paths are obtained from the file storage system. The structured description document is packaged with the physical file to generate a structured data package.

[0071] This application provides a data packet generation apparatus, specifically used for: parsing a configuration snapshot to obtain a configuration object; obtaining a complete configuration data object based on the option identifier in the configuration object; assembling the complete configuration data object in a structured manner according to a preset data architecture template to generate a structured description document; extracting resource references from the structured description document to obtain the corresponding physical file, and generating a structured data packet based on the structured description document and the physical file. This application parses configuration snapshots into intermediate configuration objects and automatically associates them with backend digital master data using option identifiers as indexes. This yields a complete configuration data object containing full technical attributes, relationships, and version information, fundamentally bridging the semantic gap between simple option records and engineering data requirements, ensuring the depth and accuracy of output information. Subsequently, it performs structured assembly according to a pre-defined standardized data architecture template, resulting in a highly consistent, predictable, and machine-readable structured description document that can be directly parsed and consumed without manual secondary processing or interpretation. Simultaneously, by automatically extracting resource references from this description document and accurately collecting corresponding physical files, it integrates structured metadata with entity resources, effectively avoiding the persistent problems of scattered storage, omissions, or version mismatches of resource files. Finally, this method automatically and faithfully converts simple user configuration selections into a self-contained, self-describing structured data package that can directly drive downstream CAD, ERP, PLM, and other systems, significantly reducing manual conversion costs and error risks.

[0072] This application Figure 4 A schematic diagram of a computer device is provided. (Example) Figure 4 As shown, the computer device 4 in this embodiment includes a processor 401, a memory 402, and a computer program 404 stored in the memory 402 and executable on the processor 401. When the processor 401 executes the computer program 404, it implements the steps in the various data packet generation method embodiments described above, for example... Figure 1 Steps 101 to 104 are shown. Alternatively, when processor 401 executes computer program 404, it implements the functions of each module / unit in the above-described embodiments of the data packet generation apparatus, for example... Figure 3 The functions of modules / units 301 to 304 shown.

[0073] This application also provides a readable storage medium storing a computer program, which, when executed by a processor, is used to implement the data packet generation method provided in the various embodiments described above.

[0074] The readable storage medium can be a computer storage medium or a communication medium. A communication medium includes any medium that facilitates the transfer of computer programs from one location to another. A computer storage medium can be any available medium accessible to a general-purpose or special-purpose computer. For example, a readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application-Specific Integrated Circuit (ASIC). Alternatively, the ASIC can be located in a user equipment. Of course, the processor and the readable storage medium can also exist as discrete components in a communication device. The readable storage medium can be a read-only memory (ROM), random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0075] This application also provides a program product including executable instructions stored in a readable storage medium. At least one processor of the device can read the executable instructions from the readable storage medium, and the execution of the executable instructions by the at least one processor causes the device to implement the data packet generation methods provided in the various embodiments described above.

[0076] In the embodiments of the above-described device, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this application can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.

[0077] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A data packet generation method, characterized in that, include: Parse the configuration snapshot to obtain the configuration object; Based on the option identifiers in the configuration object, obtain the complete configuration data object; The complete configuration data object is structurally assembled according to a preset data architecture template to generate a structured description document; Extract resource references from the structured description document to obtain the corresponding physical files, and generate a structured data package based on the structured description document and the physical files.

2. The data packet generation method as described in claim 1, characterized in that, The process of parsing the configuration snapshot to obtain the configuration object includes: Perform data integrity verification on the configuration snapshot; If the verification passes, the configuration snapshot is parsed to extract the field content from the configuration snapshot; The extracted field content is instantiated according to a preset internal data structure to generate the configuration object.

3. The data packet generation method as described in claim 1, characterized in that, The step of obtaining the complete configuration data object based on the option identifier in the configuration object includes: Using the option identifier in the configuration object as an index, obtain the corresponding complete digital definition unit in the product digital master data; Associating the complete digital definition unit with the option identifier yields a complete configuration data object.

4. The data packet generation method as described in claim 3, characterized in that, The step of retrieving the corresponding complete digital definition unit in the product digital master data using the option identifier in the configuration object as an index includes: Iterate through each option identifier in the configuration object, use each option identifier as a unique matching key to perform a matching query in the product digital master data, extract all field data that match each option identifier, and obtain the complete digital definition record corresponding to each option identifier; The complete digital definition record is extracted as an independent data unit, and each option identifier is used as the associated primary key of the independent data unit to obtain the complete digital definition unit corresponding to each option identifier.

5. The data packet generation method as described in claim 4, characterized in that, The step of associating the complete digital definition unit with the option identifier to obtain a complete configuration data object includes: Using the option identifier as the association primary key, the field content in the complete digital definition unit is merged with the corresponding option entry in the configuration object to generate a complete configuration data item corresponding to each option identifier; The complete configuration data items corresponding to each option identifier are summarized to obtain a complete configuration data object.

6. The data packet generation method as described in claim 1, characterized in that, The step of assembling the complete configuration data object in a structured manner according to a preset data architecture template to generate a structured description document includes: Load the preset data architecture template, wherein the data architecture template defines the field structure, data type, hierarchical relationship and grouping logic of the output document; According to the preset data architecture template, the complete configuration data items in the complete configuration data object are filled into the corresponding field positions in the preset data architecture template, and the filled data items are classified and organized according to the grouping logic defined in the preset data architecture template to obtain the classified and organized data items; The data items after being categorized and organized are processed into a structured serialization based on the hierarchical relationship defined by the preset data architecture template, generating a machine-readable structured description document.

7. The data packet generation method as described in claim 1, characterized in that, The step of extracting resource references from the structured description document and obtaining the corresponding physical files, to generate a structured data package based on the structured description document and the physical files, includes: The structured description document is parsed to extract all resource paths pointing to physical files from the structured description document; The paths in all the resource paths are deduplicated, and the physical files corresponding to the deduplicated resource paths are obtained from the file storage system. The structured description document and the physical file are packaged together to generate the structured data package.

8. A data packet generation apparatus, characterized in that, include: The parsing module is used to parse the configuration snapshot to obtain the configuration object; The data object acquisition module is used to acquire the complete configuration data object based on the option identifier in the configuration object; The assembly module is used to structurally assemble the complete configuration data object according to a preset data architecture template, and generate a structured description document; The data packet generation module is used to extract resource references from the structured description document, obtain the corresponding physical files, and generate structured data packets based on the structured description document and the physical files.

9. A computer device, characterized in that, Includes a memory, and one or more processors communicatively connected to the memory; The memory stores instructions that can be executed by the one or more processors to cause the one or more processors to implement the data packet generation method as described in any one of claims 1 to 7.

10. A computer program product, characterized in that, The method includes a computer program that, when executed by a processor, implements the data packet generation method according to any one of claims 1 to 7.

Images