Server delivery method and verification method, storage medium, and electronic device

Abstract

The present application discloses a server delivery method and verification method, storage medium, and electronic device, which are applied to the server manufacturer side. The method includes: receiving at least one client test task sent by the client; generating at least one delivery standard test task of the server manufacturer side based on the server manufacturer test task and the client test task; controlling multiple servers to execute at least one delivery standard test task, generating a test result for each server, and obtaining the identity of the server that meets the preset delivery conditions based on the multiple test results, so as to deliver the server corresponding to the identity to the corresponding client. The method of the present application can integrate the test tasks of the server manufacturer and the test tasks of the client, generate a unified delivery standard test task, ensure that the server passes all necessary tests before shipment, thereby improving the quality and efficiency of server delivery and enhancing customer satisfaction.

Description

Technical Field

[0001] The present invention relates to the technical field of servers, and in particular to a server delivery method and verification method, a storage medium, and an electronic device. Background Art

[0002] During server manufacturing and delivery, ensuring that servers fully meet the client's quality standards and functional requirements before shipment is crucial. The current server delivery process typically involves the following stages: The server manufacturer produces the server according to design specifications. The manufacturer then subjects the server to a series of standard tests to ensure that its basic functionality and performance meet requirements. Upon receipt of the server, the client undergoes additional testing to verify that the server meets its specific needs. Once the server passes all tests, the manufacturer ships it to the client.

[0003] However, in the above method, server manufacturers and clients may each have their own set of testing standards and lack unified coordination, which results in the server needing to undergo multiple tests, increasing time and cost, resulting in lower quality and efficiency of server delivery, and providing customers with a poor experience. Summary of the Invention

[0004] The present application provides a server delivery method and storage medium, electronic device, and computer program product to at least solve the problem in related technologies that server manufacturers and clients may each have a set of testing standards and lack unified coordination, resulting in the need for multiple tests on the server, which increases time and cost. The application can integrate the testing tasks of the server manufacturer and the testing tasks of the client to generate unified delivery standard testing tasks, ensuring that the server passes all necessary tests before shipment, thereby improving the quality and efficiency of server delivery and enhancing customer satisfaction.

[0005] The present application provides a server delivery method, characterized in that it is applied to a server manufacturer, and the method includes:

[0006] Receive at least one client test task sent by a client;

[0007] Generate at least one delivery standard test task of the server manufacturer based on the server manufacturer test task and the customer test task;

[0008] Control multiple servers to execute the at least one delivery standard test task, generate test results for each server, and obtain the identity of the server that meets the preset delivery conditions based on the multiple test results, so as to deliver the server corresponding to the identity to the corresponding client.

[0009] The present application also provides a server delivery method, which is applied to a client, and the method includes:

[0010] Receive the test results of each server sent by the server manufacturer;

[0011] Determining a target server based on preset test criteria and the test results;

[0012] A server quality code is determined based on the target server, and the server quality code is sent to the server manufacturer.

[0013] The present application also provides a non-volatile computer-readable storage medium on which a program is stored. When the program is executed by a processor, the above-mentioned server delivery method or server verification method is implemented.

[0014] The present application also provides an electronic device, including a memory, a processor, and a program stored in the memory and executable on the processor. When the processor executes the program, the above-mentioned server delivery method is implemented.

[0015] The present application also provides an electronic device, comprising a memory, a processor, and a program stored in the memory and executable on the processor, wherein when the processor executes the program, the above-mentioned server verification method is implemented.

[0016] The present application also provides a computer program product, including a computer program / instruction, which implements the above-mentioned server delivery method when executed by a processor.

[0017] The present application also provides a computer program product, including a computer program / instruction, which implements the above-mentioned server verification method when executed by a processor.

[0018] Through this application, at least one client test task sent by a client is received, and at least one delivery standard test task on the server manufacturer's side is generated based on the server manufacturer's test task and the client test task. Multiple servers are controlled to execute at least one delivery standard test task, and test results for each server are generated. Based on multiple test results, the identity of the server that meets the preset delivery conditions is obtained, so that the server corresponding to the identity is delivered to the corresponding client. As a result, this method can integrate the server manufacturer's test tasks and the client's test tasks, generate a unified delivery standard test task, and ensure that the server passes all necessary tests before shipment, thereby improving the quality and efficiency of server delivery and enhancing customer satisfaction. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0020] Figure 1 Flowchart of a method for delivering a server according to an embodiment of the present application;

[0021] Figure 2 A flowchart of a server delivery method according to a specific example of the present application;

[0022] Figure 3 Flowchart of a method for delivering a server according to an embodiment of the present application;

[0023] Figure 4 This is a schematic diagram of the interaction between a server manufacturer and a client according to a specific example of the present application;

[0024] Figure 5 is a block diagram of an electronic device according to an embodiment of the present application;

[0025] Figure 6 Schematic diagram of a block diagram of an electronic device according to an embodiment of the present application.

[0026] Reference numerals: 200 - electronic device, 210 - memory, 220 - processor, 300 - electronic device, 310 - memory, 320 - processor. DETAILED DESCRIPTION

[0027] The following describes in detail embodiments of the present application, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present application, and should not be construed as limiting the present application.

[0028] The following describes the server delivery method, server verification method, computer-readable storage medium, electronic device and computer program product proposed in the embodiments of the present application with reference to the accompanying drawings.

[0029] Figure 1 The present invention is a flowchart of a method for delivering a server according to an embodiment of the present application.

[0030] like Figure 1 As shown, the delivery method of the server in the embodiment of the present application may include the following steps:

[0031] S1, receiving at least one client test task sent by a client.

[0032] S2: Generate at least one delivery standard test task on the server manufacturer side based on the server manufacturer test task and the customer test task.

[0033] S3, controls multiple servers to execute at least one delivery standard test task, generates test results for each server, and obtains the identity of the server that meets the preset delivery conditions based on the multiple test results, so as to deliver the server corresponding to the identity to the corresponding client.

[0034] Specifically, the server manufacturer can receive at least one client test task sent by the client. Specifically, the client can define a series of test tasks based on their needs (e.g., business scenarios, performance requirements, etc.). These tasks may include hardware performance testing (e.g., CPU (Central Processing Unit) performance, memory bandwidth testing), software compatibility testing (e.g., compatibility testing with specific operating systems or applications), and stability testing (e.g., long-running stress testing). The client encapsulates these test tasks into a test task data packet in a standardized format (e.g., JSON (JavaScript Object Notation) or XML (Extensible Markup Language)). For example, the client sends the encapsulated test task data packet to the server manufacturer's test system via a network (e.g., an enterprise intranet or the internet). The server manufacturer's test system then receives the test task data packet sent by the client via a network interface (e.g., an API (Application Programming Interface)). The system can then parse the received data packet to extract the specific test task content, including test items, test parameters, test standards, and other information.

