Label management method and label management system for electronic equipment test information

Abstract

The embodiment of the invention provides a label management method and a label management system for electronic equipment test information. The method comprises the steps that the method is applied to a tested electronic device, and the electronic device is connected with a pipe side device through a communication interface; the label management method comprises the steps of obtaining test result information of a target detection item of electronic equipment under the condition that the electronic equipment is connected to management side equipment; the test result information is used for indicating attribute parameters and control parameters of the electronic equipment; based on the attribute parameters and the control parameters of the electronic equipment, performing updating operation on historical test information of the electronic equipment; and in the form of the electronic tag, continuously displaying the target test information when the interface of the electronic equipment is in the specific state. By adopting the method, the target test information of the electronic equipment can be automatically and visually managed, and the reliability, traceability and management efficiency of the target test information are effectively improved.

Description

Technical Field

[0001] This application relates to the field of terminal equipment technology, and in particular to a label management method and label management system for electronic equipment test information. Background Technology

[0002] With the rapid development of electronic information technology, the functions of electronic devices are becoming increasingly complex, placing higher demands on the accuracy, efficiency, and traceability of testing in their manufacturing and quality control processes. Before electronic devices officially leave the factory, they need to undergo outgoing quality inspection. Functional and performance testing is an indispensable and crucial step in this process. This testing not only determines whether the equipment meets factory standards but also requires complete recording of the functional and performance test information generated during the testing process, enabling subsequent quality traceability.

[0003] However, the current common management method is to attach test information to the protective film of electronic devices in the form of paper labels. This method separates the test data from the electronic device itself, making it impossible to manage the reliability of the electronic device. This results in a lag in the overall test data management and difficulty in traceability. Summary of the Invention

[0004] This application provides a tag management method and tag management system for electronic device test information. By acquiring test result information, updating historical test information, and directly displaying the latest target test information on the device interface in the form of electronic tags, the system can automate and visualize the management of target test information of electronic devices, effectively improving the reliability, traceability, and management efficiency of target test information.

[0005] To achieve the above objectives, in a first aspect, embodiments of this application provide a tag management method for electronic device test information, applied to the electronic device under test, wherein the electronic device and the monitoring device are connected via a communication interface; the tag management method includes: when the electronic device is connected to the monitoring device, acquiring test result information of the target test items of the electronic device; the test result information is used to indicate the attribute parameters and control parameters of the electronic device; updating the historical test information of the electronic device based on the attribute parameters and control parameters of the electronic device; and continuously displaying the target test information in the form of electronic tags in a specific state on the interface of the electronic device.

[0006] The tag management method for electronic device test information provided in this application automatically acquires test result information of target testing items when the electronic device is connected to the monitoring device, and dynamically updates historical test information based on the electronic device attribute parameters and control parameters reflected in the test result information, thereby achieving real-time synchronization and accurate maintenance of target test information. Simultaneously, the target test information is continuously displayed in the form of electronic tags in specific states on the device interface. This allows for automated and visual management of target test information for electronic devices, effectively improving the reliability, traceability, and management efficiency of the target test information.

[0007] In one feasible implementation, acquiring target test information for an electronic device includes: receiving control commands sent by a receiving device; wherein the control commands originate from control commands generated by a managing device, or are generated by a cloud computing device and forwarded by the managing device; and acquiring target test information based on the control commands. This approach, by being compatible with multi-source control commands (local or cloud-based), flexibly adapts to different testing scenarios, effectively improving the automation, response speed, and scalability of the testing process, while reducing dependence on a single device and ensuring the timeliness and robustness of test information acquisition.

[0008] In one feasible implementation, acquiring target test information of an electronic device includes: responding to a user's triggering operation on a target application of the electronic device, displaying a tag update control through a graphical user interface; wherein the tag update control includes any one of a tag adding control, a tag editing control, and a tag deleting control; generating control instructions based on the update operation performed by the user through the tag update control; and acquiring target test information based on the control instructions. In this way, through a user interface, testers can flexibly manage target test information according to actual needs, significantly improving the convenience and adaptability of target test information operation, lowering the professional operation threshold, and enhancing the human-machine collaboration efficiency and user experience of the testing process.

[0009] In one feasible implementation, updating the historical test information of the electronic device based on its attribute parameters and control parameters includes: writing the attribute parameters and control parameters of the electronic device into an asynchronous processing queue; retrieving the attribute parameters and control parameters of the electronic device from the asynchronous processing queue; and updating the historical test information of the electronic device based on the attribute parameters of the electronic device; wherein the update operation includes at least one of an add operation, an edit operation, and a modify operation. By employing an asynchronous processing mechanism, the target test information acquisition and data update processes are effectively decoupled, which not only improves the response speed and throughput of the electronic device but also avoids interface lag or data blocking problems caused by real-time writing; at the same time, the buffering characteristics of the asynchronous queue can also enhance the stability of the electronic device under high load or network fluctuation environments, ensuring the integrity and consistency of the test data.

[0010] In one feasible implementation, target test information is continuously displayed in the form of electronic tags on the interface of an electronic device when it is in a specific state. This includes: upon detecting a screen lock event, acquiring the target test information corresponding to the displayable state; and displaying the target test information corresponding to the displayable state on the lock screen interface in the form of electronic tags. By presenting the target test information while the electronic device is locked, key test data is ensured to be quickly viewed even when the device is locked, eliminating the need for frequent device unlocking by the user, significantly improving test monitoring efficiency and user experience.

[0011] In one feasible implementation, the method further includes displaying target test information in the target application interface of the electronic device in the form of electronic tags. This ensures accurate presentation of ordinary test information in the corresponding application scenario by displaying target test information in the application interface of the electronic device, significantly improving test monitoring efficiency and user experience. Secondly, embodiments of this application provide another method for tag management of electronic device test information. The control-side device communicates with the electronic device under test and the cloud computing device through communication interfaces. The tag management method includes: acquiring captured images; if the captured images include at least one physical tag object representing the attributes of the electronic device, processing the physical tag object representing the attributes of the electronic device in the captured images to obtain control instructions; the control instructions include target test information of the electronic device; and sending the target test information to the electronic device through the communication interface, so that the electronic device updates its historical test information based on the target test information.

[0012] The tag management method for electronic device test information provided in this application acquires images containing physical tags of electronic devices through a monitoring device, intelligently identifies and processes the tags that characterize the attributes of the electronic devices, extracts control commands containing target test information, and transmits the control commands to the electronic devices to automatically update their historical test data. This enables the conversion of physical tag information into digital test data, improves the automation and adaptability of the testing process, and effectively reduces the complexity of test management.

[0013] In one feasible implementation, the physical tag objects representing the functions and performance of an electronic device in a captured image are processed to obtain control commands. This includes: identifying the physical tag objects representing the functions and performance of the electronic device in the captured image to determine a target image; the target image includes multiple tag text boxes; using the multiple tag text boxes as input to a neural network model, at least one electronic tag is obtained using the neural network model; the electronic tag is structured data containing tag type and / or tag text content; and based on the structured data of tag type and / or tag text content, control commands for controlling the electronic device are generated. In this way, the intelligent conversion of tags from paper data to structured data through the neural network model improves the accuracy and robustness of tag recognition.

[0014] In one feasible implementation, identifying physical tag objects representing the functions and performance of electronic devices in captured images to determine target images includes: preprocessing the captured image to obtain a processed captured image; filtering the processed captured image based on a contour algorithm to obtain at least one candidate tag block; the candidate tag block is used to characterize tag regions in the image that may contain text information; filtering the candidate tag blocks based on color features to obtain at least one target tag block; wherein, the target tag block is used to characterize regions that match a preset color template; and obtaining the target image based on the target tag block and the processed captured image. Thus, through a multi-stage image processing strategy combined with a dual verification mechanism of geometric and color features, interference factors such as uneven lighting, complex backgrounds, or partial tag occlusion in actual shooting can be effectively overcome, significantly improving the accuracy and stability of tag region localization.

[0015] In one feasible implementation, the method further includes: displaying a tag configuration interface in response to a user's request to launch the tag management program; the tag configuration interface includes at least one batch operation entry point, which includes at least one of batch adding tags, batch editing tags, and batch deleting tags; and generating control commands in response to operations triggered by the user through the batch operation entry point. In this way, by providing batch operation functionality through an intuitive human-machine interface via the monitoring device, the efficiency and accuracy of test tag management are effectively improved. This allows testers to complete the unified configuration of test information for multiple electronic devices or multiple targets in a single operation, significantly reducing repetitive manual operations and potential human errors.

[0016] Thirdly, embodiments of this application provide a tag management device for electronic device test information. This device includes: a first acquisition module configured to acquire test result information of target testing items of the electronic device when the electronic device is connected to a control-side device; the test result information is used to indicate the attribute parameters and control parameters of the electronic device; an update module configured to update historical test information of the electronic device based on the attribute parameters and control parameters of the electronic device; and a first display module configured to continuously display the target test information in the form of an electronic tag when the interface of the electronic device is in a specific state.

[0017] In one feasible implementation, the first acquisition module is specifically configured to receive control commands sent by the management-side device; wherein the control commands originate from control commands generated by the management-side device, or are control commands generated by a cloud computing device and forwarded by the management-side device; and acquire target test information based on the control commands.

[0018] In one feasible implementation, the first acquisition module is specifically configured to, in response to a user's triggering operation on a target application of the electronic device, display a tag update control through a graphical user interface; wherein the tag update control includes any one of a tag adding control, a tag editing control, and a tag deleting control; generate control instructions based on the update operation performed by the user through the tag update control; and acquire target test information based on the control instructions.

[0019] In one feasible implementation, the first acquisition module is specifically configured to write the attribute parameters and control parameters of the electronic device into an asynchronous processing queue; acquire the attribute parameters and control parameters of the electronic device from the asynchronous processing queue; and update the historical test information of the electronic device based on the attribute parameters of the electronic device; wherein the update operation includes at least one of the following: add operation, edit operation, and modify operation.

[0020] In one feasible implementation, the first display module is configured to, upon detecting a screen lock event, acquire target test information corresponding to the displayable state; and display the target test information corresponding to the displayable state on the screen lock interface in the form of an electronic tag.

[0021] In one feasible implementation, the first display module is configured to display target test information in the target application interface of the electronic device in the form of an electronic tag.

[0022] Fourthly, embodiments of this application provide another tag management device for electronic device test information. This device includes: a second acquisition module configured to acquire a captured image; the second acquisition module is further configured to: if the captured image includes at least one physical tag object representing an attribute of the electronic device, process the physical tag object representing the attribute of the electronic device in the captured image to acquire a control command; the control command includes target test information of the electronic device; and a sending module configured to: send the target test information to the electronic device via a communication interface, so that the electronic device updates its historical test information based on the target test information.

[0023] In one feasible implementation, the second acquisition module is further configured to: identify physical tag objects representing the functions and performance of electronic devices in the captured image to determine a target image; the target image includes multiple tag text boxes; using the multiple tag text boxes as input to a neural network model, at least one electronic tag is obtained using the neural network model; the electronic tag is structured data containing tag type and / or tag text content; and based on the structured data containing tag type and / or tag text content, control instructions for controlling the electronic device are generated.

[0024] In one feasible implementation, the second acquisition module is further configured to: preprocess the captured image to obtain a processed captured image; filter the processed captured image based on a contour algorithm to obtain at least one candidate label block; the candidate label block is used to characterize a label region in the image that may contain text information; filter the candidate label block based on color features to obtain at least one target label block; wherein the target label block is used to characterize a region that matches a preset color template; and obtain a target image based on the target label block and the processed captured image.

[0025] In one feasible implementation, the second display module is further configured to: display a tag configuration interface in response to a user's request to start the tag management program; the tag configuration interface includes at least one batch operation entry, which includes at least one of batch adding tags, batch editing tags, and batch deleting tags; and generate control instructions in response to operations triggered by the user through the batch operation entry.

