WO2015062494A1

WO2015062494A1 - Method and device for sdk uploading and downloading of a file

Info

Publication number: WO2015062494A1
Application number: PCT/CN2014/089765
Authority: WO
Inventors: 张劲辉
Original assignee: 北京奇虎科技有限公司; 奇智软件（北京）有限公司
Priority date: 2013-10-29
Filing date: 2014-10-29
Publication date: 2015-05-07

Abstract

The present invention provides a method and device for SDK uploading and downloading of a file, the SDK being used for a cloud storage system, and the method for SDK uploading of a file comprising: receiving a file upload command, obtaining information of the file to be uploaded, and uploading the uniform context of said file to be uploaded; by means of the application callback information class member variable which is set in the upload interface, invoking a plurality of file upload functions encapsulated in said upload interface, making said plurality of file upload functions be based on said information of the file to be uploaded, and using said uniform context to upload said file to be uploaded. The present invention significantly reduces difficulty for developers and raises the efficiency and quality of development, accelerates its speed, reduces its cost, and effectively prevents defects.

Description

Method and device for implementing file uploading and downloading by SDK

Technical field

The present invention relates to the field of communications technologies, and in particular, to a method and apparatus for uploading and downloading files based on an SDK (Software Development Kit) of an Android system.

Background technique

The SDK is a collection of development tools used by software engineers to create application software for specific software packages, software frameworks, hardware platforms, operating systems, etc. It can simply provide an API for an application programming language (Application Programming Interface). Some files of the programming interface, but may also include complex hardware that can communicate with an embedded system.

With the development of cloud storage technology, SDKs are increasingly being used to develop applications related to cloud storage. Through the functions of cluster application, grid technology, or distributed file system, cloud storage integrates a large number of different types of storage devices in the network through application software to jointly provide data storage and service access functions. Currently, the most common business access features provided by cloud storage include data uploading and downloading. When developers use the existing SDK to develop cloud storage upload tasks and download tasks, they not only need to be familiar with the implementation and functions of the interfaces of each SDK used for uploading and downloading, but also need to be familiar with the various tasks of uploading and downloading. And can correctly select the API interface used by each task link.

However, this kind of development method has higher requirements for developers, resulting in development difficulties, slow development speed, and high development cost. On the other hand, due to the inappropriate selection of API interfaces, the development tasks are inefficient and the defects are relatively poor. More, you need to continue to upgrade and improve the version.

Summary of the invention

In view of the above-mentioned existing SDK implementation file uploading, the development speed is slow, the development cost is high, the efficiency is low, and the defects are more. The present invention has been proposed to provide an SDK implementation file that overcomes the above problems or at least partially solves the above problems. Upload and download methods and devices.

According to an aspect of the present invention, a method for implementing file uploading by an SDK is provided, The SDK is applied to the cloud storage system, and the method includes: receiving a file uploading instruction, acquiring information of the file to be uploaded, and uploading a unified context of the file to be uploaded; and using a member of the application callback information class set in the upload interface. The variable, the plurality of file uploading functions encapsulated in the uploading interface are invoked, so that the plurality of file uploading functions use the unified context environment to upload the file to be uploaded according to the information of the file to be uploaded.

According to another aspect of the present invention, an apparatus for uploading a file by an SDK is provided. The SDK is applied to a cloud storage system, and the device includes: a first acquiring module, configured to receive a file uploading instruction, and obtain a file to be uploaded. And a unified context of uploading the file to be uploaded; and an uploading module, configured to invoke a plurality of file uploading functions encapsulated in the uploading interface by using a member variable in the application callback information class set in the uploading interface, so that The plurality of file uploading functions perform uploading of the file to be uploaded using the unified context environment according to the information of the file to be uploaded.

According to still another aspect of the present invention, a software development kit for implementing file downloading is provided, the software development kit being applied to a cloud storage system, the method comprising: receiving a file download instruction, where the file download instruction is Carrying the information of the file to be downloaded; acquiring the file to be downloaded from the cloud storage end according to the file downloading instruction and the information of the file to be downloaded, and obtaining a unified context for downloading the file to be downloaded; and downloading a member variable in the application callback information class set in the interface, calling a plurality of file download functions encapsulated in the download interface, so that the plurality of file download functions use the unified context environment to download the file to be downloaded .

According to still another aspect of the present invention, a device for downloading a file by a software development kit is provided, the software development kit being applied to a cloud storage system, the device comprising: a receiving module, configured to receive a file download instruction, The file downloading instruction carries the information of the file to be downloaded, and the second obtaining module is configured to obtain the file to be downloaded from the cloud storage end according to the file downloading instruction and the information of the file to be downloaded, and obtain the downloading station. Determining a unified context of the downloaded file; and downloading a module, by using a member variable in the application callback information class set in the download interface, calling a plurality of file download functions encapsulated in the download interface, so that the multiple The file download function performs downloading of the file to be downloaded using the unified context environment.

According to another aspect of the present invention, a computer program is provided, comprising computer readable code, when said computer readable code is run on a computing device, causing said computing device to execute said software development kit implementation file Upload and / or download methods.

According to still another aspect of the present invention, a computer readable medium storing a computer program as described above is provided.

In this application, the uploading interface and/or downloading interface of the SDK provides a good external cooperation mechanism, and the uploading interface and/or the downloading interface abstracts and encapsulates the method for uploading files and/or downloading files on the cloud storage end to generate Have member variables and multiple file upload functions and/or download functions in the application callback information class. When using the SDK for file uploading and/or downloading, obtain a unified context for uploading the file to be uploaded and/or download a unified context for the file to be downloaded, in the unified context, through the upload interface and/or download The member variables in the application callback information class in the interface call the file upload function and/or the file download function to implement the corresponding file upload and / or download, without the developer familiar with the SDK used to upload files and / or download files. The implementation and functions of the interface do not require developers to be familiar with the various task links of uploading files and/or downloading files and the API interfaces used in each task link, thereby greatly reducing the development difficulty of developers and improving development efficiency and development. Quality, speed up development, reduce development costs, and effectively avoid development defects.

The above description is only an overview of the technical solutions of the present invention, and the above-described and other objects, features and advantages of the present invention can be more clearly understood. Specific embodiments of the invention are set forth below.

DRAWINGS

Various other advantages and benefits will become apparent to those skilled in the art from a The drawings are only for the purpose of illustrating the preferred embodiments and are not to be construed as limiting. Throughout the drawings, the same reference numerals are used to refer to the same parts. In the drawing:

1 is a flow chart showing the steps of a method for implementing file uploading by an SDK according to a first embodiment of the present invention;

2 is a flow chart showing the steps of a method for implementing file uploading by an SDK according to Embodiment 2 of the present invention;

3 is a flow chart showing the steps of a method for implementing file uploading by an SDK according to Embodiment 3 of the present invention;

4 is a flow chart showing the steps of a method for implementing file downloading by an SDK according to Embodiment 4 of the present invention;

5 is a flow chart showing the steps of a method for implementing file downloading by an SDK according to Embodiment 5 of the present invention;

6 is a flow chart showing the steps of a method for implementing file downloading by an SDK according to Embodiment 6 of the present invention;

7 is a structural block diagram of an apparatus for implementing file uploading by an SDK according to Embodiment 7 of the present invention;

FIG. 8 is a structural block diagram of an apparatus for implementing file uploading by an SDK according to Embodiment 8 of the present invention; FIG.

