Cloud mobile phone file distribution system and method based on object storage and debugging bridge

Abstract

The invention relates to the technical field of cloud services, and discloses a cloud mobile phone file distribution system and method based on object storage and a debugging bridge. According to the system, the sharing mounting capacity of object storage and the ADB (Android Debugging Bridge) technology are fused, a high-performance sharing storage pool is constructed, a standardized API (Application Program Interface) is provided, and the problems of low file distribution efficiency, difficulty in sharing, poor reliability and tedious management in the prior art are solved. According to the method, an efficient distribution mode of'one-time uploading and everywhere availability 'is realized, real-time data sharing of cross-cloud mobile phone instances is supported, high reliability and persistence of data are guaranteed, automatic business process integration is adapted, and the method is suitable for scenes such as large-scale cloud mobile phone file distribution and cross-instance data collaboration.

Description

Technical Field

[0001] This invention relates to the fields of cloud phone technology, file distribution and data sharing, and specifically to a cloud phone file distribution system and method based on object storage and a debug bridge, which is applicable to scenarios requiring large-scale cloud phone file management, such as automated testing, mobile office, data collection, and application hosting. Background Technology

[0002] With the widespread application of cloud phones in scenarios such as automated testing, mobile office, data collection, and application hosting, large-scale and efficient file management and distribution have become core requirements. Whether it is deploying test applications (APKs), data files, and scripts to hundreds of cloud phones in batches, or achieving data sharing among multiple cloud phone instances, traditional file transfer methods face many challenges.

[0003] First, current cloud phone file transfer methods suffer from inefficiency and bandwidth waste. Traditional methods often rely on traversing all cloud phone instances and pushing files one by one using the push command of the Android Debug Bridge (ADB). When the file is large or the number of instances is large, the outbound bandwidth of the central control server is repeatedly occupied N times (N is the number of instances), resulting in extremely long total transmission time and very low efficiency.

[0004] Secondly, the lack of an inter-instance sharing mechanism means that cloud phone instances are essentially isolated virtual environments. In traditional architectures, data generated by one instance cannot be directly and in real-time accessed by other instances, hindering business scenarios that require data interaction and collaborative work.

[0005] Furthermore, reliability and durability are poor. Files pushed via ADB exist only in the volatile storage of a single instance. Once the instance is reset or destroyed, the files will be lost. If the target instance is offline when pushing, the distribution will fail, requiring an additional retry mechanism, which complicates management.

[0006] Moreover, the operation is cumbersome and difficult to manage. In the current cloud phone file transfer, there is a lack of a unified, API-based management interface, making it difficult to distribute files in batches and track their status, which is not conducive to integration with automated business processes.

[0007] Therefore, there is an urgent need for a cloud phone file distribution and sharing solution that can solve the above problems and achieve high efficiency, real-time performance, reliability and easy management. Summary of the Invention

[0008] This invention aims to overcome the shortcomings of existing technologies and provide a cloud mobile phone file distribution system and method based on object storage and debugging bridge, so as to realize efficient distribution of large-scale cloud mobile phone files, real-time sharing across instances, high-reliability data persistence, and automated management.

[0009] Specifically, this invention provides a cloud phone file distribution method based on object storage and a debug bridge. The method includes the following steps: Shared storage mounting step: A storage bucket of the object storage module is opened in the cloud platform to store shared files and files to be distributed; the storage bucket is mounted as a local directory of at least one physical host machine (which can be extended to all physical host machines) via a file system plugin; when any cloud phone instance starts, the local directory of the host machine is mapped to a shared directory within the cloud phone instance via a file system sharing protocol (e.g., a specific network protocol). At this time, the shared directories of all cloud phone instances point to the same object storage bucket; File push step: The file to be distributed is uploaded to the object storage module, and the URL value of the file to be distributed is obtained; the API interface of the control platform module is called based on the request content; after receiving the request content, the control platform module sends a download instruction to the proxy module of each target cloud phone instance, which is transmitted via ADB. Channel transmission; after receiving the instruction, each cloud phone agent module independently downloads the file from the file URL corresponding to the URL value and stores it to the specified path; after all cloud phone instances complete the operation, the control platform module provides feedback on the execution result to the user; cross-instance data real-time sharing steps: first, data is written to cloud phone instance A. After the business program of cloud phone instance A generates the data file, it writes it to its own shared directory; through the underlying mechanism of the storage mounting module, the operation of writing to the shared directory is transparently converted into an upload operation to the object storage module, and the file is persisted to the storage bucket in real time; the business program of cloud phone instance B directly accesses the shared directory of cloud phone instance A.

