Second-hand server and part traceability method, device, medium and electronic equipment

Abstract

The application relates to a second-hand server and part tracing method and device, a medium and electronic equipment, and relates to the technical field of data processing. The method comprises the following steps: in the recycling warehouse-in stage, a special OID corresponding to a target recycling object is generated according to an enterprise special root node OID, and the original SN code and basic information of the target recycling object are obtained; the special OID is taken as a primary key field, the original SN code is taken as a business index field, and the basic information is combined to construct a traceability file corresponding to the target recycling object; in the whole life cycle circulation process of the target recycling object, business data of multiple circulation links in the circulation is collected, and life cycle traceability data is obtained according to the traceability file and the business data; and in response to a terminal traceability query request, corresponding life cycle traceability data is output to the terminal according to the special OID. The application has the effect of solving the problem of second-hand server and part traceability distortion.

Description

Technical Field

[0001] This application relates to the field of data processing technology, specifically to a method, apparatus, medium, and electronic equipment for tracing used servers and components. Background Technology

[0002] With the rapid development of the digital economy and the accelerating pace of data center computing power iteration, a large number of outdated servers are being phased out and delisted. This has spurred the rapid rise of the second-hand server and major component recycling industry, which aligns perfectly with the national policies of digital transformation and green circular economy development. Currently, this industry is still in a stage of extensive development, lacking a unified and authoritative traceability system, which seriously hinders the industry's standardization and upgrading.

[0003] Currently, the industry commonly uses proprietary identifiers such as enterprise-built serial numbers (SNs), QR codes, and RFID for equipment management, which has significant drawbacks. These proprietary identifiers lack unified national standards, are not universally applicable across domains, and are easily tampered with and forged. This results in low reliability of equipment usage history, fault and maintenance records, leading to inaccurate traceability of used servers and components. Summary of the Invention

[0004] To address the problem of distorted traceability of used servers and components, this application provides a method, apparatus, medium, and electronic device for tracing used servers and components.

[0005] The first aspect of this application provides a method for tracing used servers and components, specifically including: Obtain the enterprise-specific root node OID corresponding to the target enterprise; During the recovery and warehousing phase, based on the enterprise-specific root node OID, a unique OID corresponding to the target recycling object is generated, and the native SN code and basic information of the target recycling object are obtained. The target recycling object is the target server or target component to be recycled. The unique OID is used as the primary key field, the native SN code is used as the business index field, and the source traceability file corresponding to the target recycling object is constructed by combining the basic information; During the entire lifecycle of the target recyclable object, business data from multiple stages of the process are collected, and lifecycle traceability data is obtained based on the traceability file and the business data. In response to the terminal's traceability query request, the corresponding lifecycle traceability data is output to the terminal based on the unique OID.

[0006] Obtain the unique root node OID of the target enterprise. During the asset recovery and warehousing process, generate a unique OID for each target recovery object (target server or target component) based on this enterprise-specific root node OID. Simultaneously collect the native SN code and basic information of the target recovery object. Use the tamper-proof, enterprise-controlled unique OID as the primary key of the traceability file, and the native SN code, used only for business retrieval purposes, as the auxiliary business index field. Combined with the asset's basic information, build a unique traceability file for the target recovery object. Isolate the subject identification failure problem caused by the tampering of the native SN code from the underlying field architecture of the file. Continuously collect business flow data generated at each stage of the entire lifecycle, including server and component warehousing, inspection, refurbishment, and secondary warehousing. Based on the pre-established... The system integrates and links all transaction data to form complete and continuous full lifecycle traceability data. When a terminal initiates a traceability query request, the system uses a unique, globally unique, and tamper-proof OID, endorsed by the enterprise's root node, as the core index to retrieve and push the complete lifecycle traceability data to the terminal. This solution establishes a unique and trustworthy identity for assets by deriving a unique OID from the enterprise's private root node, weakening the core positioning role of the easily tampered native SN code and retaining only its retrieval auxiliary function. The entire process is linked by the unique OID to connect all transaction records from asset recovery to secondary circulation, avoiding the distortion of asset origin and transaction trajectory traceability caused by SN code forgery and replacement. This ensures the integrity and trustworthiness of the traceability chain for each second-hand server and component, effectively solving the problem of traceability distortion for second-hand servers and components.

[0007] In one implementation, generating a unique OID corresponding to the target reclaimed object based on the enterprise-specific root node OID specifically includes: Based on the object type of the target recycling object, a matching type segment code is determined, and the target server and the target component each correspond to different type segment codes; Based on the date the target recycled object is returned to the warehouse, generate a batch code for the warehouse entry time, and obtain the unique incremental sequence code of the target recycled object; The enterprise-specific root node OID, the type segment code, the entry time batch code, and the unique incremental sequence code are concatenated sequentially to obtain the unique OID corresponding to the target recycling object.

[0008] In one implementation, obtaining lifecycle traceability data based on the traceability archive and the business data specifically includes: When the entire machine is disassembled during the circulation process, an independent OID is generated for each disassembled component based on the enterprise-specific root node OID. Using the independent OID of a single disassembled component as the primary key field and the SN code of a single disassembled component as the business retrieval field, a corresponding component traceability file is constructed. The exclusive OID of the target server is recorded in the component traceability file, and a bidirectional traceability association is established between the independent OID and the exclusive OID of the target server. The disassembly time and operator identification of each disassembled component are recorded in the corresponding component traceability file to obtain lifecycle traceability data.

[0009] In one implementation, generating independent OIDs for disassembled components based on the enterprise-specific root node OID specifically includes: Obtain the unique type segment code of the disassembled parts; Based on the disassembly date of the disassembled parts, a disassembly time batch code is generated, and the unique incremental sequence code of the disassembled parts is obtained. The enterprise-specific root node OID, the specific type segment code, the disassembly time batch code, and the specific incremental sequence code are concatenated sequentially to obtain the independent OID corresponding to the disassembled component.

