WO2017114190A1

WO2017114190A1 - File uploading processing method and device

Info

Publication number: WO2017114190A1
Application number: PCT/CN2016/110357
Authority: WO
Inventors: 林锦成; 金立
Original assignee: 阿里巴巴集团控股有限公司; 林锦成; 金立
Priority date: 2015-12-30
Filing date: 2016-12-16
Publication date: 2017-07-06
Also published as: CN106933853A

Abstract

A file uploading processing method and device are provided. The method comprises: after a server obtains file data sent by a mobile terminal, the server obtains file description information and file content in the file data, and stores the obtained file content into a database according to the obtained file description information. Compared with the prior art, the server, after receiving an uploaded file from the mobile terminal, does not cache the uploaded file as a temporary file, instead, stores the uploaded file right after receiving the same, thereby reducing the time delay in file uploading, improving the efficiency of file uploading, and saving memory overhead of the server.

Description

File upload processing method and device

Technical field

The present application relates to the field of communications technologies, and in particular, to a file upload processing method and apparatus.

Background technique

With the rapid development of mobile communication technology and the advent of the mobile multimedia era, mobile phones, as a necessary mobile communication tool for people, have evolved from simple call tools to intelligent development, and have evolved into a mobile information collection and processing platform. In the current mobile Internet era, mobile phones play an important role as a common terminal.

In the era of cloud computing, image uploading via mobile phones has been widely used in different business scenarios. The traditional image uploading process includes a front-end processing process and a back-end processing process. The front-end processing process is performed after the mobile phone performs image processing (such as image special effect processing, file compression, etc.), and the back-end processing process is performed on the server side, and the server receives the uploading process. After the picture data, a temporary file is generated on the server side, and then the data of the temporary file is read out by the application, the picture description information such as the picture specification is written into the database, and the picture content data is sent to the picture storage system, and the picture is stored by the picture. The system stores.

Since the network where the mobile phone is located may be a 2G network, a 3G network, or a wireless local area network, the stability of the network is uncertain, and the image upload process needs to be cached in the memory of the server, which often results in a long image upload delay. , uploading efficiency is low. Moreover, caching temporary files in the server also occupies a large amount of memory resources on the server.

Application content

The embodiment of the present application provides a file upload processing method and device, which are used to improve file uploading efficiency.

The file upload processing method provided by the embodiment of the present application includes:

Obtaining file data sent by the mobile terminal;

Obtaining file description information and file content in the file data;

According to the obtained file description information, the obtained file content is stored in a database; wherein In the database, the file description information is associated with the file content.

Preferably, the file data is picture file data, and the file description information and file content are file description information and picture content of the picture file.

Preferably, the acquired image file data includes a protocol part and a file part, and the file part includes a file description part and a file content part, and the adjacent parts are separated by a separator;

Obtaining the file description information and the picture content in the picture file data, including:

Determining a location of the file description information and the picture content in the picture file data according to a separator between adjacent portions;

And obtaining file description information and picture content in the picture file data according to the determined file description information and the location of the picture content in the picture file data.

Preferably, the storing, according to the obtained file description information, the acquired image content in a database, including:

Querying corresponding records in the database according to the obtained file description information;

If not found, a record is created in the database, and the obtained file description information is stored in the file description field of the record, and the obtained image content is stored in the picture content field of the record;

If queried, the obtained picture content is stored in the picture content field of the record.

Preferably, after the stored image content is stored in the database according to the obtained file description information, the method further includes:

Using the client user identity information of the mobile terminal to invoke a server-side application program interface, where the server-side application program interface is configured to apply the image uploaded by the mobile terminal to the client according to the client user identity information after being invoked. End application.

Preferably, the file description information includes one or a combination of the following information: a file name, a file type, and a picture size.

Preferably, the picture content is secondary data.

The server provided in this embodiment of the present application includes:

a first acquiring module, configured to acquire file data sent by the mobile terminal;

