Uninstalling method and device of USB (Universal Serial Bus) equipment

Abstract

The invention provides a method and a device for uninstalling USB (Universal Serial Bus) equipment, relates to the field of data processing, and aims to give consideration to the use safety of equipment on a zero terminal and improve the operation experience of a user for uninstalling the USB equipment. According to the specific technical scheme, an S end sends request information of USB equipment to an R end; the R end judges whether to-be-processed write operation exists or not according to the request information popping up the USB equipment; the R end processes the USB equipment according to a judgment result in a processing mode of unloading the USB equipment or generating a report of refusing to pop up the USB equipment; the R end sends information containing the processing mode to the S end; and after the S end receives the information containing the processing mode from the R end, the processing mode is prompted to the user. According to the method and the device, in a zero-terminal VFS redirection scene, a user can safely pull out the USB equipment according to a prompt under the condition of confirming that the to-be-processed write operation does not exist.

Description

Technical Field

[0001] The present disclosure relates to the field of data processing, and in particular to a method and apparatus for uninstalling a USB device. Background Art

[0002] Currently, in the zero-terminal virtual file system (VFS) redirection scenario, the S end (i.e., the sending end) sees a mapped disk instead of an actual USB flash drive, so the user cannot eject the device on the S end. When the S end shows that the read and write are completed (especially the write operation), the data on the R end may be in the cache and has not been synchronized to the device. If the user thinks that the operation is completed and unplugs the device on the R end, it will inevitably cause problems.

[0003] In the existing method, real-time writing can be used when writing on the R side, and the data is no longer written to the cache, but is directly synchronized to the device through IO operations. However, this will cause the copying speed to decrease, affecting the user experience. Summary of the invention

[0004] The disclosed embodiment provides a method and apparatus for uninstalling a USB device, which can take into account the use safety of the device on the zero terminal and improve the user's experience of uninstalling the USB device. The technical solution is as follows:

[0005] According to a first aspect of an embodiment of the present disclosure, a method for uninstalling a USB device is provided, the method comprising: an S end sends request information of a USB device to an R end; the R end determines whether there is a pending write operation based on the request information for ejecting the USB device; the R end processes the USB device based on a result of the determination, the processing method being to uninstall the USB device or to generate a report refusing to eject the USB device; the R end sends information containing the processing method to the S end; after the S end receives the information containing the processing method from the R end, the S end prompts a user with the processing method.

[0006] Specifically, the S end may send a request message for ejecting the USB device to the R end by sending a FS_EJECT_USB_REQUEST message to the R end.

[0007] Based on the above solution, through the relatively safe USB device uninstallation method in the zero-terminal VFS redirection scenario, the user can unplug the USB device according to the prompt after confirming that there is no pending write operation, which can provide users with a more user-friendly operation experience of uninstalling USB devices while taking into account the safety of the device on the zero terminal.

[0008] In some embodiments, determining whether there is a pending write operation includes: the R end determines whether there is a pending write operation by checking whether there are any remaining unprocessed write request messages in the current operation queue.

[0009] As an example, the R end may check whether there are any remaining unprocessed FS_WRITE_REQUEST messages in the current operation queue (ie, check whether there are any remaining unprocessed write request messages in the current operation queue) to determine whether there are any pending write operations.

[0010] In some embodiments, the R end processes the USB device according to the result of the judgment, including: when there is no pending write operation, uninstalling the USB device; when there is a pending write operation, generating a report refusing to eject the USB device.

[0011] Specifically, when there is a pending write operation, that is, there is an unprocessed FS_WRITE_REQUEST message, a report refusing to eject the USB device may be generated to reject the user operation.

[0012] In some embodiments, uninstalling a USB device includes: preparing to start uninstalling the USB device, synchronizing cached data, closing an open file handle, and uninstalling the USB device.

[0013] Specifically, when there is no pending write operation, the USB preparation can be started to be uninstalled, and then the cached data is synchronized, and then the opened file handle is closed, and finally the device is uninstalled (mounted).

