A method and device for realizing file intercommunication between Windows and andorid system platforms

Abstract

The application provides a method and device for realizing file mutual transmission between Windows and andorid system platforms, which comprises the following steps: binding a session generated by a Windows end with a MAC address of an andorid end; automatically starting a windows registry and registering software information on a system; starting a background process on a windows system desktop to listen to a file background uploading request; executing an uploading command after the uploading request is received; and notifying the andorid end to receive and process the file after the transmission is completed. The device realizes the above method.

Description

Technical Field

[0001] This invention relates to the field of communication between different computer operating systems, and in particular to a method and apparatus for file transfer between Windows and Android system platforms. Background Technology

[0002] With the improvement of bandwidth speed and the development of information technology, data file downloading has significant advantages in server, network, and cloud storage management. It can greatly reduce server pressure, improve user download experience, increase resource utilization, and improve maintenance efficiency. In related cloud technologies, cloud computing platforms are basically built on the Linux operating system. Currently, most clients of all-in-one machines (Android and Windows) use Android and Windows operating systems, which involves file transfer between two different operating systems. Although there are many file transfer methods between Android and Windows, such as FTP and Samba, most of these methods require setting up a server on Linux or using external storage such as USB drives, which is cumbersome. Furthermore, file transfer between different systems has certain technical limitations and requires complex security protocols. Deploying security protocols on large-scale cluster computers must cover technologies such as SSH2 and open necessary ports, leading to excessive workload and system insecurity. Summary of the Invention

[0003] The purpose of this invention is to address the problem of file transfer between Android and Windows by providing a method and apparatus for file transfer between Windows and Android system platforms, so as to achieve simple, secure and stable cross-operating system file transfer between Windows and Android system platforms.

[0004] The technical solution of this invention to achieve its technical objective is: a method for file transfer between Windows and Android system platforms, comprising the following steps:

[0005] S1. Bind the session generated on the Windows side to the MAC address on the Android side;

[0006] S2. Enable auto-start and register software information on the system in the Windows Registry;

[0007] S3. Start a background process on the Windows system desktop to listen for background file upload requests;

[0008] S4. When the Windows system detects a file upload request, it executes the upload command.

[0009] The upload commands include:

[0010] S41. The Windows system determines whether a file is selected. If a file is selected, proceed to step S42; otherwise, end the process.

[0011] S42. The Windows system determines whether the cursor has moved to the specified area. If the cursor has moved to the specified area, proceed to step S43; otherwise, end the process.

[0012] S43, the Windows system uploads the transferred files to the OSS service;

[0013] S44: The Windows system notifies the Android system to download files from the OSS service.

[0014] Furthermore, in the above methods for implementing file transfer between Windows and Android system platforms:

[0015] In step S1, shell programming techniques are used to process user operations using Windows middleware and Hook messages.

[0016] Furthermore, in the above method for implementing file transfer between Windows and Android system platforms: in step S4, when a user needs to upload a file, the user operation information includes: selecting the file, right-clicking and selecting the program upload option, and dragging the mouse to the screen boundary.

[0017] Furthermore, in the above method for implementing file transfer between Windows and Android system platforms, the execution of the upload command includes: performing file size prediction; if the file size is greater than 50MB, then performing chunked upload; otherwise, performing single file upload directly.

[0018] Furthermore, in the above method for file transfer between Windows and Android system platforms: chunked uploads are processed using Alibaba Cloud computing.

[0019] Furthermore, the above-mentioned method for implementing file transfer between Windows and Android system platforms also includes: S6, deleting cloud files 30 seconds after sending and receiving requests, and releasing Windows system cache.

[0020] The present invention also includes an apparatus for enabling file transfer between Windows and Android system platforms, comprising a host computer with both Windows and Android systems installed; and further comprising:

[0021] A module that binds the Windows-generated session to the Android MAC address;

[0022] The module that performs automatic startup and registers software information on the system in the Windows Registry;