[0010] In one implementation, obtaining lifecycle traceability data based on the traceability archive and the business data further includes: When the process involves assembling the complete machine, a new complete machine OID is generated for the assembled new complete machine, and the component OIDs of each assembled part in the assembled new complete machine are obtained. Write the OIDs of each component into the BOM configuration list of the traceability file corresponding to the OID of the new complete machine to obtain lifecycle traceability data.

[0011] In one implementation, the step of using the unique OID as the primary key field, the native SN code as the business index field, and combining the basic information to construct the traceability file corresponding to the target recycling object specifically includes: When the target object to be recycled is the target server, the exclusive OID is stored as the primary key field and the native SN code is stored as the business index field in the preset initial whole machine traceability file; The basic information is collected and attached to the primary key file corresponding to the primary key field in the initial whole machine traceability file by using the preset association fields, so as to obtain the traceability file corresponding to the target recycling object.

[0012] In one implementation, the step of using the unique OID as the primary key field, the native SN code as the business index field, and combining the basic information to construct the traceability file corresponding to the target reclaimed object further includes: When the target recycling object is a target component, the exclusive OID is stored as the primary key field and the native SN code is stored as the business index field in the preset initial component traceability file; In the initial component traceability file, the whole machine OID to which the target component belongs is recorded through a preset historical traceability field, and the basic information is archived in the initial component traceability file to obtain the traceability file corresponding to the target recycling object.

[0013] A second aspect of this application provides a traceability device for used servers and components, specifically including: The information acquisition module is used to obtain the enterprise-specific root node OID corresponding to the target enterprise; The OID generation module is used to generate a unique OID corresponding to the target recycling object based on the enterprise-specific root node OID during the recycling and warehousing stage, and to obtain the native SN code and basic information of the target recycling object, which is the target server or target component to be recycled. The traceability and filing module is used to construct the traceability file corresponding to the target recycling object by using the exclusive OID as the primary key field, the native SN code as the business index field, and combining the basic information. The data collection module is used to collect business data from multiple circulation stages during the entire life cycle circulation of the target recycling object, and obtain life cycle traceability data based on the traceability file and the business data. The data traceability module is used to respond to the traceability query request from the terminal and output the corresponding lifecycle traceability data to the terminal based on the unique OID.

[0014] A third aspect of this application provides a computer-readable storage medium storing a computer program that, when loaded and executed by a processor, performs the steps of the method described in any one of the first aspects.

[0015] A fourth aspect of this application provides an electronic device, specifically comprising: A processor, a memory, and a computer program stored in the memory and capable of running on the processor, the processor being configured to load and execute the computer program stored in the memory to cause the electronic device to perform the method as described in any one of the first aspects.

[0016] In summary, this application includes at least one of the following beneficial technical effects: the entire process of asset transfer records from recycling to secondary circulation is linked by a unique OID, avoiding the distortion of asset origin and transfer trajectory due to SN code forgery and replacement, ensuring the integrity and credibility of the traceability chain for each second-hand server and component, and effectively solving the problem of traceability distortion of second-hand servers and components. Attached Figure Description

[0017] Figure 1 This is a flowchart illustrating a method for tracing used servers and components provided in an embodiment of this application; Figure 2 This is a schematic diagram of the system architecture of a method for tracing used servers and components provided in an embodiment of this application; Figure 3 This is a schematic diagram of the structure of a used server and component traceability device provided in an embodiment of this application; Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0018] Explanation of reference numerals in the attached diagram: 11. Information acquisition module; 12. OID generation module; 13. Traceability and filing module; 14. Data collection module; 15. Data traceability module; 201. Processor; 202. Memory; 203. Bus; 204. Network interface. Detailed Implementation

[0019] To enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification 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.

[0020] In the description of the embodiments of this application, words such as "exemplarily," "for example," or "for instance" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplarily," "for example," or "for instance" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of words such as "exemplarily," "for example," or "for instance" is intended to present the relevant concepts in a specific manner.

[0021] In the description of the embodiments of this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, B existing alone, or A and B existing simultaneously. Furthermore, unless otherwise stated, the term "multiple" means two or more. For example, multiple systems refer to two or more systems, and multiple screen terminals refer to two or more screen terminals. In addition, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the indicated technical features. Thus, a feature defined with "first" or "second" may explicitly or implicitly include one or more of that feature. The terms "comprising," "including," "having," and their variations all mean "including but not limited to," unless otherwise specifically emphasized.

[0022] See Figure 1 This application discloses a flowchart illustrating a method for tracing used servers and components. This method can be implemented using a computer program or run on a used server and component tracing device based on the von Neumann architecture. The computer program can be integrated into an application or run as a standalone utility application, specifically including: S101: Obtain the enterprise-specific root node OID corresponding to the target enterprise.

[0023] Specifically, in this step, the target company submits its qualification certification materials to the National OID Registry Center. These materials include, but are not limited to, the company's business license, unified social credit code certificate, operating license for the recycling of used servers, and a power of attorney from the legal representative. After receiving the above materials, the National OID Registry Center conducts a compliance review of the target company's qualifications and business scope. Once the review is approved, the center issues a globally unique enterprise-specific root node OID to the target company and writes the enterprise-specific root node OID and its corresponding filing information into the root node filing database of the National OID Registry Center, thus completing the official registration. The data format of the enterprise-specific root node OID follows the hierarchical dotted decimal notation of the ISO / IEC 9834-1 international standard. Its complete coding structure is composed of the national unified OID prefix and the enterprise-specific registration root segment concatenated sequentially, specifically represented as "national unified OID prefix.enterprise-specific registration root segment". The national unified OID prefix is ​​a fixed prefix segment "1.2.156" shared by all registered entities in China (1 represents the ISO identification system, 2 represents ISO member body, and 156 represents the Chinese country code). The enterprise-specific registration root segment is a unique numerical code segment assigned to the target enterprise by the national OID registration center, such as "12345". The complete instance of the enterprise-specific root node OID obtained by the target enterprise is "1.2.156.12345". After obtaining its own root node OID, the target enterprise stores the root node code, registration time, validity status identifier, and official communication credentials for interacting with the national OID registration center in its local root node management data table. All subsequent sub-OID codes generated for recycled equipment or parts are hierarchically extended based on this enterprise-specific root node OID, ensuring that all sub-codes form a hierarchical relationship with the root node, inheriting global uniqueness and officially resolvable characteristics. OID, short for Object Identifier, is an internationally recognized and universally accepted identification system issued by ISO. The national OID registration center uniformly manages domestic root nodes and possesses the characteristics of global uniqueness, national authority, immutability, and cross-national / cross-industry resolvability. It is a trusted identification infrastructure officially recognized domestically and capable of connecting to the international market.