[0035] After receiving the client's test tasks, at least one standard test task for the server manufacturer can be generated based on the database of server manufacturer test tasks and the client's test tasks. Server manufacturers develop a series of standard test tasks based on their own quality control systems and industry standards. These tasks may cover basic server functional testing (such as hardware startup and network connectivity), performance testing (such as benchmark performance testing), reliability testing (such as fault injection testing), and more. In other words, the client's test tasks are integrated with the server manufacturer's standard test tasks. For example, if there are duplicates between the client's test tasks and the manufacturer's standard test tasks, duplicates need to be removed to avoid duplicate testing. The priority of test tasks can also be adjusted based on the client's needs and the manufacturer's testing strategy. For example, specific client test tasks may have a higher priority and need to be executed first. Alternatively, testing resources (such as test equipment and test personnel) can be appropriately allocated based on the complexity and resource requirements of the test tasks.

[0036] Therefore, the integrated test tasks form a complete set of delivery standard test tasks. This set of test tasks includes both the basic quality requirements of the manufacturer and the personalized needs of the client, ensuring that the delivered server can meet the requirements of both parties, ensuring that the server can meet the manufacturer's quality standards and the client's personalized needs at the time of delivery, and transplanting the customer's test standards in advance before shipment, so that problems found on the client after shipment can be identified in advance before shipment.

[0037] After determining the delivery standard test tasks, multiple servers can be controlled to execute at least one delivery standard test task, generating test results for each server. This generated delivery standard test task can then be distributed to the multiple servers to be tested. This distribution process can be implemented using automated testing tools or a test management platform, ensuring that each server receives the complete test task. This allows multiple servers to sequentially execute the tests based on the received delivery standard test tasks. During the testing process, the servers will run the corresponding test programs according to the test task requirements and generate test data. Furthermore, after each server completes the test, it can send test results back to the test system. These results can include information such as the execution status of the test items (e.g., pass / fail), test data (e.g., performance indicator values), and test logs.

[0038] Therefore, the identity of the server that meets the preset delivery conditions can be obtained based on multiple test results, so that the server corresponding to the identity can be delivered to the corresponding client. In other words, the collected test results can be analyzed, and the servers that meet the conditions can be screened out according to the preset delivery conditions (such as performance indicator thresholds, functional test pass rates, etc.). For example, if the preset delivery conditions are that the CPU performance test score must be higher than a certain threshold and all functional test items must pass, then only servers that meet these conditions will be selected. For servers that meet the delivery conditions, their identity is generated. The identity can be in the form of a unique serial number, QR code, barcode, etc., which is used to indicate that the server has passed the test and meets the delivery standards.

[0039] Finally, the server corresponding to the identification can be prepared for delivery, including packaging and shipping arrangements. Simultaneously, the identification information is provided to the client, allowing them to quickly identify and confirm whether the server meets their requirements upon receipt. This completes the entire process, from receiving client testing tasks to screening and delivering servers that meet delivery requirements. This ensures that the delivered servers meet the manufacturer's quality standards and the client's personalized needs, guaranteeing server delivery quality and reducing the failure rate upon delivery.

[0040] According to an embodiment of the present application, the server delivery method further includes: receiving a server quality code sent by a client; and pre-freezing the corresponding server if the server quality code is not obtained for the first time.

[0041] Specifically, during the server delivery process, a server quality code is a unique identifier used to identify whether the server has passed all tests and meets delivery standards. This code is generated by the client's quality management system and assigned after the server passes all tests. If a server fails to receive a quality code after the initial test, it may not fully meet the client's requirements. Pre-freezing the server in this situation can prevent misidentification due to network issues or other non-hardware issues, and prevent unqualified servers from entering the delivery process.

[0042] First, the server quality code is received from the client. The client's quality management system then generates a unique server quality code based on the server's test results. The quality code can include information such as the server's identity, the test pass timestamp, and the client's identity to ensure its uniqueness and traceability. The quality code is in the form of numbers, letters, or a QR code for easy storage and transmission. The client sends the generated server quality code to the server manufacturer's system via a network interface (such as an API). The transmission process must ensure data security and integrity, and may utilize technologies such as encrypted transmission. After receiving the quality code from the client, the server manufacturer performs preliminary verification to confirm that it is formatted correctly and has not been tampered with. If verification is successful, the system matches the quality code with the server's test records.

[0043] After the server completes the delivery standard testing, it obtains a quality code from the client. If the quality code fails to be obtained within the specified time (e.g., 5 minutes), this failure is recorded and the reason for the failure is obtained. This failure may include network issues, client system latency, or the server not fully meeting the testing standards. If the server quality code is not obtained the first time, the corresponding server can be pre-frozen. Pre-freezing is a temporary freezing measure that temporarily removes the server from the delivery process to prevent misjudgments due to non-hardware issues. Servers that fail to obtain a quality code are marked as "pre-frozen." In this pre-frozen state, the server cannot be shipped, but further inspection and processing are possible. For example, a notification is sent to relevant technical personnel or management personnel to inform them that the server failed to obtain a quality code and has been pre-frozen. The notification may include the server's identity, the pre-freeze time, and possible reasons.

[0044] Therefore, if a server quality code is not obtained initially, the corresponding server will be pre-frozen. This effectively prevents misjudgments due to network problems or other non-hardware issues, preventing qualified servers from being mistakenly frozen and not shipped, while also preventing unqualified servers from entering the shipping process. This also allows technicians to quickly locate and address issues, avoiding the need for comprehensive inspections of large numbers of servers, optimizing resource utilization, and enhancing the traceability of the server delivery process. Specifically, the quality code allows for quick query of server test records and status, facilitating rapid problem location and resolution.

[0045] According to one embodiment of the present application, after pre-freezing the corresponding server, the server delivery method further includes: obtaining a server quality code at a preset interval; upon obtaining the server quality code, unfreezing the pre-frozen server; and if the server quality code is not obtained for a preset number of consecutive times, freezing the corresponding server, wherein the frozen server is not packaged or shipped to the customer. The preset interval can be determined based on actual conditions.

[0046] Specifically, when the server fails to obtain the server quality code sent by the client for the first time, the server can be marked as "pre-frozen" status. Pre-freezing is a temporary measure aimed at temporarily removing the server from the delivery process for further inspection and processing. The server's identity can be recorded in the pre-freeze list, and a notification can be sent to relevant technicians or managers to inform them that the server has been pre-frozen. The notification content includes the server's serial number, pre-freeze time, possible reasons, etc.