[0026] Fifthly, embodiments of this application provide a tag management system for electronic device test information. This tag management system includes: an electronic device under test, a control-side device, and a cloud computing device. The control-side device includes an imaging system and a target computing device, with the imaging system connected to the target computing device. The target computing device and the cloud computing device are connected via a communication interface. The electronic device is configured to: acquire test result information of target detection items of the electronic device when connected to the control-side device; use the test result information to indicate the attribute parameters and control parameters of the electronic device; update historical test information of the electronic device based on its functional and performance parameters; and continuously display target test information in the form of electronic tags in a specific state on the interface of the electronic device. The imaging system is configured to: acquire images of at least one physical tag object representing the attributes of the electronic device and generate captured images. The target computing device is configured to: process the captured images and obtain control commands. The cloud computing device is configured to: generate control commands.

[0027] Sixthly, this application provides an electronic device, including: a display screen, a memory, and one or more processors; the display screen, the memory, and the processors are coupled; wherein the memory stores computer program code, the computer program code including computer instructions, and when the computer instructions are executed by the processor, the electronic device performs the tag management method for electronic device test information as provided in the first and second aspects above.

[0028] In a seventh aspect, this application provides a computer-readable storage medium including computer instructions that, when executed on an electronic device, cause the electronic device to perform the tag management method for electronic device test information as described in the first and second aspects above.

[0029] Eighthly, this application provides a computer program product that, when run on a computer, causes the computer to execute the label management method for electronic device test information as described in the first and second aspects above.

[0030] It is understood that the beneficial effects that the technical solutions provided in the second to fourth aspects above can achieve can be referred to the beneficial effects of the first aspect and any feasible implementation thereof, and will not be repeated here. Attached Figure Description

[0031] Figure 1 This is a schematic diagram of a production line for an electronic device provided in an embodiment of this application; Figure 2 This is a schematic diagram of an electronic device provided in an embodiment of this application; Figure 3 This is a schematic diagram of the layered architecture of the software system of the electronic device provided in the embodiments of this application; Figure 4 This is a schematic diagram of a tag management system for electronic device test information provided in an embodiment of this application; Figure 5 This is a schematic diagram of the module operation logic of a tag management method for electronic device test information provided in an embodiment of this application; Figure 6 This is a schematic diagram of the module operation logic of another tag management method for electronic device test information provided in this application embodiment; Figure 7 This is a first flowchart illustrating a tag management method for electronic device test information provided in an embodiment of this application; Figure 8 This is a signaling flow diagram of a tag management method for electronic device test information provided in an embodiment of this application; Figure 9 This is a hardware schematic diagram of a pipe-side device provided in an embodiment of this application; Figure 10 This application provides a schematic diagram of a target image. Figure 11 This is a schematic diagram of a target test information processing flow provided in an embodiment of this application; Figure 12 This is a second flowchart illustrating a tag management method for electronic device test information provided in an embodiment of this application; Figure 13 This is a schematic diagram of the interface of a target computing device provided in an embodiment of this application; Figure 14 This is a third flowchart illustrating a tag management method for electronic device test information provided in an embodiment of this application; Figure 15 This application provides a schematic diagram of obtaining a graphical user interface. Figure 16 This is a schematic diagram of the interface flow corresponding to a label adding control provided in an embodiment of this application; Figure 17 This is a schematic diagram of the interface flow corresponding to a label editing control provided in an embodiment of this application; Figure 18This is a schematic diagram of the interface flow corresponding to a tag deletion control provided in an embodiment of this application; Figure 19 This is a fourth flowchart illustrating a tag management method for electronic device test information provided in an embodiment of this application; Figure 20 This is a fifth flowchart illustrating a tag management method for electronic device test information provided in an embodiment of this application; Figure 21 This is a sixth flowchart illustrating a tag management method for electronic device test information provided in an embodiment of this application; Figure 22 This is a schematic diagram of a tag management device for electronic device test information provided in an embodiment of this application; Figure 23 This is a schematic diagram of another tag management device for electronic device test information provided in an embodiment of this application; Figure 24 This is a schematic diagram of the chip system provided in the embodiments of this application. Detailed Implementation

[0032] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. Other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are all within the protection scope of this application.

[0033] In the following description, the terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined with "first," "second," etc., may explicitly or implicitly include one or more of that feature. In the description of this application, unless otherwise stated, "a plurality of" means two or more.

[0034] Furthermore, in this application, directional terms such as "upper," "lower," "inner," and "outer" are defined relative to the indicated placement of the components in the accompanying drawings. It should be understood that these directional terms are relative concepts, used for relative description and clarification, and can change accordingly depending on the placement of the components in the accompanying drawings.

[0035] To facilitate understanding of the technical solutions of the embodiments of this application by those skilled in the art, the technical terms involved in the embodiments of this application will be explained below.

[0036] A production line for electronic devices refers to a collection of orderly process stations and equipment established to achieve large-scale and standardized manufacturing of electronic products (such as consumer electronics, industrial control equipment, and communication modules). It covers the entire process from raw material input to finished product output, and typically includes key processes such as assembly, welding, debugging, testing, aging, and packaging.

[0037] A production management system (PMS) is an integrated software system used to plan, schedule, execute, monitor, and trace the entire manufacturing process of electronic devices. This system typically includes functional modules such as production planning management, process control, material tracking, equipment management, quality management, and data acquisition and analysis. Its aim is to achieve digitalization, visualization, and intelligentization of the production process, improve production efficiency, ensure product quality, and meet compliance and traceability requirements. The PMS manages multiple distributed test stations through a network, coordinating their execution of testing tasks and collecting test data.

[0038] A test station is a dedicated work unit or piece of equipment used in the production of electronic devices to perform automated or semi-automated testing of specific functions or performance. Deployed at designated locations on the production line, it executes pre-set test procedures. Each test station can perform specialized testing on different functional modules or testing stages of electronic devices (such as electrical performance, communication capabilities, safety compliance, etc.), and multiple stations collaborate to complete a comprehensive testing task.

[0039] In the production and testing of electronic devices, a tag is a data carrier used to identify, record, and transmit specific information about the device.

[0040] An asynchronous message queue (AMS) is a software design pattern or middleware mechanism used to implement asynchronous task processing. Its core idea is to decouple task submission (production) from task execution (consumption) and use a "queue" as a buffer to achieve asynchronous, delayed, or concurrent task processing.

[0041] The embodiments of this application will now be described with reference to the accompanying drawings.

[0042] In the production process of electronic devices, the production line usually includes multiple functional workstations, such as assembly workstations, debugging workstations and multiple testing workstations. Each testing workstation is responsible for performing testing tasks at a specific stage, such as initial testing, functional verification, post-aging retesting or final inspection, to ensure the functional integrity and performance stability of the product after key process nodes.

[0043] To more clearly illustrate the layout and collaborative relationships of the test workstations, the following will combine... Figure 1 An example will be provided.

[0044] Figure 1 This is a schematic diagram of a production line for an electronic device provided in an embodiment of this application.

[0045] like Figure 1 As shown, the electronic device under test (DUT) sequentially passes through multiple test stations (e.g., test station 1, test station 2, test station 3, ..., test station n), each responsible for performing a specific type of testing task. These test stations include, but are not limited to, initial testing, functional verification, post-aging testing review, and final inspection, ensuring that the product meets preset functional integrity and performance stability standards after each critical production stage.

[0046] For example, the electronic device under test is connected to each test station in sequence for phased testing. For instance, it first completes basic functional checks at the initial test station, then performs performance tests at the functional verification station, undergoes aging tests, enters the retest station to confirm stability, and finally is judged as qualified by the final inspection station.

[0047] To ensure the interconnectivity between multiple production lines and the efficient acquisition of test information, the traditional method is to directly affix paper labels to electronic devices after each testing station completes the test, such as attaching them to the protective film of the equipment. For example, these paper labels record specific test data, such as a concentricity of 0.019 and a bare-machine airtightness test value of 114.33. This method physically ensures that the test information of each piece of equipment flows with the equipment itself, facilitating subsequent review and tracking.

[0048] However, the management method of affixing test information to the protective film of electronic devices in the form of paper labels has obvious drawbacks: the test information exists independently in the form of a physical medium, without establishing a direct and persistent digital link with the electronic device itself. Essentially, this represents a management model that separates information from the electronic device. Such labels are prone to data loss, damage, or recording errors due to detachment, wear, contamination, or human error, failing to guarantee the integrity and authenticity of the information. This makes it impossible to manage the reliability of electronic devices, resulting in lagging overall test data management and difficulties in traceability.

[0049] In summary, the management method of attaching test information of the electronic device under test to the protective film of the electronic device in the form of paper labels makes the test information separate from the electronic device itself. This makes it impossible to manage the reliability of the electronic device, resulting in a lag in the overall test data management and difficulty in traceability.

[0050] To address the aforementioned issues, this application provides a tag management method and system for electronic device test information. This method records the latest test information in the form of electronic tags on the electronic device and displays it directly on the electronic device interface, thereby achieving automated and visual management of the electronic device's test information and effectively improving the reliability, traceability, and management efficiency of the test information.

[0051] The solutions provided in this application can be applied to electronic devices. For example, the electronic device may be a mobile phone, tablet computer, smartwatch, desktop computer, laptop computer, handheld computer, notebook computer, ultra-mobile personal computer (UMPC), netbook, as well as cellular phone, personal digital assistant (PDA), augmented reality (AR) / virtual reality (VR) device, etc. This application does not impose any special limitations on the specific form of the electronic device.

[0052] Figure 2 This is a schematic diagram of an electronic device provided in an embodiment of this application.

[0053] like Figure 2 As shown, the electronic device may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, antennas 01 and 02, a mobile communication module 150, a wireless communication module 160, an audio module 170, a sensor module 180, buttons 190, a motor 191, a camera 192, a display screen 193, and a Subscriber Identification Module (SIM) card interface 194, etc. The sensor module 180 may include a touch sensor 180A, a gyroscope sensor 180B, a pressure sensor 180C, a proximity sensor 180D, an ambient light sensor 180E, etc.

[0054] Processor 110 may include one or more processing units, such as a central processing unit (CPU), an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a digital signal processor (DSP), a baseband processor, and / or a neural network processing unit (NPU). These different processing units may be independent devices or integrated into one or more processors.

[0055] The controller can generate operation control signals based on the instruction opcode and timing signals to complete the control of instruction fetching and execution.

[0056] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0057] In some embodiments, the processor 110 may include one or more interfaces. Interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0058] The I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 may include multiple I2C buses. The processor 110 can couple to the touch sensor 180A, charger, flash, camera 192, etc., through different I2C bus interfaces. For example, the processor 110 can couple to the touch sensor 180A through the I2C interface, enabling the processor 110 and the touch sensor 180A to communicate through the I2C bus interface, thereby realizing the touch function of the electronic device.

[0059] The I2S interface can be used for audio communication. In some embodiments, the processor 110 may include multiple I2S buses. The processor 110 can be coupled to the audio module 170 via the I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 via the I2S interface to enable the function of answering phone calls through a Bluetooth headset.

[0060] The PCM interface can also be used for audio communication, sampling, quantizing, and encoding analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 can be coupled via the PCM bus interface.

[0061] The UART interface is a universal serial data bus used for asynchronous communication. This bus can be a bidirectional communication bus. It converts the data to be transmitted between serial and parallel communication. In some embodiments, the UART interface is typically used to connect the processor 110 and the wireless communication module 160. For example, the processor 110 communicates with the Bluetooth module in the wireless communication module 160 via the UART interface to implement Bluetooth functionality.