[0014] In some embodiments, the S end sends a request message for ejecting the USB device to the R end, including: the S end receives application message for uninstalling the USB device from the user; the S end sends a request message for ejecting the USB device to the R end according to the application message for uninstalling the USB device.

[0015] As an example, the user can send an exit application to the S end (i.e., the application information for uninstalling the USB device), and then the S end responds to the user's exit application (i.e., according to the application information for uninstalling the USB device) and sends a FS_EJECT_USB_REQUEST message to the R end.

[0016] In some embodiments, the R end is a hard R end or a soft R end.

[0017] In some embodiments, the method of prompting the user to process includes: when the R end is a hard R end, prompting the user to process by a pop-up message bubble on the S end, or by a flashing light on the R end; when the R end is a soft R end, prompting the user to process by a toolbar on the S end, or by a dialog box on the S end.

[0018] Specifically, in the above steps, after the S end receives the information containing the processing method from the R end, when the R end is a hard R end, in view of the fact that the hard R end has no toolbar, the processing method can be prompted to the user through a pop-up message bubble on the S end or through a flashing light on the R end; when the R end is a soft R end, the processing method can be prompted to the user through a toolbar prompt on the S end or through a dialog box prompt on the S end.

[0019] After executing the above solution, the user can check and unplug the USB device without worry if the USB device can be uninstalled according to the processing method.

[0020] According to a second aspect of an embodiment of the present disclosure, there is provided an uninstall device for a USB device, comprising a memory and a processor. The memory has a stored program. When the program is executed in the processor, the processor is used to execute the method of the first aspect and any embodiment of the first aspect.

[0021] Based on the above device, the user can unplug the USB device according to the prompt after confirming that there is no pending write operation, which can provide the user with a more user-friendly operation experience of uninstalling the USB device, while taking into account the safety of using the device on the zero terminal.

[0022] According to a third aspect of an embodiment of the present disclosure, there is provided an unloading device for a USB device, comprising: a first sending module, used for an S end to send request information for ejecting a USB device to an R end; a judging module, used for the R end to judge whether there is a pending write operation based on the request information for ejecting the USB device; a processing module, used for the R end to process the USB device based on a result of the judgment, wherein the processing method is to uninstall the USB device or to generate a report for refusing to eject the USB device; a second sending module, used for the R end to send information containing the processing method to the S end; and a prompting module, used for prompting a user with the processing method after the S end receives the information containing the processing method sent by the R end.

[0023] In some embodiments, the judgment module is specifically used to determine whether there is a pending write operation by checking whether there are any remaining unprocessed write request messages in the current operation queue at the R end.

[0024] In some embodiments, the processing module includes: a first unloading submodule, used to unload the USB device when there is no pending write operation; and a generating submodule, used to generate a report refusing to eject the USB device when there is a pending write operation.

[0025] In some embodiments, the processing module includes: a preparation submodule for preparing to start uninstalling the USB device; a synchronization submodule for synchronizing cached data; a closing submodule for closing an open file handle; and a second uninstallation submodule for uninstalling the USB device.

[0026] In some embodiments, the first sending module includes: a receiving submodule, used for the S end to receive application information for uninstalling the USB device from the user; and a sending submodule, used for the S end to send request information for ejecting the USB device to the R end according to the application information for uninstalling the USB device.

[0027] In some embodiments, the R end is a hard R end or a soft R end.

[0028] In some embodiments, the prompt module is specifically used to, when the R end is a hard R end, prompt the user of the processing method by means of a pop-up message bubble on the S end, or by means of a flashing light on the R end; when the R end is a soft R end, prompt the user of the processing method by means of an S end toolbar, or by means of an S end dialog box.

[0029] According to a fourth aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided, characterized in that the computer program storage medium has program instructions, and when the program instructions are executed by a processor, the processor executes the method of the first aspect and any embodiment of the first aspect.

[0030] According to the fifth aspect of the embodiments of the present disclosure, a chip system is provided, characterized in that the chip system includes at least one processor, and when program instructions are executed in the at least one processor, the at least one processor executes the method of the first aspect and any embodiment of the first aspect.

