Detailed Description
Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which various details of the embodiments of the disclosure are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
Fig. 1 illustrates an exemplary system architecture 100 to which embodiments of the file transfer method or file transfer apparatus of the present disclosure may be applied.
As shown in fig. 1, the system architecture 100 may include clients 101, 102, 103, a network 104, a server 105, and a cloud handset 106. The network 104 is the medium used to provide communication links between the clients 101, 102, 103 and the server 105, and the medium used to provide communication links between the server 105 and the cloud handset 106. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
Users can interact with cloud handsets 106 through network 104 and server 105 using clients 101, 102, 103 to transfer files, and the like. Various client applications, such as a cloud handset connection application, etc., may be installed on the clients 101, 102, 103.
The clients 101, 102, 103 may be hardware or software. When the clients 101, 102, 103 are hardware, they may be various electronic devices including, but not limited to, smart phones, tablet computers, laptop portable computers, desktop computers, and the like. When the clients 101, 102, 103 are software, they may be installed in the electronic devices described above. It may be implemented as multiple pieces of software or software modules, or as a single piece of software or software module. And is not particularly limited herein.
The server 105 may provide various file delivery-based services. For example, the server 105 may store a file transmission instruction acquired from the cloud mobile phone 106 and transmit the file transmission instruction to the clients 101, 102, and 103, or may store a target file acquired from the clients 101, 102, and 103 and transmit the target file to the cloud mobile phone 106.
The server 105 may be hardware or software. When the server 105 is hardware, it may be implemented as a distributed server cluster composed of a plurality of servers, or may be implemented as a single server. When the server 105 is software, it may be implemented as multiple pieces of software or software modules (e.g., to provide distributed services), or as a single piece of software or software module. And is not particularly limited herein.
It should be noted that the file transmission method provided by the embodiment of the present disclosure may be executed by the clients 101, 102, and 103, or may be executed by the cloud mobile phone 106, and accordingly, the file transmission apparatus may be disposed in the clients 101, 102, and 103, or in the cloud mobile phone 106.
It should be understood that the number of clients, networks, servers, and cloud handsets in fig. 1 is merely illustrative. There may be any number of clients, networks, and servers, as desired for an implementation.
With continued reference to FIG. 2, a flow 200 of one embodiment of a file transfer method according to the present disclosure is shown. The file transmission method comprises the following steps:
step 201, obtaining a target file to be sent.
In this embodiment, an execution subject of the file transfer method (for example, the clients 101, 102, 103 shown in fig. 1) may obtain a target file to be sent. The target file to be sent is the target file to be sent to the cloud mobile phone. The target file may be a text file, a picture, an audio file, or a video file, which is not limited in this disclosure. One or more files can be selected from a file list in the client as target files to be sent, illustratively, the target files are pictures, a picture list in the client can be read, one or more pictures can be randomly selected from the picture list as pictures to be sent, one or more pictures with the same target object in the pictures can be selected from the picture list as pictures to be sent, and the method is not limited in the disclosure.
Step 202, sending the target file to a local interactive development kit.
In this embodiment, after acquiring the target file, the execution subject may send the target file to a local interactive development kit. The interactive development kit is integrated in the client and interacts with the server, and can transmit files in the client to the server and receive files sent by the server. After the client acquires the target file, the target file can be sent to an interactive development kit in the client, so that the target file can be further sent to the server by using the interactive development kit. Specifically, after the target file is obtained, a file transmission request may be sent to the interactive development kit, and after the feedback of the interactive development kit is received, the target file is transmitted to the interactive development kit through an interface of the interactive development kit.
Step 203, sending the target file to a server through the interactive development kit, so that the server sends the target file to the cloud mobile phone.
In this embodiment, after sending the target file to the local interactive development kit, the execution subject may send the target file to the server through the interactive development kit. Specifically, a storage address in the server may be preset, a file transmission request is sent to the server, and after receiving feedback from the server, a target file in the interactive development kit is sent to the preset storage address in the server through an interface of the interactive development kit, so that the server can further send the target file to the cloud mobile phone. The cloud mobile phone is a virtual mobile phone with complete functions of a real mobile phone, the cloud mobile phone is a virtual server and has no entity, the cloud mobile phone can run in a client, a cloud mobile phone list is arranged in the client, one cloud mobile phone can be randomly selected from the cloud mobile phone list, a preset default cloud mobile phone can also be selected, and a file is transmitted to the selected cloud mobile phone, which is not limited by the disclosure.
According to the file transmission method provided by the embodiment of the disclosure, the target file to be transmitted is firstly acquired, then the target file is transmitted to the local interactive development kit, and finally the target file is transmitted to the server through the interactive development kit, so that the server transmits the target file to the cloud mobile phone. The file transmission complexity between the client and the cloud mobile phone is reduced, and the file transmission between the client and the cloud mobile phone is simpler, more convenient and faster.
With further continued reference to fig. 3, a flow 300 of another embodiment of a file transfer method according to the present disclosure is shown. The file transmission method comprises the following steps:
step 301, obtaining a target file to be sent.
In this embodiment, the specific operation of step 301 has been described in detail in step 201 in the embodiment shown in fig. 2, and is not described herein again.
Step 302, obtaining the file size of the target file.
In this embodiment, the execution subject may obtain the file size of the target file after obtaining the target file. The associated attribute table of the target file can be obtained, the file size of the target file can be extracted from the associated attribute table, and the file size of the target file can also be obtained through calculation. For example, the target file is a picture, an attribute list associated with the target picture may be read, a picture size attribute is extracted from the attribute list, a numerical value corresponding to the picture size attribute is read as the picture size of the target picture, a product of a resolution of the target picture and a size of each pixel point may also be obtained from the attribute list, and the product of the resolution and the size of each pixel point is used as the picture size of the target picture, which is not limited in this disclosure.
Step 303, in response to that the file size of the target file is larger than the file threshold, dividing the target file into a plurality of subfiles, and sending the plurality of subfiles to the interactive development kit in a file stream manner.
In this embodiment, after acquiring the file size of the target file, the execution main body may compare the file size of the target file with a file threshold. The file threshold is a preset fixed value, the target file is a picture, and the preset picture threshold is 1M.
In response to the file size of the target file being greater than the file threshold, the target file is divided into a plurality of subfiles, wherein the file size of each subfile is less than the file threshold. The file may be partitioned based on file content, one subfile per partition, the file size of the partitioned subfile compared to a file threshold, and if the file size of the partitioned subfile is less than the file threshold, the subfile is eligible, the next subfile is continued to be divided, if the file size of the divided subfile is larger than the file threshold, the sub-file is not qualified and needs to be re-divided, and illustratively, the target file is a picture, a picture threshold is preset to be 1M, the division is performed based on a target object in the picture, for example, each target object in the picture is separately divided, if the size of the sub-picture containing one target object is larger than 1M, and if the size of the sub-picture containing a target object is smaller than 1M, the sub-picture is qualified, and the next sub-picture is continuously divided from the original picture. Or, the calculation may be performed based on the file size of the target file, and the target file is averagely divided into N parts of sub-files, where N is a natural number, so that the file size of each part of sub-file is smaller than the file threshold, which is not limited in this disclosure.
After the target file is divided into a plurality of subfiles, the plurality of subfiles are sent to the interactive development toolkit in a file flow mode. The file stream is to convert the file into a binary stream, specifically, each subfile may be converted into byte data, the byte data may be converted into a binary system, the binary system is displayed in a form of a character string, and the plurality of subfiles are sent to the interactive development kit through an interface of the interactive development kit in a file stream manner.
And responding to the fact that the file size of the target file is smaller than the file threshold value, converting the target file into a file stream mode, and sending the file stream mode to the interactive development toolkit through an interface of the interactive development toolkit.
And step 304, sending the plurality of sub-files from the interactive development toolkit to a server in a file flow mode, so that the server sends the target file to the cloud mobile phone.
In this embodiment, the execution agent may send a plurality of subfiles from the interactive development kit to the server in a file stream manner. If the file size of the target file is larger than the file threshold, the interactive development kit can send the plurality of subfiles to the server in a file stream mode after receiving the plurality of subfiles, and if the file size of the target file is smaller than the file threshold, the interactive development kit can send the target file to the server in a file stream mode after receiving the target file, so that the target file is stored in the server, and the target file can be further sent to the cloud mobile phone.
As can be seen from fig. 3, compared with the embodiment corresponding to fig. 2, in the file transmission method in this embodiment, after the target file is obtained, the file size of the target file is first compared with the file threshold, if the file size of the target file is greater than the file threshold, the target file is divided into a plurality of subfiles, and the subfiles are sent to the interactive development kit and further sent to the server, so that the efficiency of file transmission is improved.
With further continued reference to fig. 4, a flow 400 of yet another embodiment of a file transfer method according to the present disclosure is shown. The file transmission method comprises the following steps:
step 401, receiving a file sending instruction through an interactive development kit.
In this embodiment, the execution subject may receive the file sending instruction through the interactive development kit. The file sending instruction is an instruction for indicating to send a file, and may include a file name to be sent or a description of the file to be sent, and a designated location to be sent. Specifically, the file sending instruction sent by the server can be received through an interface of the interactive development kit.
Step 402, determining a target file to be sent based on a file sending instruction.
In this embodiment, after receiving the file sending instruction, the execution main body may determine the target file to be sent based on the file sending instruction. Specifically, a file list in the client may be called, attribute information of each file in the file list is read, the indication information in the file sending instruction is compared with the attribute information of each file, and a file with the indication information and the attribute information matched in a consistent manner is determined as the target file to be sent. Illustratively, the file sending instruction is a picture sending instruction, the picture sending instruction includes two pictures which need to be sent and are named as "peony" and "Chinese rose", a picture list in the client is called, attribute information of each picture in the picture list is read, and the picture with the name attribute of "peony" or "Chinese rose" in the attribute information is determined as a target picture to be sent.
And step 403, acquiring the file size of the target file.
Step 404, in response to the file size of the target file being larger than the file threshold, dividing the target file into a plurality of subfiles, and sending the plurality of subfiles to the interactive development kit in a file stream manner.
Step 405, sending the plurality of sub-files from the interactive development kit to a server in a file flow mode, so that the server sends the target file to the cloud mobile phone.
In the present embodiment, the specific operations of steps 403 and 405 have been described in detail in step 302 and 304 in the embodiment shown in fig. 3, and are not described herein again.
As can be seen from fig. 4, compared with the embodiment corresponding to fig. 3, the file transmission method in this embodiment determines the target file to be sent based on the file sending instruction, so that the sent target file is more accurate.
With further continued reference to fig. 5, a flow 500 of one embodiment of a file transfer method according to the present disclosure is shown. The file transmission method comprises the following steps:
step 501, receiving a target file sent by a server through a local remote processing program.
In this embodiment, an execution subject of the file transmission method (for example, the cloud mobile phone 106 shown in fig. 1) may receive the target file sent by the server through a local remote processing program. The remote processing program is a service in the cloud mobile phone and is responsible for function operation of the cloud mobile phone, and the remote processing program can transmit files in the cloud mobile phone to the server and also can receive the files sent by the server. Specifically, a long connection is kept between the remote processing program and the server, the cloud mobile phone can interact with the server through the remote processing program, the long connection is a concept corresponding to a short connection, the short connection means that a short connection is established when data interaction exists between two communication sides, the short connection is disconnected after the data transmission is completed, only one transmission task is completed by the short connection each time, the long connection means that a plurality of data packets can be transmitted on one connection, the long connection is kept between the remote processing program and the server, real-time file transmission can be kept, and file transmission efficiency is improved. The remote processing program can receive the target file sent by the server through the long connection.
Step 502, storing the target file in a designated location.
In this embodiment, after receiving the target file through the remote processing program, the cloud mobile phone may store the target file in a specified location. The target file can be stored in the address of the corresponding file list of the cloud mobile phone, so that the cloud mobile phone can directly call the target file from the file list and use the target file. After the target file is stored in the designated position, the remote processing program can call a kernel service in the cloud mobile phone, and the target file stored in the address of the corresponding file list is written into the clipboard, wherein the kernel service is a service responsible for calling a kernel interface. After the target file is written into the clipboard, the cloud mobile phone can directly paste the target file at any position.
As can be seen from fig. 5, in the file transmission method in this embodiment, the target file sent by the server may be received and stored by the remote processing program, so that the cloud mobile phone may more conveniently receive and utilize the target file, and meanwhile, the remote processing program and the server maintain a long connection therebetween, so that the file may be sent in real time, and the file transmission efficiency is improved.
With further continued reference to fig. 6, a flow 600 of another embodiment of a file transfer method according to the present disclosure is shown. The file transmission method comprises the following steps:
step 601, generating a file sending instruction.
In this embodiment, the cloud phone may generate a file sending instruction. The file sending instruction is an instruction for instructing to send a file, and the file sending instruction may include a name of the file to be sent or a description of the file to be sent, and a designated location to be sent. Specifically, the file sending instruction may be generated when a file sending request is detected, and for example, when a picture named "peony" in the call picture list is detected and a search result of the picture is empty, a request for sending the picture named "peony" is generated, and accordingly, a picture sending instruction for sending the picture named "peony" is generated.
Step 602, sending the file sending instruction to the remote processing program.
In this embodiment, after generating the file sending instruction, the cloud mobile phone may send the file sending instruction to the remote processing program. After the file sending instruction is generated, the cloud mobile phone can firstly send the file sending instruction to the remote processing program, so that the file sending instruction can be further sent to the server by using the remote processing program. Specifically, after the file sending instruction is generated, a request for transmitting the instruction may be sent to the remote processing program, and after the feedback of the remote processing program is received, the file sending instruction may be transmitted to the remote processing program through an interface of the remote processing program.
Step 603, sending the file sending instruction to the server through the remote processing program, so that the server sends the file sending instruction to the client.
In this embodiment, the cloud mobile phone may send the file sending instruction to the server through the remote processing program. After receiving the file sending instruction, the remote processing program can send the file sending instruction to the server through long connection, so that the server stores the file sending instruction, and then sends the file sending instruction to the client.
And step 604, receiving the target file sent by the server through a local remote processing program.
Step 605, storing the target file in the designated position.
In the present embodiment, the specific operations of step 604-.
As can be seen from fig. 6, the file transmission method in this embodiment may generate a file sending instruction, send the file sending instruction to a local remote processing program, and finally send the file sending instruction to the server through the remote processing program, so that the server sends the file sending instruction to the client, and the transmitted target file may be more accurate.
With further reference to fig. 7, a flow 700 of one embodiment of a file transfer method according to the present disclosure is shown. The file transmission method comprises the following steps:
step 701, the client determines a target file to be sent, sends the target file to a local interactive development kit, and sends the target file to the server through the interactive development kit.
In this embodiment, the target file to be sent is a target file to be sent to the cloud mobile phone. The target file may be a text file, a picture, an audio file, or a video file, which is not limited in this disclosure. The client may randomly select one or more files from a local file list as target files to be sent, or may select one or more files with similar file contents as target files to be sent based on file contents, which is not limited in this disclosure. The interactive development kit is integrated in the client side and interacts with the server, the client side can send a file transmission request to the interactive development kit, after feedback of the interactive development kit is received, a target file is transmitted to the interactive development kit through an interface of the interactive development kit, then the file transmission request is sent to the server, and after the feedback of the server is received, the target file in the interactive development kit is sent to a preset storage address in the server through the interface of the interactive development kit.
Step 702, the server receives and stores the target file sent by the client through the interactive development kit, and sends the target file to a remote processing program of the cloud mobile phone.
In this embodiment, the server is permanently connected to the remote processing program in the cloud mobile phone, and the server may also receive, through the interface of the interactive development kit, the target file sent by the client through the interactive development kit, store the target file in the server, and then send the target file to the remote processing program in the cloud mobile phone through the permanent connection.
And 703, receiving the target file sent by the server through the remote processing program by the cloud mobile phone, and storing the target file at a specified position.
In this embodiment, the remote processing program in the cloud mobile phone may receive the target file sent by the server through the long connection, store the target file in the address of the corresponding file list of the cloud mobile phone, and then call the kernel service in the cloud mobile phone, write the target file stored in the address of the corresponding file list into the clipboard, and after writing the target file into the clipboard, the cloud mobile phone may directly paste the target file at any position.
As can be seen from fig. 7, the file transmission method in this embodiment can implement file transmission among the client, the server, and the cloud mobile phone, reduce the complexity of file transmission between the client and the cloud mobile phone, and make file transmission between the client and the cloud mobile phone simpler, faster, and more convenient.
With further continued reference to fig. 8, a flow 800 of another embodiment of a file transfer method according to the present disclosure is shown. The file transmission method comprises the following steps:
step 801, the cloud mobile phone generates a file sending instruction, sends the file sending instruction to a local remote processing program, and sends the file sending instruction to a server through the remote processing program.
In this embodiment, the cloud mobile phone may generate a file sending instruction when detecting that there is a file sending request, where the file sending instruction is an instruction indicating to send a file, and the file sending instruction may include a name of the file to be sent or a description of the file to be sent, and a specified location to be sent. After the file sending instruction is generated, the cloud mobile phone can firstly send a request for transmitting the instruction to the remote processing program, after feedback of the remote processing program is received, the file sending instruction is transmitted to the remote processing program through an interface of the remote processing program, and after the remote processing program receives the file sending instruction, the file sending instruction can be sent to the server through long connection, so that the file sending instruction is stored in the server.
Step 802, the server receives and stores a file sending instruction sent by the cloud mobile phone through the remote processing program, and sends the file sending instruction to an interactive development kit of the client.
In this embodiment, the server may receive, through the long connection, a file sending instruction sent by the cloud mobile phone through the remote processing program, store the file sending instruction in the server, and then send the file sending instruction to the interactive development kit of the client through the interface of the interactive development kit.
Step 803, the client receives the file sending instruction through the local interactive development toolkit, and determines a target file to be sent based on the file sending instruction.
In this embodiment, the client may receive a file sending instruction sent by the server through an interface of the interactive development kit, call a file list in the client, read attribute information of each file in the file list, compare indication information in the file sending instruction with the attribute information of each file, and determine a file with the indication information and the attribute information matching in a consistent manner as a target file to be sent.
And step 804, the client determines a target file to be sent, sends the target file to a local interactive development kit, and sends the target file to the server through the interactive development kit.
Step 805, the server receives and stores the target file sent by the client through the interactive development kit, and sends the target file to the remote processing program of the cloud mobile phone.
Step 806, the cloud mobile phone receives the target file sent by the server through the remote processing program, and stores the target file in the designated position.
In the present embodiment, the specific operations of steps 804-806 are described in detail in step 701-703 in the embodiment shown in fig. 7, and are not described herein again.
As can be seen from fig. 8, in the file transmission method in this embodiment, a file sending instruction may be generated in the cloud mobile phone, the file sending instruction is sent to the client through the server, and the client determines and sends the target file based on the received file sending instruction, so that the sent target file is more accurate.
With further reference to fig. 9, as an implementation of the above file transmission method, the present disclosure provides an embodiment of a file transmission apparatus, which corresponds to the method embodiment shown in fig. 2, and which may be applied in various electronic devices.
As shown in fig. 9, the file transfer apparatus 900 of the present embodiment may include an obtaining module 901, a first sending module 902, and a second sending module 903. The acquiring module 901 is configured to acquire a target file to be sent; a first sending module 902 configured to send the target file to a local interactive development kit; the second sending module 903 is configured to send the target file to the server through the interactive development kit, so that the server sends the target file to the cloud mobile phone.
In the present embodiment, the file transfer apparatus 900: the specific processing of the obtaining module 901, the first sending module 902, and the second sending module 903 and the technical effects thereof can refer to the related descriptions of step 201 and step 203 in the corresponding embodiment of fig. 2, which are not described herein again.
In some optional implementations of this embodiment, the first sending module 902 includes: an acquisition submodule configured to acquire a file size of a target file; and the first sending sub-module is configured to divide the target file into a plurality of sub-files and send the plurality of sub-files to the interactive development toolkit in a file flow mode in response to the file size of the target file being larger than the file threshold.
In some optional implementations of this embodiment, the second sending module 903: and the second sending submodule is configured to send the plurality of subfiles from the interactive development kit to the server in a file flow mode.
In some optional implementations of this embodiment, the obtaining module 901 includes: the receiving submodule is configured to receive a file sending instruction through the interactive development kit; and the determining submodule is configured to determine a target file to be sent based on the file sending instruction.
With further reference to fig. 10, as an implementation of the above file transmission method, the present disclosure provides an embodiment of a file transmission apparatus, which corresponds to the method embodiment shown in fig. 5, and which may be applied in various electronic devices.
As shown in fig. 10, the file transmission device 1000 of the present embodiment may include a receiving module 1001 and a storing module 1002. The receiving module 1001 is configured to receive a target file sent by a server through a local remote processing program; a storage module 1002 configured to store the target file at a specified location.
In the present embodiment, the file transfer apparatus 1000: the detailed processing of the receiving module 1001 and the storing module 1002 and the technical effects thereof can refer to the related descriptions of step 501 and step 502 in the corresponding embodiment of fig. 5, which are not repeated herein.
In some optional implementations of this embodiment, the file transmission apparatus 1000 further includes: the generation submodule is configured to generate a file sending instruction; the third sending submodule is configured to send the file sending instruction to the local remote processing program; and the fourth sending submodule is configured to send the file sending instruction to the server through the remote processing program so as to enable the server to send the file sending instruction to the client.
With further reference to fig. 11, as an implementation of the above file method, the present disclosure provides an embodiment of a file transmission system, which corresponds to the method embodiment shown in fig. 7, and which can be applied to various electronic devices.
As shown in fig. 11, the file transfer system 1100 of the present embodiment may include a client 1101, a server 1102, and a cloud cell phone 1103. The client 1101 is configured to determine a target file to be sent, send the target file to a local interactive development kit, and send the target file to the server through the interactive development kit; the server 1102 is configured to receive and store a target file sent by the client through the interactive development kit, and send the target file to a remote processing program of the cloud mobile phone; the cloud cell phone 1103 is configured to receive the target file sent by the server through the remote processing program and store the target file in a designated location.
In this embodiment, the file transfer system 1100: the specific processing of the client 1101, the server 1102 and the cloud cell phone 1103 and the technical effects thereof can refer to the related description of step 701 and step 703 in the corresponding embodiment of fig. 7, which is not repeated herein.
The present disclosure also provides an electronic device, a readable storage medium, and a computer program product according to embodiments of the present disclosure.
FIG. 12 shows a schematic block diagram of an example electronic device 1200, which can be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the disclosure described and/or claimed herein.
As shown in fig. 12, the apparatus 1200 includes a computing unit 1201 which can perform various appropriate actions and processes in accordance with a computer program stored in a Read Only Memory (ROM)1202 or a computer program loaded from a storage unit 1208 into a Random Access Memory (RAM) 1203. In the RAM 1203, various programs and data required for the operation of the device 1200 may also be stored. The computing unit 1201, the ROM 1202, and the RAM 1203 are connected to each other by a bus 1204. An input/output (I/O) interface 1205 is also connected to bus 1204.
Various components in the device 1200 are connected to the I/O interface 1205 including: an input unit 1206 such as a keyboard, a mouse, or the like; an output unit 1207 such as various types of displays, speakers, and the like; a storage unit 1208, such as a magnetic disk, optical disk, or the like; and a communication unit 1209 such as a network card, modem, wireless communication transceiver, etc. The communication unit 1209 allows the device 1200 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunication networks.
The computing unit 1201 may be a variety of general purpose and/or special purpose processing components having processing and computing capabilities. Some examples of the computing unit 1201 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, and so forth. The computing unit 1201 executes the above-described methods and processes, such as a method of acquiring a target file to be transmitted and transmitting the target file to a server, or a method of receiving and storing the target file. For example, in some embodiments, the file transfer method may be implemented as a computer software program tangibly embodied in a machine-readable medium, such as storage unit 1208. In some embodiments, part or all of the computer program may be loaded and/or installed onto the device 1200 via the ROM 1202 and/or the communication unit 1209. When the computer program is loaded into the RAM 1203 and executed by the computing unit 1201, one or more steps of the above-described method of acquiring an object file to be transmitted and transmitting the object file into a server, or a method of receiving and storing the object file may be performed. Alternatively, in other embodiments, the computing unit 1201 may be configured by any other suitable means (e.g., by means of firmware) to perform a method of acquiring a target file to be sent and sending the target file into a server, or a method of receiving and storing the target file.
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.
The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server may be a server of a distributed system or a server incorporating a blockchain. The server can also be a cloud server, or an intelligent cloud computing server or an intelligent cloud host with artificial intelligence technology. The server may be a server of a distributed system or a server incorporating a blockchain. The server can also be a cloud server, or an intelligent cloud computing server or an intelligent cloud host with artificial intelligence technology.
It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present disclosure may be executed in parallel, sequentially, or in different orders, as long as the desired results of the technical solutions disclosed in the present disclosure can be achieved, and the present disclosure is not limited herein.
The above detailed description should not be construed as limiting the scope of the disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present disclosure should be included in the scope of protection of the present disclosure.