[0062] The MIPI interface can be used to connect the processor 110 to peripheral devices such as the display screen 193 and the camera 192. The MIPI interface includes a camera serial interface (CSI) and a display serial interface (DSI). In some embodiments, the processor 110 and the camera 192 communicate via the CSI interface to enable the electronic device to capture images. The processor 110 and the display screen 193 communicate via the DSI interface to enable the electronic device to display images.

[0063] The GPIO interface can be configured via software. It can be configured as a control signal or a data signal. In some embodiments, the GPIO interface can be used to connect the processor 110 to a camera 192, a display screen 193, a wireless communication module 160, an audio module 170, a sensor module 180, etc. The GPIO interface can also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, etc.

[0064] USB port 130 is a USB standard compliant interface, which can be a Mini USB port, Micro USB port, USB Type-C port, etc. USB port 130 can be used to connect a charger to charge electronic devices, and can also be used for data transfer between electronic devices and peripheral devices. It can also be used to connect headphones for audio playback. This interface can also be used to connect other electronic devices, such as AR devices.

[0065] It is understood that the interface connection relationships between the modules illustrated in the embodiments of the present invention are merely illustrative and do not constitute a limitation on the structure of the electronic device. In other embodiments of this application, the electronic device may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0066] In some embodiments, processor 110 may include one or more interfaces.

[0067] The external memory interface 120 can be used to connect to an external non-volatile memory, thereby expanding the phone's storage capacity. The external non-volatile memory communicates with the processor 110 through the external memory interface 120 to perform data storage functions. For example, music, video, and other files can be saved in the external non-volatile memory.

[0068] Internal memory 121 may include one or more random access memory (RAM) and one or more non-volatile memory (NVM).

[0069] The charging management module 140 receives charging input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 receives charging input from the wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 receives wireless charging input via the wireless charging coil of the electronic device 1. While charging the battery 142, the charging management module 140 can also supply power to the electronic device via the power management module 141.

[0070] The power management module 141 connects the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, providing power to the processor 110, internal memory 121, display screen 193, camera 192, and wireless communication module 160, etc. The power management module 141 can also monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage current, impedance). In some other embodiments, the power management module 141 may also be located within the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may be located in the same device.

[0071] The wireless communication function of electronic devices can be implemented through antenna 01, antenna 02, mobile communication module 150, wireless communication module 160, modem processor, and baseband processor.

[0072] Antennas 01 and 02 are used to transmit and receive electromagnetic wave signals. Each antenna in the electronic device can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 01 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with a tuning switch.

[0073] The mobile communication module 150 can provide solutions for wireless communication applications including 2G / 3G / 4G / 5G in electronic devices. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via antenna 01, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 01. In some embodiments, at least some functional modules of the mobile communication module 150 may be housed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be housed in the same device.

[0074] The wireless communication module 160 can provide solutions for wireless communication applications in electronic devices, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. The wireless communication module 160 receives electromagnetic waves via antenna 02, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and then convert them into electromagnetic waves for radiation via antenna 02.

[0075] In some embodiments, antenna 01 of the electronic device is coupled to mobile communication module 110, and antenna 02 is coupled to wireless communication module 160, enabling the electronic device to communicate with networks and other devices via wireless communication technology. Wireless communication technologies may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time-Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies. GNSS may include Global Positioning System (GPS), Global Navigation Satellite System (GLONASS), BeiDou Navigation Satellite System (BDS), Quasi-Zenith Satellite System (QZSS), and / or Satellite Based Augmentation Systems (SBAS).

[0076] Electronic devices implement display functions through a GPU, a display screen 193, and an application processor. The GPU is a microprocessor for image processing, connecting the display screen 193 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. The processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0077] The display screen 193 is used to display images, videos, etc. In this embodiment, the display screen 193 can be used for test information on the application interface and lock screen interface.

[0078] Camera 192 is used to capture still images or videos. In some embodiments, the electronic device may include one or N cameras 192, where N is a positive integer greater than 1. In this embodiment, the electronic device can use camera 192 to capture backlit scenes.

[0079] Electronic devices can implement audio functions through audio modules 170 and application processors, such as music playback and recording.

[0080] The audio module 170 is used to convert digital audio information into analog audio signals for output, and also to convert analog audio input into digital audio signals. The audio module 170 can also be used for encoding and decoding audio signals. In some embodiments, the audio module 170 may be located in the processor 110, or some functional modules of the audio module 170 may be located in the processor 110.

[0081] In some embodiments, the sensor module 180 may include a touch sensor 180A, a gyroscope sensor 180B, a pressure sensor 180C, a proximity sensor 180D, an ambient light sensor 180E, etc.

[0082] Touch sensor 180A, also known as a "touch device," can be disposed on display screen 193. The touch sensor 180A and display screen 193 together form a touchscreen, also known as a "touchscreen." Touch sensor 180A is used to detect touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the touch event type. Visual output related to the touch operation can be provided through display screen 193. In this embodiment, touch sensor 180A is used to detect user click operations on display screen 193 to obtain application interfaces corresponding to different test information.

[0083] The gyroscope sensor 180B can be used to determine the motion attitude of an electronic device. In some embodiments, the gyroscope sensor 180B can determine the angular velocity of the electronic device around three axes (i.e., the x, y, and z axes). The gyroscope sensor 180B can be used for image stabilization. For example, when the shutter is pressed, the gyroscope sensor 180B detects the angle of the electronic device's shake, calculates the distance that the lens module needs to compensate based on the angle, and allows the lens to counteract the shake of the electronic device by moving in the opposite direction, thus achieving image stabilization. The gyroscope sensor 180B can also be used in navigation and motion-sensing gaming scenarios.

[0084] A pressure sensor 180C is used to sense pressure signals and convert them into electrical signals. In some embodiments, the pressure sensor 180C may be disposed on a display screen 193. There are many types of pressure sensors 180C, such as resistive pressure sensors, inductive pressure sensors, and capacitive pressure sensors. A capacitive pressure sensor may include at least two parallel plates with conductive material. When a force is applied to the pressure sensor 180C, the capacitance between the electrodes changes. The electronic device determines the pressure intensity based on the change in capacitance. When a touch operation is applied to the display screen 193, the electronic device detects the touch operation intensity based on the pressure sensor 180C. The electronic device can also calculate the touch position based on the detection signal from the pressure sensor 180C. In some embodiments, touch operations applied to the same touch position but with different touch operation intensities may correspond to different operation commands.

[0085] The proximity sensor 180D may include, for example, a light-emitting diode (LED) and a light detector, such as a photodiode. The LED may be an infrared LED. The electronic device emits infrared light outward through the LED. The electronic device uses the photodiode to detect infrared reflected light from nearby objects. When sufficient reflected light is detected, it can be determined that an object is near the electronic device. When insufficient reflected light is detected, the electronic device can determine that no object is near the electronic device. The electronic device can use the proximity sensor 180D to detect when a user holds the electronic device close to their ear for a call, so as to automatically turn off the screen to save power. The proximity sensor 180D can also be used in holster mode and pocket mode for automatic unlocking and locking of the screen.

[0086] An ambient light sensor 180E is used to sense ambient light brightness. The electronic device can adaptively adjust the brightness of the display screen 193 based on the sensed ambient light brightness. The ambient light sensor 180E can also be used to automatically adjust the white balance when taking a picture. The ambient light sensor 180E can also work in conjunction with a proximity sensor 180E to detect whether the electronic device is in a pocket, preventing accidental touches. In this embodiment, the ambient light sensor 180E can be used to sense the brightness of the display area of ​​the display screen 193.

[0087] Motor 191 can generate vibration alerts. Motor 191 can be used for incoming call vibration alerts or for touch vibration feedback. For example, different vibration feedback effects can be corresponding to touch operations applied to different applications (such as taking photos, playing audio, etc.). Motor 191 can also correspond to different vibration feedback effects for touch operations applied to different areas of the display screen 193. Different application scenarios (such as time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also be customized.

[0088] The SIM card interface 194 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to establish contact with the electronic device. The electronic device can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 supports Nano SIM cards, Micro SIM cards, and other SIM cards. Multiple cards can be inserted into the same SIM card interface 195 simultaneously. The multiple cards can be of the same or different types. The SIM card interface 195 is also compatible with different types of SIM cards. The SIM card interface 195 is also compatible with external memory cards. The electronic device interacts with the network through the SIM card to achieve functions such as calls and data communication.

[0089] It is understood that the interface connection relationships between the modules illustrated in the embodiments of the present invention are merely illustrative and do not constitute a limitation on the structure of the mobile phone. In other embodiments of this application, the mobile phone may also adopt different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0090] Of course, this is understandable. Figure 2 The illustration shown is merely an example of an electronic device in the form of a mobile phone. If the electronic device is a tablet, handheld computer, PC, PDA, wearable device (such as a smartwatch, smart bracelet), or other device form factor, the structure of the electronic device may include more advanced technologies. Figure 2 The fewer structures shown can also include more than Figure 2 The structures shown are not limited here.

[0091] Figure 3 This is a schematic diagram of the layered architecture of the software system of the electronic device provided in the embodiments of this application.

[0092] In some examples, refer to Figure 3 As shown in the embodiments of this application, the software system of the electronic device is divided into four layers, from top to bottom: application layer, application framework layer, Android runtime and system library, and kernel layer.

[0093] The application layer can include a series of applications. For example... Figure 3 As shown, the application layer may include applications such as camera, gallery, calendar, map, WLAN, music, SMS, call, video, engineering menu, or electronic tag. In this embodiment, the electronic device can update its test information, such as adding, modifying, or deleting, through the electronic tag front-end module in the engineering menu application or electronic tag application.

[0094] In addition, it includes a real-time display module, which is used to display key information, such as electronic tag content, on the lock screen or when the electronic device is powered on.

[0095] The framework layer provides application programming interfaces (APIs) and programming frameworks for applications in the application layer.

[0096] The application framework layer includes some predefined functions or services. For example, the application framework layer may include an activity manager, window manager, content provider, view system, phone manager, resource manager, notification manager, camera service, asynchronous message queue, tag data management service, communication service, etc., and this application embodiment does not impose any limitations on this.

[0097] Among them, the asynchronous message queue is a bridge to realize asynchronous communication between modules. In this embodiment, it realizes communication between the communication service and the tag data management service.

[0098] The tag data management service provides a unified data access and management interface, supporting the creation, deletion, modification and query of test information, historical data backtracking, multi-terminal data synchronization, and the generation and reading / writing of snapshot files.

[0099] The communication service encapsulates the underlying communication protocol, instruction packaging format, and message transmission mechanism. As a system-level communication middleware, it is used to realize data interaction between this device and external devices or debugging tools.

[0100] Database interface services abstract and encapsulate underlying data storage, providing a standardized data read and write entry point for upper-layer applications and framework services, thereby improving the security and consistency of data access.

[0101] The Android Runtime consists of core libraries and a virtual machine. The Android runtime is responsible for the scheduling and management of the Android system.

[0102] The core library consists of two parts: one part is the functionalities that need to be called by the Java language, and the other part is the Android core library.

[0103] The application layer and application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0104] The system library can include multiple functional modules. These include: a surface manager, media libraries, an AT command module, a snapshot file read / write module, and an information storage module, which includes an OEM information database and a general database. The surface manager manages the display subsystem and provides 2D and 3D layer blending for multiple applications. The media libraries support playback and recording of various common audio and video formats, as well as still image files. The media libraries support multiple audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG. The AT command module is responsible for receiving and processing AT commands, executing command responses, and serving as a system-level service process to support device debugging and control.

[0105] The snapshot file read / write module is used to persistently store and retrieve data required for the lock screen interface, supporting the display of key information when the device is locked. The OEM information database and system database store device test information. The databases include pre-set tag data and a public data storage area. The OEM information database primarily stores test data with permanent and immutable characteristics, while the system database manages dynamically updatable test records, including tag status and snapshot data. In addition, a boot command mechanism is included to record data and prevent data loss.