[0031] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0033] Figure 1 is a schematic diagram of a method 100 for sharing data between a remote environment and a local environment;

[0034] Figure 2 is a flowchart of a USB device uninstallation method 200 provided by an embodiment of the present disclosure;

[0035] Figure 3 is a schematic diagram of a method 300 for performing a security check through a menu provided in this embodiment;

[0036] Figure 4 is a structural diagram of an uninstall device 400 of a USB device provided by an embodiment of the present disclosure;

[0037] Figure 5is a structural diagram of an uninstallation device 500 of a USB device provided by an embodiment of the present disclosure;

[0038] Figure 6 is another structural diagram of an uninstallation device 500 of a USB device provided by an embodiment of the present disclosure;

[0039] Figure 7 is another structural diagram of an uninstallation device 500 of a USB device provided by an embodiment of the present disclosure;

[0040] Figure 8 It is another structural diagram of an uninstallation apparatus 500 for a USB device provided by an embodiment of the present disclosure. DETAILED DESCRIPTION

[0041] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0042] Currently, in the cloud era, more and more desktops and applications are running in the cloud environment. Local personal computers are connected to the cloud through remote desktops to enjoy the high-speed and secure operating environment of the cloud environment. Among them, there are many ways to share data between the remote environment and the local environment, and transferring data through disk mapping is one of the most convenient ways.

[0043] Figure 1 1 is a schematic diagram of a method 100 for sharing data between a remote environment and a local environment. Figure 1 As shown, on the remote PC, executing operations in the mapped disk, such as copying a file on the physical disk of the remote PC to the mapped disk, will trigger a request for the file content from the remote end to the local end.

[0044] As we all know, file system read and write cache is a technology used to improve file system performance. It caches file system read and write operations in memory to reduce the number of disk accesses, thereby speeding up file system access. However, in actual use, there will be data consistency issues because the page cache adopts a delayed write strategy, that is, the data is first written to the cache, and then the kernel decides when to flush it to the disk.

[0045] When a USB flash drive is inserted into a local Windows system, there is usually a menu of safe hardware removal in the system tray area in the lower right corner. After the user chooses to eject the USB flash drive, if the USB flash drive is in operation, the system will prompt that the device is busy, indicating that the system and the device are frequently synchronizing data at this time. Forcibly pulling out the USB flash drive may cause partition damage and data loss. Therefore, it is safe to pull out the USB flash drive only after it is ejected successfully.

[0046] However, in the zero-terminal virtual file system VFS redirection scenario, the S end (i.e., the sending end) sees a mapped disk instead of an actual USB flash drive, so the user cannot eject the device on the S end. Especially in the zero-terminal VFS redirection scenario, the S end and the R end (i.e., the receiving end) are different systems, so when S shows that the read and write are completed (especially the write operation), the data on the R end may be in the cache and has not been synchronized to the device. The user thinks that the operation is completed and unplugs the device on the R end, which is bound to cause problems. In the existing method, a real-time write action can be used when writing on the R end, and the data is no longer written to the cache, but is directly synchronized to the device through IO operations. However, this will cause the copying speed to decrease, affecting the user experience.

[0047] In view of this, the present disclosure provides a method for uninstalling a USB device, which can improve the above problems and enhance the user experience.

[0048] It should be understood that in the following embodiments, the R end can be divided into a hard R end or a soft R end. Among them, the hard R end does not have a toolbar layer, and the screen displayed is the captured desktop of the S end after decoding, and can be directly operated through shortcut keys and then prompted by indicator lights; the soft R end has a toolbar layer, and a dynamic menu can be added to the toolbar. When a device is mapped, the corresponding logo can be displayed on the menu, and then operations can be performed directly on the menu.

[0049] The present disclosure provides a method 200 for uninstalling a USB device. Figure 2 As shown, the USB device uninstallation method 200 is applied to the zero-terminal virtual file system and includes the following steps:

[0050] S210, the S end sends a request message for ejecting the USB device to the R end.

[0051] Specifically, the S end may send a request message for ejecting the USB device to the R end by sending a FS_EJECT_USB_REQUEST message to the R end.