[0010] Preferably, the request content includes a list of target cloud phone instance numbers, file URLs, file names, MD5 values, and sets the autoInstall parameter.

[0011] More preferably, autoInstall=1 indicates automatic installation, while autoInstall=0 indicates download only.

[0012] Preferably, if autoInstall=1, the control platform module sends installation instructions to each instance through the ADB channel, triggering automatic file installation.

[0013] Preferably, if the automatic installation parameter is 1, the control platform module sends installation instructions to each instance through the ADB channel to trigger automatic file installation.

[0014] Preferably, in the real-time cross-instance data sharing step, the business programs of cloud phone instances C and D, which are different from cloud phone instances A and B, also directly access the shared directory of cloud phone instance A.

[0015] Preferably, the storage mounting module uses a two-level mounting mechanism of "host mounting + instance mapping" to map the object storage bucket to the local shared directory of all cloud phone instances, thereby achieving interconnection of the underlying storage and providing a foundation for real-time sharing.

[0016] Preferably, a flow control tool is used on the host machine to mark and limit the bandwidth of the local directory formed by the mount, so as to control the total bandwidth of the shared files.

[0017] The present invention also provides a cloud mobile phone file distribution system based on object storage and debug bridge, for performing the method described above.

[0018] In summary, this invention provides a cloud phone file distribution system and method based on object storage and Android Debug Bridge (ADB). This system integrates the shared mounting capabilities of object storage with Android Debug Bridge (ADB) technology to build a high-performance shared storage pool and provide standardized API interfaces, solving the problems of low efficiency, difficult sharing, poor reliability, and cumbersome management in traditional file distribution. This invention achieves a highly efficient distribution mode of "upload once, use everywhere," supports real-time data sharing across cloud phone instances, ensures highly reliable data persistence, and is compatible with automated business process integration, making it suitable for scenarios such as large-scale cloud phone file distribution and cross-instance data collaboration. Attached Figure Description

[0019] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the accompanying drawings used in the description of the embodiments or the prior art will be discussed below. Obviously, the technical solutions described in conjunction with the accompanying drawings are only some embodiments of the present invention. For those skilled in the art, other embodiments and their accompanying drawings can be obtained based on the embodiments shown in these drawings without creative effort.

[0020] Figure 1 The diagram illustrates the path framework of the cloud mobile phone file distribution system based on object storage and debug bridge according to the present invention. Figure 2 A flowchart illustrating the cloud phone file distribution method based on object storage and debugging bridge according to the present invention is shown. Detailed Implementation

[0021] The technical solutions of various embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them. Based on the embodiments described in the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0022] This invention aims to overcome the shortcomings of existing technologies and provide a cloud mobile phone file distribution system and method based on object storage and debugging bridge, so as to realize efficient distribution of large-scale cloud mobile phone files, real-time sharing across instances, high-reliability data persistence, and automated management.

[0023] The following will describe in detail the specific system architecture and method flow of the system method provided by the present invention with reference to the accompanying drawings. Figure 1 The diagram illustrates the path framework of a cloud mobile phone file distribution system based on object storage and debug bridge according to the present invention. Figure 2 This illustrates a flowchart of the cloud phone file distribution method based on object storage and debugging bridge according to the present invention.

[0024] Specifically, this invention provides a cloud phone file distribution system based on object storage and a debugging bridge, including an object storage module, a control platform module, a cloud phone agent module, and a storage mounting module. These modules work collaboratively to complete file distribution and sharing functions. The characteristics of each module and the division of labor and collaboration between them will be described in detail below.