[0106] The kernel layer is the layer between hardware and software.

[0107] The kernel layer includes at least a display driver, a camera driver, an audio driver, and a sensor driver. In this embodiment, the display driver is used to transmit display test information for display on the monitor.

[0108] In the Android® system, applications are typically written in Java. Each application can include one or more class files. Each application can run its own class files as a process within the application layer. When a user interacts with an application, the application can call the relevant application programming interface (API) or service in the application framework layer to interact with system libraries or the kernel layer and implement the functionality corresponding to the user's actions.

[0109] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device. In other embodiments of this application, the electronic device may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0110] The embodiments of this application will now be described with reference to the accompanying drawings.

[0111] Figure 4 This is a schematic diagram of a tag management system for electronic device test information provided in an embodiment of this application.

[0112] like Figure 4 As shown, the tag management system 400 includes an electronic device 401 under test, a management-side device 402, and a cloud computing device 403. The management-side device 402 includes an imaging system 4021 and a target computing device 4022. The imaging system 4021 is connected to the target computing device 4022. The target computing device 4022 is connected to the cloud computing device 403 through a communication interface.

[0113] Among them, the tested electronic device 401 is used to perform operations such as inputting, editing, displaying and exporting target test information; in addition to supporting the above operations, the target computing device 4022 is also responsible for recognizing and processing the captured images obtained by the imaging system 4021 and extracting the physical tag information therein; the cloud computing device 403 is used to generate, store, manage and distribute target test information, support remote access, synchronization and download of information, and realize centralized management and cross-device collaboration of test data.

[0114] The above system architecture realizes the intelligent conversion and efficient flow of physical tags to digital information, constructing a complete closed-loop management system for test information. The following section will combine... Figure 5 This document provides a detailed explanation of the label management method for test information of electronic devices, based on the internal software module of electronic device 401.

[0115] Figure 5 This is a schematic diagram of the module operation logic of a tag management method for electronic device test information provided in an embodiment of this application.

[0116] like Figure 5 As shown, with the tested electronic device 401 as the core execution terminal, when communication connections are established between the tested electronic device 401 and the monitoring device 402, and between the monitoring device 402 and the cloud computing device 403, the AT command module (AT cmdserver) inside the electronic device 401 will first receive control commands. These control commands include test result information about the target detection items of the tested electronic device 401, which can come from control commands issued by the monitoring device 402 or the cloud computing device 403, or can be control commands generated after the electronic device 401 interacts with the user.

[0117] Next, the command communication client (end-to-pipe communication service) receives the control commands sent by the AT command module and writes the test result information contained therein to the asynchronous message queue. The database interaction layer (tag data management service) then reads the test result information from the asynchronous message queue and writes it to the database and the Original Equipment Manufacturer (OEM) information repository. The database interaction layer processes the test result information and updates the historical test information of the electronic device to ensure data integrity and timeliness.

[0118] Meanwhile, to achieve visualized information display, the database interaction layer also transmits target test information to the UI interface, enabling this information to be continuously displayed on the user interface in the form of electronic tags. Furthermore, the "Screen-on Display" module supports retrieving specific target test information from the OME database and visually displaying it on the lock screen, allowing users to access target test information even when the device is locked.

[0119] It should be noted that, Figure 5 The arrows shown indicate the data flow between the components.

[0120] In other words, the electronic device 401 under test has the ability to interact bidirectionally with the cloud computing device 403. This includes uploading and downloading target test information and remote configuration functions, thereby forming a complete closed-loop management process of "instruction issuance - local processing - information display - data synchronization", which enhances the data collaboration capabilities across devices and platforms.

[0121] With the device-side device 402 as the core execution terminal, and a communication connection established between the electronic device under test 401 and the device-side device 402, as well as between the device-side device 402 and the cloud computing device 403, the device-side device 402 internally includes an imaging system 4021 and a target computing device 4022. The imaging system 4021 is responsible for acquiring image information from the device under test and performing data processing, such as OCR recognition, through the target computing device 4022 to generate control commands.

[0122] The following is combined Figure 6 The method for managing the labels of electronic equipment test information is explained in detail from the internal software module of the pipe-side device 402.

[0123] Figure 6 This is a schematic diagram of the module operation logic of another tag management method for electronic device test information provided in this application embodiment.

[0124] like Figure 6As shown, with the pipe-side device 402 as the core execution terminal, and with communication connections established between the tested electronic device 401 and the pipe-side device 402, as well as between the pipe-side device 402 and the cloud computing device 403, multiple functional modules work together to complete the tag management of electronic device test information.

[0125] Specifically, the vision module can capture images of the electronic device under test (401), perform preliminary image processing using its built-in OCR recognition and intelligent vision capabilities, and send the pre-processed data to the electronic tag data management module. The electronic tag data management module further integrates, processes, verifies, and encapsulates the pre-processed data, and generates corresponding control commands based on the test process logic. These control commands are sent to the electronic device under test (401) via a communication module (supporting USB, serial port, and other communication methods) to drive it to execute specified test operations. The response data returned by the electronic device (401) after execution (such as test results, status codes, or newly generated electronic tags) can also be transmitted back to the management device (402) via the same communication module. Next, the data transmission module uploads the electronic tag data from the response data to the cloud computing device (403) for remote storage, auditing, or policy analysis. The upload process supports breakpoint resumption and retry mechanisms, and the transmission status is monitored by an anomaly alarm module, which triggers an alarm upon the occurrence of an anomaly. Meanwhile, the access control module implements hierarchical control over user operations, device access, and data access, such as login verification, account and password settings, and path permission settings, to ensure system security. The file management module is responsible for the path allocation, lifecycle management, polling scanning, and archiving of local test files. The printing module calls the printer based on the final label content to output physical labels, realizing a closed-loop management of the entire process of "identification—processing—execution—upload—printing". Among them, the control commands, as the data carrier of the label management system, not only include test result information about the target detection items of the tested electronic device 401, but also define multi-dimensional control parameters such as label type definition, preset parameter configuration, data entry rules, information source identification, screen lock display strategy, and label lifecycle management. This multi-dimensional parameter configuration mechanism enables the management device 402 to flexibly adapt to the refined management needs of various testing scenarios.

[0126] As a key control node in the testing process, the control-side device 402 has the ability to independently generate complete control commands, dynamically construct and issue commands to the electronic device 401 under test. The following is a detailed description of an embodiment of a tag management method for electronic device test information corresponding to control commands autonomously generated by the control-side device 402.

[0127] In the first embodiment, the pipe-side device 402 consists of an imaging system 4021 and a target computing device 4022 forming a system working unit. The imaging system 4021 is responsible for acquiring images of the physical tags of the electronic device 401. The target computing device 4022 parses the tag content through an intelligent image processing algorithm and automatically generates control commands containing test result information and management parameters. The electronic device 401 further processes the test results based on the test result information in the control commands. The following is a combination of... Figure 7 The specific implementation process will be described in detail below.

[0128] Figure 7 This is a schematic diagram of the first process of a tag management method for electronic device test information provided in an embodiment of this application. Figure 7 As shown, the tag management method for electronic device test information, applied to a tag management system, includes the following steps. S1: Establish a communication link.

[0129] Figure 8 This is a signaling flow diagram of a tag management method for electronic device test information provided in an embodiment of this application.

[0130] like Figure 8 As shown, step S1 includes step S1001.

[0131] S1001: Establish a communication link between the pipe-side device 402, the electronic device under test 401, and the cloud computing device 403.

[0132] The communication links include the connection between the pipe-side device 402 and the electronic device 401 under test, and the connection between the pipe-side device 402 and the cloud computing device 403.

[0133] Continue to combine Figure 4 As shown, electronic device 401 and pipe-side device 402 can establish a connection through various communication interfaces, including wired (such as USB, serial port) or wireless (such as Wi-Fi, Bluetooth); pipe-side device 402 and cloud computing device 403 mainly establish a communication link through network connection (such as Wi-Fi, Ethernet or mobile data network) to support remote transmission of test data and cloud collaborative processing.

[0134] For example, electronic device 401 and pipe-side device 402 can establish a high-speed wired connection via USB 3.0 interface, and pipe-side device 402 and cloud computing device 403 can be connected via enterprise-grade gigabit Ethernet.

[0135] S2: Pipe-side equipment receives control commands.

[0136] Figure 9This is a hardware schematic diagram of a pipe-side device provided in an embodiment of this application.

[0137] like Figure 9 As shown, the tube-side device 402 consists of an imaging system 4021 and a target computing device 4022. The two are connected through a standard communication interface, such as wired methods like USB or serial port, or wireless communication methods like Wi-Fi or Bluetooth. The specific connection method can be flexibly configured according to the actual application scenario, and no specific limitation is made here.

[0138] Furthermore, such as Figure 9 As shown in (a) and (b), Figure 9 (a) shows a schematic diagram of the tube-side device 402 corresponding to the three-dimensional structure of the imaging system 4021, while Figure 9 (b) in the figure is a schematic diagram of the tube-side device 402 corresponding to the front view of the imaging system 4021. The imaging system 4021 may include core components such as a camera 4021a, an adjustable lens 4021b, a ring light source system 4021c, and a stage 4021d. All components are integrated into one unit through mechanical structure and electrical interface to form a complete image acquisition unit. The camera 4021a is located at the top of the imaging system 4021 and is rigidly connected to the adjustable lens 4021b via a standard interface, forming the main body for image acquisition. The adjustable lens 4021b extends vertically downwards, with its optical axis coinciding with the system's center line, ensuring precise alignment between the center of the imaging area and the positioning reference point of the stage 4021d. The ring light source system 4021c is installed on the outer edge of the front end of the adjustable lens 4021b, arranged in a ring at a 45-degree angle, which avoids interference from direct reflections and provides uniform, shadowless illumination for the test sample on the stage 4021d. The stage 4021d adopts a three-dimensional adjustment platform design and is located at the bottom of the entire optical system. Its working plane is perpendicular to the lens's optical axis, and its surface can be equipped with positioning slots and fine-tuning knobs (not shown in the figure), which can precisely fix the electronic device 401 under test and adjust its relative distance to the lens.

[0139] In one implementation, the combination continues. Figure 8 As shown, step S2 includes steps 1002-S1003.

[0140] S1002: Imaging system acquires captured images.

[0141] Imaging system 4021 captures images of electronic device 401 placed on stage 4021d. Specifically, electronic device 401 has a physical model mounted on it, and multiple physical tags reflecting the properties of electronic device 401 are attached to the surface of the model. Imaging system 4021 precisely captures images of these physical tags. By adjusting the position of stage 4021d and the focal length of lens 4021b, it ensures that each tag is captured with high definition and contrast, resulting in an image.

[0142] For example, the imaging system 4021 takes a picture of the electronic device 401 placed on the stage 4021d to obtain a picture image A. For example, the picture image A includes physical label objects such as "orange peel on the outer screen", "floating on the outer screen", and "self-inspection after standing: film imprint on the outer screen".

[0143] S1003: The imaging system sends the captured images to the target computing device.

[0144] Continuing with the example above, the imaging system 4021 sends the captured image A to the target computing device 4022 via a communication interface. If the captured image includes at least one physical tag object characterizing an attribute of an electronic device, the target computing device can process the physical tag object representing the electronic device's attribute in the captured image to generate control commands.

[0145] First, the target computing device identifies the physical tag objects of the electronic device attributes in the captured image to determine the target image.

[0146] The target image includes multiple label text boxes.

[0147] S1004: The target computing device preprocesses the captured image to obtain the processed captured image.

[0148] The target computing device 4022 performs image preprocessing operations on the original captured image to enhance the image.