[0047] After the corresponding server is pre-frozen, the server quality code can be obtained at preset intervals. The preset interval can be adjusted according to actual conditions, such as 5 minutes, 10 minutes, or longer. This time interval needs to be determined based on the network conditions, the response speed of the client system, and the complexity of the server test. In other words, after pre-freezing, an attempt will be automatically made to obtain the server quality code from the client at preset intervals. Each time an attempt is made to obtain the quality code, the time and result of the attempt will be recorded. By regularly attempting to obtain the quality code, a quick response can be made to the resolution of network problems or other temporary issues, ensuring that the server can enter the delivery process in a timely manner.

[0048] If a server quality code is obtained, the pre-frozen server can be unfrozen, indicating that the server has passed the client's testing and meets delivery standards. The server will be automatically removed from the pre-frozen list and its status will be updated to "unfrozen." The relevant technical staff or management personnel will be notified that the server has been successfully unfrozen. If the server quality code fails to be obtained after a preset number of consecutive attempts, the corresponding server will be frozen. The preset number of attempts can be adjusted based on actual conditions, such as 2 or 5. This number should be determined based on network conditions, client system reliability, and the complexity of the server testing. If the server quality code fails to be obtained after the preset number of consecutive attempts, it may indicate that the server has serious problems and cannot meet the client's requirements. The server will be marked as "frozen" and its serial number will be recorded in the frozen list. A notification will be sent to the relevant technical staff or management personnel stating that the server has been frozen. The notification will include the server's identity, the freezing time, and the number of consecutive times the quality code has not been obtained. Frozen servers will be removed from the shipping process and will not be allowed to be packaged or shipped. This prevents unqualified servers from entering the shipping process and ensures delivery quality. The freezing mechanism allows you to focus on repairing and retesting problem servers, improving resource utilization efficiency.

[0049] Thus, through the pre-freeze, thaw, and freeze mechanisms, only servers that fully meet client requirements are shipped, reducing customer complaints and improving customer satisfaction. This also enhances the traceability of the server delivery process. The quality code allows for quick access to server test records and status, facilitating the rapid identification and resolution of issues. This delivery method allows server manufacturers to more precisely control server quality during the delivery process, ensuring that delivered servers fully meet client requirements.

[0050] According to one embodiment of the present application, the server delivery method further includes: determining the currently frozen server based on the server quality code; and sending an error message to the target person based on the identity identifier of the server.

[0051] Specifically, during the server delivery process, the server quality code is a unique identifier used to identify whether the server has passed all tests and meets delivery standards. This code allows for rapid identification of currently blocked servers and prompts notification of errors to relevant personnel, enabling rapid problem location and action. This approach improves delivery efficiency, reduces delays caused by problematic servers, and enhances customer satisfaction.

[0052] The currently frozen server can be determined based on the server quality code. For example, the serial numbers of all frozen servers are recorded in a frozen server list. When the system needs to determine the currently frozen server, the serial number in the server quality code is matched with the frozen server list. If the serial number in the quality code of a server appears in the frozen server list, the server is identified as the currently frozen server. In this way, the frozen server can be quickly and accurately identified through the server quality code, avoiding errors and delays in manual inspection, improving the degree of automation of the system, and reducing manual intervention. After the corresponding server is determined, an error message can be sent to the target person based on the server's identity. Among them, the target person can be selected according to preset rules. These personnel are usually technicians or managers responsible for server testing, maintenance or delivery. The selection of target personnel can be carried out through role assignment, responsibility area or priority.

[0053] A server's identity (such as a serial number, QR code, or barcode) is an identifier used to uniquely identify the server. When a server is identified as frozen, an error message is generated. This error message may include the server's serial number or other identifier, the reason for freezing (e.g., repeated failure to obtain a quality code, test failure, etc.), the freezing time, and recommended follow-up actions (e.g., checking network connectivity, retesting, repair, etc.). Additionally, error messages can be sent to targeted individuals via pre-defined communication methods (e.g., email, text message, instant messaging, etc.). Error messages must be sent promptly and accurately to ensure a quick response from the targeted individuals.

[0054] Therefore, through the server quality code and identity identification, the frozen server can be identified quickly and accurately, and the relevant information can be notified to the target personnel in a timely manner, reducing the time for problem location, handling the frozen server in a timely manner, avoiding delivery delays caused by problem servers, and improving overall delivery efficiency. By promptly handling problem servers, it is ensured that the delivered server fully meets the client's requirements, reducing customer complaints and improving customer satisfaction.

[0055] According to one embodiment of the present application, delivering a server corresponding to an identity identifier to a corresponding client includes: obtaining server inventory information from a server manufacturer; determining a server delivery order based on the server inventory information and the priority of customer orders; and delivering the server corresponding to the identity identifier to a corresponding client based on the server delivery order and the target address.

[0056] Specifically, when delivering the server corresponding to the ID to the corresponding client, the server manufacturer's server inventory information can be obtained first. Server inventory information refers to detailed information such as the number, model, configuration, and storage location of the currently available servers at the server manufacturer. This information can be stored in the manufacturer's warehouse management system. The latest server inventory information can be obtained in real time, such as the server serial number, server model and configuration, server storage location (such as warehouse number, shelf location), and the server's current status (such as tested, pending shipment, frozen, etc.).

[0057] The server shipment order is determined based on server inventory information and customer order priority. Customer order priority refers to the shipping priority determined by the customer's specific needs, order urgency, contract terms, or other business rules. Priorities can be categorized as high, medium, or low. Based on the acquired server inventory information and customer order priority, a shipping order list is generated. Rules for determining the shipping order may include: Prioritizing high-priority orders: Prioritizing high-priority orders to ensure that urgent needs are met promptly. Stock availability: Prioritizing server models with sufficient inventory to avoid shipping delays due to insufficient inventory. First-come, first-served: For orders of the same priority, orders are shipped in the order they arrived. Geographic location optimization: Optimizing the shipping order based on the geographic location of the destination address to reduce transportation costs and time. By optimizing the shipping order, high-priority orders are prioritized, improving customer satisfaction. Properly arranging the shipping order can reduce delays caused by insufficient inventory or transportation issues, thereby improving overall delivery efficiency.

[0058] After determining the shipping order, the servers identified by their identities are delivered to the corresponding clients based on the server shipping order and the destination address. This means that the corresponding servers are retrieved from the warehouse according to the shipping order list. Each server to be shipped is verified based on its identity (such as serial number, QR code, etc.) to ensure that the server being shipped matches the order. The destination address is the destination specified by the client for the server. Additionally, information such as shipping time, shipping method, and shipping order number can be recorded for subsequent tracking and management.