[0025] The object storage module uses enterprise-grade object storage services (such as S3 and OSS) to provide highly reliable and persistent object storage buckets for files in the cloud platform. These buckets are independent of the lifecycle of the cloud phone instance, ensuring that file data is not lost.

[0026] As the core control unit of the system, the control platform module provides standardized REST API interfaces (such as POST / resources / instance / fileupload), receives user file distribution and installation requests, generates lightweight control commands, and sends them to the target cloud phone instance through the ADB channel, without directly transmitting file data to avoid bandwidth waste.

[0027] The cloud phone agent module is deployed in each cloud phone instance, responsible for communicating with the control platform module, receiving control commands, and performing file download, storage, installation, and data writing operations to ensure accurate execution of commands. It should be noted that the cloud phone agent module provided in this invention can fully utilize the built-in ADB daemon of the cloud phone instance for communication, so even if the cloud phone does not have a public IP address, distribution can be completed as long as the ADB channel is open.

[0028] The storage mounting module uses a two-level mounting mechanism of "host mounting + instance mapping" to map the object storage bucket to the local shared directory ( / sdcard / shared) of all cloud phone instances, thereby enabling the underlying storage to be interconnected and providing a foundation for real-time sharing.

[0029] It should be noted that in the storage mounting module, by combining the backend object storage strategy and using traffic control tools such as tc / netem on the host machine to mark and limit the bandwidth of the mounted directory, the total bandwidth of shared files can be precisely controlled, avoiding sudden I / O from affecting the network performance of other instances on the host machine.

[0030] Furthermore, this system can also achieve permission isolation. Specifically, it can utilize the object storage bucket policy, the IAM sub-account system, or the directory-level POSIX ACL at the host mounting level to allocate mutually isolated shared directories for different tenants or business groups, ensuring data security.

[0031] Based on the above system, the present invention also provides a corresponding file distribution method, including a shared storage mounting process, an API file push process, and a cross-instance data real-time sharing method, which will be described in detail below.

[0032] The first step is to mount the shared storage. This step is a system-level initialization operation that lays the foundation for cross-instance sharing.

[0033] In this step, the first step is to open a storage bucket. In the cloud platform, a storage bucket of the object storage module is opened to store shared files and distribute files.

[0034] Subsequently, the storage bucket is mounted on the host machine using file system plugins such as CSI or S3FS, making it a local directory on all physical host machines (e.g., / mnt / shared).

[0035] Then, instance mapping is performed. When any cloud phone instance starts, the system uses a network protocol (e.g., virtio-9p or NFS) to map the host machine's local directory to the shared directory ( / sdcard / shared) of the Android system inside the cloud phone instance. At this point, the shared directory ( / sdcard / shared) of all cloud phone instances points to the same object storage bucket, achieving underlying storage connectivity.

[0036] The next step is API file push. This process is suitable for scenarios where files (such as APKs) are distributed in batches to multiple cloud phone instances from external sources.

[0037] In this step, the first step is to upload the file and obtain the URL. The user uploads the file to be distributed (such as test.apk) to the object storage module or an accessible web server and obtains the file's URL and MD5 value.

[0038] Then, an API call is made. Specifically, the user requests to call the API interface of the control platform module (POST / resources / instance / fileupload interface). The request content includes, for example, a list of target cloud phone instance numbers, file URLs, file names, MD5 values, and sets the autoInstall parameter as needed (1 indicates automatic installation, 0 indicates download only).

[0039] Then, the command is issued. After the control platform module receives the request content, it sends a download command (including the file URL and storage path, such as / sdcard / Download / ) to the agent module of each target cloud phone instance. This command is transmitted through the ADB channel and is only lightweight data, which does not consume a lot of bandwidth.

[0040] Then, the file download proceeds. After receiving the instruction, each cloud phone agent module independently downloads the file from the file URL and stores it in the specified path. The file data traffic is distributed to each cloud phone instance, avoiding bandwidth pressure on the central server.