[0149] For example, noise adjustment, contrast adjustment, sharpness adjustment, and brightness adjustment can be performed on the captured image. For instance, noise adjustment can use an adaptive Gaussian filtering algorithm to eliminate image noise while preserving label edge details; contrast adjustment can use histogram equalization technology to dynamically adjust image contrast, making the label text clearly distinguishable from the background; sharpness adjustment can use unsharp masking technology to improve image sharpness and enhance character edge features; brightness adjustment can correct brightness parameters based on scene lighting conditions to ensure that the image brightness distribution is uniform and meets the preset threshold range.

[0150] It should be noted that the order of noise adjustment, contrast adjustment, sharpness adjustment, and brightness adjustment in preprocessing is not specifically limited.

[0151] Figure 10 This application provides a schematic diagram of a target image.

[0152] Continuing with the example above, the target computing device 4022 preprocesses the captured image A to obtain the processed captured image A1, as shown below. Figure 10 As shown in (a) of the diagram.

[0153] S1005: The target computing device uses a contour algorithm to filter the processed captured image and obtain at least one candidate label block.

[0154] Contour algorithms are methods used to detect object boundaries in images. When an image contains multiple physically labeled objects, this algorithm can distinguish and extract them based on the contour features of each object, thereby generating corresponding candidate label blocks. These candidate label blocks represent label regions in the image that may contain text information.

[0155] Continuing with the example above, the target computing device uses a contour algorithm to filter the processed captured image and obtain at least one candidate tag block, such as: "orange peel on outer screen adhesive line", "outer screen floating height", "self-inspection after standing: outer screen film imprint", etc.

[0156] S1006: The target computing device filters candidate label blocks based on color features to obtain at least one target label block.

[0157] Color features are used to measure the distribution attributes of candidate label blocks in the color space, including hue (H), saturation (S), brightness (V), RGB channel mean, or the pixel proportion of a specific color region. The target computing device compares the color features with a preset color template and retains candidate label blocks whose matching degree meets a set threshold as target label blocks. The target label block is used to represent the region that matches the preset color template.

[0158] Continuing with the example above, the target computing device filters candidate tag blocks containing physical tag objects such as "orange peel of outer screen adhesive line", "outer screen floating height", and "self-inspection after standing: outer screen film imprint" based on color features, and excludes items whose color features do not match the preset template (such as "self-inspection after standing: outer screen film imprint"), and finally obtains at least one target tag block, namely "orange peel of outer screen adhesive line" and "outer screen floating height".

[0159] S1007: The target computing device obtains the target image based on the target tag block and the processed captured image.

[0160] like Figure 10 As shown in (b), the target image is an image that includes multiple label text boxes.

[0161] In one example, the target tag block typically contains its spatial location information on the processed captured image, such as the coordinates of an outer rectangle (x, y, w, h) or polygon vertices. The target computing device maps these coordinates back to the processed captured image to obtain the target image.

[0162] Based on the previous example, the target computing device maps the coordinate information of the target label block back to the processed captured image to generate target image A2. Target image A2 contains multiple text boxes, each corresponding to an confirmed target label block, used to identify the physical label object it represents, such as "outer screen adhesive line orange peel" or "outer screen floating height".

[0163] Secondly, using multiple label text boxes as input to the neural network model, the target computing device uses the neural network model to obtain at least one electronic label.

[0164] Electronic tags are structured data that includes tag type and / or tag text content.

[0165] In this context, a pre-trained neural network model refers to a neural network model that has been trained on a large-scale dataset before use. To ensure the generalization ability of the neural network model, it needs to be trained on a large amount of data. For example, the neural network model can be a recognition model, such as the T5 model or the RoBERTa model.

[0166] The training method for neural network models includes the following steps: First, obtain the training set.

[0167] The training set includes at least one sample image and the corresponding target label for each sample image. Each sample image includes multiple label text boxes.

[0168] Next, the neural network model is trained by using at least one sample image containing multiple labeled text boxes as input and the target label corresponding to each sample image as output. This yields the predicted label for each sample image. A preset loss function is then used to calculate the loss value between the target label and the predicted label for each sample image. Based on this loss value, the original neural network model is continuously adjusted. When the loss value is less than a preset threshold, the initial neural network model is considered successfully trained, resulting in a well-trained neural network model.

[0169] After the neural network model is trained, a target image A2, including multiple label text boxes, is used as input to the neural network model. The neural network model then performs inference on the target image A2 and outputs at least one electronic tag. The electronic tag is structured data, containing at least one of the following: tag type and tag text content, used to readablely represent the semantic information of the corresponding physical tag object.

[0170] S1008: The target computing device generates control instructions for controlling electronic devices based on structured data of tag type and / or tag text content.

[0171] The control instructions include initial test result information, which comprises attribute parameters and control parameters. These instructions are used to update the initial test result information, including adding, modifying, or deleting data. Attribute parameters include the electronic device's functional and performance parameters, specifically describing the device's test data, such as "orange peel texture on the outer screen" or "outer screen floating height." Control parameters include tag type definition, preset parameter configuration, data entry rules, information source identification, lock screen display strategy, and tag lifecycle management.

[0172] Specifically, control instructions distinguish operation types through instruction codes in control parameters and carry corresponding structured fields: Taking the addition operation as an example, the control parameter M1 in the control instruction M1 (initial test result information M1) specifically includes the following fields: the instruction code is "0000", which is used to identify that the current operation is an addition operation; the tag type code is an integer between 0 and 7, which is used to specify the category to which the tag belongs; the preset content is the standardized text or parameter value predefined by the system, which corresponds to the tag type code; the input content is the user-defined supplementary information; the tag source is used to identify the data acquisition method, where 0 indicates that it is obtained by OCR recognition, 1 indicates that it is manually entered, and 2 indicates that it comes from the tag on the equipment itself; the screen display field is used to control whether the tag is displayed on the device lock screen interface, where 1 indicates that it needs to be displayed and 0 indicates that it is not displayed; the tag lifecycle status is used to mark the validity of the tag, such as indicating whether the tag has been deleted or is in a valid state.

[0173] Taking the modification operation as an example, the control parameter M2 in the control instruction M2 (initial test result information M2) specifically includes the following fields: the instruction code is "0002", which is used to identify that the current operation is a modification operation; the label number (id), which is used to uniquely identify the label to be modified, such as id=5; the input section (labelDescription), which is used to provide the updated custom content, such as labelDescription=20, which means that the label description information is modified to the predefined or user-specified 20th content; and whether to display it on the screen (displayStatus), which is used to control whether the label is displayed on the device lock screen after modification, where displayStatus=0 means not to display, and 1 means to display.

[0174] Taking the deletion operation as an example, the control parameter M3 in the control instruction M3 (initial test result information M3) specifically includes the following fields: the instruction code is "0003", which is used to identify that the current operation is deletion; the tag number (id), which is used to uniquely identify the tag to be deleted, for example, id=5 means deleting the tag with the number 5; and the life cycle status (lifeCycleStatus), where lifeCycleStatus=0 means that the tag is marked as "deleted" or removed from the list of valid tags.

[0175] It should be noted that the control commands not only support add, modify, and delete operations, but also read operations. Taking a read operation as an example, its command code is "0002," used to request the electronic device to obtain the storage path or content of specified test result information. After executing this command, the electronic device returns the corresponding result data, for example: path=xxxxxx, where this path points to the location of the database (DB) storing the test result information, facilitating subsequent data querying, synchronization, or visualization processing by the target computing device.

[0176] Continuing with the example above, the following explanation uses control command M1 as an example. Control command M1 includes attribute parameter M1' and control parameter M1". Attribute parameter M1' contains the specific detection content to be processed, such as "orange peel texture on the outer screen" or "outer screen floating height", which characterizes the actual description obtained by the electronic device in the target detection item. Control parameter M1" defines the operation method and context rules performed on the above test result information, specifically including: command code "0002", used to identify that the current operation is a modification; label number (id), used to uniquely identify the label to be modified, such as id=5; input section (labelDescription), used to provide updated custom content, such as labelDescription=20 indicating that the label description information is modified to the predefined or user-specified 20th content; and whether to display on screen (displayStatus), used to control whether the modified label is displayed on the device lock screen, where displayStatus=0 indicates no display, and 1 indicates display.

[0177] S3: The target computing device sends control commands to the electronic device.

[0178] Continue to combine Figure 8 As shown, step S3 includes step S1009.

[0179] S1009: The target computing device sends control commands to the electronic device.

[0180] Continuing with the example above, the target computing device sends control command M1 to the electronic device.

[0181] S4: The electronic device acquires the test result information of the target detection items of the electronic device based on the control command.

[0182] Continue to combine Figure 8 As shown, step S3 includes step S1009.

[0183] S1009: The electronic device acquires the test result information of the target detection items of the electronic device based on the control command.

[0184] Figure 11 This is a schematic diagram of a target test information processing flow provided in an embodiment of this application.

[0185] like Figure 11 As shown, step S1009 includes the following steps: S41: The electronic device obtains initial test result information according to the control command.

[0186] Continuing with the example above, the electronic device first receives a control command from an external control system or software. This command contains specific instructions and parameters (such as M1 in the example) that need to be executed. The electronic device parses the command and determines to check concentricity, orange peel effect of the outer screen adhesive lines, and outer screen floating height, etc.

[0187] Continuing with the example above, the electronic device acquires the initial test result information M1.

[0188] S42: The electronic device writes the preliminary test results information into the database.