9 is a structural block diagram of an apparatus for implementing file downloading by an SDK according to Embodiment 9 of the present invention;

FIG. 10 is a structural block diagram of an apparatus for implementing file downloading by an SDK according to Embodiment 10 of the present invention; FIG.

Figure 11 schematically shows a block diagram of a computing device for performing the method according to the invention;

Fig. 12 schematically shows a storage unit for holding or carrying program code implementing the method according to the invention.

detailed description

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While the embodiments of the present invention have been shown in the drawings, the embodiments Rather, these embodiments are provided so that this disclosure will be more fully understood and the scope of the disclosure will be fully disclosed.

Embodiment 1

Referring to FIG. 1, a flow chart of steps of a method for implementing file uploading by an SDK according to a first embodiment of the present invention is shown.

The method for implementing file uploading by the SDK in this embodiment is applied to a cloud storage system, and the method includes the following steps:

Step S102: Receive a file upload instruction, obtain information of the file to be uploaded, and upload a unified context of the file to be uploaded.

When a file needs to be uploaded, the device that uploads the file, such as the client, sends a file upload instruction to the cloud storage server. After receiving the instruction, the cloud storage server obtains the information of the file to be uploaded from the corresponding device, such as the client, such as Information about the file to be uploaded, such as the location of the file to be uploaded, the file size, the location to be uploaded, and so on. More importantly, the cloud storage server also obtains a unified context for uploading files to be uploaded from the device that uploads the file. When uploading a file with a traditional one, each call to a function or interface needs to obtain a different context. The unified context needs to be acquired only once, and is used in all subsequent uploading processes of the file to be uploaded.

Step S104: Calling a plurality of file uploading functions encapsulated in the uploading interface by uploading the member variables in the application callback information class set in the interface, so that the multiple file uploading functions use the unified context environment according to the information of the file to be uploaded. Report the upload of the uploaded file.

The member variable and the multiple file upload function in the application callback information class in the upload interface are determined by analyzing the file uploading process of the cloud storage system, and may only include the basic functions (ie, the core function, the basic function) for implementing the file upload function. Any one of the missing ones can not complete the file upload function), while other function functions can be excluded, such as file upload progress display function, interface prompt function and other functions that do not affect the file upload function can be excluded.

The member variables in the callback information class can connect multiple file upload functions according to the execution order of the file upload task, and execute them in the unified context obtained to implement file uploading. As described above, each file upload function uses the acquired unified context environment when it is executed, and does not need to be acquired separately.

In this embodiment, the upload interface of the SDK provides a good external cooperation mechanism, and the upload interface abstracts and encapsulates the method for uploading files on the cloud storage end to generate the application callback information. Member variables in the class and multiple file upload functions. When using the SDK for file uploading, the unified context for uploading the file to be uploaded is obtained at one time. In the unified context, the file upload function is called by the member variable in the application callback information class in the upload interface, and the file can be implemented. Uploading, no need for developers to be familiar with the implementation and functions of the interfaces of the various SDKs used to upload files, and no need for developers to be familiar with the various task links of uploading files and the API interfaces used in each task link, thus greatly reducing the development of developers. Difficulty and improved development efficiency and development quality, speed up development, reduce development costs, and effectively avoid development defects.

Embodiment 2

Referring to FIG. 2, a flow chart of steps of a method for implementing file uploading by an SDK according to a second embodiment of the present invention is shown.

Step S202: Encapsulating an upload interface of the SDK.

In this embodiment, a preferred method for packaging an SDK uploading interface includes: analyzing a file uploading process of the cloud storage system, obtaining a basic function of completing a file uploading task from all file uploading functions; abstracting the basic function into an application callback Information class, and according to the basic function definition member variable in the callback information class; use member variables to pass parameters between the basic functions, and determine the calling order of the basic function according to the file upload process; the callback information class is applied and the calling order is determined The basic function is packaged into the upload interface of the SDK.

The above analyzes the file uploading process of the cloud storage system, obtains the basic function of completing the file uploading task from all the file uploading functions, and abstracts the basic function into an application callback information class, and defines the application callback information class according to the basic function. The process of the member variable can be manually performed by a person skilled in the art in the actual operation, or can be implemented by a mature artificial intelligence model. Of course, other feasible and appropriate methods are also applicable.

In a preferred embodiment, the uploading interface of the SDK further encapsulates an uploading thread parameter, and the uploading thread parameter is used to indicate the number of threads used when uploading the file to be uploaded. By uploading thread parameters, you can flexibly set the number of threads to upload files and improve the flexibility of file uploading.

Step S204: The SDK receives the file uploading instruction, and obtains the information of the file to be uploaded and the uploading station. A unified context for the uploaded file.

The unified context environment has been used in the subsequent file uploading process of this embodiment.

Step S206: The SDK calls a plurality of file upload functions encapsulated in the upload interface by uploading member variables in the application callback information class set in the interface.

Preferably, when the upload thread parameter is encapsulated in the upload interface of the SDK, before the step of calling the multiple file upload functions encapsulated in the upload interface by using the member variable in the application callback information class set in the upload interface, : receiving the upload thread parameter setting instruction, according to the upload thread parameter set by the upload thread parameter setting instruction, starting the uploading thread of the upload thread parameter indicating quantity to upload the file to be uploaded. For example, if the upload thread parameter in the upload thread parameter setting instruction indicates that five threads are used for file uploading, the SDK upload interface starts five threads to receive the file data block of the file to be uploaded and then uploads. The upload thread parameter setting instruction may be set and sent by the device that uploads the file for each file to be uploaded, or may be sent to the SDK by using a default setting value.

In a preferred embodiment, the upload interface invokes a plurality of file upload functions encapsulated in the upload interface by using member variables and handle parameters in the set application callback information class; wherein the handle parameters are used in multiple files The message is conveyed between the upload functions.

Step S208: The SDK uses a plurality of file upload functions to upload the file to be uploaded using the unified context environment according to the information of the file to be uploaded.

In a preferred embodiment of the invention, the file interface is also encapsulated with a file second pass function. After the file upload function is encapsulated in the upload interface, after receiving the file upload instruction, obtaining the information of the file to be uploaded, and uploading the unified context of the file to be uploaded, the method further includes: calling the file second pass function according to the file to be uploaded. If the file to be uploaded exists on the cloud storage end, the link between the user identifier of the user and the existing file is established; if not, the step S206 is performed.

In this embodiment, when the file is uploaded by using the SDK, the unified context of uploading the file to be uploaded is obtained at one time, and in the unified context, the file upload function is called by the member variable in the application callback information class in the upload interface. File upload is possible, no need for developers to be familiar with the implementation and functions of the interfaces of the various SDKs used to upload files, and no need to develop The personnel are familiar with the various task links of the uploaded files and the API interfaces used in each task link, thereby greatly reducing the development difficulty of the developer and improving the development efficiency and development quality, speeding up the development, reducing the development cost, and effectively avoiding the development. defect.

Embodiment 3

This embodiment describes a method for uploading a file implementation of the SDK of the present invention by using a specific example, and the method is applied to a cloud storage system.

The method for implementing file uploading by the SDK of this embodiment includes the following steps:

Step 1: Generate an upload interface for the SDK.

Hereinafter, the process of generating an upload interface of the SDK will be described from various aspects.

(1) Software environment requirements:

a, development environment: android2.1 and above 2.1;