[0041] Optionally, automatic installation can also be performed. If the autoInstall parameter is 1, the control platform module sends installation commands (such as pm install / sdcard / Download / test.apk) to each instance through the ADB channel, triggering automatic file installation.

[0042] In this step, the final result feedback is provided. After all instances have completed their operations, the control platform module provides feedback on the execution results (success / failure status) to the user.

[0043] Next, we will proceed to the step of real-time data sharing across instances. This step is suitable for scenarios involving real-time data collaboration between cloud phone instances.

[0044] In this step, the data is written first. After the business program of cloud phone instance A generates a data file (such as report.csv), it writes it to its own shared directory ( / sdcard / shared).

[0045] Next, transparent persistence is ensured. Specifically, through the underlying mechanism of the storage mount module, the operation of writing to the shared ( / sdcard / shared) directory is transparently converted into an upload operation to the object storage module, and the file is persisted to the storage bucket in real time.

[0046] Subsequently, data reading is performed. The business programs of cloud phone instance B (which can be more than one cloud phone instance, or cloud phone instances C and D can be added at the same time) other than cloud phone instance A can directly access their respective shared ( / sdcard / shared) directories to read the data file. This read operation is transparently converted into a download operation from the object storage module, realizing real-time data sharing.

[0047] To make the technical solution of the present invention clearer and easier to understand, the present invention will be described in detail below with reference to specific embodiments.

[0048] First, we introduce the first embodiment 1, which performs batch distribution of APKs and automatic installation. It should be noted that the specific numbers, protocols, and directory names mentioned in the following specific embodiments are merely examples and do not constitute a limitation of the present invention.

[0049] This embodiment addresses a scenario where an administrator distributes test.apk to 100 cloud phones in batches and installs it automatically. The following operations are performed in this scenario.

[0050] First, system initialization is performed. After the shared storage mounting process is completed, the shared directories of 100 cloud phone instances are all mapped to the same object storage bucket (OSS type). The host machine mounts the storage bucket to the shared directory through the S3FS plugin, and the instances complete the mapping through the virtio-9p protocol.

[0051] Next, the file is uploaded. The administrator uploads test.apk (50MB in size) to the object storage module of this system and obtains the file URL, for example, https: / / oss.example.com / files / test.apk. The MD5 value of the file is calculated to be "e10adc3949ba59abbe56e057f20f883e".

[0052] Then, an API call is made. The administrator sends a request in JSON format to programmatically call the POST / resources / instance / fileupload interface of the control platform module. The request sets relevant specific parameters, which are reflected in the JSON file.

[0053] Command issuance: After receiving the request, the control platform module sends a download command to the agent modules of 100 cloud phone instances through the ADB channel: "Download the file from https: / / oss.example.com / files / test.apk and store it in the / sdcard / Download / directory". The data size of this command is only about 100 bytes.

[0054] Then, the file download proceeds. After receiving the instruction, the agent modules of the 100 cloud phone instances independently download test.apk from the file URL. During the download process, the file data traffic is distributed to the network links of each instance. The control platform server only maintains instruction communication and does not transmit file data.

[0055] Then, automatic installation begins. After all instances have finished downloading, the control platform module detects that autoInstall=1 and sends the installation command "pm install / sdcard / Download / test.apk" to each instance via the ADB channel.

[0056] Finally, the results were reported. Within 10 seconds, all 100 cloud phones had completed the download and installation of test.apk, and the control platform module returned a successful execution result to the administrator for all instances.

[0057] In this embodiment, the traditional solution requires the central server to repeatedly transmit a large amount of data, while the present invention only transmits a few KB of control data, which greatly improves efficiency and effectively avoids bandwidth congestion of the central server.

[0058] This concludes the basic introduction of the present invention. As can be seen from the above description, the present invention effectively overcomes many defects of the prior art, and compared with the prior art, the present invention achieves many beneficial effects.