[0052] Optionally, the S end sends a request message for ejecting the USB device to the R end, which can be implemented by the following steps:

[0053] The S end receives the application information for uninstalling the USB device from the user; then, the S end sends the request information for ejecting the USB device to the R end according to the application information for uninstalling the USB device.

[0054] As an example, the user can send an exit application to the S end (i.e., the application information for uninstalling the USB device), and then the S end responds to the user's exit application (i.e., according to the application information for uninstalling the USB device) and sends a FS_EJECT_USB_REQUEST message to the R end.

[0055] It should be understood that in the above scheme, when the R end is a hard R end, the user can send an application information for uninstalling the USB device to the S end through a shortcut key; when the R end is a soft R end, the user can send an application information for uninstalling the USB device to the S end through a toolbar menu or other means.

[0056] S220, the R end determines whether there is a pending write operation based on the request information of ejecting the USB device.

[0057] Specifically, whether there is a pending write operation can be determined in the following ways:

[0058] The R end determines whether there is a pending write operation by checking whether there are any remaining unprocessed write request messages in the current operation queue.

[0059] As an example, the R end may check whether there are any remaining unprocessed FS_WRITE_REQUEST messages in the current operation queue (ie, check whether there are any remaining unprocessed write request messages in the current operation queue) to determine whether there are any pending write operations.

[0060] S230, the R end processes the USB device according to the judgment result.

[0061] The processing method is to uninstall the USB device or generate a report refusing to eject the USB device.

[0062] Specifically, it can be divided into the following two methods:

[0063] In one possible implementation, when there are no pending write operations, the USB device is unmounted.

[0064] Furthermore, uninstalling the USB device can be achieved by following the steps below:

[0065] Prepare to start unmounting the USB device, sync cached data, close open file handles, and unmount the USB device.

[0066] Specifically, when there is no pending write operation, the USB preparation can be started to be uninstalled, and then the cached data is synchronized, and then the opened file handle is closed, and finally the device is uninstalled (umount).

[0067] In another way that this may be implemented, when there is a pending write operation, a report is generated that denies ejecting the USB device.

[0068] Specifically, when there is a pending write operation, that is, there is an unprocessed FS_WRITE_REQUEST message, a report refusing to eject the USB device may be generated to reject the user operation.

[0069] S240, the R end sends information including the processing method to the S end.

[0070] S250, after receiving the information including the processing method from the R end, the S end prompts the user with the processing method.

[0071] Optionally, in the above solution, the R end may be a hard R end or a soft R end.

[0072] Furthermore, according to the types of different R terminals, the processing methods for prompting the user can be divided into the following two situations:

[0073] In one possible implementation, when the R end is a hard R end, the user may be prompted with a pop-up message bubble on the S end or with a flashing light on the R end;

[0074] In another possible implementation method, when the R end is a soft R end, the user can be prompted with a processing method through an S end toolbar or an S end dialog box.

[0075] Specifically, in the above steps, after the S end receives the information containing the processing method from the R end, when the R end is a hard R end, in view of the fact that the hard R end has no toolbar, the processing method can be prompted to the user through a pop-up message bubble on the S end or through a flashing light on the R end; when the R end is a soft R end, the processing method can be prompted to the user through a toolbar prompt on the S end or through a dialog box prompt on the S end.

[0076] It should be understood that in the above solution, for the hard R end, the user can trigger safe uninstallation by physical or virtual keys. For example, it can be done by Alt+Ctrl+number keys, where the number keys can correspond to the directories mapped in sequence from 1 to 9 on the S end, and exit in sequence.

[0077] After executing the above solution, the user can check and unplug the USB device without worry if the USB device can be uninstalled according to the processing method.

[0078] As an example, Figure 3 It is a schematic diagram of a method 300 for performing a security check through a menu provided in this embodiment. The method 300 is applicable to the method 200 provided in the embodiment of the present disclosure.

[0079] Based on the above solution, through the relatively safe USB device uninstallation method in the zero-terminal VFS redirection scenario, the user can unplug the USB device according to the prompt after confirming that there is no pending write operation, which can provide users with a more user-friendly operation experience of uninstalling USB devices while taking into account the safety of the device on the zero terminal.