[0189] Following the example above, the object detection project is completed and the corresponding initial test result information (such as M1' in the example) is obtained and stored in the database.

[0190] S43: Determine whether the write was successful.

[0191] The electronic device periodically checks whether the preliminary test result information writing operation in step S42 was successful.

[0192] S44: If the write operation is successful, the electronic device reads the test result information corresponding to the target detection item from the database.

[0193] The test result information refers to the complete test result information corresponding to the target detection items in the electronic device. The test result information is used to indicate the attribute parameters and control parameters of the electronic device. Attribute parameters include the functional parameters and performance parameters of the electronic device. Functional parameters reflect whether the electronic device possesses specific functions or meets functional specifications, such as communication protocol support, interface type, sensor activation status, and tag recognition capability. Performance parameters characterize the performance of the electronic device during operation, such as processing latency, recognition accuracy, response time, power consumption level, image resolution, or detection repeatability.

[0194] Following the example above, obtain the attribute parameter M11' and control parameter M11 of the target detection item of the electronic device.

[0195] In the testing scenarios of electronic devices, updating historical test information (such as writing to a long-term database, synchronizing to the OEM information database, triggering audit logs, etc.) is usually a non-real-time critical path operation, but it cannot block the main test process such as command response, tag generation and display, etc. In order to balance system response efficiency and data integrity, this embodiment introduces an asynchronous processing queue mechanism: the update task is temporarily stored in the queue and consumed asynchronously by the background task, thereby avoiding the impact of database I / O or network latency on the front-end interactive experience, while improving system throughput and fault tolerance.

[0196] S5: The electronic device updates its historical test information based on its attribute parameters and control parameters.

[0197] Continue to combine Figure 8 As shown, step S5 includes steps S1010-S1012.

[0198] S1010: The electronic device writes attribute parameters and control parameters into the asynchronous processing queue.

[0199] After completing the test and obtaining structured attribute parameters (such as functional and performance parameters), the electronic device encapsulates the target test information containing the complete test results into an update task and submits it to the asynchronous processing queue in the local or peripheral device 402.

[0200] Continuing with the example above, the electronic device's M11' and control parameter M11" are written into the asynchronous processing queue.

[0201] S1011: The electronic device retrieves test result information from the asynchronous processing queue.

[0202] Continuing with the example above, the test result information, namely M11' and control parameter M11, is retrieved from the asynchronous processing queue.

[0203] S1012: The electronic device updates its historical test information based on the test result information.

[0204] The update operation includes at least one of the following: add operation, edit operation, and modify operation.

[0205] Following the example above, the historical test information of the electronic device is added based on the test result information (M11' and control parameter M11).

[0206] After updating the historical test information of the electronic device based on the test results, to further support tag display and system status management, the test results information also needs to be written to the OEM information database (oeminfo) and its corresponding data status identifier needs to be updated synchronously. This process ensures that key test data can be accurately identified and accessed by upper-layer applications (such as the lock screen display module). The following continues in conjunction with... Figure 11 Further explanation is needed.

[0207] S45: The electronic device parses the complete result test information and determines the test result information that can be displayed.

[0208] The complete test results are structured and analyzed. Based on preset display strategies (such as field whitelists, permission configurations, or the displayFlag field in control instructions), a subset suitable for user interface display is selected. For example, only items related to appearance quality inspection or key performance indicators (such as "orange peel texture of outer screen adhesive lines" or "outer screen floating height") are retained, while internal debugging or redundant data are removed.

[0209] S46: The electronic device writes the test result information that can be displayed into the OEM database.

[0210] The filtered and displayable test results are written into the device's dedicated OEM information database (oeminfo). This database serves as the core storage unit for device metadata, supporting device status display, factory information verification, and subsequent operation and maintenance analysis, ensuring the authority and consistency of the label content.

[0211] Following the example above, write "orange peel texture on outer screen" and "outer screen floating height" into the OEM information database.

[0212] S47: Status indicator for updating test result information of electronic equipment.

[0213] After successfully writing to the OEM information database, the data status identifier corresponding to the test result information is updated synchronously (such as setting the status field to "display_ready" or "uploaded") to indicate that the test result information has been processed and can be used for interface rendering or triggering subsequent actions.

[0214] S6: Electronic devices can display target test information in the form of electronic tags on the interface of the electronic device.

[0215] Step S6 includes the following two execution paths: Path 1 executes step S1013; Path 2 executes S1014-S1015.

[0216] S1013: Display target test information in the target application interface of an electronic device in the form of an electronic tag.

[0217] The target application interface is a dedicated interface such as label management, quality inspection records, or equipment status monitoring, used to intuitively present the test results related to the current equipment to the user.

[0218] It should be noted that the target test information can be the complete test result information of the electronic device or the initial result information, and there is no specific limitation here.

[0219] Following the example above, "orange peel texture of outer screen adhesive line" and "outer screen floating height" will be displayed as electronic tags in the target application interface for users to view and operate.

[0220] In one implementation, for ease of viewing, the electronic device can also continuously display the target test information in the form of an electronic tag when the electronic device's interface is in a specific state. The specific state indicates when the electronic device's screen is locked and lit.

[0221] In one example, step S6 includes steps S1014-S1015.

[0222] S1014: Upon detecting a screen lock event, the electronic device retrieves target test information in a "displayable" state from the OEM database.

[0223] The "displayable" status is determined by the display strategy field in the control command (e.g., display_ready = 1), which only allows labels marked as needing to be displayed to participate in subsequent display.

[0224] Continuing with the example above, if a screen lock event is detected, "Outer screen adhesive line orange peel" and "Outer screen floating height" are marked as displayable (i.e., their displayStatus=1), and the system will only extract these two items as content to be displayed.

[0225] S1015: The electronic device displays target test information on the lock screen.

[0226] Continuing with the example above, "orange peel texture on the outer screen" and "outer screen floating height" will be continuously displayed on the lock screen in the form of electronic tags, allowing users to quickly obtain key detection results without unlocking the device.

[0227] It should be noted that, for system security and user privacy protection, the lock screen only allows the display of authorized, non-sensitive electronic tags; other test information will be restricted from display. If the number of non-sensitive electronic tags exceeds the available display space, the system will prioritize displaying higher-priority electronic tags according to a preset priority strategy.

[0228] In addition, the electronic device establishes a communication connection with the target computing device in the pipe-side device. Therefore, the test result information of the update operation is uploaded to the cloud computing device for storage, which will be explained in conjunction with step S7 below.

[0229] S7: Upload the target test information to the cloud computing device.

[0230] Continue to combine Figure 8 As shown, step S7 includes steps S1016 and S1017.

[0231] S1016: The electronic device sends target test information to the target computing device in the pipe-side device.

[0232] S1017: The target computing device (cloud computing device) sends target test information.

[0233] In summary, this approach enables automated and visualized management of target test information for electronic devices, effectively improving the reliability, traceability, and management efficiency of this information.

[0234] Corresponding to the first embodiment, this application also provides another embodiment. In this second embodiment, the target computing device 4022 of the pipe-side device 402 provides an intuitive human-computer interaction interface. Testers can directly configure label parameters, define display rules, and set attributes such as lifecycle through this interface, and the system generates control commands. For detailed operation logic of this interactive command generation process, please refer to [link to relevant documentation]. Figure 12 The user configuration and command construction process is shown.

[0235] Figure 12 This is a second flowchart illustrating a tag management method for electronic device test information provided in an embodiment of this application.

[0236] like Figure 12 As shown, the tag management method for electronic device test information, applied to a tag management system, includes the following steps: S01: Establish a communication link.

[0237] The specific details of step S01 can be found in step S1 above, and will not be repeated here.

[0238] S02: Pipe-side equipment receives control commands.

[0239] Continue to combine Figure 12 As shown, step S02 includes steps S021-S022.

[0240] S021: The target computing device responds to the user's operation triggered through the batch operation entry, generates control commands in response to the user's request to start the tag management program, and displays the tag configuration interface.

[0241] Figure 13 This is a schematic diagram of the interface of a target computing device provided in an embodiment of this application.

[0242] like Figure 13 As shown in (a), the target computing device, in response to the user's input operation of opening a tab management program in the browser interface 131, displays as shown in (a). Figure 13 The tag management program interface 132 is shown in (b) of the document.

[0243] The tag management program interface 132 adopts a modular layout, including an image display area 132a for real-time display of images of the device under test; a tag display area 132b for presenting the content of electronic tags after OCR recognition and data processing; an attribute setting area 132c; and a running display area 132d (for recording system running logs and events). The attribute setting area 132c provides parameter configuration entries such as the setting control 1321.

[0244] In addition, the tag management program interface 132 has an operation area 132e, which contains two tab controls: "Run" and "Passage Record". Figure 13 (c) shows the interface 133 when the "Passing Records" tab is selected, while the interface corresponding to the "Run" tab is mainly used for related operation control and status display. Through the design of these functional areas, users can easily perform visual configuration of test information, real-time viewing, and historical record querying, thereby achieving efficient management of the entire system.

[0245] Furthermore, such as Figure 13As shown in (b) and (d), in response to a click on the setting control 1321, the tag configuration interface 134 is displayed. The tag configuration interface 134 includes at least one batch operation entry point and configuration controls. The batch operation entry point includes at least one of batch adding tags, batch editing tags, and batch deleting tags; batch adding tags is used to import or create multiple tag templates at once, suitable for standardized testing scenarios; batch editing tags is used to uniformly modify the content, display status, or associated parameters of existing tag fields; batch deleting tags selects multiple invalid or expired tags for quick cleanup and improved data management efficiency. The configuration controls can include various configuration controls such as tag field definition, display rule configuration, data source binding, status identifier settings, and template preview, supporting users to flexibly and efficiently manage the content structure, display logic, and lifecycle of electronic tags in a unified manner.

[0246] S022: The target computing device generates control commands in response to an operation triggered by the user through a batch operation entry.

[0247] Among them, the control command is a batch command containing multiple sub-commands, used to uniformly execute tag management tasks.

[0248] For example, in response to a user initiating an operation through the batch operation entry corresponding to "batch add tags", a control instruction B for batch creating tags will be generated, which includes test result information.

[0249] It should be noted that the above embodiment is illustrated by taking the access of the tag management program through a URL in a browser as an example, but the program can also be deployed on the target computing device. The specific implementation form (such as web application, desktop application or embedded application) can be flexibly selected according to the actual deployment environment and system architecture, and no specific limitation is made here.

[0250] S03: The target computing device sends control commands to the electronic device.

[0251] S04: The electronic device acquires the test result information of the target detection items of the electronic device based on the control command.

[0252] S05: The electronic device updates its historical test information based on its attribute parameters and control parameters.

[0253] S06: Display target test information in the form of electronic tags on the interface of electronic devices.

[0254] S07: Upload the test results information to the cloud computing device.

[0255] The specific details of steps S03-S07 can be found in steps S3-S7 above, and will not be repeated here.

[0256] In summary, by generating control commands through interaction between the target computing device and the user, and based on the test items and parameter requirements carried in the control commands, the electronic device executes the corresponding testing tasks, acquires test result information, and dynamically updates historical test information based on the electronic device attribute parameters and control parameters reflected in the test result information, thus achieving real-time synchronization and precise maintenance of target test information. Simultaneously, the target test information is continuously displayed in the form of electronic tags in specific states on the device interface. This allows for automated and visual management of the target test information of the electronic device, effectively improving the reliability, traceability, and management efficiency of the target test information.

[0257] Corresponding to the above embodiments, this application also provides another embodiment. In this third embodiment, the user interacts with the electronic device to generate control commands. For detailed operational logic of this interactive command generation process, please refer to [link to relevant documentation]. Figure 14 The user configuration and command construction process is shown.

[0258] Figure 14 This is a third flowchart illustrating a tag management method for electronic device test information provided in an embodiment of this application.

[0259] like Figure 14 As shown, the tag management method for electronic device test information, applied to a tag management system, includes the following steps: S141: Establish a communication link.

[0260] The specific details of step S141 can be found in step S1 above, and will not be repeated here.

[0261] S142: Electronic device acquires control command.

[0262] Continue to combine Figure 14 As shown, step S142 includes steps S1421-S142.

[0263] S1421: In response to a user's trigger action on a target application of an electronic device, display a label update control via a graphical user interface.

[0264] Alternatively, the target application can be an engineering menu application or an electronic tag application.

[0265] Figure 15 This application provides a schematic diagram of obtaining a graphical user interface.

[0266] like Figure 15 As shown, electronic device 401 can display a graphical user interface through an engineering menu application or an electronic tag application.

[0267] Specifically, in one implementation, the main interface 151 of the electronic device 401 (e.g., Figure 15 The interface 151 of the electronic device 401 can display various types of application icons, such as a phone application icon, an engineering menu application 1511, and an electronic tag application 1512. The main interface 151 of the electronic device 401 can also display a status bar, which may include: one or more signal strength indicators for mobile communication signals, one or more signal strength indicators for Wi-Fi signals, a battery indicator for the electronic device, a time indicator, etc.

[0268] In response to a user's click operation on the engineering menu application 1511 on the main interface 151, the electronic device 401 launches the engineering menu application 1511 and displays the engineering menu interface 152 (e.g., ...). Figure 15 (as shown in (b)). In the engineering menu interface 152, multiple engineering menus can be displayed, such as "Backend Settings", "Single Board Information Query", "Network Information Query", "Software Upgrade", "Restore Factory Settings", "Electronic Tag" 1521, etc.

[0269] In another embodiment, the electronic device 401, in response to a user's click operation on the "electronic tag" 1521 in the engineering menu interface 152, displays the tag operation interface 153 (e.g., ...). Figure 15 (As shown in (c)). The label operation interface 153 includes a selection control 1531 and an "Add Label" control 1532. The selection control 1531 is used to filter or configure label attributes, specifically including: a label type selection control 1531a, a screen display selection control 1531b, and a deletion selection control 1531c. In addition, the interface also displays several specific test result information (such as multiple historical labels), such as "Overall Process 666", which facilitates label management and operation by users in conjunction with actual test data.

[0270] In another embodiment, the electronic device 401, in response to a user's click operation on the electronic tag application 1512 on the main interface 151, displays the tag operation interface 153 (e.g., ...). Figure 15 (as shown in (c)).

[0271] S1422: Obtain control instructions based on the update operation performed by the user through the label update control.

[0272] The tag update control includes any one of the following: tag addition control, tag editing control, and tag deletion control. When a user performs a tag update operation using any type of control, the electronic device will automatically generate corresponding control instructions based on the operation. The following provides a detailed explanation of the specific interface flow.

[0273] In the first example, the interface flow corresponding to adding a label control is explained with reference to Figure 16.

[0274] Figure 16 This is a schematic diagram of the interface flow corresponding to a label adding control provided in an embodiment of this application.

[0275] like Figure 15 (c) and Figure 16 As shown, in response to a user's click on the "Add Tag" control 1532 on the tag operation interface 153, the electronic device 401 displays the Add Tag interface 161 (e.g., ...). Figure 16 As shown in (a), the tag addition interface 161 includes multiple operation controls, such as the add control 1611, the clear tag content control 1612, and the save control 1613. In addition, the tag addition interface 161 also includes a screen display selection control 1614 and text input fields, such as a preset input field 1615 and a manual input field 1616. The screen display selection control 1614 indicates whether the current tag is displayed in a specific state of the electronic device. Users can combine the preset input field 1615 and the add control 1611 for partial input and partial preset; they can also directly perform a complete preset based on the add control 1611; or they can perform complete input based on the manual input field 1616.

[0276] Example 1: Fully preset directly based on adding control 1611.

[0277] Specifically, in response to the user's click operation on "Add Control" 1611, electronic device 401 displays a preset label operation interface 162 (such as...). Figure 16 As shown in (b), the preset label operation interface 162 includes multiple preset labels, such as "Appearance Label," "Assembly Label," and "Measurement Label" 1621, etc. Combined with... Figure 16 As shown in (c), in response to a user's click on "Measurement Label" 1621 in the preset label operation interface 162, the electronic device 401 displays a drop-down menu 163 showing multiple labels under various measurement label types, such as battery cover gap 1621a. In response to a click on battery cover gap 1621a, the electronic device 401 returns to the label addition interface 161, resulting in a label addition interface 164. At this point, the label content corresponding to the battery cover gap is displayed in the preset input field 1615 of the label addition interface 164, and display options are configured as needed. Furthermore, in response to a user's click on the save control 1613, the electronic device 401 generates control commands.

[0278] Example 2: All data is entered based on the manual input field 1616.

[0279] Specifically, the electronic device 401 responds to the user entering custom label content in the manual input field 1616 of the preset label operation interface 162, and configures the screen display options as needed. After the input is completed, it generates control instructions in response to the user's click operation on the save control 1613.

[0280] Example 3: Combine the preset input field 1615 and the added control 1611 to perform partial data entry and partial preset.

[0281] Specifically, the electronic device 401 responds to the user selecting partial content through preset labels in the preset input field 1615 of the preset label operation interface 162, while simultaneously supplementing additional information in the manual input field 1616, and configuring screen display options as needed. After the input is completed, it generates control commands in response to the user's click operation on the save control 1613.

[0282] In the second example, the interface flow corresponding to the label editing control is explained with reference to Figure 17.

[0283] Figure 17 This is a schematic diagram of the interface flow corresponding to a label editing control provided in an embodiment of this application.

[0284] like Figure 15 (c) and Figure 17 As shown, in response to a user clicking on any historical tag among several specific test result information on the tag operation interface 153, the electronic device 401 displays the tag details interface 171 (e.g., ...). Figure 17 (As shown in (a)). The tag details interface 171 may include several elements such as tag type, operable tag content input field, operable on-screen display option, entry time, and tag save control 1711. Among them, tag type is used to display the basic category of the currently viewed tag. The tag content input field allows users to edit or modify the specific content of the tag in this area. The on-screen display option indicates whether the tag needs to be displayed on the device interface. The entry time indicates the initial creation time of the tag.

[0285] Electronic device 401 updates the information of the label in the label details interface 171 (e.g., in response to a user editing operation on at least one of the operable label content input field and the operable on-screen display option field) by the user. Figure 17 As shown in (b) in the figure, in response to the user's click operation on the save tag control 1711 in the updated display tag details interface 171, the electronic device 401 returns to the tag operation interface 153. In addition, the electronic device 401 also generates control instructions.

[0286] In the third example, the interface flow corresponding to the label deletion control is explained with reference to Figure 18.

[0287] Figure 18 This is a schematic diagram of the interface flow corresponding to a tag deletion control provided in an embodiment of this application.

[0288] like Figure 18 As shown in (a), in response to a user swiping left or long-pressing any historical tag among several specific test result information on the tag operation interface 153, the electronic device 401 displays a prompt box 1811 in the tag operation interface 181. Figure 18 As shown in (a) of the diagram, the prompt box 1811 includes a confirm control and a cancel control. Additionally, the prompt box 1811 includes prompt text asking the user whether they are sure they want to delete the selected tag. In response to the user's operation on the confirm control, the electronic device 401 deletes the tag information and generates a control command.

[0289] It should be noted that although a label is removed from the view, the system still retains a record of that label, usually marked in gray with a strikethrough or other means to indicate that it has been deleted but the record still exists.

[0290] The following section provides a detailed explanation of the interface flow corresponding to the tag deletion control based on the left swipe or long press operation.

[0291] Example 1: A detailed explanation of the interface flow corresponding to the label deletion control based on the left swipe operation.

[0292] like Figure 18 As shown in (a), in response to a user swiping left on a software prototype in several specific test result information on the tag operation interface 153, the electronic device 401 displays a prompt box 1811 in the tag operation interface 181. Figure 18 As shown in (b)), further, in response to the user's click operation on the confirm control in the prompt box 1811, the electronic device 401 returns to the label operation interface 181' (as shown in [example]). Figure 18 As shown in (c)), and generates control commands. Additionally, if the electronic device 401 responds to a user's click on the cancel control in the prompt 1811, it returns to the updated tab operation interface 153 (as shown in [example]). Figure 18 (as shown in (a)).

[0293] Example 2: A detailed explanation of the interface flow corresponding to the tag deletion control based on the long press operation.

[0294] like Figure 18As shown in (a), in response to a user's long-press operation on a software prototype in several specific test result information on the tag operation interface 153, the electronic device 401 updates the tag operation interface 153, resulting in the tag operation interface 182. Figure 18 As shown in (d)). The tag operation interface 182 includes multiple selection boxes, a delete control, and a return control. In response to the user's selection operation of at least one history tag to be deleted and the delete control, the tag operation interface 182 is displayed. Figure 18 As shown in (b) of the diagram, the label operation interface 182 includes a display prompt box 1811. The electronic device 401 further responds to a user's click on the confirm control, returning to the label operation interface 181' and generating a control command. Additionally, if the electronic device 401 responds to a user's click on the cancel control in the prompt box 1811, it returns to the label operation interface 181. If the electronic device 401 responds to a user's click on the return control, it returns to the label operation interface 153.

[0295] After obtaining the control command in the above manner, the following will continue to explain in conjunction with steps S143-S146.

[0296] S143: The electronic device acquires test result information of the target detection items of the electronic device based on control commands.

[0297] The aforementioned control instructions include test result information, which includes the electronic device's attribute parameters and control parameters.

[0298] S144: The electronic device updates its historical test information based on its attribute parameters and control parameters.

[0299] S145: Display target test information in the form of electronic tags on the interface of electronic devices.

[0300] S146: Upload the test results information to the cloud computing device.

[0301] The specific details of steps S143-S146 can be found in steps S4-S7 above, and will not be repeated here.

[0302] In summary, by generating control commands through interaction between electronic devices and users, acquiring test results based on these commands, and dynamically updating historical test information based on the electronic device's attribute parameters and control parameters reflected in these test results, real-time synchronization and precise maintenance of target test information are achieved. Simultaneously, the target test information is continuously displayed in the form of electronic tags under specific device interface states. This allows for automated and visual management of the electronic device's target test information, effectively improving its reliability, traceability, and management efficiency.

[0303] Corresponding to the above embodiments, this application also provides another embodiment. In the fourth embodiment, control commands are issued to electronic devices via cloud computing devices. For detailed operational logic of the control command generation process, please refer to [link to relevant documentation]. Figure 19 The user configuration and command construction process is shown.

[0304] Figure 19 This is a fourth flowchart illustrating a tag management method for electronic device test information provided in an embodiment of this application.

[0305] like Figure 19 As shown, the tag management method for electronic device test information, applied to a tag management system, includes the following steps: S191: Establish a communication link.

[0306] The specific details of step S191 can be found in step S1 above, and will not be repeated here.

[0307] S192: Cloud computing device generates control instructions.

[0308] For example, the control command may be a tag management request issued by the cloud computing device based on the upper-layer business system.

[0309] S193: The cloud computing device sends control commands to the electronic device via the target computing device.

[0310] Since electronic devices are typically deployed on production lines or in field environments, they may not have the ability to communicate directly with the cloud. Therefore, cloud computing devices do not interact directly with electronic devices, but instead send the generated control commands to the target computing device. This target computing device acts as a communication relay and protocol conversion node. It can receive cloud commands, perform security verification and format adaptation, and then reliably send the control commands to the corresponding electronic devices through a local network (such as a LAN, USB, serial port, or industrial bus), thereby triggering them to perform operations such as tag updates, test execution, or status synchronization.

[0311] S194: The electronic device acquires test result information of the target detection items of the electronic device based on control commands.

[0312] The aforementioned control instructions include test result information, which includes the electronic device's attribute parameters and control parameters.

[0313] S195: The electronic device updates its historical test information based on its attribute parameters and control parameters.

[0314] S196: Display target test information in the form of electronic tags on the interface of electronic devices.

[0315] S197: Upload the test results information to the cloud computing device.

[0316] The specific details of steps S194-S197 can be found in steps S4-S7 above, and will not be repeated here.

[0317] In summary, by generating control commands from cloud computing devices and distributing them to electronic devices via the target computing device, test results are obtained based on these commands. Historical test information is then dynamically updated based on the electronic device's attribute parameters and control parameters reflected in these test results, achieving real-time synchronization and precise maintenance of target test information. Simultaneously, the target test information is continuously displayed in the form of electronic tags under specific device interface states. This allows for automated and visualized management of target test information on electronic devices, effectively improving the reliability, traceability, and management efficiency of the target test information.

[0318] Corresponding to the above embodiments, this application also provides an embodiment of a tag management method for electronic device test information applied to the tested electronic device. The following is a detailed description... Figure 20 An example is provided.

[0319] Figure 20 This is the fifth flowchart of a tag management method for electronic device test information provided in an embodiment of this application.

[0320] like Figure 20 As shown, the electronic device under test is connected to the control-side device via a communication interface; the tag management method includes the following steps: S201: When the electronic device is connected to the pipe-side device, obtain the test result information of the target detection items of the electronic device.

[0321] Test results information is used to indicate the attribute parameters and control parameters of electronic devices.

[0322] The specific details of step S201 can be found in step S4 above, and will not be repeated here.

[0323] S202: Update the historical test information of the electronic device based on its attribute parameters and control parameters.

[0324] The specific details of step S202 can be found in step S5 above, and will not be repeated here.

[0325] S203: The target test information is continuously displayed in the form of an electronic tag on the interface of an electronic device when it is in a specific state.

[0326] The specific details of step S203 can be found in step S62 above, and will not be repeated here.

[0327] In summary, by dynamically updating historical test information based on the electronic device's attribute and control parameters reflected in the test results, real-time synchronization and precise maintenance of target test information are achieved. Simultaneously, the target test information is continuously displayed in the form of electronic tags under specific device interface states. This enables automated and visual management of the electronic device's target test information.

[0328] Corresponding to the above embodiments, this application also provides an embodiment of a tag management method for electronic equipment test information applied to the pipe-side equipment side, which will be described below in conjunction with... Figure 21 An example is provided.

[0329] Figure 21 This is a sixth flowchart illustrating a tag management method for electronic device test information provided in an embodiment of this application.

[0330] like Figure 21 As shown, this method is applied to the pipe-side equipment, which communicates with the tested electronic device and cloud computing device through communication interfaces. The tag management method includes the following steps: S211: Acquire captured image.

[0331] The specific details of step S211 can be found in step S21 above, and will not be repeated here.

[0332] S212: If the captured image includes at least one physical tag object for characterizing the attributes of an electronic device, then the physical tag object representing the attributes of the electronic device in the captured image is processed to obtain control instructions.

[0333] Control commands include target test information for electronic devices.

[0334] The specific details of step S212 can be found in step S23 above, and will not be repeated here.

[0335] S213: The target test information is sent to the electronic device through the communication interface, so that the electronic device can update the historical test information of the electronic device based on the target test information.

[0336] The specific details of step S213 can be found in step S3 above, and will not be repeated here.

[0337] In summary, by using the device to capture images of electronic equipment, the system identifies and extracts target test information representing attributes from the captured images, generates control commands and sends them to the electronic equipment, automatically updates its historical test data, realizes the automatic conversion of physical tags to digital test data, improves the automation level and adaptability of the testing process, and reduces management complexity.

[0338] Corresponding to the aforementioned embodiments of the label management method for electronic device test information, this application provides an embodiment of a label management device for electronic device test information.

[0339] Figure 22 This is a schematic diagram of a tag management device for electronic device test information provided in an embodiment of this application.

[0340] like Figure 22 As shown, the tag management device 2200 includes a first acquisition module 2201, an update module 2202, and a first display module 2203.

[0341] The first acquisition module 2201 is configured to acquire test result information of the target detection items of the electronic device when the electronic device is connected to the pipe-side device; the test result information is used to indicate the attribute parameters and control parameters of the electronic device; the update module 2202 is configured to update the historical test information of the electronic device based on the attribute parameters and control parameters of the electronic device; the first display module 2203 is configured to continuously display the target test information in the form of an electronic tag when the interface of the electronic device is in a specific state.

[0342] In one feasible implementation, the first acquisition module 2201 is specifically configured to receive control commands sent by the management-side device; wherein the control commands originate from control commands generated by the management-side device, or are control commands generated by the cloud computing device and forwarded by the management-side device; and acquire target test information based on the control commands.

[0343] In one feasible implementation, the first acquisition module 2201 is specifically configured to, in response to a user's trigger operation on a target application of the electronic device, display a tag update control through a graphical user interface; wherein the tag update control includes any one of a tag addition control, a tag editing control, and a tag deletion control; generate control instructions based on the update operation performed by the user through the tag update control; and acquire target test information based on the control instructions.

[0344] In one feasible implementation, the first acquisition module 2201 is specifically configured to write the attribute parameters and control parameters of the electronic device into an asynchronous processing queue; acquire the attribute parameters and control parameters of the electronic device from the asynchronous processing queue; and update the historical test information of the electronic device based on the attribute parameters of the electronic device; wherein the update operation includes at least one of the following: add operation, edit operation, and modify operation.

[0345] In one feasible implementation, the first display module 2203 is configured to, upon detecting a screen lock event, acquire target test information corresponding to the displayable state; and display the target test information corresponding to the displayable state on the screen lock interface in the form of an electronic tag.

[0346] In one feasible implementation, the first display module 2203 is configured to display target test information in the target application interface of the electronic device in the form of an electronic tag.

[0347] Corresponding to the aforementioned embodiments of the label management method for electronic device test information, this application provides an embodiment of a label management device for electronic device test information.

[0348] Figure 23 This is a schematic diagram of another tag management device for electronic device test information provided in an embodiment of this application.

[0349] like Figure 23 As shown, the tag management device 2300 includes a second acquisition module 2301, a sending module 2302, and a second display module 2303.

[0350] The second acquisition module 2301 is configured to: acquire captured images; the second acquisition module 2301 is also configured to: if the captured image includes at least one physical tag object for characterizing the attributes of the electronic device, process the physical tag object of the attributes of the electronic device in the captured image to acquire control instructions; the control instructions include target test information of the electronic device; the sending module 2302 is configured to: send the target test information to the electronic device through a communication interface, so that the electronic device updates its historical test information based on the target test information.

[0351] In one feasible implementation, the second acquisition module 2301 is further configured to: identify physical tag objects representing the functions and performance of electronic devices in the captured image to determine a target image; the target image includes multiple tag text boxes; using the multiple tag text boxes as input to a neural network model, at least one electronic tag is obtained using the neural network model; the electronic tag is structured data containing tag type and / or tag text content; based on the structured data containing tag type and / or tag text content, control instructions for controlling the electronic device are generated.

[0352] In one feasible implementation, the second acquisition module 2301 is further configured to: preprocess the captured image to obtain a processed captured image; filter the processed captured image based on a contour algorithm to obtain at least one candidate label block; the candidate label block is used to characterize a label region in the image that may contain text information; filter the candidate label block based on color features to obtain at least one target label block; wherein the target label block is used to characterize a region that matches a preset color template; and obtain a target image based on the target label block and the processed captured image.

[0353] In one feasible implementation, a second display module 2303 is also included. The second display module 2303 is further configured to: display a tag configuration interface in response to a user's request to start the tag management program; the tag configuration interface includes at least one batch operation entry, which includes at least one of batch adding tags, batch editing tags, and batch deleting tags; and generate control instructions in response to an operation triggered by the user through the batch operation entry.

[0354] Figure 24 This is a schematic diagram of the chip system provided in the embodiments of this application.

[0355] like Figure 24 As shown, this application embodiment also provides a chip system 2400, such as a SoC, which includes at least one processor 2401 and at least one interface circuit 2402. The processor 2401 and the interface circuit 2402 can be interconnected via lines. For example, the interface circuit 2402 can be used to receive signals from other devices (e.g., the memory of an electronic device). As another example, the interface circuit 2402 can be used to send signals to other devices (e.g., the processor 2401 or the touchscreen of an electronic device). Exemplarily, the interface circuit 2402 can read instructions stored in the memory and send the instructions to the processor 2401. When the instructions are executed by the processor 2401, the electronic device can perform the steps in the above embodiments. Of course, the chip system may also include other discrete devices, which are not specifically limited in this application embodiment.

[0356] This application also provides a computer-readable storage medium including computer instructions that, when executed on the electronic device, cause the electronic device to perform various functions or steps performed by the electronic device in the above method embodiments.

[0357] This application also provides a computer program product that, when run on an electronic device, causes the electronic device to perform various functions or steps performed by the electronic device in the above method embodiments.

[0358] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual 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.

[0359] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another apparatus, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0360] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0361] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0362] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, essentially or in other words, the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0363] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for managing tags of electronic device test information, characterized in that, The device is applied to the electronic equipment under test, and the electronic equipment is connected to the pipe-side device via a communication interface; The tag management method includes: When the electronic device is connected to the pipe-side device, test result information of the target detection items of the electronic device is acquired; the test result information is used to indicate the attribute parameters and control parameters of the electronic device. Based on the attribute parameters and control parameters of the electronic device, the historical test information of the electronic device is updated. The target test information is continuously displayed in the form of an electronic tag when the interface of the electronic device is in a specific state.