[0023] A module that starts a background process on the Windows system desktop to listen for background file upload requests;

[0024] The module that executes the upload command;

[0025] Notify the Android module to receive and process the data.

[0026] Furthermore, in the aforementioned device, the module that binds the Windows-generated session to the Android MAC address utilizes shell programming techniques, relying on Windows middleware and Hook messages to process user operations.

[0027] This invention provides a file transfer method and apparatus that enables simple, secure, and stable file transfer between Windows and Android system platforms across operating systems.

[0028] This invention solves the problems of cumbersome cross-operating system file transfer and poor user experience between Windows and Android. It achieves simple, secure, and stable cross-operating system file transfer between Windows and Android cloud computing platforms, and enhances the user experience. Specifically, it uses Alibaba Cloud technology to manage and control the maximum upload speed, which can adapt to different local Windows operating systems and match the bandwidth that the local Windows network card can handle, forming a stable and efficient transmission link and improving the flexibility to adapt to corresponding services.

[0029] This reduces the use of external storage devices such as USB flash drives.

[0030] It improves file transfer efficiency.

[0031] This ensures the security of the files.

[0032] This increases the operability of the dual-system setup.

[0033] This reduces unnecessary plugging and unplugging of the equipment's physical channels, increasing the equipment's lifespan.

[0034] The present invention will now be described in more detail with reference to the accompanying drawings and embodiments. Attached Figure Description

[0035] Appendix Figure 1This is a flowchart of the present invention;

[0036] Appendix Figure 2 This is a flowchart of Embodiment 1 of the present invention. Detailed Implementation

[0037] Example 1 Figure 1 and Figure 2 As shown: This embodiment provides a simple, secure, and stable file transfer method and apparatus for cross-operating system platforms, namely Windows and Android. The main objective is to provide a simple, secure, and stable file transfer method and apparatus for cross-operating system platforms, namely Windows and Android. In this embodiment, as... Figure 1 As shown, to achieve file transfer between Windows and Android system platforms, the following steps are included:

[0038] S1. Bind the session generated on the Windows side to the Android MAC address. This step involves opening a Windows application window containing two buttons: a bind button and an unbind button, as well as a MAC address input box. Enter the MAC address of the all-in-one device (Android) and click the bind button to bind it to the all-in-one device.

[0039] S2. After successful binding, the system automatically starts the application in the Windows registry and registers the software information on the system. It utilizes shell programming techniques, relying on Windows middleware and hook messages to handle user operations. During this step, the Linux server receives the binding request from Windows and performs a binding login in the background. This serves as the basis for subsequent direct data transmission. At this point, if the program is shut down, restarted, or restarted, a second binding is not required.

[0040] S3. A background process is started on the Windows desktop to listen for file upload requests. This background process is a Windows program with advantages such as no user interface, low resource consumption, and the ease of cleanup compared to Windows service programs. The all-in-one device (Android with the receiving service enabled) receives the Linux service message and waits for file reception processing. After successful binding, the Windows application registers program messages in the registry for startup and right-click event registration. After the registry data is entered, no further user interaction is required for right-clicking and dragging to the boundary.

[0041] S4. When a user selects a file, right-clicks, and chooses the program upload option, or drags the selected file to the screen boundary using the mouse (touch-selected file), the system receives the user's operation information and executes the multi-threaded upload command. When the user right-clicks and selects quick upload or drags the file to the boundary, the background application responds to the command and executes the upload command. The file path is passed in, and then the file stream is used to upload the file to OSS for temporary storage.

[0042] S5 performs file size prediction during file uploads. If the file size exceeds 50MB, it is uploaded in chunks; otherwise, it is uploaded as a single file. After stress testing with Alibaba Cloud OSS under varying bandwidth and OPS performance of the all-in-one machine, it was found that single file uploads under 50MB can respond to user operations more quickly. This takes network transmission speed into account.