[0059] Therefore, by optimizing the delivery sequence, we ensure that high-priority orders can be shipped first, reduce delays caused by insufficient inventory or transportation problems, ensure that the shipped servers are consistent with the orders, reduce customer complaints caused by delivery errors, and ensure that the delivered servers fully meet the client's requirements, while improving delivery efficiency and customer satisfaction.

[0060] According to one embodiment of the present application, the server delivery method further includes: determining a target packaging solution based on physical characteristics of the server; and delivering the server to a corresponding client based on the target packaging solution.

[0061] Specifically, during server delivery, the server's physical characteristics (such as weight, size, and shape) directly influence the packaging solution. A suitable packaging solution not only protects the server from damage during transportation but also optimizes transportation costs and storage space. By determining a targeted packaging solution based on the server's physical characteristics and delivering accordingly, delivery efficiency can be improved, transportation risks can be reduced, and customer satisfaction can be enhanced.

[0062] Therefore, the target packaging solution can be determined based on the server's physical characteristics. These physical characteristics can include the server's weight, measured in kilograms (kg). Weight influences the choice of packaging materials and shipping methods. The server's physical dimensions, typically expressed in millimeters (mm) or centimeters (cm), affect the size of the packaging box and the space available for shipping. The server's physical form, such as standard rack-mount servers or tower servers, influences the customization requirements for packaging. When determining the target packaging solution, heavier servers require sturdier packaging materials, such as thickened corrugated cardboard, shock-absorbing foam, or wooden boxes, to prevent weight damage during shipping. Lighter servers can be packaged in lighter materials to reduce packaging costs and shipping weight. Alternatively, select an appropriately sized box based on the server's size to avoid wasting material by using oversized boxes. Larger servers may require customized boxes to ensure stability during shipping. Standard rack-mount servers and tower servers may require different packaging solutions. For example, rack-mounted servers may require special brackets or fixtures to prevent sliding or collision during transportation. For servers with special shapes, customized packaging solutions may be required to ensure their safety during transportation.

[0063] After determining the target packaging solution, the server can be delivered to the client according to the target packaging solution. This means that the server is packaged according to the target packaging solution, ensuring that the server is securely secured within the packaging box to prevent movement or collision during transportation. Once packaged, the server is moved to the shipping area and prepared for shipment to the client's specified destination address.

[0064] Therefore, through a reasonable packaging solution, we can ensure that the server is not damaged during transportation, improve the delivery quality, optimize the use of packaging materials and packaging boxes, reduce packaging costs and transportation weight, and lower transportation costs.

[0065] According to one embodiment of the present application, customer test items include at least one of server memory performance test, server central processing unit performance test, and server target function and compatibility test; server manufacturer test items include at least one of server performance stress test, server firmware and version check, and server target hardware function check.

[0066] Specifically, during the server delivery process, testing items can be divided into two categories: customer testing items and server manufacturer testing items. These testing items are designed to ensure that the server fully meets the client's requirements and meets the server manufacturer's quality standards upon delivery.

[0067] Customer test items are test tasks defined by the client based on its own business needs and usage scenarios, and are used to verify whether the server meets specific performance and functional requirements. Customer test items include at least one of server memory performance testing, server central processing unit performance testing, and server target function and compatibility testing. Among them, the test content of the server memory performance test may include memory bandwidth testing: measuring the read and write speeds of the server memory to ensure that it can meet applications with high bandwidth requirements. Memory latency testing: measuring the response time of the memory to ensure that it can quickly respond to CPU requests. Memory stability testing: by running the memory stress testing tool for a long time, detect whether there are errors or failures in the memory. Server memory performance testing is used to ensure that the server's memory performance can meet the client's business needs, especially when processing big data and high-performance computing tasks.

[0068] Server CPU performance testing can include CPU benchmark testing: measuring the CPU's single-threaded and multi-threaded performance to ensure it can handle complex computing tasks. CPU stress testing: testing the CPU's stability and reliability by running high-load CPU tasks for extended periods. CPU performance optimization testing: testing the CPU's performance under different workloads to ensure it can operate efficiently. Server CPU performance testing is used to ensure that the server's CPU performance can meet the client's business needs, especially when handling highly concurrent and complex computing tasks.

[0069] Targeted functionality and compatibility testing of servers may include: Targeted functionality testing: Testing whether the server has the specific functionality required by the client, such as virtualization support, network functions, storage functions, etc. Compatibility testing: Testing the compatibility of the server with the operating system, applications, and third-party devices used by the client. Integration testing: Testing the server's integration capabilities within the client's existing IT environment to ensure seamless integration. Targeted functionality and compatibility testing of servers is used to ensure that the server can meet the client's specific functional requirements and is compatible with the client's existing IT (Information Technology Environment).

[0070] Server manufacturer test items are test tasks defined by server manufacturers based on their own quality control systems and industry standards to ensure that the basic functions and performance of the server meet the standards. Server manufacturer test items may include at least one of the server's performance stress test, server firmware and version check, and server target hardware function check. Among them, the server's performance stress test may include comprehensive performance testing: by running multiple loads, testing the server's performance under high load. Long-term operation test: by running high-load tasks for a long time, detecting the stability and reliability of the server. Performance optimization test: testing the performance of the server under different configurations to ensure that it can run efficiently. The server's performance stress test is used to ensure that the server can run stably under high load and meet basic performance requirements.

[0071] The test content of the server's firmware and version check may include firmware version check: ensuring that the server's BIOS (Basic Input / Output System), BMC (Baseboard Management Controller), CPLD (Complex Programmable Logic Device), network card FW (Network Card Firmware), and other firmware versions meet the requirements. Firmware function test: testing the basic functions of the firmware, such as startup, network connection, etc. Firmware update test: testing the stability and reliability of the firmware update process. The server's firmware and version check test is used to ensure that the server's firmware version is correct and the firmware functions normally, avoiding failures caused by firmware problems.

[0072] The server's targeted hardware functionality check includes hardware functionality testing: testing the server's hardware functions, such as the CPU, memory, hard drive, and network interface card. Hardware compatibility testing: testing the compatibility between the server's hardware components. Hardware stability testing: testing the stability of the hardware by running high-load tasks for a long time. This server's targeted hardware functionality check is designed to ensure that the server's hardware functions properly and that hardware components are compatible, thus preventing failures caused by hardware issues.