2. The method for tagging test information of electronic devices according to claim 1, characterized in that, The acquisition of the target test information of the electronic device includes: Receive control commands sent by the pipe-side device; wherein the control commands originate from control commands generated by the pipe-side device, or are control commands generated by a cloud computing device and forwarded by the pipe-side device; Based on the control commands, the target test information is obtained.

3. The method for tagging test information of electronic devices according to claim 1, characterized in that, The acquisition of the target test information of the electronic device includes: In response to a user's triggering operation on a target application of the electronic device, a tag update control is displayed through a graphical user interface; wherein, the tag update control includes any one of a tag addition control, a tag editing control, and a tag deletion control; Based on the update operation performed by the user through the label update control, generate control instructions; Based on the control commands, the target test information is obtained.

4. The method for tagging test information of electronic devices according to claim 1, characterized in that, The operation of updating the historical test information of the electronic device based on its attribute parameters and control parameters includes: Write the attribute parameters and control parameters of the electronic device into the asynchronous processing queue; The system retrieves the attribute parameters and control parameters of the electronic device from the asynchronous processing queue, and updates the historical test information of the electronic device based on the attribute parameters of the electronic device; wherein the update operation includes at least one of the operations of adding, editing and modifying.

5. The method for managing tags of electronic device test information according to claim 1 or 2, characterized in that, The method of continuously displaying the target test information in the form of an electronic tag on the interface of the electronic device in a specific state includes: Upon detecting a screen lock event, obtain the target test information corresponding to the displayable state; The target test information corresponding to the displayable state is displayed on the lock screen interface in the form of the electronic tag.