b. Required permissions: At least the permissions required to generate the SDK, such as the permission configuration of the android application, such as:

c, necessary conditions

(1), set the Application object, by obtaining the Application object of the application, the SDK can get the context of the current application, such as the unified context of the currently uploaded file. The Application object is a system component of the android framework. When the android program starts, the system creates an application object to store some information about the system. Android system will create an Application class object for each program runtime and only create one, so Application can be said to be a singleton (singleton) mode of a class, and the Application object's health The life cycle is the longest in the entire program, and its life cycle is equal to the life cycle of the program. Because it is a global singleton, so through the Application object for some data transfer, data sharing, data cache and other operations.

Such as: setting

com.qihoo.yunpan.sdk.android.config.YunpanApplication.setApplication() method;

Or, set

<application android:name=

One of "com.qihoo.yunpan.sdk.android.config.YunpanApplication".../>.

(2), set development permissions

For example, key(AUTH_NAME, AUTH_KEY, AUTH_SECRET) must be assigned to the corresponding value in com.qihoo.yunpan.sdk.android.config.YunpanSDKConstants.

(3) must be achieved

The com.qihoo.yunpan.sdk.android.config.YunpanSDKConstants.setYunpanInter face(IYunpanInterface yunpanInterface) interface ensures the security of the file upload task.

The onNewUserToken function and the onUserCookieInvalid function are implemented through the interface, wherein the onNewUserToken function is used to refresh the user token, and the onUserCookieInvalid is used to require the user to re-login when the user cookie fails.

(two)

Analyze the file uploading process of the cloud storage system, obtain the basic function of completing the file uploading task from all the file uploading functions; abstract the basic function into the application callback information class, and define the member variables in the application callback information class according to the basic function; The member variable is used to pass parameters between the basic functions, and the calling sequence of the basic function is determined according to the file uploading process; the application callback information class and the basic function that determines the calling sequence are encapsulated into an SDK uploading interface. For example, when the cloud storage system uploads a file, the client sends a file upload instruction to upload the file; and after receiving the file upload instruction, the cloud storage server learns that there is a file upload task, and starts to obtain the file data block. The obtained file data block is stored to the specified location according to the file upload instruction. After analyzing the process, it is determined that for the SDK, each function corresponding to the uploaded data (including file name, size, location, file context, file data, etc.) is acquired, and the file is stored according to the data related to the uploaded file. Each function corresponding to the specified position can be regarded as a basic function, abstracting and encapsulating these basic functions, and finally generating an upload interface of the SDK.

(1) The abstracted application callback information class is:

Class com.qihoo.yunpan.sdk.android.task.TransferStatus; its included member variables are:

Name: actionType

Type: ActionType, Description: Current delivery status

Name: localFileName

Type: String, Description: Local file name

Name: remoteFileName

Type: String, Description: Cloud storage file name

Name: requestCode

Type: String, Description: Request code (application control)

The ActionType (message type enumeration) is com.qihoo.yunpan.sdk.android.task.TransferStatus.ActionType, and its values include:

Name: NULL

Description: meaningless

Name: UPLOAD_PROCESSING

Description: Upload task processing

Name: UPLOAD_FILE_HASH

Description: Calculate the upload file shal

Name: UPLOAD_TRANSFER_DATA

Description: Uploading data in the upload task

Name: UPLOAD_COMPLETE

Description: Upload task completed

(2) Construct a file upload function to implement a file upload task

For example, generate Class com.qihoo.yunpan.sdk.android.task.UploadTask

Constructor: UploadTask()

Parameter 1: (name: localFileName, type: String, description: local file name)

Parameter 2: (name: remoteFileName, type: String, description: cloud storage file name)

Parameter 3: (name: upload_handler, type: Handler, description: convey message)

After the application callback information class and the upload function are implemented, the package can be encapsulated as an upload interface.

Preferably, the upload progress step size can also be set in the upload interface: (default is 5% trigger once, minimum 1 and maximum 20), and the position of the returned data set can be set by calling setProgressStep() and getProgressStep().

Preferably, the current task can also be set in the upload interface: (If restarting, restart the current task in the thread container), the current task can be stopped by calling setIsRun(false).

Preferably, the number of threads in a single task runtime can also be set in the upload interface: (default is 1, maximum 5), which can be set by calling setUploadThreadNum (upload task thread). By setting the number of threads, the SDK package upload task supports the JAVA standard multi-threaded environment.

Other major cloud disk SDK methods also include:

a, user registration (UserIntfRegister)

Generate Class com.qihoo.yunpan.sdk.android.http.action.UserIntfRegister

The constructor is as follows:

Function name: doUserIntfRegister()

Parameter 1: (name: userName, type: String, description: username)

Parameter 2: (name: passWord, type: String, description: password)

(If you call the get verification code interface, please pass the sc parameter via setSc(), and the setCaptcha() method will pass the verification code entered by the user)

Return type: UserCenterInfo

(If the errno=5010 in the return value, you need to call the method to get the verification code (UserIntfGetCaptcha) to get)

b, user login (UserIntfLogin)

Generate Class com.qihoo.yunpan.sdk.android.http.action.UserIntfLogin

The constructor is as follows:

Function name: login()

Parameter 1: (name: username, type: String, description: username)

Parameter 2: (name: passWord, type: String, description: password)

Parameter 3: (name: captcha, type: String, description: the verification code entered by the user)

Parameter 4: (name: sc, type: String, description: sc parameter returned by the server)

(If you call the get verification code interface, please assign the captcha and sc parameters, and leave a null value when there is no verification code)

Return type: UserCenterInfo

c, get the cloud disk list (FileGetNodeList)

Generate Class com.qihoo.yunpan.sdk.android.http.action.getNodeList

The constructor is as follows:

Function name: getNodeList()

Parameters: (name: path, type: String, description: cloud disk directory, / is the root directory)

Return type: FileNodeList

Pagination function: (Two simultaneous settings take effect, the default is all from 0)

This includes setting the position of the returned dataset by calling the setStart() and getStart() methods, and setting the number of returned datasets by calling the setCount() and getCount() methods; implementing the sorting function: by calling the setOrderParam() and getOrderParam() methods Set the sort field (the default is to sort by file name), set the positive or reverse order by calling setIsdesc() and isIsdesc() (the default is positive); set the inner class

Enum com.qihoo.yunpan.sdk.android.http.action.getNodeList.OrderType

The values of this inner class enumeration type include:

Name: name

Description: by file name

Name: mtime

Description: By modification time

Name: fsize

Description: by file size

d, get the file share link (LinkCreateFile)

Generate Class com.qihoo.yunpan.sdk.android.http.action.LinkCreateFile

The constructor is as follows:

Function name: getFileLink()

Parameters: (name: nameList, type: List<String>, description: list of files or folders that need to generate a connection)

Return type: LinkCreateFileData

Through the above functions, the second transmission of the SDK upload task is realized.

One or more of the other major cloud disk SDK methods may be encapsulated into the upload interface in an optional manner to provide a better user experience for uploading files.

Step 2: Upload the file using the generated SDK upload interface.

A process for uploading a file using the upload interface generated in step one is as shown in FIG. 3, and the process includes:

Step S302: Receive a file upload instruction, and the upload task starts.

Step S304: The file upload function in the SDK upload interface calculates a hash value of the file to be uploaded.

Step S306: The file upload function application file upload task in the SDK upload interface.