[0073] By combining customer testing with server manufacturer testing, we can fully verify the server's performance, functionality, and compatibility, ensuring that the delivered server fully meets the client's requirements and the server manufacturer's quality standards. This comprehensive testing approach can effectively improve delivery quality, reduce customer complaints, and increase customer satisfaction.

[0074] According to one embodiment of the present application, multiple servers are controlled to execute at least one delivery standard test task, and the server delivery method also includes: obtaining the configuration information and historical test records of the server, and adjusting the delivery standard test task based on the configuration information and historical test records.

[0075] Specifically, when controlling multiple servers to execute at least one delivery standard test task, big data analysis can also be used to dynamically adjust the test strategy based on factors such as the server model, configuration, historical test records, etc., so as to automatically identify the test focus and difficulty of different servers, and adjust the delivery standard test tasks to improve test efficiency and accuracy.

[0076] First, obtain server configuration information and historical test records. For example, the server manufacturer collects server configuration information, including hardware configuration (such as CPU model, memory capacity, hard drive type), and software versions (such as BIOS, BMC, and CPLD). Historical test records may include test results (such as pass / fail status, performance metrics, and maintenance records). After obtaining these configuration information and historical test records, the standard test tasks for delivery can be adjusted based on these information and historical test records. Machine learning algorithms can be used to analyze the collected data to identify key testing areas and challenges for different servers. For example, cluster analysis and association rule mining can be used to determine whether servers with specific configurations frequently experience issues in a particular test item. Based on these analysis results, the standard test tasks for delivery can be adjusted, and a personalized test plan can be automatically generated. For example, for test items that frequently fail, the weight and test depth of these items can be automatically increased to ensure that these potential issues are fully detected. At the same time, for test items with high stability and reliability, the test depth can be appropriately reduced to improve testing efficiency. This allows for continuous optimization of test strategies based on the latest test data and feedback. For example, if a test item no longer has frequent problems after improvement, the test strategy will be automatically adjusted to reduce the weight and depth of the test item.

[0077] For example, a certain server model frequently experiences performance fluctuations during memory performance testing, resulting in a high test failure rate. After identifying this issue through data analysis, the weight and depth of the memory performance test can be automatically increased. For example, the load level can be increased, gradually moving from low to high load, and the test duration can be extended from short tests to long stability tests. This increased test depth allows for more comprehensive detection of memory performance issues, proactively identifying potential failure points, and improving server reliability and stability. Another example is that after hardware improvements, the failure rate of a particular test item has significantly decreased. Real-time monitoring and data analysis reveal a decrease in the failure rate of this test item, and the test strategy is automatically adjusted to reduce the weight and depth of this test item, allocating more resources to other high-risk test items. This dynamic adjustment of the test strategy enables more efficient utilization of test resources, improving overall test efficiency while ensuring server quality is not compromised.

[0078] In this way, the test focus and difficulty of different servers can be automatically identified, and personalized test plans can be automatically generated to improve test efficiency and accuracy.

[0079] In one embodiment of the present application, server manufacturers can also utilize artificial intelligence algorithms to analyze and mine the large amounts of data generated during server testing to establish a fault prediction model. By learning from historical data and identifying patterns, potential failure risks can be predicted in advance and early warnings can be issued during the testing phase. For example, performance indicator data can be collected from servers under different load conditions, including but not limited to CPU usage, memory usage, disk I / O (Input / Output), network bandwidth, temperature, and voltage. Furthermore, server hardware configuration information, software version information, and historical maintenance records are collected. The collected data is then cleaned, standardized, and features extracted to ensure data quality and usability. For example, noise removal, missing value filling, and data conversion to a unified format are performed. Machine learning algorithms (such as decision trees, random forests, support vector machines, and neural networks) are used to train the preprocessed data to establish a fault prediction model. The model learns patterns and regularities in historical data and identifies feature combinations that may lead to failures. Consequently, performance indicator data is collected in real time during server operation and fed into the trained model, which then outputs a fault prediction result. If the prediction results indicate a potential failure risk, an early warning will be issued, such as via email, text message, or instant messaging, to maintenance personnel. The warning information includes the failure type, risk level, and recommended repair measures. This allows for early warnings and preventive maintenance recommendations based on the failure prediction results. Maintenance personnel can use this information to proactively inspect and maintain the server, preventing failures from occurring.

[0080] For example, consider a server whose historical data includes the following performance metrics: CPU usage, memory usage, hard disk read / write error rate, and CPU temperature. Analysis of this data reveals the following correlation patterns: a cyclical pattern: CPU usage increases significantly during daily peak hours (9:00 AM to 5:00 PM); a trending pattern: the hard disk read / write error rate gradually increases over time; a correlation pattern: a positive correlation between CPU temperature and CPU usage; and an anomaly pattern: a sudden rise in CPU temperature exceeding 80°C and a sudden increase in hard disk read / write error rate exceeding 10%. Based on these patterns, a fault prediction model can be built. The model monitors these performance metrics in real time and issues alerts when the following conditions are detected: CPU temperature exceeding 80°C, hard disk read / write error rate exceeding 10%, and CPU usage consistently exceeding 90% during off-peak hours. This approach can identify potential fault risks in advance and issue alerts, enabling maintenance personnel to perform preventive maintenance and avoid failures.

[0081] Therefore, intelligent fault prediction and prevention utilizes artificial intelligence algorithms to analyze and mine the vast amounts of data generated during server testing to establish a fault prediction model. By learning from historical data and identifying associated patterns, it can predict potential failure risks in advance and issue early warnings during the testing phase. By implementing preventive maintenance in advance, it effectively reduces failure rates and improves server reliability and stability. This approach not only improves server operational efficiency but also reduces downtime and repair costs caused by failures.

[0082] The following combination Figure 2 To describe the method of this application.

[0083] As a specific example, the server delivery method of the present application may include the following steps:

[0084] S101: Receive at least one client test task sent by a client.

[0085] S102: Generate at least one delivery standard test task on the server manufacturer side based on the server manufacturer test task and the customer test task.

[0086] S103: Control multiple servers to execute at least one delivery standard test task, and generate a test result for each server.

[0087] S104: Obtain an identity of a server that meets a preset delivery condition based on multiple test results.

[0088] S105: Receive the server quality code sent by the client.

[0089] S106: Determine whether the server quality code is not obtained for the first time. If yes, go to step S107; if not, go to step S111.

[0090] S107: Pre-freeze the corresponding server.

[0091] S108: Obtain the server quality code at every preset time interval.

[0092] S109, when the server quality code is obtained, the frozen server is unfrozen, and when the server quality code is not obtained for a preset number of consecutive times, the corresponding server is frozen, wherein the frozen server is not packaged and shipped to the customer.