[0080] Based on the above Figure 2 The USB device uninstallation method described in the corresponding embodiment is as follows: an apparatus embodiment of the present disclosure, which can be used to execute the method embodiment of the present disclosure.

[0081] The present disclosure embodiment provides an uninstall device 400 of a USB device, such as Figure 4 The USB device uninstallation device 400 includes: a memory 401 and a processor 402 .

[0082] The memory 401 is used to store programs.

[0083] When the program is executed in the processor 402, the processor 402 is used to execute the above-mentioned USB device uninstallation method.

[0084] Processor 402 is used for: the S end sends a request message for ejecting a USB device to the R end; the R end determines whether there is a pending write operation based on the request message for ejecting the USB device; the R end processes the USB device based on the result of the determination, and the processing method is to uninstall the USB device or generate a report refusing to eject the USB device; the R end sends information containing the processing method to the S end; after the S end receives the information containing the processing method from the R end, the S end prompts the user with the processing method.

[0085] Optionally, the processor 402 is specifically configured to: the R end determines whether there is a pending write operation by checking whether there are any remaining unprocessed write request messages in the current operation queue.

[0086] Optionally, the processor 402 is specifically configured to: when there is no pending write operation, uninstall the USB device; when there is a pending write operation, generate a report for refusing to eject the USB device.

[0087] Optionally, the processor 402 is specifically configured to: prepare to start uninstalling the USB device, synchronize cached data, close an opened file handle, and uninstall the USB device.

[0088] Optionally, the processor 402 is specifically configured to: the S end receives application information for uninstalling the USB device from the user; and the S end sends request information for ejecting the USB device to the R end according to the application information for uninstalling the USB device.

[0089] Optionally, the R end is a hard R end or a soft R end.

[0090] Optionally, the processor 402 is specifically used to, when the R end is a hard R end, prompt the user of the processing method by means of a pop-up message bubble on the S end, or by means of a flashing light on the R end; when the R end is a soft R end, prompt the user of the processing method by means of the S end toolbar, or by means of the S end dialog box.

[0091] The USB device uninstallation device provided in the embodiment of the present disclosure allows the user to unplug the USB device according to the prompt after confirming that there is no pending write operation, which can provide the user with a more user-friendly operation experience of uninstalling the USB device while taking into account the safety of the device on the zero terminal.

[0092] Based on the above Figure 2 The USB device uninstallation method described in the corresponding embodiment is as follows: an apparatus embodiment of the present disclosure, which can be used to execute the method embodiment of the present disclosure.

[0093] Based on the above Figure 2 Corresponding to the USB device uninstallation method described in the embodiment, the present disclosure also provides a USB device uninstallation device 500, such as Figure 5 shown.

[0094] The USB device uninstallation device 500 includes: a first sending module 510, which is used by the S end to send a request information for ejecting the USB device to the R end; a judgment module 520, which is used by the R end to judge whether there is a pending write operation based on the request information for ejecting the USB device; a processing module 530, which is used by the R end to process the USB device based on the result of the judgment, and the processing method is to uninstall the USB device or generate a report refusing to eject the USB device; a second sending module 540, which is used by the R end to send information containing the processing method to the S end; and a prompt module 550, which is used to prompt the user with the processing method after the S end receives the information containing the processing method sent by the R end.

[0095] Optionally, the judgment module 520 is specifically used to determine whether there is a pending write operation by checking whether there are any remaining unprocessed write request messages in the current operation queue at the R end.

[0096] Alternatively, if Figure 6 As shown, the processing module 530 includes: a first unloading submodule 5301, used to unload the USB device when there is no pending write operation; a generating submodule 5302, used to generate a report for refusing to eject the USB device when there is a pending write operation.

[0097] Alternatively, if Figure 7 As shown, the processing module 530 includes: a preparation submodule 5303, used for preparing to start uninstalling the USB device; a synchronization submodule 5304, used for synchronizing cached data; a closing submodule 5305, used for closing the opened file handle; and a second uninstallation submodule 5306, used for uninstalling the USB device.