[0059] This invention achieves extreme efficiency by adopting a "upload once, available everywhere" model. Files only need to be uploaded once, and all cloud phone instances can access them in milliseconds, eliminating bandwidth waste and time delays caused by N repeated transmissions.

[0060] This invention also enables real-time sharing; data written by cloud phone instances to the shared directory is persisted in real time and visible to all instances, supporting cross-instance data collaborative processing. Furthermore, it achieves high reliability and persistence; files are stored in enterprise-grade object storage, unaffected by the lifecycle of a single cloud phone instance, and can automatically access the latest files when an offline instance comes back online.

[0061] Furthermore, this invention can also achieve automated management, provide a standardized REST API interface, support programmatic file uploading, distribution, and automatic installation, and facilitate integration with existing automated business processes.

[0062] In summary, this invention, through the innovative combination of object storage and debug bridge technology, constructs an efficient, reliable, and easily manageable cloud phone file distribution and sharing system and method, overcoming many shortcomings of traditional solutions. This invention supports large-scale batch file distribution, real-time cross-instance data collaboration, and other scenarios, making it suitable for various cloud phone applications such as automated testing and mobile office, and possessing broad application prospects and practical value.

[0063] The above description is merely an exemplary embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A cloud phone file distribution method based on object storage and debug bridge, characterized in that, The method includes the following steps: Shared storage mounting steps: Activate a storage bucket in the object storage module in the cloud platform to store shared files and files to be distributed; mount the storage bucket as a local directory of at least one physical host machine through the file system plugin; when any cloud phone instance starts, map the local directory of the host machine to the shared directory inside the cloud phone instance through the file system sharing protocol. At this time, the shared directories of all cloud phone instances point to the same object storage bucket. File push steps: Upload the file to be distributed to the object storage module and obtain the URL value of the file to be distributed; based on the request content, request and call the API interface of the control platform module; after receiving the request content, the control platform module sends a download instruction to the proxy module of each target cloud phone instance, which is transmitted through the ADB channel; after receiving the instruction, each cloud phone proxy module independently downloads the file from the file URL corresponding to the URL value and stores it to the specified path; after all cloud phone instances complete the operation, the control platform module provides feedback on the execution result to the user. The steps for real-time data sharing across instances are as follows: First, data is written to cloud phone instance A. After the business application of cloud phone instance A generates a data file, it writes it to its own shared directory. Through the underlying mechanism of the storage mounting module, the operation of writing to the shared directory is transparently converted into an upload operation to the object storage module, and the file is persisted to the storage bucket in real time. The business application of cloud phone instance B directly accesses the shared directory of cloud phone instance A.

2. The method according to claim 1, characterized in that, The request content includes a list of target cloud phone instance IDs, file URLs, file names, MD5 values, and sets the autoInstall parameter.

3. The method according to claim 2, characterized in that, The request also includes an installation control identifier, which indicates whether the cloud phone agent module should perform an automatic installation operation after the download is complete.

4. The method according to claim 2, characterized in that, autoInstall=1 means automatic installation, while autoInstall=0 means only downloading.

5. The method according to claim 4, characterized in that, If autoInstall=1, the control platform module sends installation commands to each instance via the ADB channel, triggering automatic file installation.

6. The method according to claim 1, characterized in that, In the real-time data sharing process across instances, the business applications of cloud phone instances C and D, which are different from cloud phone instances A and B, also directly access the shared directory of cloud phone instance A.

7. The method according to claim 1, characterized in that, The storage mounting module uses a two-level mounting mechanism of "host mounting + instance mapping" to map the object storage bucket to the local shared directory of all cloud phone instances, thereby enabling the underlying storage to be interconnected and providing a foundation for real-time sharing.

8. The method according to claim 1, characterized in that, On the host machine, traffic control tools are used to mark and limit the bandwidth of the local directories formed by the mount, in order to control the total bandwidth of shared files.

9. A cloud mobile phone file distribution system based on object storage and debug bridge, used to perform the method according to any one of claims 1-8.

Images