[0093] S110: Determine the currently frozen server based on the server quality code, and send an error message to a target person based on the server's identity.

[0094] S111 , obtaining server inventory information from the server manufacturer and determining a target packaging solution based on the physical characteristics of the server.

[0095] S112: Determine the server delivery order based on the server inventory information and the priority of the customer order.

[0096] S113: Deliver the server corresponding to the identity identifier to the corresponding client based on the server shipping sequence, target address, and target packaging solution.

[0097] In summary, according to the server delivery method of the embodiment of the present application, at least one client test task sent by the client is received, at least one delivery standard test task of the server manufacturer is generated based on the server manufacturer test task and the client test task, multiple servers are controlled to execute at least one delivery standard test task, a test result of each server is generated, and the identity of the server that meets the preset delivery conditions is obtained based on multiple test results, so as to deliver the server corresponding to the identity to the corresponding client. As a result, the method can integrate the test tasks of the server manufacturer and the test tasks of the client, generate a unified delivery standard test task, ensure that the server passes all necessary tests before shipment, thereby improving the quality and efficiency of server delivery and enhancing customer satisfaction.

[0098] Figure 3 Flowchart of a server verification method according to an embodiment of the present invention.

[0099] like Figure 3 As shown, the server verification method of the embodiment of the present invention may include the following steps:

[0100] S10, receiving the test results of each server sent by the server manufacturer.

[0101] S11, determining a target server based on preset test criteria and test results.

[0102] S12: determining a server quality code based on the target server, and sending the server quality code to the server manufacturer.

[0103] Specifically, during the server delivery process, the client needs to verify and evaluate the test results sent by the server manufacturer to ensure that the server meets pre-set quality standards and functional requirements. By receiving the test results, evaluating whether the server meets the standards, and generating a server quality code, the client can ensure that the delivered server fully meets its business requirements. First, the client receives the test results for each server from the server manufacturer. After completing all tests, the server manufacturer encapsulates each server's test results into a data package in a standardized format (such as JSON or XML). The test results may include: a server identifier (which uniquely identifies the server); test items (such as memory performance test, CPU performance test, and firmware version check); test results (pass / fail status for each test item, along with specific test data (such as performance indicator values); and a test log (which records detailed information from the test process for subsequent analysis). The client receives the test result data package sent by the server manufacturer via a network interface (such as an API). The client (such as its test management system) parses the received data package to extract the specific test result information.

[0104] After obtaining the test results, the target server can be determined based on the preset test criteria and test results. In other words, the client presets a series of test criteria based on its own business needs and quality standards. These criteria define the minimum standards that the server must meet, such as: the minimum bandwidth requirement for memory performance testing, the minimum performance indicators for CPU performance testing, the firmware version must meet specific requirements, and the server must pass all functional tests. The client can compare the received test results with the preset test criteria to evaluate whether each server meets the standards. For each test item, check whether the test results meet the preset performance indicators or pass status. If the server's test results fully meet the preset test criteria, the server is marked as a "target server." If the server's test results do not meet the preset test criteria, the server is marked as "failed" and the specific reason for failure is recorded.

[0105] After determining the target server, the server quality code can be determined based on the target server and sent to the server manufacturer. That is, for each server marked as a target server, the client generates a unique server quality code. The server quality code can include the following information:

[0106] Server ID: Uniquely identifies the server. Test Pass Timestamp: Records the specific time the server passed the test. Client ID: Identifies the client that generated the quality code. Quality Code Version: Identifies the quality code version. The server quality code can be a numeric sequence, an alphanumeric combination, or a QR code for easy storage and transmission. The client sends the generated server quality code back to the server manufacturer via a network interface. After receiving the quality code, the server manufacturer matches it with the server's records to confirm that the server has passed the client's test.

[0107] By receiving test results from server manufacturers, assessing whether the servers meet pre-set test criteria, and generating a server quality code, clients can ensure that the delivered servers fully meet their business requirements. This process not only improves delivery quality but also enhances transparency and traceability of the delivery process.

[0108] According to one embodiment of the present application, the target server is determined based on preset test criteria and test results, including: if all test tasks in the test results meet the preset test criteria, then the corresponding server is determined as the target server; if there is at least one test task in the test results that does not meet the preset test criteria, then an error message is sent to the server manufacturer.

[0109] Specifically, during the server delivery process, clients need to evaluate the test results provided by the server manufacturer against pre-set test criteria to determine whether the server meets delivery standards. This process not only ensures that the server meets the client's quality and functional requirements, but also promptly identifies and addresses non-compliant servers, improving delivery efficiency and quality.

[0110] When determining the target server based on the preset test criteria and test results, for each server's test results, check each test task item by item to see if it meets the preset test criteria. If all test tasks meet the preset test criteria, the server can be determined as the target server, and the server's identity and test pass timestamp can be recorded. If at least one test task does not meet the preset test criteria, the non-compliant test task and its specific problem can be recorded, and an error message can be generated, detailing the non-compliant test task and the reason. The error message may include: the server's identity, the non-compliant test task and its specific problem, recommended follow-up measures (such as retesting, repair, etc.), sending the error message back to the server manufacturer through a network interface (such as an API), sending the server quality code back to the server manufacturer, confirming that the server meets the delivery standards, etc.

[0111] For example, the preset test criteria are: in the memory performance test, bandwidth ≥ 30GB / s, latency ≤ 20ns, in the CPU performance test, performance index ≥ 90%, and in the firmware version check, BIOS version = 1.2.3, BMC version = 4.5.6. If all test tasks meet the preset test criteria, server SN12345678 can be determined as the target server, and a server quality code can be generated and sent back to the server manufacturer. If the CPU performance index of a test task is lower than 90%, an error message indicating the low CPU performance index can be sent back to the server manufacturer.

[0112] By determining target servers based on pre-set test criteria and test results, clients can ensure that the delivered servers fully meet their business requirements. This process not only improves delivery quality but also enhances transparency and traceability of the delivery process. By promptly identifying and addressing non-compliant servers, delivery delays caused by problematic servers can be reduced, improving customer satisfaction.

[0113] According to one embodiment of the present application, the server quality code includes server manufacturer information, the time when the server passed the test, and the server identity.

[0114] Specifically, the server quality code is a unique identifier that identifies whether a server has passed all tests and meets delivery standards. It not only ensures that the server fully meets client requirements upon delivery but also provides traceability, facilitating subsequent management and auditing. The server quality code includes information about the server manufacturer, the date the server passed testing, and the server's identity, providing comprehensive information about the server's status.