[0043] S6, segmented upload, leverages Alibaba Cloud's cloud computing capabilities to maximize bandwidth upload processing using the maximum number of threads on the Windows system. Once the file arrives at the OSS temporary storage path, an upload process is initiated, receiving the command and downloading the file from the network path to the local machine. After uploading to OSS, a message is sent to the all-in-one device (Android terminal) informing it that the upload is complete. Upon receiving the message, the device then deletes the file from the OSS temporary storage, reducing OSS storage requirements.

[0044] S7. After the upload is complete, notify the Android client to receive and process the data. Send a shortened HTTPS request to the service program on the Linux server, which will then forward the request.

[0045] S8: Deletes cloud files and Windows system cache 30 seconds after sending / receiving requests to reduce program resource consumption.

[0046] In this embodiment, the file transfer method solves the problems of cumbersome cross-operating system file transfer and poor user experience between Windows and Android. It realizes simple, secure, and stable cross-operating system file transfer between Windows and Android cloud computing platforms, and enhances the user experience. Specifically, the use of Alibaba Cloud technology to perform maximum upload control for management of the transfer can adapt to different local Windows operating systems and match the bandwidth that the local Windows network card can handle, forming a stable and efficient transmission link and improving the flexibility to adapt to corresponding services.

[0047] 1. Reduced the use of external storage devices such as USB flash drives.

[0048] 2. Improved file transfer efficiency.

[0049] 3. Ensured the security of the files.

[0050] 4. Increased the operability of the dual system.

[0051] This reduces unnecessary plugging and unplugging of the equipment's physical channels, increasing the equipment's lifespan.

Claims

1. A method for enabling file transfer between Windows and Android system platforms, characterized in that: Includes the following steps: S1. Bind the session generated on the Windows side to the MAC address on the Android side; S2. Enable auto-start and register software information on the system in the Windows Registry; S3. Start a background process on the Windows system desktop to listen for background file upload requests; S4. When the Windows system detects a file upload request, it executes the upload command. The upload commands include: S41. The Windows system determines whether a file is selected. If a file is selected, proceed to step S42; otherwise, end the process. S42. The Windows system determines whether the cursor has moved to the specified area. If the cursor has moved to the specified area, proceed to step S43; otherwise, end the process. S43, the Windows system uploads the transferred files to the OSS service; S44: The Windows system notifies the Android system to download files from the OSS service.

2. The method for file transfer between Windows and Android system platforms according to claim 1, characterized in that: In step S1, shell programming techniques are used to process user operations using Windows middleware and Hook messages.

3. The method for file transfer between Windows and Android system platforms according to claim 1, characterized in that: In step S4, when a user needs to upload a file, the user operation information includes: selecting the file, right-clicking and selecting the program upload option, and dragging the mouse to the screen boundary.

4. The method for file transfer between Windows and Android system platforms according to claim 1, characterized in that: The upload command execution includes: performing file size prediction; if the file size is greater than 50MB, performing multi-file upload; otherwise, performing single file upload directly.

5. The method for file transfer between Windows and Android system platforms according to claim 4, characterized in that: Segmented uploads utilize Alibaba Cloud computing processing.

6. The method for file transfer between Windows and Android system platforms according to any one of claims 1 to 5, characterized in that: Also includes S6. Delete cloud files and release Windows system cache 30 seconds after sending the receive request.

7. An apparatus for enabling file transfer between Windows and Android system platforms, comprising a host computer with both Windows and Android systems installed; characterized in that: Also includes: A module that binds the Windows-generated session to the Android MAC address; The module that performs automatic startup and registers software information on the system in the Windows Registry; A module that starts a background process on the Windows system desktop to listen for background file upload requests; The module that executes the upload command; The module that executes the upload command includes: Determine whether to select a module with files; A module to determine whether the cursor has moved to a specified area; The module that uploads the transmitted files to the OSS service; Notify the Android module to receive and process the data.

8. The apparatus according to claim 7, characterized in that: In the module that binds the Windows-generated session to the Android MAC address, user operations are handled using shell programming techniques relying on Windows middleware and Hook messages.

Images