Step S308: The file upload function in the SDK uploading interface determines whether the file data to be uploaded already exists. If not, step S310 is performed; if yes, step S318 is performed.

Step S310: The file upload function in the SDK upload interface acquires file block information of the file to be uploaded.

Step S312: The file upload function in the SDK uploading interface determines whether the file upload is completed. If yes, step S314 is performed; if not, the file upload fails.

Step S314: The file upload function in the SDK uploading interface confirms that all the file data of the file to be uploaded is completely uploaded, and step S318 is performed.

Step S316: The file upload function in the SDK upload interface confirms that the upload task is completed.

Step S318: The file upload function in the SDK upload interface prompts that the upload is completed.

Through the embodiment, the task of uploading files through the SDK is realized on the mobile terminal of the android system, the development difficulty of the mobile terminal developer is greatly reduced, the development efficiency and development quality of the mobile terminal are improved, the development speed is accelerated, and the development speed is lowered. The development cost effectively avoids development defects.

Embodiment 4

Referring to FIG. 4, a flow chart of steps of a method for implementing file downloading by an SDK according to Embodiment 4 of the present invention is shown.

The method for implementing file downloading by the SDK in this embodiment is applied to a cloud storage system, and the method includes the following steps:

Step S402: Receive a file download instruction.

The file download instruction carries information about the file to be downloaded.

When the client needs to download the file, it sends a file download command to the cloud storage server, where the command carries information about the file to be downloaded, such as the location of the file to be downloaded, the file size, the location to be stored, and the like. The cloud storage server obtains the information of the files to be downloaded from the file download instruction.

Step S404: Obtain a file to be downloaded from the cloud storage end according to the file download instruction and the information of the file to be downloaded, and obtain a unified context for downloading the file to be downloaded.

The cloud storage system includes a client and a cloud, and the cloud includes at least one server for storing data. In the embodiment of the present invention, it is simply referred to as a cloud storage terminal, and the cloud storage terminal stores files to be downloaded.

In the present invention, the cloud storage server obtains a unified context environment for downloading the file to be downloaded when the file to be downloaded is obtained, and the unified context is obtained. It only needs to be obtained once and used in all subsequent downloads of the file to be downloaded.

Step S406: Calling a plurality of file download functions encapsulated in the download interface by using a member variable in the application callback information class set in the download interface, so that the plurality of file download functions use the unified context environment to download the file to be downloaded.

The member variable and the multiple file download function in the application callback information class in the download interface are determined by analyzing the file downloading process of the cloud storage system, and may only include the basic functions (ie, the core function, the basic function) for implementing the file download function. The lack of any of the files can not complete the file download function), for example, to obtain the corresponding data of the downloaded file (including file name, size, location, file context, file data, etc.) and the data according to the downloaded file. Download the file to each function corresponding to the specified location; other functions can be excluded, such as file download progress display function, interface prompt function, etc. Functions that do not affect the file download function can be excluded.

The member variables in the application callback information class can connect multiple file download functions according to the execution order of the file download task, execute sequentially in the acquired unified context environment, and implement file download. As described above, each file download function uses the acquired unified context environment when it is executed, and does not need to be acquired sequentially.

Through this embodiment, the download interface of the SDK provides a better external cooperation mechanism, and the download interface The port abstracts and encapsulates the method of downloading files from the cloud storage terminal, and generates a member variable and a plurality of file download functions in the application callback information class. When the file is downloaded by using the SDK, the unified context for downloading the file to be downloaded is obtained at one time. In the unified context, the file download function is called by the member variable in the application callback information class in the download interface, and the file can be implemented. Download, no need for developers to be familiar with the implementation and function of the interface of each SDK used to download files, and no need for developers to be familiar with the various task links of downloading files and API interfaces used in each task link, thus greatly reducing developer development. Difficulty and improved development efficiency and development quality, speed up development, reduce development costs, and effectively avoid development defects.

Embodiment 5

Referring to FIG. 5, a flow chart of steps of a method for implementing file downloading by an SDK according to Embodiment 5 of the present invention is shown.

Step S502: Encapsulating the download interface of the SDK.

In this embodiment, a preferred method for packaging the SDK download interface includes: analyzing a file downloading process of the cloud storage system, obtaining a basic function of completing a file download task from all file download functions; abstracting the basic function into an application callback Information class, and according to the basic function definition member variable in the callback information class; use member variables to pass parameters between the basic functions, and determine the calling order of the basic function according to the file download process; the callback information class is applied and the calling order is determined The basic function is packaged into the download interface of the SDK.

The above analyzes the file downloading process of the cloud storage system, obtains the basic function of completing the file download task from all file download functions, and abstracts the basic function into an application callback information class, and defines the application callback information class according to the basic function. The process of the member variable can be manually performed by a person skilled in the art in the actual operation, or can be implemented by a mature artificial intelligence model. Of course, other feasible and appropriate methods are also applicable.

In a preferred embodiment, the download interface of the SDK further encapsulates a download thread parameter, and the download thread parameter is used to indicate the number of threads used when downloading the file to be downloaded. By downloading the thread parameters, you can flexibly set the number of threads for downloading files, improving the flexibility of file downloading.

Step S504: The SDK receives a file download instruction, where the file download instruction carries information of the file to be downloaded.

Step S506: The SDK obtains the file to be downloaded from the cloud storage end according to the file download instruction and the information of the file to be downloaded, and obtains a unified context environment for downloading the file to be downloaded.

This unified context environment has been used throughout the subsequent file downloading process of this embodiment.

Preferably, when the download thread parameter is encapsulated in the download interface of the SDK, the SDK obtains the file to be downloaded from the cloud storage terminal according to the file download instruction and the information of the file to be downloaded, and obtains a unified context for downloading the file to be downloaded. Before the step of the environment, the method further includes: receiving a download thread parameter setting instruction, and starting a download thread of the number of indications of the download thread parameter to download the file to be downloaded according to the download thread parameter set by the download thread parameter setting instruction. For example, if the download thread parameter in the download thread parameter setting instruction indicates that the file is downloaded using 5 threads, the SDK download interface starts 5 threads to obtain the file data block of the file to be downloaded from the cloud storage end, and then downloads the file. The download thread parameter setting instruction may be set and sent by the device that downloads the file for each file to be downloaded, or may be sent to the SDK by using a default setting value.

Step S508: The SDK calls a plurality of file download functions encapsulated in the download interface by downloading member variables in the application callback information class set in the interface.

In an optional embodiment, the download interface invokes a plurality of file download functions encapsulated in the download interface by using a member variable and a handle parameter in the set application callback information class; wherein the handle parameter is used in multiple Messages are sent between file download functions.

Step S510: The SDK uses a plurality of file download functions to download the file to be downloaded using the unified context.

In an optional embodiment of the invention, the download interface is also encapsulated with a download history function. When the download history function is encapsulated in the download interface, after the step of receiving the file download instruction by the SDK, the method further includes: calling the download history function encapsulated in the download interface by using a member variable in the application callback information class in the download interface, The download history function determines whether the client that sent the file download instruction has downloaded the file to be downloaded; if it has been downloaded, it determines whether the downloaded file to be downloaded in the client is valid; if it is valid, the download of the file to be downloaded is ended. If it is invalid or if the file to be downloaded has not been downloaded, step S506 is performed. By downloading the history function, Can effectively avoid repeated downloads of files.