a second obtaining module, configured to acquire file description information and file content in the file data;

And a storage module, configured to store, according to the obtained file description information, the obtained file content into a database; wherein, in the database, the file description information is associated with the file content.

The second acquiring module is specifically configured to:

Preferably, the storage module is specifically configured to:

Preferably, the method further comprises:

a calling module, configured to invoke a server-side application program interface by using the client user identity information of the mobile terminal after storing the acquired image content to the database according to the obtained file description information, where the server-side application program interface is used Applying the picture uploaded by the mobile terminal to the client application according to the client user identity information after being called.

Preferably, the picture content is secondary data.

In the above embodiment of the present application, after the server obtains the file data sent by the mobile terminal, Obtaining the file description information and the file content in the file data, and storing the obtained file content into the database according to the obtained file description information. Compared with the prior art, after receiving the file uploaded by the mobile terminal, the server does not cache the file as a temporary file, but stores it after receiving, thereby reducing the delay of file uploading and improving the efficiency of file uploading. And can also save server-side memory resource overhead.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following drawings will be briefly described in the description of the embodiments. It is obvious that the drawings in the following description are only some embodiments of the present application, Those skilled in the art can also obtain other drawings based on these drawings without paying for inventive labor.

1 is a schematic structural diagram of a system applicable to an embodiment of the present invention;

2 is a schematic diagram of a file uploading process according to an embodiment of the present invention;

FIG. 3 is a schematic structural diagram of a server according to an embodiment of the present invention.

detailed description

The present application will be further described in detail below with reference to the accompanying drawings, and it is obvious that the described embodiments are only a part of the embodiments of the present application, but not all embodiments. . All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope are the scope of the present application.

The embodiment of the present application provides a file uploading scheme for improving file uploading efficiency. The solution provided by the embodiment of the present application can be applied to a process in which a mobile terminal uploads a file to a network side, where the mobile terminal can be a wireless communication capability device such as a mobile phone, a PDA (Personal Digital Assistant), or a smart wearable device. device. The file types involved may be multimedia files such as pictures, audio and video, or other files, such as text files. The embodiment of the present application is particularly applicable to a file type uploading process.

The embodiments of the present application are described in detail below with reference to the accompanying drawings.

FIG. 1 exemplarily shows a network architecture to which the embodiment of the present application is applied. As shown in Figure 1, this The network architecture may include a mobile terminal and a server on the network side, and the mobile terminal and the server communicate through the network.

The mobile terminal in the above architecture can upload files to the server on the network side through the network. Taking the image upload as an example, the mobile terminal can also process the uploaded image before uploading the file, for example, performing image special effect processing, file compression processing, etc., and then encapsulating the image file into a file of the corresponding format according to a prescribed protocol. And upload to the server on the network side.

The server in the above architecture can implement storage of files uploaded by the mobile terminal.

Still taking image upload as an example, in order to implement some kind of image-related application, such as a social application (which requires the user to provide an avatar and display the user avatar in the user interface of the client application), The client application of the application needs to be installed on the mobile terminal, and the server side needs to install the server-side application of the application, and the client application and the server-side application cooperate with each other to complete the social application.

In the above network architecture, the mobile terminal and the server can exchange information through the network, and the network can be a wide area network, a local area network or the Internet, or an Internet using mobile communication technology. The mobile terminal can access the Internet wirelessly, and the server usually connects to the Internet in a wired manner.

Preferably, the mobile terminal and the server can adopt cloud computing technology to implement information processing based on the powerful functions of the cloud computing technology. Servers and mobile terminals can use cloud-based technology-based operating systems, such as YunOS, to integrate the resources and services of the cloud and mobile terminals.

2 is a schematic flowchart of a file uploading process provided by an embodiment of the present application. This process can be implemented on the server side of the network side. As shown, the process can include the following steps:

Step 201: The server acquires file data sent by the mobile terminal.