6. A tag management method for electronic device test information, applied to a regulatory-side device, wherein the regulatory-side device communicates with the electronic device under test and a cloud computing device via communication interfaces, the tag management method comprising: Acquire captured images; If the captured image includes at least one physical tag object for characterizing the attributes of the electronic device, then the physical tag object of the attributes of the electronic device in the captured image is processed to obtain control instructions; the control instructions include target test information of the electronic device. The target test information is sent to the electronic device through the communication interface, so that the electronic device can update its historical test information based on the target test information.

7. The method for tagging test information of electronic devices according to claim 6, characterized in that, The process of processing the physical tag objects representing the functions and performance of the electronic device in the captured image to obtain control commands includes: The physical tag objects of the attributes of the electronic device in the captured image are identified to determine the target image; the target image includes multiple tag text boxes; Using the plurality of label text boxes as input to a neural network model, the neural network model is used to obtain at least one electronic label; the electronic label is structured data containing label type and / or label text content; Based on the structured data of the tag type and / or tag text content, the control instructions for controlling the electronic device are generated.

8. The method for managing tags of electronic device test information according to claim 7, characterized in that, The process of identifying physical tag objects representing the functions and performance of the electronic device in the captured image to determine the target image includes: The captured image is preprocessed to obtain the processed captured image; Based on the contour algorithm, the processed captured image is filtered to obtain at least one candidate label block; the candidate label block is used to characterize the label region in the image that may contain text information. Based on color features, the candidate label blocks are filtered to obtain at least one target label block; wherein, the target label block is used to represent the region that matches the preset color template; The target image is obtained based on the target tag block and the processed captured image.

9. The method for managing tags of electronic device test information according to any one of claims 6-8, characterized in that, Also includes: In response to a user's request to launch the tag management program, a tag configuration interface is displayed; the tag configuration interface includes at least one batch operation entry, which includes at least one of batch adding tags, batch editing tags, and batch deleting tags; The control command is generated in response to the user's operation triggered through the batch operation entry.

10. A label management system, characterized in that, include: The tested electronic device, pipe-side device, and cloud computing device, wherein the pipe-side device includes an imaging system and a target computing device, the imaging system being connected to the target computing device; and the target computing device being connected to the cloud computing device via a communication interface. in, The electronic device is configured to: when connected to a pipe-side device, acquire test result information of the target detection item of the electronic device; the test result information is used to indicate the attribute parameters and control parameters of the electronic device; update the historical test information of the electronic device based on the attribute parameters and control parameters of the electronic device; and continuously display the target test information in the form of an electronic tag when the interface of the electronic device is in a specific state. The imaging system is configured to: acquire images of a physical tag object including at least one object for characterizing the properties of the electronic device, and generate captured images; The target computing device is configured to: process the captured image and obtain control commands; The cloud computing device is configured to generate control commands.

11. A computer-readable storage medium, characterized in that, Includes computer instructions that, when executed on a computer, cause the computer to perform the tag management method as described in any one of claims 1-9.

12. A computer program product, characterized in that, When the computer program product is run on a computer, the computer performs the tag management method as described in any one of claims 1-9.

Images