In this embodiment, when the file is downloaded by using the SDK, the unified context for downloading the file to be downloaded is obtained at one time, and in the unified context, the file download function is invoked by using the member variable in the application callback information class in the download interface. File download can be realized, no need for developers to be familiar with the implementation and functions of the interfaces of each SDK used to download files, and no need for developers to be familiar with the various task links of downloading files and the API interfaces used in each task link, thus greatly reducing the number of The development difficulty of developers and the improvement of development efficiency and development quality, speed up development, reduce development costs, and effectively avoid development defects.

Embodiment 6

This embodiment describes a method for downloading the SDK implementation file of the present invention by using a specific example, and the method is applied to a cloud storage system.

The method for implementing the file downloading by the SDK of this embodiment includes the following steps:

Step 1: Generate the download interface of the SDK.

Hereinafter, the process of generating the download interface of the SDK will be described from various aspects.

(1) Software environment requirements:

a, development environment: android2.1 and above 2.1;

c, necessary conditions

(1), set the Application object, by obtaining the application object of the application, You can let the SDK get the context of the current application, such as the unified context of the currently downloaded file. The Application object is a system component of the android framework. When the android program starts, the system creates an application object to store some information about the system. Android system will create an Application class object for each program runtime and only create one, so Application can be said to be a singleton (singleton) pattern of a class, and the Application object's life cycle is the longest in the entire program, it The life cycle is equal to the life cycle of this program. Because it is a global singleton, so through the Application object for some data transfer, data sharing, data cache and other operations.

Such as: setting

com.qihoo.yunpan.sdk.android.config.YunpanApplication.setApplication() method;

Or, set

<application android:name=

One of "com.qihoo.yunpan.sdk.android.config.YunpanApplication".../>.

(2), set development permissions

(3) must be achieved

The com.qihoo.yunpan.sdk.android.config.YunpanSDKConstants.setYunpanInterface(IYunpanInterface yunpanInterface) interface ensures the security of the file download task.

(two)

Analyze the file download process of the cloud storage system, obtain the basic function of completing the file download task from all the file download functions; abstract the basic function into the application callback information class, and according to the basis This function defines the member variables in the application callback information class; uses member variables to pass parameters between the basic functions, and determines the calling order of the basic functions according to the file downloading process; encapsulates the application callback information class and the basic functions that determine the calling order into SDKs. Download interface. For example, when the cloud storage system downloads the file, the client sends a file download instruction, and after receiving the file download instruction, the cloud storage server learns that there is a file download task, starts to acquire the file data block, and then according to the file download instruction. The obtained file data block is downloaded to the specified location. After analyzing the process, it is determined that for the SDK, each function corresponding to the downloaded data (including file name, size, location, file context, file data, etc.) is obtained, and the file is downloaded according to the data related to the downloaded file. Each function corresponding to the specified position can be regarded as a basic function, and these basic functions are abstracted and encapsulated, and finally the download interface of the SDK is generated.

(1) The abstracted application callback information class is:

Name: actionType

Type: ActionType, Description: Current delivery status

Name: localFileName

Type: String, Description: Local file name

Name: remoteFileName

Type: String, Description: Cloud storage file name

Name: requestCode

Type: String, Description: Request code (application control)

Name: NULL

Description: meaningless

Name: DOWNLOAD_PROCESSING

Description: Download task processing

Name: DOWNLOAD_TRANSFER_DATA

Description: Downloading data in the download task

Name: DOWNLOAD_COMPLETE

Description: Download task completed

(2) construct file download function to achieve file download task

For example, generate Class com.qihoo.yunpan.sdk.android.task.DownloadTask class

Constructor: DownloadTask()

Parameter 1: (name: localFileName, type: String, description: local file name)

Parameter 3: (name: download_handler, type: Handler, description: convey message)

After the above application callback information class and download function are implemented, the package interface can be provided as a download interface.

Preferably, the download progress step size can also be set in the download interface: (default is 5% trigger once, minimum 1 and maximum 20), and the position of the returned data set can be set by calling setProgressStep() and getProgressStep().

Preferably, the current task can also be set in the download interface: (If restarting, restart the current task in the thread container), the current task can be stopped by calling setIsRun(false).

Preferably, the number of threads in a single task runtime can also be set in the download interface: (default is 1, maximum 5), which can be set by calling setDownloadThreadNum. By setting the number of threads, the download task of the SDK package supports the JAVA standard multi-threaded environment.

Other major cloud disk SDK methods also include:

a, user registration (UserIntfRegister)

Generate Class com.qihoo.yunpan.sdk.android.http.action.UserIntfRegister class

The constructor is as follows:

Function name: doUserIntfRegister()

Parameter 1: (name: userName, type: String, description: username)

Parameter 2: (name: passWord, type: String, description: password)

Return type: UserCenterInfo

b, user login (UserIntfLogin)

Generate Class com.qihoo.yunpan.sdk.android.http.action.UserIntfLogin class

The constructor is as follows:

Function name: login()

Parameter 1: (name: username, type: String, description: username)

Parameter 2: (name: passWord, type: String, description: password)

Return type: UserCenterInfo

c, get the cloud disk list (FileGetNodeList)

Generate Class com.qihoo.yunpan.sdk.android.http.action.getNodeList class

The constructor is as follows:

Function name: getNodeList()

Return type: FileNodeList

Enum com.qihoo.yunpan.sdk.android.http.action.getNodeList.OrderType

The values of this inner class enumeration type include:

Name: name

Description: by file name

Name: mtime

Description: By modification time

Name: fsize

Description: by file size

One or more of the other major cloud disk SDK methods may be encapsulated into the download interface in an optional manner to provide a better user experience for downloading files.

Step 2: Download the file using the generated SDK download interface.

A process for downloading a file using the download interface generated in step one is as shown in FIG. 6, and the process includes:

Step S602: Receive a file download instruction, and the download task starts.

Step S604: The file download function in the SDK download interface acquires the download task information.

The obtained download task information includes: information of the file to be downloaded and a file to be downloaded. A context.

Step S606: The file download function in the SDK download interface determines whether the file data to be downloaded exists locally in the client. If not, step S608 is performed; if yes, step S612 is performed.

Step S608: The file download function in the SDK download interface acquires file block information of the file to be downloaded.

Step S610: If the download of the file is completed, go to step S612; otherwise, the file download fails.

Step S612: The file download function in the SDK download interface prompts that the download is completed.

Through the embodiment, the task of downloading files through the SDK is realized on the mobile terminal of the android system, the development difficulty of the mobile terminal developer is greatly reduced, the development efficiency and development quality of the mobile terminal are improved, the development speed is accelerated, and the development speed is lowered. The development cost effectively avoids development defects.

Example 7

Referring to FIG. 7, a block diagram of a device for implementing file uploading by an SDK according to Embodiment 7 of the present invention is shown.

The SDK in the device for uploading a file in the SDK of this embodiment is applied to a cloud storage system, and the device includes:

The first obtaining module 702 is configured to receive a file uploading instruction, obtain the information of the file to be uploaded, and upload a unified context of the file to be uploaded; the uploading module 704 is configured to use the application callback information class set in the uploading interface. The member variable invokes multiple file upload functions encapsulated in the upload interface, so that multiple file upload functions use the unified context to upload the file to be uploaded according to the information of the file to be uploaded.