Step 202: The server acquires file description information and file content in the file data.

Step 203: The server stores the obtained file content in a database according to the obtained file description information. The file description information is associated with the file content in the database.

In the above process, after receiving the file data sent by the mobile terminal, the server does not need to perform caching to generate a temporary file, but can store the received file data, thereby reducing the delay of file uploading and improving the time. The efficiency of file uploading, on the other hand, can save server storage resources Source overhead.

In the above process, the file types involved may be multiple. The following takes the picture type file as an example to describe the image uploading process in detail.

The mobile terminal encapsulates the picture file data to be uploaded according to a prescribed protocol, and then sends the picture file data to the server. The protocol for transferring picture files may be an HTML (Hyper Text Mark-up Language) protocol. The following takes the HTML protocol as an example to describe the image uploading process shown in FIG. 1 in detail.

In step 201, the mobile terminal encapsulates the picture file data to be uploaded according to the HTML protocol. Multipart/form-data (multi-part form data) format is used when encapsulating image file data using the HTML protocol. Generally, a message in a multipart/form-data format usually includes a protocol part, a file description part, and a file content part, and the adjacent components are divided by a separator.

The following code exemplarily shows a multipart/form-data format message content of picture file data.

Assume that the mobile terminal needs to send a picture file named "kn.jpg", and the web page program accepting the file is located at: http://192.168.24.56/logsys/home/uploadIspeedLog! doDefault.html, then, after the mobile terminal client link 192.168.24.56, send the following HTTP (HyperText Transfer Protoco, Hypertext Transfer Protocol) request:

POST/logsys/home/uploadIspeedLog! doDefault.html HTTP/1.1