[0024] It should be noted that by connecting to the national-level OID registration system to obtain an officially authoritative root node identifier, all subsequent sub-codes generated for second-hand servers and components will have national-level credit endorsement and cross-industry mutual recognition capabilities, fundamentally solving the problem that the existing private identifier system lacks unified standards and cross-domain universality.

[0025] Furthermore, the execution entity of the second-hand server and component traceability method disclosed in this application is a cloud server, which is wirelessly connected to the recycling personnel's terminal, the user's terminal, and a PDA handheld terminal. The recycling personnel's terminal has an application related to the second-hand server and component traceability system installed. The cloud server can be understood as the system server. The terminal is a smartphone or personal computer. When a server or component is being recycled, an activation command is initiated through the recycling personnel's terminal. Then, the native serial number and basic information (including some manually entered basic information) are obtained through the PDA handheld terminal, and the lifecycle traceability data is determined accordingly. Finally, based on the traceability query request sent by the user's terminal, the corresponding lifecycle traceability data is output. For details, please refer to [link to relevant documentation]. Figure 2 .

[0026] S102: During the recovery and warehousing phase, based on the enterprise's exclusive root node OID, generate the exclusive OID corresponding to the target recovery object, and obtain the original SN code and basic information of the target recovery object. The target recovery object is the target server or target component to be recovered.

[0027] Specifically, in this step, when the target recycling object completes physical acceptance and enters the recycling and warehousing stage, the operator uses a PDA handheld terminal to scan the original SN code label on the surface of the target recycling object. The system automatically extracts the string information of the original SN code through optical character recognition and temporarily stores it. Subsequently, the operator supplements the basic information of the target recycling object through the system input interface. This basic information includes equipment brand, equipment model, hardware specifications, manufacturing date, appearance condition level, recycling source channel and hardware configuration list.

[0028] After obtaining the native SN code and basic information, the system determines the matching type segment code based on the object type of the target recycling object. The mapping relationship between object type and type segment code is pre-configured in the system's encoding rule configuration table. This configuration table is defined by the enterprise's technical management personnel during the system initialization and deployment phase based on the actual range of equipment categories that the enterprise is recycling and operating, and is persistently stored in the database. The specific mapping rules are as follows: the type segment code is "01" when the target recycling object is a server, "02" when it is a CPU, "03" when it is a memory module, "04" when it is a hard drive, "05" when it is a motherboard, and "06" when it is a network card or RAID card. The above segment codes can be extended according to the actual categories of products operated by the enterprise.

[0029] After determining the type segment code, the system reads the system date of the day the target reclaimed object was returned to the warehouse. This date is then encoded into a 6-digit format: "last 2 digits of year + 2 digits of month + 2 digits of day" to obtain the warehouse entry time batch code. For example, the warehouse entry time batch code for July 23, 2026 is "260723". Subsequently, the system obtains the unique incrementing sequence code of the target reclaimed object from the sequence code generator. This generator maintains an independent incrementing counter for each combination of "type segment code + warehouse entry time batch code". The counter's initial value is "00001" and increments by 1 with each call, generating a zero-padded decimal sequence number of at least 5 digits. This ensures that each target reclaimed object within the same type and date range obtains a unique and non-repeating sequence code. Finally, the enterprise-specific root node OID, type segment code, entry time batch code, and unique incremental sequence code are concatenated in dotted decimal notation according to the hierarchical order of "enterprise-specific root node OID.type segment code.entry time batch code.unique incremental sequence code" to obtain the unique OID corresponding to the target recycling object. For example, if the target recycling object is a server, the entry date is July 23, 2026, and the serial number of this type of device is the first on that day, then the generated unique OID is "1.2.156.12345.01.260723.00001". After the unique OID is generated, the system calls the label printing interface to drive the label printing device to output a QR code label containing the unique OID information. The operator then physically affixes the QR code label to the designated area on the shell of the target recycling object to complete the physical coding operation of the OID identification.

[0030] Among them, "target recycling object" refers to the physical equipment to be managed that has entered the recycling and warehousing stage. The object type is target server or target component. The target server is a complete server machine, and the target component is an independently recycled functional component such as CPU, memory module, hard drive, motherboard, network card or array card; "Native SN code" refers to the serial number code assigned to the equipment by the original manufacturer at the time of manufacture and physically marked on the surface of the equipment. It is the unique identifier of the equipment within the manufacturer's system; "Type segment code" refers to a fixed 2-digit numerical code segment under the enterprise's exclusive root node OID, used to distinguish different equipment categories; "Warehousing time batch code" refers to a 6-digit numerical code generated according to the date of the target recycling object's warehousing, used to identify the time batch of the equipment's warehousing; "Unique incremental sequence code" refers to a unique serial number of no less than 5 digits automatically generated by the system within the same type segment code and the same warehousing time batch code. By combining the national authoritative OID coding system with information such as equipment category, warehousing time, and serial number, a structured coding generation method is used to give each recycled server or component a globally unique, structurally resolvable, and hierarchically clear identification code. At the same time, the original SN code is retained as the business retrieval entry point, laying the coding foundation for subsequent dual-code linkage filing and full life cycle traceability management.