[0115] Server manufacturer information may include: Manufacturer Name: The name or code of the server manufacturer, used to identify the company that produced the server. Manufacturer Address: The address or contact information of the server manufacturer, which facilitates subsequent communication and traceability. Manufacturer ID: A unique identifier, such as a company code or registration number, that uniquely identifies the manufacturer. Manufacturer information allows for quick tracing of the server's production source, facilitating subsequent quality management and problem resolution. It also clarifies the server manufacturer, making it easier to assign responsibility if problems arise.

[0116] The server's test pass time includes a test pass timestamp: the specific time the server passed all tests, typically recorded in a standard time format (such as ISO 8601), for example, 2025-10-01T14:30:00Z. Test batch number: If the server is part of a batch test, the test batch number can be recorded for management and traceability. The server's test pass time is used to record the specific time the server passed the test, facilitating subsequent auditing and management. The timestamp also allows verification that the server's test results are within the validity period, especially when there are shelf life or timeliness requirements.

[0117] Server identification can include the server serial number: a unique serial number used to uniquely identify each server. The server model: information about the server's model, which facilitates identification of its specifications and configuration. Other identifiers, such as QR codes and barcodes, are used for quick identification and scanning. Serial numbers and other identifiers allow for quick identification and management of each server, while QR codes and barcodes allow for quick scanning and recording of server information, improving management efficiency.

[0118] After the server passes all tests, the client generates a server quality code. This code can be generated by combining data, such as combining the server manufacturer information, the test pass timestamp, and the server identity into a single data structure. Alternatively, the code can be generated by encoding the data structure into a unique string of numbers, letters, or a QR code. To ensure the security and immutability of the quality code, the data can be encrypted.

[0119] The client then sends the generated server quality code back to the server manufacturer via a network interface. Upon receiving the quality code, the server manufacturer matches it with the server's records to confirm that the server has passed the client's testing. After the server manufacturer verifies that the server meets delivery standards based on the quality code, it packages and ships the server. The quality code can be printed on the packaging or included in shipping documents for easy verification by the client upon receipt. Upon receiving the server, the client scans or enters the quality code to verify that the server meets delivery standards. If the quality code is valid, the client can confirm that the server has passed all tests and meets delivery requirements. Through this mechanism, clients and server manufacturers can effectively manage the server delivery process, improving delivery quality and efficiency.

[0120] In summary, the server verification method according to the embodiments of the present application receives the test results of each server sent by the server manufacturer, determines the target server based on preset test criteria and test results, determines the server quality code based on the target server, and sends the server quality code to the server manufacturer. This method can thus integrate the server manufacturer's test tasks with the client's test tasks, generating a unified delivery standard test task, ensuring that the server passes all necessary tests before shipment, thereby improving the quality and efficiency of server delivery and enhancing customer satisfaction.

[0121] For ease of understanding, the interaction between the server manufacturer and the client of the present invention is described in a specific embodiment. Figure 4 As shown, the interaction method of the embodiment of the present invention may include the following steps:

[0122] S201: Send at least one test task to a client.

[0123] S202: Receive at least one client test task sent by a client.

[0124] S203: Generate at least one delivery standard test task on the server manufacturer side based on the server manufacturer test task and the customer test task.

[0125] S204: Control multiple servers to execute at least one delivery standard test task, and generate a test result for each server.

[0126] S205: Send the test result of each server.

[0127] S206: Receive the test results of each server sent by the server manufacturer.

[0128] S207: Determine the target server based on the preset test criteria and the test results.

[0129] S208: Determine a server quality code based on the target server.

[0130] S209: Send the server quality code to the server manufacturer.

[0131] S210, receiving the server quality code sent by the client, and proceeding to step S213 if the server quality code is received; and proceeding to step S211 if the server quality code is not received.

[0132] S211: If the server quality code is not obtained for the first time, the corresponding server is pre-frozen.

[0133] S212, obtaining the server quality code at every preset interval. When the server quality code is obtained, the frozen server will be unfrozen. When the server quality code is not obtained for the preset number of consecutive times, the corresponding server will be frozen. The frozen server will not be packaged or shipped to the customer.

[0134] S213: When the server quality code is obtained, the corresponding server is delivered to the corresponding client.

[0135] Corresponding to the above embodiment, the present application also proposes a non-volatile computer-readable storage medium.

[0136] The non-volatile computer-readable storage medium of an embodiment of the present application stores a program thereon, which, when executed by a processor, implements the above-mentioned server delivery method or the above-mentioned server verification method.

[0137] According to the non-volatile computer-readable storage medium of the embodiment of the present application, by executing the above-mentioned server delivery method or verification method, it is possible to integrate the testing tasks of the server manufacturer and the testing tasks of the client, generate a unified delivery standard testing task, and ensure that the server passes all necessary tests before shipment, thereby improving the quality and efficiency of server delivery and enhancing customer satisfaction.

[0138] Corresponding to the above embodiment, the present application also proposes an electronic device.

[0139] like Figure 5 As shown, the electronic device 200 of an embodiment of the present application may include: a memory 210, a processor 220, and a program stored in the memory 210 and executable on the processor 220. When the processor 220 executes the program, the above-mentioned server delivery method is implemented.

[0140] According to the electronic device of the embodiment of the present application, by executing the above-mentioned server delivery method, it is possible to integrate the testing tasks of the server manufacturer and the testing tasks of the client, generate a unified delivery standard testing task, and ensure that the server passes all necessary tests before shipment, thereby improving the quality and efficiency of server delivery and enhancing customer satisfaction.

[0141] Corresponding to the above embodiment, the present application also proposes an electronic device.

[0142] like Figure 6 As shown, the electronic device 300 of the embodiment of the present application may include: a memory 310, a processor 320, and a program stored in the memory 310 and executable on the processor 320. When the processor 320 executes the program, the above-mentioned server verification method is implemented.

[0143] According to the electronic device of the embodiment of the present application, by executing the above-mentioned server verification method, it is possible to integrate the testing tasks of the server manufacturer and the testing tasks of the client, generate a unified delivery standard testing task, and ensure that the server passes all necessary tests before shipment, thereby improving the quality and efficiency of server delivery and enhancing customer satisfaction.

[0144] Corresponding to the above embodiments, the present application also proposes a computer program product.

[0145] A computer program product in an embodiment of the present application includes a computer program / instruction, which implements the above-mentioned server delivery method when executed by a processor.

[0146] According to the computer program product of the embodiment of the present application, by executing the above-mentioned server delivery method, it is possible to integrate the testing tasks of the server manufacturer and the testing tasks of the client, generate a unified delivery standard testing task, and ensure that the server passes all necessary tests before shipment, thereby improving the quality and efficiency of server delivery and enhancing customer satisfaction.