Accept: text/plain, */*

Accept-Language: zh-cn

Host: 192.168.24.56

Content-Type: multipart/form-data;boundary=---------------------7db372eb000e2

User-Agent: WinHttpClient

Content-Length: 3693

Connection: Keep-Alive

---------------------7db372eb000e2

Content-Disposition:form-data;name="file";filename="kn.jpg"

Content-Type: image/jpeg

(The jpeg file binary data is omitted here...)

---------------------7db372eb000e2--

In the above code, lines 1 to 8 are the headers of the protocol, that is, the protocol part, which mainly declares that the type of the command is POST, protocol version information, server address, content-type is multipart/form-data, and is defined. The separator "---------------------7db372eb000e2" is used to separate multiple files, form items, etc., and the separator does not match the contents of the file or form item. The data conflicts. When uploading an image, not every field in the header part of the protocol needs to be specified. The content-type field needs to be defined. It includes a flag-like flag called boundary, which can be a random input character. A string that is used to distinguish the beginning of a piece of content. Content-Length: 3693, here 3693 is the total length of the file to be uploaded.

The part after the 10th line to the position of the separator is the data to be uploaded, which may be text or a picture. The data content is preceded by a description field such as Content-Disposition, Content-Type, and Content-Transfer-Encoding, which is used to define file description information, including data type (file), file name, file type (such as image format). This is followed by the specific file content, which is the binary data of the image file for the image file.

Each of the separated data can use Content-Type to indicate the type of the following data, refer to rfc1341 (http://www.ietf.org/rfc/rfc1341.txt). For example, Contect-Type: image/jpeg indicates that the following data is jpeg file data.

In step 202, after receiving the picture file data of the above format sent by the mobile terminal, the server parses the received message, and obtains the file description information and the picture content therein. Since the picture file data sent by the mobile terminal is in the multipart/form-data format specified by the protocol, the server can parse the received picture file data in the multipart/form-data format according to the protocol.

Specifically, the server may determine the file description information and the location of the image content in the image file data according to the separator between the adjacent portions in the image file data message, and then describe the file according to the determined image file data. The location of the information and image content, and the text in the image file data Description information and picture content (such as binary data).

In step 203, the server may store the obtained file content (such as binary data) into the database according to the obtained file description information. The server can store images in the following two ways:

Method 1: Store the image in the specified directory and add the storage path as a field value to the database record;

Method 2: Store the image in binary data in the database as the value of the OLE field.

Depending on how the images are stored, the data storage structure of the database is also different.

For the above method 1, in the data table of the database, the following fields can be set:

ID: serial number;

Filename: the name of the file;

Ext: file extension;

Size: the file size;

Intro: a brief description of the file;

Submit_date: upload time

For the above mode 2, if the picture information is stored in the database, the field for storing the picture (OLE type) can be added in the database. The field name fileimage of the stored image is added to the database, and the data type is "OLE object", which is used to store binary image data. As an example, the following fields can be set:

ID: serial number;

Filename: the name of the file;

Fileimage: store the contents of the uploaded file (binary data);

Ext: file extension;

Size: the file size;

Intro: a brief description of the file;

Submit_date: upload time;

Width: the length of the image;

Height: the width of the image.

In the above data structure, the fileimage field is a "picture content field" for storing picture binary data; the remaining fields are used to describe a picture or picture file, which may be collectively referred to as "file description field", and the "file description field" specifically includes fields. One or a combination of the fields listed above. The specific content in the "file description field" can be extracted from the picture file data received by the server.

The embodiment of the present invention preferably performs picture storage by using the above manner 2.

Taking the image storage in the above manner 2 as an example, the server may query the records in the database according to the obtained file description information, for example, may further combine the sender's user information (such as the user according to the file ID, the file name, and the like). ID) Query the database to query whether there is a record matching the information (a record contains fields such as "file description information field" and "picture content field", and further, may also include a user ID field); if not queried , indicating that the currently received packet is the first packet of all the packets corresponding to the image file, and a record is created in the database, and the obtained file description information is stored in the file description of the record. The field stores the obtained image content in the picture content field of the record; if the query is found, the current received message is a message other than the first message in all the messages corresponding to the image file. Text, at this time the corresponding data record has been created, the server will store the obtained image content to the picture of the record Yung field.

It should be noted that the data volume of an image file is usually large, and the packet format specified by the transmission protocol has a certain length requirement. Therefore, it is usually required to split one image file data into multiple packets for transmission.

As an example, the server can use the BinaryRead method of the Request object of the ASP to read the binary information of the uploaded image of the mobile terminal, obtain the file name and absolute path of the uploaded image file, and the file type, etc., and specifically determine the identifier according to the separator. The starting position of the binary data of the file name, and then use ASP technology to convert the binary data into a file name to save. Further, the server writes the contents of the binary file into the OLE field of the database through the AppendChunk method of the recordset object.

Further, if the mobile terminal performs compression processing on the picture before uploading the picture, the server first performs decompression processing after receiving the picture file data sent by the mobile terminal, and recovers. To the original image data.

As can be seen from the above description, after the server obtains the file data sent by the mobile terminal, the file description information and the file content in the file data are obtained, and the obtained file content is stored according to the obtained file description information. In the database. Compared with the prior art, after receiving the file uploaded by the mobile terminal, the server does not cache the file as a temporary file, but stores it after receiving, thereby reducing the delay of file uploading and improving the efficiency of file uploading. And can also save server-side memory resource overhead.

Further, in some embodiments, after the server stores the acquired image content to the database according to the obtained file description information, the server may also use the client user identity information (such as the user ID) of the mobile terminal to invoke the server-side application interface. The server-side application program interface is configured to apply the image uploaded by the mobile terminal to the client application according to the client user identity information after being called. By using a server instead of a mobile terminal to call back to the developer application, high reliability of the callback information can be achieved.

In the existing image uploading process, after the image upload is completed, the client user initiates a callback process through its client App. Since the network where the mobile terminal is located may be a 2G network, a 3G network, or a wireless local area network, the stability of the network is uncertain. Therefore, the client user initiates a callback process on the mobile terminal side. On the one hand, the delay may be long. It is also possible that the callback process fails, and on the other hand, the user operation is cumbersome. In the above embodiment of the present invention, the server side simulates the client user identity to initiate a callback, that is, instead of the client user initiating the callback, compared with the prior art, the delay can be reduced, and the success rate of the callback process is improved. It also simplifies user operations.

In order to more clearly understand the above-mentioned embodiments of the present invention, a specific implementation process of the foregoing embodiments of the present invention will be described in detail below by taking a specific application scenario as an example.

The client application of the application A needs to be installed on the mobile terminal, and the server-side application of the application needs to be installed on the server. The application A is a social application, and the user is required to provide an avatar and display it in the user interface of the client application.

On the mobile terminal side:

The user uses the user account (user ID) to log in to the client app of the mobile terminal, and selects a function button or a menu command of "set user avatar" in the user avatar setting interface provided by the client app, and according to the prompt of the setting interface, Select a picture as the avatar in the picture library of the mobile terminal. It After that, the user selects the function button or menu command of “Upload Picture” according to the prompt of the setting interface.

The client App obtains the image file description information and the binary data of the image content according to the command of “uploading the image”, and the obtained image file description information may include: a picture file name, a picture type (such as a JPEG format or other pictures). One or a combination of information such as format, absolute path, and length and width of the picture. Then, according to the HTML protocol, the obtained picture file description information and the binary data of the picture content are encapsulated into one or more messages. For the specific packet format, refer to the foregoing embodiment, which is not repeated here.

The client App sends the encapsulated message to the server, where the address of the server can be preset in the client App, or the client App can obtain the address of the server in other manners.

On the server side:

The server receives the picture data message sent by the mobile terminal, parses the message according to the HTML protocol, and obtains the picture file description information and the binary data of the picture content. The picture description information includes an image file name, a picture file format, and a picture size. The server creates a record in the database, and fills in the obtained image file name, image file format, image size, and user ID into the corresponding field of the record, and adds the binary data of the obtained image content to the record. OLE field.

After that, the server calls the developer API (Application Programming Interface) of the application A with the user ID of the client. After the API is invoked, the following process is triggered to apply the image uploaded by the client user to the client application, that is, the image is displayed in the avatar display area of the user interface. This process is called a callback process.

Based on the same technical concept, the embodiment of the present application further provides a server, which can implement the above file upload processing flow.

FIG. 3 is a schematic structural diagram of a server according to an embodiment of the present disclosure. As shown in the figure, the device may include: a first obtaining module 301, a second obtaining module 302, and a storage module 303, where:

The first obtaining module 301 is configured to acquire file data sent by the mobile terminal;

The second obtaining module 302 is configured to acquire file description information and file content in the file data.

The storage module 303 is configured to store the obtained file content into a database according to the obtained file description information, where the file description information is associated with the file content.

Preferably, the acquired picture file data includes a protocol part and a file part, and the file part includes a file description part and a file content part, and the adjacent parts are separated by a separator. Correspondingly, the second obtaining module 302 is specifically configured to: determine, according to a separator between adjacent portions, file description information and a location of the image content in the image file data; according to the determined image file data The file description information and the location of the picture content, and the file description information and the picture content in the picture file data are obtained.

Preferably, the storage module 303 is specifically configured to: query a corresponding record in the database according to the obtained file description information; if not, create a record in the database, and store the obtained file description information. Go to the file description field of the record, and store the obtained image content in the picture content field of the record; if queried, store the obtained picture content in the picture content field of the record.

Further, the server may further include a calling module 304, configured to invoke the server-side application program interface by using the client user identity information of the mobile terminal after storing the acquired image content to the database according to the obtained file description information. The server-side application program interface is configured to apply the image uploaded by the mobile terminal to the client application according to the client user identity information after being invoked.

Preferably, the picture content is secondary data.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (system), and computer program products according to embodiments of the present application. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG. These computer program instructions can be provided to a processor of a general purpose computer, a special purpose computer, an embedded processor or other programmable data processing device to produce a machine such that The instructions executed by the processor of the machine or other programmable data processing device generate means for implementing the functions specified in one or more blocks of the flow or in a block or blocks of the flowchart.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.

These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

While the preferred embodiment of the present application has been described, it will be apparent that those skilled in the art can make further changes and modifications to the embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and the modifications and

It will be apparent to those skilled in the art that various modifications and changes can be made in the present application without departing from the spirit and scope of the application. Thus, it is intended that the present invention cover the modifications and variations of the present invention.

Claims

A file upload processing method, comprising:

Obtaining file data sent by the mobile terminal;

Obtaining file description information and file content in the file data;

And storing, according to the obtained file description information, the obtained file content into a database; wherein, in the database, the file description information is associated with the file content.
The method according to claim 1, wherein the file data is picture file data, and the file description information and file content are file description information and picture content of the picture file.
The method according to claim 2, wherein the acquired picture file data comprises a protocol part and a file part, the file part comprising a file description part and a file content part, and the adjacent parts are separated by a separator;

Obtaining the file description information and the picture content in the picture file data, including:

Determining a location of the file description information and the picture content in the picture file data according to a separator between adjacent portions;

And obtaining file description information and picture content in the picture file data according to the determined file description information and the location of the picture content in the picture file data.
The method of claim 2, wherein the storing the acquired image content in the database according to the obtained file description information comprises:

Querying corresponding records in the database according to the obtained file description information;

If not found, a record is created in the database, and the obtained file description information is stored in the file description field of the record, and the obtained image content is stored in the picture content field of the record;

If queried, the obtained picture content is stored in the picture content field of the record.
The method according to claim 2, wherein the storing the acquired image content to the database according to the obtained file description information further includes:

Invoking a server-side application program interface by using the client user identity information of the mobile terminal, where the server-side application program interface is configured to be based on the client user identity information after being invoked Applying the image uploaded by the mobile terminal to the client application.
The method according to any one of claims 2 to 5, wherein the file description information comprises one or a combination of the following information: a file name, a file type, and a picture size.
The method according to any one of claims 2 to 5, wherein the picture content is secondary data.
A server, comprising:

a first acquiring module, configured to acquire file data sent by the mobile terminal;

a second obtaining module, configured to acquire file description information and file content in the file data;

And a storage module, configured to store, according to the obtained file description information, the obtained file content into a database; wherein, in the database, the file description information is associated with the file content.
The server according to claim 8, wherein the file data is picture file data, and the file description information and file content are file description information and picture content of the picture file.
The server according to claim 9, wherein the acquired image file data includes a protocol portion and a file portion, and the file portion includes a file description portion and a file content portion, and the adjacent portions are separated by a separator;

The second acquiring module is specifically configured to:

Determining a location of the file description information and the picture content in the picture file data according to a separator between adjacent portions;

And obtaining file description information and picture content in the picture file data according to the determined file description information and the location of the picture content in the picture file data.
The server according to claim 9, wherein the storage module is specifically configured to:

Querying corresponding records in the database according to the obtained file description information;

If not found, a record is created in the database, and the obtained file description information is stored in the file description field of the record, and the obtained image content is stored in the picture content field of the record;

If queried, the obtained picture content is stored in the picture content field of the record.
The server according to claim 9, further comprising:

a calling module, configured to invoke a server-side application program interface by using the client user identity information of the mobile terminal after storing the acquired image content to the database according to the obtained file description information, where the server-side application program interface is used Applying the picture uploaded by the mobile terminal to the client application according to the client user identity information after being called.
The server according to any one of claims 9 to 12, wherein the file description information comprises one or a combination of the following information: a file name, a file type, and a picture size.
The server according to any one of claims 9 to 12, wherein the picture content is secondary data.