[0031] S103: Use the exclusive OID as the primary key field, the native SN code as the business index field, and combine it with basic information to construct the traceability file corresponding to the target recycling object.

[0032] Specifically, in this step, the system uses the structured relational database MySQL as the persistent storage engine and executes the corresponding filing logic according to the object type of the target reclaimed object. When the target reclaimed object is the target server, the system writes the unique OID generated in step S102 into the primary key field "main_oid" of the preset initial whole machine traceability file. This primary key field has a database-level uniqueness constraint to ensure that there are no duplicate primary keys globally. At the same time, the target server's original SN code is written into the business index field "original_sn" of the initial whole machine traceability file. This field has a database B-tree index to support efficient business retrieval, thereby realizing a one-to-one bidirectional binding between the unique OID and the original SN code. Subsequently, the system uses the preset association field "pare The `nt_oid` field aggregates and mounts the basic information of the target server to the primary key file corresponding to the primary key field in the initial whole machine traceability file. Specifically, it writes information such as equipment brand, equipment model, hardware specifications, manufacturing date, appearance condition level, and recycling source channel into the corresponding structured fields in the primary key file. It also associates and mounts the basic information of each built-in component contained within the target server with the `parent_oid` field pointing to the whole machine's primary key OID, forming a hierarchical summary ledger structure with the whole machine OID as the top-level node and the information of each built-in component as child nodes, thus completing the construction of the traceability file corresponding to the target server. An example is shown below: { "main_oid":"1.2.156.12345.01.260723.00001", "original_sn":"S202509180076", "brand":"XX", "model":"2288H V5", "part_list":[ {"part_oid":"1.2.156.12345.03.260723.00002","part_sn":"M393A4K40BB1-CRC","parent_oid":"1.2.156.12345.01.260723.00086"} ] } When the target recycling object is a target component, the system writes the unique OID generated in step S102 into the primary key field "part_oid" of the preset initial component traceability file, and writes the original SN code of the target component into the business index field "original_sn" to complete a one-to-one binding; then, in the initial component traceability file, the system records the whole machine OID to which the target component belonged before disassembly through the preset historical traceability field "origin_main_oid". If the target component is independently recycled rather than obtained from the disassembly of the whole machine, the historical traceability field is recorded as null and marked as "independent recycling"; finally, the basic information such as the category name, hardware specifications, and manufacturing date of the target component is written into the structured fields corresponding to the initial component traceability file to complete the construction of the traceability file corresponding to the target component. An example is as follows: { "part_oid":"1.2.156.12345.03.260723.000002", "original_sn":"M393A4K40BB1-CRC", "origin_main_oid":"1.2.156.12345.01.260723.00001", "category":"DDR4 memory sticks", "spec":"32GB 2666MHz" } The aforementioned preset initial whole machine traceability files and initial component traceability files are both standard data table structures pre-created by the system during the database initialization phase. The data table corresponding to the initial whole machine traceability file includes standard column definitions such as the primary key field "main_oid", the business index field "original_sn", the related field "parent_oid", the brand field "brand", the model field "model", the component list field "part_list", and the creation time field "create_time". The data table corresponding to the initial component traceability file includes standard column definitions such as the primary key field "part_oid", the business index field "original_sn", the historical traceability field "origin_main_oid", the category field "category", the specification field "spec", and the creation time field "create_time". Both types of data tables are automatically created by the database table creation script during the system deployment phase. In this step, the "primary key field" refers to the field in the database table that serves as a unique identifier for each record, with the constraint of being non-nullable and unique. In this solution, a dedicated OID is used as the primary key field to ensure that each server or component corresponds to exactly one file record in the system. The "business index field" refers to the field in the database table where a retrieval index is created. In this solution, the native SN code is used as the business index field, allowing operators to quickly locate the corresponding traceability file record by scanning the device's native SN code. The "association field" refers to the foreign key reference field used to establish hierarchical relationships between different data records. The "historical traceability field" refers to a dedicated field used to record the OID information of the whole machine to which the component belonged before disassembly. In this solution, it is the "origin_main_oid" field, which enables reverse traceability from the component to the original whole machine. This step uses a dual-code linkage filing method with OID as the primary key and SN code as the business index. This ensures that each device has a globally unique and authoritative identity in the system, while retaining the industry-standard SN code as an efficient business retrieval entry point. At the same time, it establishes a hierarchical data structure for the whole machine and components through associated fields, providing a structured data foundation for the accurate collection and traceability of subsequent full lifecycle business data.

[0033] S104: During the entire lifecycle of the target recyclable object, collect business data from multiple stages of the process and obtain lifecycle traceability data based on the traceability archives and business data.