[0098] Alternatively, if Figure 8 As shown, the first sending module 510 includes: a receiving submodule 5101, which is used by the S end to receive application information for uninstalling the USB device from the user; and a sending submodule 5102, which is used by the S end to send request information for ejecting the USB device to the R end according to the application information for uninstalling the USB device.

[0099] Optionally, the R end is a hard R end or a soft R end.

[0100] Optionally, the prompt module 550 is specifically used to, when the R end is a hard R end, prompt the user of the processing method by means of a pop-up message bubble on the S end, or by means of a flashing light on the R end; when the R end is a soft R end, prompt the user of the processing method by means of an S end toolbar, or by means of an S end dialog box.

[0101] Based on the above Figure 2 Corresponding to the USB device uninstallation method described in the embodiment, the embodiment of the present disclosure also provides a computer-readable storage medium, for example, a non-temporary computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, and an optical data storage device. The storage medium stores computer instructions for executing the above Figure 2 The method for uninstalling the USB device described in the corresponding embodiment will not be repeated here.

[0102] Based on the above Figure 2Corresponding to the uninstall method of the USB device described in the embodiment, the embodiment of the present disclosure also provides a chip system, the chip system includes at least one processor, when the program instruction is executed in the at least one processor, the at least one processor executes the above Figure 2 The method for uninstalling the USB device described in the corresponding embodiment will not be repeated here.

[0103] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The description and examples are intended to be exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.

[0104] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A method for ejecting a universal serial bus (USB) device, characterized in that: The method comprises: The S end sends a request message of the USB device to the R end; The R end determines whether there is a pending write operation according to the request information of ejecting the USB device; The R end processes the USB device according to the result of the judgment, and the processing method is to uninstall the USB device or generate a report refusing to eject the USB device; The R terminal sends information including the processing method to the S terminal; After the S end receives the information including the processing method from the R end, the S end prompts the user with the processing method.

2. The method according to claim 1, characterized in that The determining whether there is a pending write operation includes: The R end determines whether there is the pending write operation by checking whether there are any remaining unprocessed write request messages in the current operation queue.

3. The method according to claim 1, characterized in that The R end processes the USB device according to the result of the determination, including: When there is no pending write operation, uninstalling the USB device; When there is the pending write operation, a report for refusing to eject the USB device is generated.

4. The method according to claim 1, characterized in that: The step of uninstalling the USB device comprises: Prepare to start uninstalling the USB device, synchronize cache data, close open file handles, and uninstall the USB device.

5. The method according to claim 1, characterized in that The S end sends a request message for ejecting the USB device to the R end, including: The S terminal receives application information for uninstalling the USB device from the user; The S end sends the request information of ejecting the USB device to the R end according to the application information of uninstalling the USB device.

6. The method according to claim 1, characterized in that The R end is a hard R end or a soft R end.

7. The method according to claim 6, characterized in that The method of prompting the user about the processing includes: When the R end is a hard R end, the processing method is prompted to the user by a pop-up message bubble on the S end or a flashing light on the R end; When the R end is a soft R end, the processing method is prompted to the user through the S end toolbar or the S end dialog box.

8. An uninstallation device for a USB device, characterized in that: include: The first sending module is used for the S end to send a request message for ejecting the USB device to the R end; A judgment module, used for the R end to judge whether there is a pending write operation according to the request information of the ejected USB device; A processing module, used for the R end to process the USB device according to the result of the judgment, wherein the processing method is to uninstall the USB device or generate a report refusing to eject the USB device; A second sending module, configured for the R end to send information including the processing method to the S end; A prompt module is used to prompt the user of the processing method after the S end receives the information containing the processing method sent by the R end.

9. An uninstall device for a USB device, characterized in that: including memory and processor; The memory has a stored program; When the program is executed in the processor, the processor is configured to execute the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer program storage medium has program instructions, and when the program instructions are executed by a processor, the processor is caused to execute the method according to any one of claims 1 to 6.

Images