[0147] Corresponding to the above embodiments, the present application also proposes a computer program product.

[0148] A computer program product in an embodiment of the present application includes a computer program / instruction, and when the computer program / instruction is executed by a processor, the above-mentioned server verification method is implemented.

[0149] According to the computer program product of the embodiment of the present application, by executing the above-mentioned server verification method, it is possible to integrate the testing tasks of the server manufacturer and the testing tasks of the client, generate a unified delivery standard testing task, and ensure that the server passes all necessary tests before shipment, thereby improving the quality and efficiency of server delivery and enhancing customer satisfaction.

[0150] It should be noted that the logic and / or steps represented in flowcharts or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (e.g., a computer-based system, a system including a processor, or other system that can fetch and execute instructions from an instruction execution system, apparatus, or device). For purposes of this specification, a "computer-readable medium" can be any device that can contain, store, communicate, propagate, or transport a program for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (non-exhaustive list) of computer-readable media include the following: an electrical connection with one or more wires (electronic device), a portable computer disk cartridge (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and programmable read-only memory (EPROM or flash memory), fiber optic devices, and a portable compact disc read-only memory (CDROM). Furthermore, the computer-readable medium may even be paper or other suitable medium on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium and then editing, interpreting or processing it in another suitable manner if necessary, and then storing it in a computer memory.

[0151] It should be understood that various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above-described embodiments, multiple steps or methods can be implemented using software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented using hardware, as in another embodiment, any one of the following technologies known in the art or a combination thereof can be used: a discrete logic circuit having logic gate circuits for implementing logic functions on data signals, an application-specific integrated circuit having suitable combinational logic gate circuits, a programmable gate array (PGA), a field-programmable gate array (FPGA), etc.

[0152] Throughout this specification, reference to terms such as "one embodiment," "some embodiments," "examples," "specific examples," or "some examples" means that a specific feature, structure, material, or characteristic described in conjunction with that embodiment or example is included in at least one embodiment or example of the present application. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.

[0153] Furthermore, 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 number of the technical features being referred to. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of such features. Throughout the description of this application, "plurality" means at least two, for example, two, three, etc., unless otherwise specifically defined.

[0154] In this application, unless otherwise specified or limited, the terms "installed," "connected," "connect," "fixed," etc. should be understood in a broad sense. For example, they can refer to fixed connection, detachable connection, or integration; mechanical connection or electrical connection; direct connection or indirect connection through an intermediate medium; internal communication between two elements or interaction between two elements, unless otherwise specified. Those skilled in the art will understand the specific meanings of the above terms in this application based on specific circumstances.

[0155] Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limitations on the present application. Ordinary technicians in this field can change, modify, replace and modify the above embodiments within the scope of the present application.

Claims

1. A server delivery method, characterized in that: Applied to a server manufacturer, the method includes: Receiving at least one customer test task sent by a client, wherein the customer test task is determined based on the user's own business needs and performance requirements; Deduplication and priority adjustment of the server manufacturer's test tasks and the customer's test tasks to generate at least one delivery standard test task on the server manufacturer's side, wherein the server manufacturer's test task is determined based on server industry standards and the server manufacturer's own server quality control system; Controlling multiple servers to execute the at least one delivery standard test task, generating a test result for each server, and obtaining an identity identifier of a server that meets a preset delivery condition based on the multiple test results, so as to deliver the server corresponding to the identity identifier to the corresponding client; Receiving a server quality code sent by the client; In the case that the server quality code is not obtained for the first time, the corresponding server is pre-frozen.

2. The server delivery method according to claim 1, characterized in that: After pre-freezing the corresponding server, the method further includes: Obtaining the server quality code at preset intervals; When the server quality code is obtained, the pre-frozen server is unfrozen; In the case that the server quality code is not obtained for a preset number of consecutive times, the corresponding server will be frozen, wherein the frozen server will not be packaged and shipped to the customer.

3. The server delivery method according to claim 2, characterized in that: The method further comprises: Determining a currently frozen server based on the server quality code; Send an error message to the target person based on the identity identification of the server.

4. The server delivery method according to claim 1, characterized in that: The delivering the server corresponding to the identity identifier to the corresponding client includes: Obtaining server inventory information from the server manufacturer; Determining a server delivery order based on the server inventory information and the priority of the customer orders; The server corresponding to the identity identifier is delivered to the corresponding client based on the server shipping order and target address.

5. The server delivery method according to claim 4, characterized in that: The method further comprises: determining a target packaging solution based on physical characteristics of the server; The server is delivered to the corresponding client based on the target packaging solution.

6. The server delivery method according to claim 1, characterized in that: The controlling of the plurality of servers to execute the at least one delivery standard test task, the method further comprising: Obtaining configuration information and historical test records of the server; The delivery standard test task is adjusted based on the configuration information and the historical test records.

7. A server verification method, characterized in that: Applied to a client, the method includes: Receiving a test result of each server sent by a server manufacturer, wherein the test result is determined based on the execution of the at least one delivery standard test task by the plurality of servers, and the delivery standard test task is determined based on the server manufacturer's test task and the customer's test task; determining a target server based on preset test criteria and the test results, wherein the preset test criteria define minimum standards that the target server should meet, including at least one of memory performance, central processing unit performance, firmware version, and whether the server passes all tests; A server quality code is determined based on the target server, and the server quality code is sent to the server manufacturer, wherein the server quality code includes server manufacturer information, server passing test time, and server identity.

8. The server verification method according to claim 7, characterized in that: The determining of the target server based on the preset test criteria and the test result includes: If all the test tasks in the test results meet the preset test criteria, determining the corresponding server as the target server; If at least one of the test tasks in the test result does not meet the preset test criteria, an error message is sent to the server manufacturer.

9. A non-volatile computer-readable storage medium, characterized in that: A program is stored thereon, which, when executed by a processor, implements the server delivery method according to any one of claims 1-6 or the server verification method according to any one of claims 7-8.

10. An electronic device, characterized in that: include: A memory, a processor, and a program stored in the memory and executable on the processor, wherein when the processor executes the program, the server delivery method according to any one of claims 1 to 6 is implemented.

11. An electronic device, characterized in that: include: A memory, a processor, and a program stored in the memory and executable on the processor, wherein when the processor executes the program, the server verification method according to any one of claims 7 to 8 is implemented.

12. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instructions are executed by a processor, the server delivery method according to any one of claims 1 to 6 is implemented.

13. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instruction is executed by a processor, the server verification method according to any one of claims 7 to 8 is implemented.

Images