[0034] Specifically, in this step, after the target recycling object completes its filing and warehousing, it will undergo multiple transfer stages. Each stage generates corresponding business data, which is appended to the corresponding traceability file, ultimately forming complete lifecycle traceability data. When the transfer stage involves disassembling the entire machine, the operator uses a PDA handheld terminal to scan the OID QR code label on the surface of the target server's casing to obtain the target server's unique OID. Then, the target server is physically disassembled, and each functional component is removed from the machine one by one. After disassembly, the operator scans the original SN code label on the surface of each disassembled component. After the system obtains the SN code of each disassembled component, it generates an independent OID for each disassembled component according to the following encoding generation logic: First, based on the hardware category of the disassembled component, the unique type segment code of the component is obtained from the encoding rule configuration table (e.g., CPU corresponds to "02", memory module corresponds to "03", hard drive corresponds to "04"). (Corresponding to "04"), then read the system date of the disassembly operation and encode it according to the 6-digit number format of "last 2 digits of year + 2 digits of month + 2 digits of day" to obtain the disassembly time batch code. Next, obtain the unique incremental serial code of the component under the same type segment code and disassembly time batch code combination from the serial code generator. Finally, concatenate the enterprise-specific root node OID, exclusive type segment code, disassembly time batch code and exclusive incremental serial code in the order of dotted decimal hierarchy to obtain the unique OID corresponding to the disassembled component. For example, the unique OID obtained by a disassembled memory stick is "1.2.156.12345.03.260723.000002". After each disassembled component has its own unique OID, the system uses the unique OID of each disassembled component as the primary key field and the SN code of that component as the business retrieval field to build a corresponding component traceability file in the database. The system also writes the exclusive OID of the target server to which the component belonged before disassembly into the historical traceability field "origin_main_oid" of each component traceability file. At the same time, the system appends the disassembly operation record to the traceability file of the target server. The record includes a list of unique OIDs of each disassembled component, a disassembly timestamp, and the employee number of the operator. This establishes a two-way traceability association between the unique OID and the exclusive OID of the target server. That is, the historical traceability field in the component traceability file can be used to trace back to the original whole machine, and the disassembly record in the whole machine traceability file can be used to trace back to each component. The system also writes the disassembly time and operator identification of each disassembled component into the disassembly information field of the corresponding component traceability file in the form of structured records. Each disassembly record includes a disassembly timestamp (standard time format accurate to the second), the operator's employee number, and a unique disassembly record number. The above records are stored in an append-only manner, and historical data cannot be modified or deleted, thus obtaining the life cycle traceability data of the whole machine disassembly process.

[0035] When the process involves assembling a complete machine, the company uses qualified components (which can be components disassembled from recycled servers or directly recycled components, whose corresponding OIDs have been pre-generated) to refurbish and assemble new complete machines. Operators initiate the assembly process in the system. The system generates a new complete machine OID based on the same coding logic as in step S102. Specifically, it generates a complete new complete machine OID code by concatenating the company's unique root node OID with the complete machine type segment code "01", the assembly time batch code for the day, and a unique incrementing sequence code. Subsequently, operators use a PDA handheld terminal to scan... The system scans the OID QR code labels on the surfaces of each assembly component, reads and obtains the component OID of each component one by one, and then writes the component OIDs of all assembly components into the "bom_child_oid_list" field of the BOM configuration list in the traceability file corresponding to the new complete machine OID in the form of an array. At the same time, the BOM version number, assembly timestamp, and operator employee number of this assembly are recorded. Simultaneously, the new complete machine OID and assembly time to which the current assembly belongs are appended to the traceability file of each assembly component, realizing bidirectional data recording of the assembly relationship between the complete machine and the components. Every hardware configuration change (including subsequent component replacement, upgrades, expansions, etc.) is added as new BOM version data to the traceability file of the new complete machine. The version number increments according to the rule of "V + 2 digits" (e.g., V01, V02, V03). Historical version data is permanently retained and cannot be overwritten, thus forming a complete historical trajectory of hardware configuration changes and obtaining lifecycle traceability data of the complete machine assembly process. In addition to the disassembly and assembly stages mentioned above, the target recycled object undergoes multiple circulation stages throughout its lifecycle, including AI appearance defect detection, functional testing and repair, warehousing and circulation, outbound quality inspection, sales logistics, and after-sales maintenance. Business data generated at each stage is appended to the traceability file corresponding to the target recycled object's unique OID, sequentially in chronological order. Append-only writing means the system only performs new insertion operations on the data in the traceability file; at the database level, access control policies prohibit UPDATE and DELETE operations on existing records, ensuring that historical data, once written, cannot be modified, overwritten, or deleted, and that all historical circulation data is completely retained in chronological order of writing time. Furthermore, the construction logic of the traceability file corresponding to the new complete machine OID (using the new complete machine OID as the primary key field and the corresponding SN code as the business index field) is consistent with the construction logic of the traceability file corresponding to the target recycled object, and will not be elaborated further here.

[0036] In the process of AI-based appearance defect detection, the operator places the target recyclable object on a preset detection station. This detection station is equipped with a multi-angle industrial camera array, which includes no fewer than four high-resolution industrial cameras. These cameras capture images of the target recyclable object's outer shell surface from multiple preset angles, such as the front, back, left, right, and top sides. Each industrial camera automatically completes image acquisition and outputs high-resolution digital image data according to preset shooting parameters (including exposure time, white balance, and focal length). The system takes all image data acquired by a multi-angle industrial camera array as input and feeds it into a pre-trained deep learning appearance defect detection model for inference calculation. This deep learning appearance defect detection model is built on a convolutional neural network architecture. Before system deployment, it has been trained and its parameters optimized using a large dataset of server and component images labeled with various appearance defect samples. Specifically, the dataset is divided into training, validation, and test sets in a 7:2:1 ratio. The model is then trained using these divided datasets, with cross-entropy loss function used for supervised training and backpropagation algorithm used for parameter tuning, continuously minimizing the loss value until the model converges. This training process is existing technology and will not be elaborated further. The deep learning appearance defect detection model has the ability to automatically identify various appearance defect types such as scratches, deformation, interface damage, chip breakage, and missing labels. The deep learning-based appearance defect detection model performs pixel-by-pixel feature extraction and classification on the input image, automatically identifies the appearance defect areas in the image, and outputs the defect type label, spatial coordinates of the defect in the image (represented by the coordinates of the upper left and lower right corners of the rectangular bounding box), and damage level assessment results for each defect area, ultimately generating an AI appearance defect detection report.

[0037] In one embodiment, based on pre-cached after-sales fault records, multiple historical fault types (including those with the same fault type) that have occurred in sold servers or components are obtained. The number of times a single historical fault type repeatedly occurs among these multiple historical fault types is counted. If the number exceeds a preset threshold, the historical fault type is identified as a key fault type, i.e., a fault type that is prone to occur. At least one key fault type exists, and the threshold is a critical value that measures the magnitude of the frequency. The after-sales fault records include historical fault types that have occurred in sold servers or components within a preset historical period, as well as the types of appearance defects that caused individual historical fault types. In this embodiment, the preset historical period is the past 2 years or 5 years.