In this embodiment, the uploading interface of the SDK provides a good external cooperation mechanism. The uploading interface abstracts and encapsulates the method for uploading files on the cloud storage end, and generates member variables and multiple file uploads in the application callback information class. function. When using the SDK for file uploading, the unified context for uploading the file to be uploaded is obtained at one time. In the unified context, the file upload function is called by the member variable in the application callback information class in the upload interface, and the file can be implemented. Upload, no need for developers to be familiar with the implementation of the interface of each SDK used to upload files And functions, without the need for developers to be familiar with the various task links of uploading files and the API interfaces used in each task link, thus greatly reducing the development difficulty of developers and improving development efficiency and development quality, speeding up development and reducing development. Cost, effectively avoiding development defects.

Example eight

Referring to FIG. 8, there is shown a structural block diagram of an apparatus for implementing file uploading by an SDK according to Embodiment 8 of the present invention.

The SDK in the device for uploading the file in the embodiment of the present invention is applied to the cloud storage system, and the device includes: a first obtaining module 802, configured to receive a file uploading instruction, obtain information of the file to be uploaded, and upload the file to be uploaded. The unified context environment; the uploading module 804 is configured to invoke multiple file uploading functions encapsulated in the uploading interface by uploading the member variables in the application callback information class set in the interface, so that multiple file uploading functions are based on the information of the file to be uploaded. , use the unified context to upload files to be uploaded.

Preferably, the device for uploading the file in the SDK of the embodiment further includes: a first encapsulating module 806, configured to pre-package the plurality of file uploading functions in the uploading interface in the following manner: a file uploading process to the cloud storage system Analyze, obtain the basic function of completing the file upload task from all file upload functions; abstract the basic function into the application callback information class, and define the member variables in the application callback information class according to the basic function; use member variables to pass between the basic functions Parameters, and determine the calling order of the basic function according to the file uploading process; package the application callback information class and the basic function that determines the calling sequence into an upload interface.

Preferably, the uploading interface further includes an uploading thread parameter. The device for uploading the file in the SDK of the embodiment further includes: a first thread setting module 808, configured to upload an application callback information class in the uploading module 804 through the uploading interface. In the member variable, before calling the file upload function encapsulated in the upload interface, receiving the upload thread parameter setting instruction, starting the upload thread parameter set by the upload thread parameter setting instruction, starting the upload thread of the upload thread parameter indicating the number to be uploaded. File upload.

Preferably, the uploading module 804 calls a plurality of file uploading functions encapsulated in the uploading interface by using a member variable in the application callback information class set in the uploading interface: by using the uploading interface by using the set application callback information class Member variables and handle parameters, called in the upload interface encapsulated Multiple file upload functions; where the handle parameters are used to convey messages between multiple file upload functions.

Preferably, the file uploading function is further encapsulated in the uploading interface. The device for uploading the file in the SDK of the embodiment further includes: a second transmitting module 810, configured to receive the file uploading instruction in the first obtaining module 802, and obtain the file to be uploaded. After the information and the unified context of the file to be uploaded are uploaded, the file second pass function is used to determine whether the file to be uploaded exists on the cloud storage end according to the information of the file to be uploaded; if the file to be uploaded already exists on the cloud storage end, Establish a link between the user's user ID and the existing file.

The device for uploading a file in the SDK of the embodiment is used to implement the method for uploading the corresponding SDK in the foregoing multiple method embodiments, and has the beneficial effects of the corresponding method embodiments, and details are not described herein again.

Example nine

Referring to FIG. 9, a block diagram of a device for implementing file downloading by an SDK according to Embodiment 9 of the present invention is shown.

The SDK in the device for implementing file downloading in the SDK of this embodiment is applied to a cloud storage system, and the device includes:

The receiving module 902 is configured to receive a file downloading instruction, where the file downloading instruction carries the information of the file to be downloaded, and the second obtaining module 904 is configured to obtain the file to be downloaded from the cloud storage end according to the file downloading instruction and the information of the file to be downloaded. And obtaining a unified context environment for downloading the file to be downloaded; the downloading module 906 is configured to invoke multiple file download functions encapsulated in the download interface by using a member variable in the application callback information class set in the download interface, so that multiple The file download function uses a unified context to download the files to be downloaded.

Through the embodiment, the download interface of the SDK provides a good external cooperation mechanism. The download interface abstracts and encapsulates the method for downloading files on the cloud storage end, and generates member variables and multiple file downloads in the application callback information class. function. When the file is downloaded by using the SDK, the unified context for downloading the file to be downloaded is obtained at one time. In the unified context, the file download function is called by the member variable in the application callback information class in the download interface, and the file can be implemented. Download, no need for developers to be familiar with the implementation and functions of the interfaces of the various SDKs used to download files, nor the need for developers to be familiar with the various task links and task links of downloading files. The API interface is used, which greatly reduces the development difficulty of developers and improves development efficiency and development quality, speeds up development, reduces development costs, and effectively avoids development defects.

Example ten

Referring to FIG. 10, a block diagram showing the structure of an apparatus for implementing file downloading by an SDK according to Embodiment 10 of the present invention is shown.

The SDK in the device for downloading the file in the embodiment of the present invention is applied to the cloud storage system, and the device includes: a receiving module 1002, configured to receive a file downloading instruction, where the file downloading instruction carries information of the file to be downloaded; and the second acquiring module 1004, configured to obtain a file to be downloaded from the cloud storage terminal according to the file downloading instruction and the information to be downloaded, and obtain a unified context for downloading the file to be downloaded; and the downloading module 1006 is configured to download the application set in the interface. The member variable in the callback information class calls multiple file download functions encapsulated in the download interface, so that multiple file download functions use a unified context to download the file to be downloaded.

Preferably, the apparatus for downloading the file of the SDK in this embodiment further includes: a second encapsulating module 1008, configured to pre-package the plurality of file downloading functions in the upper downloading interface by: performing a file downloading process of the cloud storage system Analysis, get the basic function of completing the file download task from all file download functions; abstract the basic function into the application callback information class, and define the member variables in the callback information class according to the basic function; use the member variable to pass the parameters between the basic functions And according to the file download process to determine the calling order of the basic function; the application callback information class and the basic function that determines the calling sequence are packaged into a download interface.

Preferably, the download interface further includes a download history function; the device for downloading the file in the SDK of the embodiment further includes: an effective determining module 1010, configured to use the application in the download interface after the receiving module 1002 receives the file download command Calling the member variable in the information class, calling the download history function encapsulated in the download interface, and determining whether the client that sent the file download instruction has downloaded the file to be downloaded by downloading the history function; if it has been downloaded, determining the client Whether the downloaded file to be downloaded is valid; if it is valid, the download of the file to be downloaded is ended; if it is invalid or if the file to be downloaded has not been downloaded, the second obtaining module 1004 is entered.

Preferably, the downloading interface further includes a downloading thread parameter; the device for downloading the file in the SDK of the embodiment further includes: a second thread setting module 1012, configured to be in the second obtaining module 1004 Obtaining a file to be downloaded from the cloud storage terminal according to the file downloading instruction and the information of the file to be downloaded, and obtaining a downloading thread parameter setting instruction according to the downloading thread parameter setting instruction before obtaining the unified context environment for downloading the file to be downloaded The parameter starts the download thread parameter indicating the number of download threads to download the file to be downloaded.

Preferably, the downloading module 1006 invokes a plurality of file download functions encapsulated in the download interface by using a member variable in the application callback information class set in the download interface: by using the downloaded interface in the set application callback information class The member variable and the handle parameter call multiple file download functions encapsulated in the download interface; wherein the handle parameter is used to convey a message between multiple file download functions.