[0038] Furthermore, based on the aforementioned after-sales fault records, multiple appearance defect types that trigger a single key fault type are obtained. The frequency of recurrence of a single appearance defect type among these multiple types is statistically analyzed. If the frequency exceeds a preset frequency threshold, then that appearance defect type is identified as a key defect type corresponding to the single key fault type; that is, an appearance defect type that is likely to trigger the key fault type. Each key fault type corresponds to a specific key defect type. The frequency threshold is a critical value used to measure the magnitude of the frequency. For example, a key fault type might be: a server experiencing a hard drive offline failure; key defect types that trigger this failure include, but are not limited to: hard drive bay rail deformation due to impact, and hard drive backplate casing denting.

[0039] The weight of each key fault type is determined. The weight is the ratio of the frequency of occurrence of this key fault type to the sum of the frequencies of occurrence of all key fault types, representing the likelihood of this key fault type appearing after the sale. Next, the weights of each key defect type corresponding to this key fault type are determined. The weights are the ratio of the frequency of occurrence of this key defect type to the sum of the frequencies of occurrence of all key defect types, representing the likelihood of this key defect type triggering the key fault type.

[0040] Furthermore, the weight of a single key fault type is multiplied by the weights of its corresponding key defect types to obtain multiple products for that single key fault type. These products represent the likelihood of a single key fault type occurring in the after-sales service and being caused by a key defect type. The products corresponding to the same key defect type are summed across all key fault types to obtain a total sum. This sum represents the overall likelihood of a fault occurring in the after-sales service caused by that specific key defect type. The sums of the products corresponding to all key defect types are then accumulated to obtain a comprehensive result, and the fault contribution percentage of a single key defect type is determined. This percentage is the ratio of the sum of the products corresponding to a single key defect type to the comprehensive result. The larger the ratio, the more likely the fault occurring in the sale is due to that specific key defect type. Furthermore, when training the deep learning appearance defect detection model using appearance defect samples, the proportion of a single key defect type in all appearance defect samples is its corresponding failure contribution proportion. This enables targeted training of the deep learning appearance defect detection model, allowing for more focused training on defects that are prone to causing after-sales failures. This enables the model to more accurately identify such defects, thereby more precisely classifying the causes and responsible parties of after-sales failures.

[0041] In another embodiment, the actual fault type of the sold equipment (server or component) is obtained from the after-sales personnel's terminal (smartphone or personal computer), and the actual appearance defect type of the sold equipment is determined through the traceability file corresponding to the sold equipment. When the actual fault type is a key fault type, at least one actual appearance defect type among the key defect types corresponding to the actual fault type is determined as the target defect type. The weight of the actual fault type is calculated and multiplied by the weight of the corresponding at least one target defect type to obtain the multiplication result, which represents the probability that the target defect type causes the actual fault type. The multiplication results are summed to obtain the sum result, which represents the overall probability that the actual fault type is caused by the actual appearance defect type. If the sum result is greater than a preset result threshold, which is a critical value for measuring the magnitude of the sum result, it indicates that the overall probability that the actual fault type is caused by the actual appearance defect type is relatively high. Then, the investigation order of each target defect type is determined. The larger the multiplication result corresponding to the target defect type, the earlier the investigation order, and the higher the priority for investigating "whether it causes a fault". The investigation order of each target defect type is sent to the after-sales personnel's terminal.

[0042] Furthermore, the system uses the SM4 national cryptographic algorithm to encrypt and store each traceability data record when it is written to the database. Simultaneously, the traceability files associated with the OID are synchronized to the National OID Registration Center for backup, and all personnel operation logs are recorded. Data tampering is prevented from multiple dimensions, including storage, permissions, and cloud backup.

[0043] It should be noted that in this step, "transfer process" refers to all business operation nodes experienced by the target recycling object from warehousing to final outbound or secondary scrapping, including but not limited to recycling inspection, AI appearance defect detection, functional testing and repair, whole machine disassembly, component coding, whole machine assembly, warehousing changes, outbound quality inspection, sales logistics and after-sales maintenance; "two-way traceability association" means that the source whole machine OID is recorded in the component traceability file through the historical traceability field, and the independent OID of each disassembled component is recorded in the whole machine traceability file through the disassembly record field, thereby supporting traceability queries in two directions: tracing back from the component to the original whole machine and tracing back from the whole machine to all disassembled components; "append-only writing" means that the data in the traceability file can only be added and inserted, and the modification, overwriting or deletion of existing records is prohibited; "BOM configuration list" refers to the structured data field that records the OID codes of all assembled components in a whole machine. BOM is an abbreviation for Bill of Materials. Furthermore, by generating independent OIDs for components during the disassembly process and establishing a two-way traceability association with the original complete machine, and by writing the component OIDs into the new complete machine BOM list during the assembly process and realizing configuration version traceability, the industry pain point of broken component traceability links after the disassembly and reassembly of used servers is solved, and the continuous maintenance and complete recording of the traceability relationship between the complete machine and components in dynamic disassembly and assembly scenarios are realized.

[0044] S105: In response to the terminal's traceability query request, output the corresponding lifecycle traceability data to the terminal based on the exclusive OID.

[0045] Specifically, end users use smartphones or other mobile devices with cameras and network communication capabilities to scan the OID QR code labels physically affixed to the surface of the target recycling object. The scanning application on the terminal device parses the QR code image to obtain the encoded unique OID string, and sends a traceability query request to the system server accordingly. This request carries the unique OID as a query parameter. After receiving the traceability query request, the system server uses the unique OID carried in the request as the primary key search condition to perform an exact match query in the traceability archive data table of the database to locate the traceability archive record corresponding to the unique OID. Subsequently, the system extracts all collected lifecycle traceability data from the traceability archive in chronological order. The extracted content includes basic information on entry into the database (equipment brand, model, specifications, manufacturing date, recycling source), AI appearance defect detection report (defect type, defect location marked image, damage level), functional testing and maintenance records, and disassembly records (source whole machine OID, disassembly time, operator). The system includes component coding records, assembly BOM configuration lists (hardware composition and change times for each version), warehousing and circulation records, outbound quality inspection reports, customer information, and logistics and transportation data. If the target recycling object corresponding to this exclusive OID is a complete machine and there are disassembly records, the system will further cascade and query the corresponding component traceability files through the independent OIDs of each component associated in the disassembly records, integrating the component-level circulation data. If the target recycling object corresponding to this exclusive OID is a component and the historical traceability field records the source complete machine OID, the system will also cascade and query the original complete machine's traceability file summary information through this field and integrate and output it.

[0046] By using OID as a unique index to achieve one-code access to full traceability data, end users can easily obtain the complete circulation history and testing records of the equipment. The mandatory quality inspection and verification mechanism before shipment ensures that all outgoing equipment has complete quality inspection certificates. Combined with the official filing characteristics of the National OID Registration Center, it provides authoritative, reliable and tamper-proof data support for the determination of responsibility in after-sales fault disputes.

[0047] The implementation principle of the second-hand server and component traceability method in this application embodiment is as follows: During the asset recovery and warehousing stage, a unique OID is generated for each target recovery object (target server or target component) based on the enterprise's exclusive root node OID. Simultaneously, the native SN code and basic information of the target recovery object are collected. The tamper-proof, enterprise-controlled exclusive OID serves as the primary key of the traceability file, while the native SN code, used only for business retrieval purposes, serves as an auxiliary business index field. This, combined with basic asset information, jointly constructs a unique traceability file for the target recovery object. This isolates the issue of subject identification failure caused by native SN code tampering from the underlying field architecture of the file. Business flow data generated at each stage of the entire lifecycle, including server and component warehousing, inspection, refurbishment, and secondary warehousing, is continuously collected. Based on pre-... The established traceability archives are linked and integrated with all circulation business data to form complete and continuous full lifecycle traceability data. When a terminal initiates a traceability query request, the system uses a unique, globally unique, and difficult-to-forge exclusive OID, endorsed by the enterprise's root node, as the core index to retrieve and push the complete lifecycle traceability data to the terminal. This solution establishes a unique and trustworthy identity identifier for assets by deriving exclusive OIDs from the enterprise's private root node, weakening the core positioning role of the easily tampered native SN code and retaining only its retrieval auxiliary function. The exclusive OID is used to link all circulation records of assets from recycling to secondary circulation, avoiding the distortion of asset origin and circulation trajectory traceability caused by SN code forgery and replacement. This ensures the integrity and trustworthiness of the traceability chain for each second-hand server and component, effectively solving the problem of traceability distortion for second-hand servers and components.

[0048] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.

[0049] Please see Figure 3 This is a schematic diagram of the structure of the used server and component traceability device provided in this application embodiment. This device for tracing used servers and components can be implemented as all or part of the device through software, hardware, or a combination of both. The device includes an information acquisition module 11, an OID generation module 12, a traceability and documentation module 13, a data collection module 14, and a data traceability module 15.

[0050] Information acquisition module 11 is used to acquire the enterprise-specific root node OID corresponding to the target enterprise; OID generation module 12 is used to generate a unique OID corresponding to the target recycling object based on the enterprise's unique root node OID during the recycling and warehousing stage, and to obtain the target recycling object's original SN code and basic information. The target recycling object is the target server or target component to be recycled. The traceability and filing module 13 is used to construct the traceability file corresponding to the target recycling object by using the exclusive OID as the primary key field, the native SN code as the business index field, and combining basic information. The data collection module 14 is used to collect business data from multiple circulation stages during the entire life cycle of the target recycling object, and obtain life cycle traceability data based on the traceability archives and business data. The data traceability module 15 is used to respond to the traceability query request from the terminal and output the corresponding lifecycle traceability data to the terminal based on the unique OID.

[0051] It should be noted that the above embodiments of the used server and component traceability device, when executing the used server and component traceability method, are only illustrative examples of the above-described functional module division. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. Furthermore, the used server and component traceability device and the used server and component traceability method embodiment provided in the above embodiments belong to the same concept, and their implementation process is detailed in the method embodiment, which will not be repeated here.

[0052] This application also discloses a computer-readable storage medium, which stores a computer program, wherein when the computer program is executed by a processor, it implements a method for tracing used servers and components as described in the above embodiments.

[0053] The computer program can be stored in a computer-readable medium. The computer program includes computer program code, which can be in the form of source code, object code, executable file, or certain middleware. The computer-readable medium includes any entity or device capable of carrying computer program code, recording media, USB flash drive, portable hard drive, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the computer-readable medium includes, but is not limited to, the above-mentioned components.

[0054] The above-described method for tracing a second-hand server and its components is stored in the computer-readable storage medium and loaded and executed on the processor to facilitate the storage and application of the method.

[0055] like Figure 4As shown in the embodiments of this application, an electronic device is also disclosed. The electronic device is a cloud server, and the electronic device includes, but is not limited to, a processor 201 and a memory 202. For example, the electronic device may also include a bus 203 and a network interface 204.

[0056] The processor 201 can be a central processing unit (CPU). Of course, depending on the actual use, it can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), off-the-shelf programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor, etc., and this application does not limit it in this regard.

[0057] The memory 202 can be an internal storage unit of an electronic device, such as a hard disk or memory of the electronic device, or an external storage device of the electronic device, such as a plug-in hard disk, smart memory card (SMC), secure digital card (SD) or flash memory card (FC) equipped on the electronic device. Furthermore, the memory 202 can also be a combination of an internal storage unit and an external storage device of the electronic device. The memory is used to store computer programs and other programs and data required by the electronic device. The memory can also be used to temporarily store data that has been output or will be output. This application does not limit this.