The apparatus for downloading the file in the SDK of the embodiment is used to implement the method for downloading the corresponding SDK in the foregoing multiple method embodiments, and has the beneficial effects of the corresponding method embodiments, and details are not described herein again.

The SDK implementation file uploading and/or downloading scheme provided herein is not inherently related to any particular computer, virtual system, or other device. Various general purpose systems can also be used with the teaching based on the teachings herein. According to the above description, it is obvious that the structure required to construct the system having the solution of the present invention is obvious. Moreover, the invention is not directed to any particular programming language. It is to be understood that the invention may be embodied in a variety of programming language, and the description of the specific language has been described above in order to disclose the preferred embodiments of the invention.

In the description provided herein, numerous specific details are set forth. However, it is understood that the embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures, and techniques are not shown in detail so as not to obscure the understanding of the description.

Similarly, the various features of the invention are sometimes grouped together into a single embodiment, in the above description of the exemplary embodiments of the invention, Figure, or a description of it. However, the method disclosed is not to be interpreted as reflecting the intention that the claimed invention requires more features than those recited in the claims. Rather, as the following claims reflect, inventive aspects lie in less than all features of the single embodiments disclosed herein. Therefore, the claims following the specific embodiments are hereby explicitly incorporated into the specific embodiments, wherein each claim itself Both are separate embodiments of the invention.

Those skilled in the art will appreciate that the modules in the devices of the embodiments can be adaptively changed and placed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and further they may be divided into a plurality of sub-modules or sub-units or sub-components. In addition to such features and/or at least some of the processes or units being mutually exclusive, any combination of the features disclosed in the specification, including the accompanying claims, the abstract and the drawings, and any methods so disclosed, or All processes or units of the device are combined. Each feature disclosed in this specification (including the accompanying claims, the abstract and the drawings) may be replaced by alternative features that provide the same, equivalent or similar purpose.

In addition, those skilled in the art will appreciate that, although some embodiments described herein include certain features that are included in other embodiments and not in other features, combinations of features of different embodiments are intended to be within the scope of the present invention. Different embodiments are formed and formed. For example, in the claims, any one of the claimed embodiments can be used in any combination.

The various component embodiments of the present invention may be implemented in hardware, or in a software module running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that a microprocessor or digital signal processor (DSP) may be used in practice to implement some or all of the functionality of some or all of the components of the SDK implementation file uploading in accordance with embodiments of the present invention. The invention can also be implemented as a device or device program (e.g., a computer program and a computer program product) for performing some or all of the methods described herein. Such a program implementing the invention may be stored on a computer readable medium or may be in the form of one or more signals. Such signals may be downloaded from an Internet website, provided on a carrier signal, or provided in any other form.

For example, Figure 11 illustrates a computing device, such as an application server, that can implement file upload and/or download in accordance with the SDK of the present invention. The server conventionally includes a processor 1110 and a computer program product or computer readable medium in the form of a memory 1120. The memory 1120 may be an electronic memory such as a flash memory, an EEPROM (Electrically Erasable Programmable Read Only Memory), an EPROM, a hard disk, or a ROM. Memory 1120 has a memory space 1130 for program code 1131 for performing any of the method steps described above. For example, storage space 1130 for program code Each program code 1131 for implementing various steps in the above method may be included. The program code can be read from or written to one or more computer program products. These computer program products include program code carriers such as hard disks, compact disks (CDs), memory cards or floppy disks. Such a computer program product is typically a portable or fixed storage unit as described with reference to FIG. The storage unit may have a storage section, a storage space, and the like arranged similarly to the storage 1120 in the server of FIG. The program code can be compressed, for example, in an appropriate form. Typically, the storage unit includes computer readable code 1131', i.e., code that can be read by, for example, a processor such as 1110, which when executed by a server causes the server to perform various steps in the methods described above.

"an embodiment," or "an embodiment," or "an embodiment," In addition, it is noted that the phrase "in one embodiment" is not necessarily referring to the same embodiment.

It is to be noted that the above-described embodiments are illustrative of the invention and are not intended to be limiting, and that the invention may be devised without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as a limitation. The word 'comprising' does not exclude the presence of the elements or steps that are not recited in the claims. The word "a" or "an" The invention can be implemented by means of hardware comprising several distinct elements and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means can be embodied by the same hardware item. The use of the words first, second, and third does not indicate any order. These words can be interpreted as names.

In addition, it should be noted that the language used in the specification has been selected for the purpose of readability and teaching, and is not intended to be construed or limited. Therefore, many modifications and changes will be apparent to those skilled in the art without departing from the scope of the invention. For the scope of the present invention, the present invention The disclosure is intended to be illustrative, and not restrictive, and the scope of the invention is defined by the appended claims.

Claims

A software development kit for implementing file uploading, the software development kit being applied to a cloud storage system, the method comprising:

Receiving a file uploading instruction, obtaining information of the file to be uploaded, and uploading a unified context of the file to be uploaded;

And calling, by the member variable in the application callback information class set in the uploading interface, a plurality of file uploading functions encapsulated in the uploading interface, so that the multiple file uploading functions use the information according to the information of the file to be uploaded. The unified context is used to upload the file to be uploaded.
The method of claim 1, wherein the plurality of file upload functions are pre-packaged in the upload interface by:

Performing an analysis on the file uploading process of the cloud storage system, and obtaining a basic function of completing the file uploading task from all file uploading functions;

Extracting the basic function into the application callback information class, and defining a member variable in the application callback information class according to the basic function;

Passing parameters between the basic functions using the member variables, and determining a calling order of the basic functions according to the file uploading process;

The application callback information class and the basic function that determines the calling sequence are encapsulated into the upload interface.
The method of claim 2, wherein the uploading interface further encapsulates an upload thread parameter;

Before the step of calling the multiple file uploading functions encapsulated in the uploading interface by using the member variable in the application callback information class set in the uploading interface, the method further includes:

The uploading thread parameter setting instruction is received, and the uploading thread of the uploading thread parameter indicating quantity is started to upload the file to be uploaded according to the uploading thread parameter set by the uploading thread parameter setting instruction.
The method according to claim 1, wherein the step of calling a plurality of file upload functions encapsulated in the upload interface by using a member variable in an application callback information class set in an upload interface comprises:

The upload interface uses a member variable and a handle in the set of application callback information classes a parameter, calling a plurality of file upload functions encapsulated in the upload interface;

Wherein the handle parameter is used to convey a message between the plurality of file upload functions.
The method according to claim 1, wherein the upload interface is further encapsulated with a file second transfer function;

After the step of receiving the file uploading instruction, obtaining the information of the file to be uploaded, and uploading the unified context of the file to be uploaded, the method further includes:

Calling the file second pass function to determine whether the file to be uploaded exists on the cloud storage end according to the information of the file to be uploaded;

If the file to be uploaded already exists on the cloud storage end, a link between the user identifier of the user and the existing file is established.
A device for implementing file uploading by a software development kit, the software development kit being applied to a cloud storage system, the device comprising:

a first acquiring module, configured to receive a file uploading instruction, obtain information about the file to be uploaded, and upload a unified context of the file to be uploaded;

The uploading module is configured to invoke a plurality of file uploading functions encapsulated in the uploading interface by using a member variable in the application callback information class set in the uploading interface, so that the multiple file uploading functions are based on the file to be uploaded. The information is used to upload the file to be uploaded using the unified context.
The apparatus of claim 6 wherein said apparatus further comprises:

a first encapsulating module, configured to pre-package the plurality of file uploading functions in the uploading interface by:

Performing an analysis on the file uploading process of the cloud storage system, and obtaining a basic function of completing the file uploading task from all file uploading functions;

Extracting the basic function into the application callback information class, and defining a member variable in the application callback information class according to the basic function;

Passing parameters between the basic functions using the member variables, and determining a calling order of the basic functions according to the file uploading process;

Encapsulating the application callback information class and the basic function determining the calling sequence into the Upload interface.
The device according to claim 7, wherein the uploading interface further encapsulates an upload thread parameter;

The device also includes:

a first thread setting module, configured to receive an upload thread parameter setting instruction before the uploading module calls a plurality of file uploading functions encapsulated in the uploading interface by using a member variable in an application callback information class set in the uploading interface And uploading, according to the uploading thread parameter set by the uploading thread parameter setting instruction, the uploading thread of the uploading thread parameter indicating the uploading of the file to be uploaded.
The apparatus according to claim 6, wherein the uploading module invokes a plurality of file uploading functions encapsulated in the uploading interface when a member variable in the application callback information class set in the uploading interface is called:

Calling, by the uploading interface, a plurality of file uploading functions encapsulated in the uploading interface by using a member variable and a handle parameter in the set application callback information class;

Wherein the handle parameter is used to convey a message between the plurality of file upload functions.
The device according to claim 6, wherein the upload interface is further encapsulated with a file second transfer function;

The device also includes:

a second transmission module, configured to: after receiving the file uploading instruction by the first acquiring module, obtaining the information of the file to be uploaded, and uploading the unified context of the file to be uploaded, calling the file second sending function according to the file to be uploaded If the file to be uploaded exists on the cloud storage end, the link between the user identifier of the user and the existing file is established.
A software development kit implements a method for downloading a file, the software development kit being applied to a cloud storage system, the method comprising:

Receiving a file download instruction, where the file download instruction carries information of the file to be downloaded;

Obtaining the information from the cloud storage end according to the file download instruction and the information of the file to be downloaded Waiting for the file to be downloaded, and obtaining a unified context for downloading the file to be downloaded;

Calling, by the member variable in the application callback information class set in the interface, a plurality of file download functions encapsulated in the download interface, so that the plurality of file download functions use the unified context to perform the file to be downloaded Download.
The method of claim 11 wherein said plurality of file download functions are pre-packaged in said download interface in the following manner:

Performing an analysis on the file downloading process of the cloud storage system, and obtaining a basic function of completing the file downloading task from all file downloading functions;

Extracting the basic function into the application callback information class, and defining a member variable in the application callback information class according to the basic function;

Passing parameters between the basic functions using the member variables, and determining a calling order of the basic functions according to the file downloading process;

The application callback information class and the basic function that determines the calling order are encapsulated into the download interface.
The method of claim 12, wherein the download interface is further encapsulated with a download history function;

After the step of receiving the file download instruction, the method further includes:

Using the member variable in the application callback information class in the download interface, calling the download history record function encapsulated in the download interface, and determining, by using the download history record function, a client that sends the file download instruction Whether the file to be downloaded has been downloaded;

If it has been downloaded, determining whether the file to be downloaded that has been downloaded in the client is valid;

If valid, the download of the file to be downloaded is ended;

If the file to be downloaded is not valid, or if the file to be downloaded is not downloaded, the file to be downloaded is obtained from the cloud storage terminal, and the downloaded file is obtained. The steps to download a unified context for a file.
The method of claim 12, wherein the download interface further encapsulates a download thread parameter;

Obtaining information from the cloud storage terminal according to the file download instruction and the information of the file to be downloaded Before the step of downloading the file to be downloaded and obtaining the unified context of the file to be downloaded, the method further includes:

Receiving a download thread parameter setting instruction, and starting a download thread of the download thread parameter indicating quantity to download the file to be downloaded according to the download thread parameter set by the download thread parameter setting instruction.
The method according to claim 12, wherein the step of calling the plurality of file download functions encapsulated in the download interface by using a member variable in the application callback information class set in the download interface comprises:

The download interface invokes a plurality of file download functions encapsulated in the download interface by using a member variable and a handle parameter in the set application callback information class;

Wherein the handle parameter is used to convey a message between the plurality of file download functions.
A software development kit for implementing file downloading, the software development kit being applied to a cloud storage system, the device comprising:

a receiving module, configured to receive a file downloading instruction, where the file downloading instruction carries information about the file to be downloaded;

a second obtaining module, configured to acquire the file to be downloaded from the cloud storage end according to the file downloading instruction and the information of the file to be downloaded, and obtain a unified context environment for downloading the file to be downloaded;

a downloading module, configured to invoke a plurality of file downloading functions encapsulated in the download interface by using a member variable in an application callback information class set in the download interface, so that the multiple file download functions are performed by using the unified context environment Downloading of the file to be downloaded.
The apparatus of claim 16 wherein said apparatus further comprises:

a second encapsulating module, configured to pre-package the plurality of file download functions in the upper download interface by:

Performing an analysis on the file downloading process of the cloud storage system, and obtaining a basic function of completing the file downloading task from all file downloading functions;

Abstracting the basic function into the application callback information class and defining according to the basic function The application calls back a member variable in the information class;

Passing parameters between the basic functions using the member variables, and determining a calling order of the basic functions according to the file downloading process;

The application callback information class and the basic function that determines the calling order are encapsulated into the download interface.
The device according to claim 17, wherein the download interface is further encapsulated with a download history function;

The device also includes:

An effective determining module, configured to: after the receiving module receives the file downloading instruction, use the member variable in the application callback information class in the download interface to invoke the download history record function encapsulated in the download interface, Determining, by the download history function, whether the client that sends the file download instruction has downloaded the file to be downloaded;

If it has been downloaded, determining whether the file to be downloaded that has been downloaded in the client is valid;

If valid, the download of the file to be downloaded is ended;

If it is invalid or if the file to be downloaded has not been downloaded, the second acquiring module is entered.
The device of claim 17, wherein the download interface further encapsulates a download thread parameter;

The device also includes:

a second thread setting module, configured to acquire the file to be downloaded from the cloud storage end according to the file downloading instruction and the information of the file to be downloaded, and obtain the downloaded file to be downloaded Before receiving the unified context, the downloading thread parameter setting instruction is received, and the downloading thread of the number of the downloading thread parameter is started to download the file to be downloaded according to the downloading thread parameter set by the downloading thread parameter setting instruction.
The apparatus according to claim 17, wherein the downloading module invokes a plurality of file download functions encapsulated in the download interface by a member variable in an application callback information class set in a download interface:

Calling, by the download interface, a plurality of file download functions encapsulated in the download interface by using a member variable and a handle parameter in the set application callback information class;

Wherein the handle parameter is used to convey a message between the plurality of file download functions.
A computer program comprising computer readable code, when said computer readable code is run on a computing device, causing said computing device to execute a software development kit implementation file according to any of claims 1-5 Upload method.
A computer readable medium storing the computer program of claim 21.
A computer program comprising computer readable code, when said computer readable code is run on a computing device, causing said computing device to execute a software development kit implementation file according to any of claims 11-15 The method of downloading.
A computer readable medium storing the computer program of claim 23.