[0058] In this electronic device, a method for tracing a second-hand server and its components according to the above embodiment is stored in the memory 202 of the electronic device and loaded and executed on the processor 201 of the electronic device for convenient use.

[0059] The foregoing description is merely an exemplary embodiment of this disclosure and should not be construed as limiting the scope of this disclosure. Any equivalent changes and modifications made in accordance with the teachings of this disclosure shall still fall within the scope of this disclosure. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not described in this disclosure. The specification and embodiments are considered exemplary only, and the scope and spirit of this disclosure are defined by the claims.

Claims

1. A method for tracing used servers and components, characterized in that, The method includes: Obtain the enterprise-specific root node OID corresponding to the target enterprise; During the recovery and warehousing phase, based on the enterprise-specific root node OID, a unique OID corresponding to the target recycling object is generated, and the native SN code and basic information of the target recycling object are obtained. The target recycling object is the target server or target component to be recycled. The unique OID is used as the primary key field, the native SN code is used as the business index field, and the source traceability file corresponding to the target recycling object is constructed by combining the basic information; During the entire lifecycle of the target recyclable object, business data from multiple stages of the process are collected, and lifecycle traceability data is obtained based on the traceability file and the business data. In response to the terminal's traceability query request, the corresponding lifecycle traceability data is output to the terminal based on the unique OID.

2. The method for tracing used servers and components according to claim 1, characterized in that, The step of generating a unique OID corresponding to the target reclaimed object based on the enterprise-specific root node OID specifically includes: Based on the object type of the target recycling object, a matching type segment code is determined, and the target server and the target component each correspond to different type segment codes; Based on the date the target recycled object is returned to the warehouse, generate a batch code for the warehouse entry time, and obtain the unique incremental sequence code of the target recycled object; The enterprise-specific root node OID, the type segment code, the entry time batch code, and the unique incremental sequence code are concatenated sequentially to obtain the unique OID corresponding to the target recycling object.

3. The method for tracing used servers and components according to claim 1, characterized in that, The process of obtaining lifecycle traceability data based on the traceability archives and the business data specifically includes: When the entire machine is disassembled during the circulation process, an independent OID is generated for each disassembled component based on the enterprise-specific root node OID. Using the independent OID of a single disassembled component as the primary key field and the SN code of a single disassembled component as the business retrieval field, a corresponding component traceability file is constructed. The exclusive OID of the target server is recorded in the component traceability file, and a bidirectional traceability association is established between the independent OID and the exclusive OID of the target server. The disassembly time and operator identification of each disassembled component are recorded in the corresponding component traceability file to obtain lifecycle traceability data.

4. The method for tracing used servers and components according to claim 3, characterized in that, The process of generating independent OIDs for disassembled components based on the enterprise-specific root node OID specifically includes: Obtain the unique type segment code of the disassembled parts; Based on the disassembly date of the disassembled parts, a disassembly time batch code is generated, and the unique incremental sequence code of the disassembled parts is obtained. The enterprise-specific root node OID, the specific type segment code, the disassembly time batch code, and the specific incremental sequence code are concatenated sequentially to obtain the independent OID corresponding to the disassembled component.

5. The method for tracing used servers and components according to claim 1, characterized in that, The step of obtaining lifecycle traceability data based on the traceability archives and the business data specifically includes: When the process involves assembling the complete machine, a new complete machine OID is generated for the assembled new complete machine, and the component OIDs of each assembled part in the assembled new complete machine are obtained. Write the OIDs of each component into the BOM configuration list of the traceability file corresponding to the OID of the new complete machine to obtain lifecycle traceability data.

6. The method for tracing used servers and components according to claim 1, characterized in that, The step of using the unique OID as the primary key field, the native SN code as the business index field, and combining the basic information to construct the traceability file corresponding to the target recycling object specifically includes: When the target object to be recycled is the target server, the exclusive OID is stored as the primary key field and the native SN code is stored as the business index field in the preset initial whole machine traceability file; The basic information is collected and attached to the primary key file corresponding to the primary key field in the initial whole machine traceability file by using the preset association fields, so as to obtain the traceability file corresponding to the target recycling object.

7. The method for tracing used servers and components according to claim 1, characterized in that, The step of using the unique OID as the primary key field, the native SN code as the business index field, and combining the basic information to construct the traceability file corresponding to the target recycling object specifically includes: When the target recycling object is a target component, the exclusive OID is stored as the primary key field and the native SN code is stored as the business index field in the preset initial component traceability file; In the initial component traceability file, the whole machine OID to which the target component belongs is recorded through a preset historical traceability field, and the basic information is archived in the initial component traceability file to obtain the traceability file corresponding to the target recycling object.

8. A device for tracing used servers and components, used to implement the method for tracing used servers and components as described in any one of claims 1 to 7, characterized in that, include: The information acquisition module (11) is used to acquire the enterprise-specific root node OID corresponding to the target enterprise; OID generation module (12) is used to generate a unique OID corresponding to the target recycling object based on the enterprise-specific root node OID during the recycling stage, and obtain the native SN code and basic information of the target recycling object, wherein the target recycling object is the target server or target component to be recycled. The traceability and filing module (13) is used to construct the traceability file corresponding to the target recycling object by using the exclusive OID as the primary key field, the native SN code as the business index field, and combining the basic information. The data collection module (14) is used to collect business data from multiple circulation links in the entire life cycle circulation process of the target recycling object, and obtain life cycle traceability data based on the traceability file and the business data. The data traceability module (15) is used to respond to the traceability query request of the terminal and output the corresponding lifecycle traceability data to the terminal according to the exclusive OID.

9. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is loaded and executed by the processor, it implements the method of any one of claims 1-7.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and capable of running on the processor, characterized in that, When the processor loads and executes the computer program, it implements the method of any one of claims 1-7.

Images