CN110213313B

CN110213313B - File uploading method, related device and system

Info

Publication number: CN110213313B
Application number: CN201810403755.4A
Authority: CN
Inventors: 李火荣; 王松健; 段克晓; 杨程; 杨帆; 王健; 周礼军
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2018-04-28
Filing date: 2018-04-28
Publication date: 2021-09-28
Anticipated expiration: 2038-04-28
Also published as: CN110213313A

Abstract

The embodiment of the invention discloses a file uploading method, which comprises the following steps: if the first APP generates a target file to be uploaded, a file uploading request is sent to a server, the file uploading request carries a unique device identifier, and the device identifier is used for associating APPs installed on the same terminal device; if the second APP and the first APP are APPs on the same terminal device, when the second APP is started, file path information sent by a server is received, wherein the file path information is determined by the server according to a file uploading request; and uploading the target file to the server according to the file path information. The embodiment of the invention also discloses a client, a server and a file uploading system. In the embodiment of the invention, when the file generated by the APP with lower activity needs to be uploaded, the file can be uploaded after the other APP is started, and the user does not need to wait for starting the APP with lower activity again, so that the file uploading efficiency is improved.

Description

File uploading method, related device and system

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a method, a related apparatus, and a system for uploading a file.

Background

With the development of the mobile internet, the popularity of the terminal device is higher and higher, and the development of the Application (APP) is faster and faster. However, different applications may have different development qualities, and may have an operation problem in a specific model of the smart phone.

Currently, when an operation problem occurs, a terminal device generally captures a log file of an APP and stores the log file locally. If the developer needs to locate the problem by obtaining the log file, the APP should be started first, thereby establishing a connection of the APP with the server, and then the APP can upload the log file to the server.

However, the activity of different APPs is different, and the time for waiting until an inactive APP is started again is very long. If the log file required to be acquired by the developer is from the APP with low activity, much time is consumed for waiting for the APP to be started again, so that the efficiency of uploading the log file is reduced.

Disclosure of Invention

The embodiment of the invention provides a file uploading method, a related device and a system, when a file generated by an APP with low activity needs to be uploaded, the file can be uploaded after another APP is started, and a user does not need to wait for starting the APP with low activity again, so that the file uploading efficiency is improved.

The first aspect of the present invention provides a method for uploading a file, including:

if a first application program APP generates a target file to be uploaded, sending a file uploading request to a server, wherein the file uploading request carries a unique device identifier, and the device identifier is used for associating APPs installed on the same terminal device;

if the second APP is the APP on the same terminal device as the first APP, receiving file path information sent by the server when the second APP is started, wherein the file path information is determined by the server according to the file uploading request;

and uploading the target file to the server according to the file path information.

A second aspect of the present invention provides a method for uploading a file, including:

if a first application program APP generates a target file to be uploaded, receiving a first file uploading request sent by a client, wherein the first file uploading request carries a unique device identifier, and the device identifier is used for associating APPs installed on the same terminal device;

determining file path information according to the first file uploading request;

if the second APP is the APP on the same terminal device as the first APP, the file path information is sent to the client when the second APP is started;

and receiving the target file sent by the client according to the file path information.

A third aspect of the present invention provides a client, comprising:

the device comprises a sending module and a processing module, wherein the sending module is used for sending a file uploading request to a server if a first application program APP generates a target file to be uploaded, the file uploading request carries a unique device identifier, and the device identifier is used for associating APPs installed on the same terminal device;

a receiving module, configured to receive file path information sent by the server when a second APP is started if the second APP and the first APP are APPs on the same terminal device, where the file path information is determined by the server according to the file upload request sent by the sending module;

and the uploading module is used for uploading the target file to the server according to the file path information received by the receiving module.

A fourth aspect of the present invention provides a server comprising:

the device comprises a receiving module and a processing module, wherein the receiving module is used for receiving a first file uploading request sent by a client if a first application program APP generates a target file to be uploaded, the first file uploading request carries a unique device identifier, and the device identifier is used for associating APPs installed on the same terminal device;

the determining module is used for determining file path information according to the first file uploading request received by the receiving module;

a sending module, configured to send the file path information determined by the determining module to the client when a second APP is started if the second APP and the first APP are APPs on the same terminal device;

the receiving module is further configured to receive the target file sent by the client according to the file path information.

A fifth aspect of the present invention provides a client, comprising: a memory, a transceiver, a processor, and a bus system;

wherein the memory is used for storing programs;

the processor is used for executing the program in the memory and comprises the following steps:

uploading the target file to the server according to the file path information;

the bus system is used for connecting the memory and the processor so as to enable the memory and the processor to communicate.

A sixth aspect of the present invention provides a server comprising a memory, a transceiver, a processor, and a bus system;

wherein the memory is used for storing programs;

if a first application program APP generates a target file to be uploaded, receiving a file uploading request sent by a client, wherein the file uploading request carries a unique device identifier, and the device identifier is used for associating APPs installed on the same terminal device;

determining file path information according to the file uploading request;

receiving the target file sent by the client according to the file path information;

A seventh aspect of the present invention provides a file uploading system, including a client and a server;

if a first application program APP generates a target file to be uploaded, the client sends a file uploading request to a server, wherein the file uploading request carries a unique device identifier, and the device identifier is used for associating APPs installed on the same terminal device;

the server determines file path information according to the first file uploading request;

if a second APP is the same APP on the terminal device as the first APP, when the second APP is started, the server sends the file path information to the client;

and the client uploads the target file to the server according to the file path information.

An eighth aspect of the present invention provides a computer-readable storage medium having stored therein instructions, which, when run on a computer, cause the computer to perform the method of the above-described aspects.

According to the technical scheme, the embodiment of the invention has the following advantages:

the embodiment of the invention provides a file uploading method, wherein if a first application program APP generates a target file to be uploaded, a client sends a file uploading request to a server, wherein the file uploading request carries a unique device identifier which is used for associating the APPs installed on the same terminal device, when a second APP is started, the client can receive file path information sent by the server, the file path information is determined by the server according to the file uploading request, and finally, the client uploads the target file to the server according to the file path information. Through the mode, the client associates the first APP with the second APP by using the unique equipment identifier, if the file generated by the first APP needs to be uploaded, the file can be uploaded when the second APP is started, the first APP is not required to be started again by a user, and therefore the file uploading efficiency is improved.

Drawings

FIG. 1 is a schematic diagram of an architecture of a file upload system according to an embodiment of the present invention;

fig. 2A is a schematic view of an application scenario of the file uploading system in the embodiment of the present invention;

fig. 2B is an interaction diagram of a file uploading method according to an embodiment of the present invention;

FIG. 3 is a schematic diagram of an embodiment of a method for uploading a file according to an embodiment of the present invention;

FIG. 4 is a diagram illustrating the generation of device identifiers in an embodiment of the present invention;

FIG. 5 is a diagram illustrating uploading of a file to a server according to an embodiment of the present invention;

FIG. 6 is a schematic diagram of another embodiment of a method for uploading a file according to an embodiment of the present invention;

FIG. 7 is a flowchart illustrating a process for uploading a file by a client in an application scenario of the present invention;

FIG. 8 is a flowchart illustrating a process of receiving a file by a server in an application scenario of the present invention;

FIG. 9 is a diagram of an embodiment of a client according to the present invention;

FIG. 10 is a schematic diagram of another embodiment of the client according to the embodiment of the present invention;

FIG. 11 is a diagram of another embodiment of a client according to the embodiment of the present invention;

FIG. 12 is a diagram of another embodiment of a client according to the embodiment of the present invention;

FIG. 13 is a diagram of one embodiment of a server in an embodiment of the invention;

FIG. 14 is a diagram of another embodiment of a server in an embodiment of the present invention;

FIG. 15 is a schematic structural diagram of a client according to an embodiment of the present invention;

FIG. 16 is a block diagram of a server according to an embodiment of the present invention;

fig. 17 is a schematic diagram of an embodiment of a file uploading system in the embodiment of the present invention.

Detailed Description

The terms "first," "second," "third," "fourth," and the like in the description and in the claims, as well as in the drawings, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

It should be understood that the present invention may be applied to a scenario of uploading a file between a server and a client, please refer to fig. 1, where fig. 1 is a schematic structural diagram of a file uploading system in an embodiment of the present invention, and a client provided by the present invention is disposed on a terminal device, as shown in the figure, the device may include, but is not limited to, a mobile phone, a notebook computer, a tablet computer, a personal computer, and a palmtop computer, and the number and the type of each terminal device in fig. 1 are only one schematic diagram. Fig. 2A is continued to refer to the terminal device according to that there are at least two Applications (APPs) using the client, where fig. 2A is a schematic view of an application scenario of the file uploading system in the embodiment of the present invention.

As shown in fig. 2A, an application a and an application B are installed on a certain terminal device, where the application a is an application with a low start frequency and is started 3 times a week on average, and the application B is an application that is started frequently and is started 8 times a day on average. The client may be called in both application a and application B, and in particular may be a plug-in such as "midars" Software Development Kit (SDK). If the application program a runs and crashes, the application program a generates a related log file for background analysis by the server, but if the application program a wants to upload the log file X, a communication connection needs to be established with the server.

Considering that the opening frequency of the application program a is very low, in the present invention, when the user installs the first application program with the "Midas" SDK, the user first generates a device identifier of a terminal device, and other application programs can also obtain the device identifier on the specified path. Then, when the user starts the application program B, the 'Midas' SDK can carry the equipment identifier in the file uploading request, and the server issues the appointed path information according to the equipment identifier, so that when the user starts the application program B, the log file X can be uploaded to the server through the 'Midas' SDK.

The Midas is a virtual payment platform which supports Q points, WeChat payment, balance of financial payment, quick payment of financial payment, a mobile phone rechargeable card, mobile phone charges, a QQ card and the like. It should be noted that the client provided by the present invention is not limited to the "Midas" SDK, and may also be other clients having a function of associating multiple applications.

Referring to fig. 2B, fig. 2B is an interactive schematic diagram of a file uploading method in an embodiment of the present invention, as shown in the figure, a client, such as "Midas", is installed in both a first APP and a second APP, where the first APP may refer to a specific APP or a group of unusual APPs (for example, five unusual APPs may be referred to as the first APP). The second APP may refer to a certain APP, or a group of commonly used APPs (for example, three less commonly used APPs may be referred to as the second APP).

In step S1, an object file to be uploaded is first generated by a first APP, where the object file may be a log file belonging to the first APP, and the first APP here may be one APP or multiple APPs. If the first APP comprises a plurality of APPs, such as APP 1 and APP2, APP 1 and APP2 respectively generate files belonging to their own target files.

In step S2, once the client obtains the target file generated by the first APP, a file upload request is sent to the server, and the server responds to the request and may determine the file storage space that needs to be allocated to the first APP according to the request.

In step S3, the server parses the file upload request to obtain a unique device identifier, and can associate the APPs installed on the same terminal device according to the unique device identifier, that is, find a second APP associated with the first APP, where the second APP may also be multiple APPs. The server determines file path information based on the request.

In step S4, the user starts a second APP, which may be any one of commonly used APPs, but the premise is that the second APP and the first APP are APPs installed on the same terminal device.

In step S5, the server sends file path information to the client, where the file related to the first APP can be stored.

In step S6, the client uploads the object file belonging to the first APP to the server 7 through the file path information.

Referring to fig. 3, a method for uploading a file according to the present invention is described below from the perspective of a client, where an embodiment of the method for uploading a file according to the present invention includes:

101. if the first application program APP generates a target file to be uploaded, sending a file uploading request to a server, wherein the file uploading request carries a unique device identifier, and the device identifier is used for associating APPs installed on the same terminal device;

in this embodiment, a first APP is installed on a terminal device, and the first APP may have a compatibility problem or an operation problem, and at this time, the first APP needs to capture an operating log file and store the log file locally in the first APP. The log file refers to a code operation record printed by the APP at the terminal equipment for positioning problems.

It is understood that, in practical applications, the target file may be, in addition to the log file, an Android Package (APK) file, an initialization (INI) file, or a Document (DOC) file, which is not limited herein.

The client side sends a file uploading request to the server after detecting the target file generated by the first APP, the file uploading request carries the unique equipment identifier of the terminal equipment, and the server can determine other APPs installed on the same terminal equipment according to the equipment identifier.

For convenience of understanding, please refer to fig. 4, fig. 4 is a schematic diagram of generating an apparatus identifier according to an embodiment of the present invention, and as shown in the figure, assuming that the first APP integrated with the client installed on the terminal device by the user is "see-through", the client generates an apparatus identifier for use by a subsequent APP (e.g., "royal glory" or the like). Typically, the client stores the generated device identifier in a local storage area of the terminal device, such as a built-in memory card, a Secure Digital (SD) card, or a Subscriber Identity Module (SIM) card.

102. If the second APP and the first APP are APPs on the same terminal device, when the second APP is started, file path information sent by a server is received, wherein the file path information is determined by the server according to a file uploading request;

in this embodiment, when the user starts the second APP, the server may detect whether the device identifiers of the second APP and the first APP are consistent, and if so, determine that the two APPs belong to the same APP on one terminal device. And when the second APP and the first APP are determined to be installed on the same terminal device, the server sends file path information to the client.

For convenience of introduction, please refer to fig. 5, where fig. 5 is a schematic diagram illustrating uploading a file to a server according to an embodiment of the present invention, and as shown in the figure, assuming that a first APP integrated with a client installed on a terminal device by a user is "continuously watching", the client generates a device identifier and sends the device identifier to the server. Subsequently, the server can detect the APPs with the same equipment identification, and if the second APP is detected to be "royal glory", then the server can issue the file path information belonging to "continuous watching" to "royal glory", and at this time, the second APP can establish an uploading connection with the server, so that the target file generated by the first APP (namely, "continuous watching") can be uploaded to the server.

It is understood that the file path information may be a root directory, such as "/Tencent/Midas/Log/com.tence.test/Midas 20180101. txt" and "com.tence.test" as a file package name, and the APP types can be distinguished by the file package name.

103. And uploading the target file to the server according to the file path information.

In this embodiment, the client integrated on the second APP uploads the target file to the server according to the file path information issued by the server.

Optionally, on the basis of the embodiment corresponding to fig. 3, in a first optional embodiment of the method for uploading a file provided in the embodiment of the present invention, before sending the file upload request to the server, the method may further include:

after a first installation completion instruction of a first APP is acquired, generating an equipment identifier;

sending the equipment identification to a server;

after the second APP is installed, a second installation completion instruction is sent to the server, wherein the second installation completion instruction carries the identifier to be identified;

receiving file path information sent by a server, wherein the file path information comprises:

and if the server determines that the identifier to be identified is consistent with the equipment identifier, receiving file path information sent by the server.

In this embodiment, when the client acquires the first installation completion instruction generated by the first APP, an only one device identifier may be generated according to the first installation completion instruction, where the device identifier is in one-to-one correspondence with the terminal device, and APPs belonging to the same terminal device all correspond to the same device identifier. The device identifier may specifically be a 32-bit string generated by the client, and may also be an identifier such as an International Mobile Equipment Identity (IMEI) or a Media Access Control (MAC), which is not limited herein.

The client sends the device identification to the server. After the second APP is installed, the client may generate an identifier to be identified, which is associated with the second APP, and then the client sends a second installation completion instruction to the server, where the second installation completion instruction carries the identifier to be identified. Whether the identification mark to be recognized corresponding to the second APP is consistent with the equipment identification corresponding to the first APP is judged by the server, if so, the first APP and the second APP belong to APPs installed on the same terminal equipment, and then the server can send file path information to the client.

Secondly, in the embodiment of the invention, the client carries the equipment identifier in the instruction, the first APP carries the equipment identifier, the second APP carries the identifier to be identified, and if the identifier to be identified is consistent with the equipment identifier, the file path information sent by the server is received. Through the mode, the APP installed on the same terminal device can be accurately associated by using the unique device identification, so that uploading of files between the APPs is guaranteed, and operability of the scheme is improved.

Optionally, on the basis of the embodiment corresponding to fig. 3, in a second optional embodiment of the method for uploading a file provided in the embodiment of the present invention, when the second APP is started, the method may further include:

and sending an application identifier to the server so that the server determines that the target file belongs to the first APP according to the application identifier, wherein the application identifier and the first APP have a unique corresponding relationship.

In this embodiment, when the second APP is started, the application identifier may also be sent to the server, and since the uploaded target file is a file of the first APP, the application identifier belongs to the first APP. For convenience of introduction, please refer to table 1, where table 1 illustrates a correspondence relationship between an application identifier and an APP.

TABLE 1

Application identification	APP
		1	See in succession
2	Rong Yao of the king
		3	QQ dance
4	QQ aerodyne
		5	Absolutely seeking survival
6	Live wire crossing
		7	QQ hall

Therefore, the server can determine what type of APP the first APP is according to the application identifier corresponding to the first APP sent by the client. Although the APP type can also be identified by the package name in the file path information, it is more complicated than identifying the APP type directly by the application identification.

Secondly, in the embodiment of the invention, the client sends the application identifier to the server so that the server determines that the target file belongs to the first APP according to the application identifier, wherein the application identifier and the first APP have a unique corresponding relationship. By means of the method, different APPs can be visually represented by the application identifiers, so that background operators can acquire the APP to which the file belongs more quickly, and the practicability and feasibility of the scheme are improved.

Optionally, on the basis of the embodiment corresponding to fig. 3, in a third optional embodiment of the method for uploading a file according to the embodiment of the present invention, after the target file is uploaded to the server according to the file path information, the method may further include:

judging whether the target file is uploaded successfully;

if the target file is uploaded successfully, carrying out integrity check on the target file;

and if the target file fails to be uploaded, the target file is uploaded again according to the file retransmission rule.

In this embodiment, after the client uploads the target file to the server according to the file path information, the client further needs to further determine the uploading condition of the target file. If the target file is successfully uploaded, the integrity check of the target file is performed to check the integrity of the target file, because the target file may be in the process of transmission, and data transmission is lost due to network problems.

And if the target file is failed to be uploaded, the client uploads the target file again according to the file retransmission rule. The file retransmission rule is a preset file transmission rule.

Secondly, in the embodiment of the invention, the client can also judge whether the target file is uploaded successfully, and can carry out integrity check on the target file under the successful condition, otherwise, the target file is uploaded again according to the file retransmission rule under the failed condition. Through the method, a reasonable processing mode can be selected according to different success or failure conditions after uploading, so that the feasibility and operability of the scheme are improved.

Optionally, on the basis of the third embodiment corresponding to fig. 3, in a fourth optional embodiment of the method for uploading a file according to the embodiment of the present invention, uploading a target file again according to a file retransmission rule may include:

if the uploading frequency of the target file reaches the preset uploading frequency, stopping uploading the target file to the server;

and if the uploading frequency of the target file does not reach the preset uploading frequency, continuously uploading the target file to the server.

In this embodiment, in the process of uploading the target file again according to the file retransmission rule, the client needs to count the uploading times in each uploading.

Specifically, assuming that the preset uploading frequency is three times, if the client fails to upload the target file to the server for the first time, the server issues a retransmission instruction to the client, and after receiving the retransmission instruction, the client uploads the target file to the server again. If the client fails to upload the target file to the server for the second time, the server issues a retransmission instruction to the client again, and the client uploads the target file to the server again after receiving the retransmission instruction.

At this time, the client uploads the target file to the server for the third time, and the third uploading reaches the preset uploading times, so that if the transmission still fails, the client stops uploading the target file to the server.

In the embodiment of the invention, if the uploading frequency of the target file reaches the preset uploading frequency, the client stops uploading the target file to the server, and if the uploading frequency of the target file does not reach the preset uploading frequency, the client continues uploading the target file to the server. By the method, under the condition that file transmission fails, the client does not upload the file to the server endlessly, but uploads the file to the server again within the specified uploading times, so that network resources are saved, and the file transmission cannot be continuously occupied. In addition, the retransmission mechanism can also improve the success rate of file transmission.

Optionally, on the basis of the third embodiment corresponding to fig. 3, in a fifth optional embodiment of the method for uploading a file according to the embodiment of the present invention, before uploading a target file to a server according to file path information, the method may further include:

generating first signature information corresponding to a target file;

and carrying out integrity check on the target file, wherein the integrity check comprises the following steps:

receiving second signature information sent by the server, wherein the second signature information is generated by the server according to the target file;

if the second signature information is consistent with the first signature information, determining that the target file belongs to the integrity file;

and if the second signature information is inconsistent with the first signature information, determining that the target file belongs to the non-integrity file.

In this embodiment, the integrity of the target file needs to be checked, and specifically, the following verification methods are provided below.

The first method is that the target file uploaded by the client and the target file received by the server are directly compared, and if the target file is completely the same, the target file is considered to have no data loss in the transmission process.

In the second method, a parity check method is adopted, and one bit is additionally added in a byte in data storage and transmission to check errors. The check bits may be calculated by xoring the data bits.

And thirdly, performing Cyclic Redundancy Check (CRC) by utilizing the principles of division and remainder to detect errors. And (4) carrying out division operation on the received code group, and if the code group is completely divided, indicating that the transmission is correct. Otherwise, if not, it indicates that the transmission is in error.

And a fourth method, adopting a Message Digest Algorithm fifth version (MD 5) Algorithm, generating MD5 signature information of the complete target file, namely first signature information, before the client uploads the target file, and then sending the first signature information to the background server. After the target file is uploaded by the client, the server calculates the MD5 signature information, namely the second signature information, again, and if the first signature information is consistent with the second signature information, the target file is considered to have no data loss in the transmission process.

It is understood that the MD5 algorithm is mainly used for integrity check in the present invention, however, in practical applications, other suitable algorithms may also be used for integrity check, and the present invention is not limited herein.

In the embodiment of the present invention, the client may also generate first signature information corresponding to the target file, then the server generates second signature information according to the target file, and compares the consistency of the two signature information, and if the two signature information are consistent, it is determined that the data transmission is complete, otherwise, the target file acquired by the server is considered to be missing. Through the mode, the data integrity can be verified by adopting data verification, a verification value is usually calculated for original data by using a specified algorithm, a receiver calculates a verification value once by using the same algorithm, and if the verification values obtained by two times of calculation are the same, the data is complete. The method and the device prevent the program of the device from being tampered, and therefore the safety of file transmission is improved.

Optionally, on the basis of any one of the first to fifth embodiments corresponding to fig. 3 and fig. 3, in a sixth optional embodiment of the method for uploading a file provided in the embodiment of the present invention, before sending the file upload request to the server, the method may further include:

judging whether the first APP is abnormal or not, if so, triggering a file generation instruction, wherein the file generation instruction is used for indicating the first APP to generate a target file;

or the like, or, alternatively,

and acquiring an optional file from a storage area of the terminal device, wherein the optional file carries a first identifier, and if the first identifier is matched with a second identifier, determining that the first APP generates a target file, and the second identifier has a corresponding relation with the target file.

In this embodiment, after the client sends the file upload request to the server, it is further required to first determine whether the first APP has an abnormal condition, such as a downtime, a system crash, or an operation error. If the first APP is abnormal, the client can generate and trigger a file generation instruction, and certainly, the file generation instruction can also be generated by the first APP and then triggered by the client, so that the first APP generates a corresponding target file according to the file generation instruction. The client may then send a file upload request to the server.

In addition, the client may also find whether an optional file exists in the storage area of the terminal device, and if the optional file corresponds to the first identifier, match the first identifier with the second identifier of the target file, and if the optional file is matched without error, the optional file is the target file, so the client may extract the target file from the storage area of the terminal device and then send a file upload request to the server.

Further, in the embodiment of the present invention, a trigger condition for uploading a file is introduced, where one condition is to determine whether the first APP has an abnormal condition, and if so, the first APP generates a target file. And if the first identifier is matched with the second identifier, determining that the first APP generates the target file. By means of the method, whether the file needs to be uploaded or not can be accurately known, so that the success rate of file uploading is improved, and the feasibility of a scheme is improved.

Referring to fig. 6, a method for uploading a file according to the present invention will be described below from the perspective of a server, where another embodiment of the method for uploading a file according to the present invention includes:

201. if a first application program APP generates a target file to be uploaded, receiving a first file uploading request sent by a client, wherein the first file uploading request carries a unique device identifier, and the device identifier is used for associating APPs installed on the same terminal device;

It is understood that, in practical applications, the target file may be, in addition to the log file, an APK file, an INI file, a DOC file, or the like, and is not limited herein.

The client side sends a first file uploading request to the server after detecting the target file generated by the first APP, the first file uploading request carries the unique equipment identifier of the terminal equipment, and the server can determine other APPs installed on the same terminal equipment according to the equipment identifier.

202. Determining file path information according to the first file uploading request;

in this embodiment, the server determines, according to a first file upload request sent by the client, file path information belonging to a first APP, where it can be understood that the file path information may also be a common path, such as a path of a log file, and information such as log files uploaded by multiple different APPs is stored under the common path. The file path information may be a root directory, for example, "/time/Midas/Log/com.intent.test/Midas 20180101. txt", "com.intent.test" is a file package name, and the type of APP can be distinguished by the file package name.

203. If the second APP and the first APP are APPs on the same terminal device, sending file path information to the client when the second APP is started;

204. And receiving the target file sent by the client according to the file path information.

The embodiment of the invention provides a file uploading method, wherein if a first application program APP generates a target file to be uploaded, a server receives a first file uploading request sent by a client, wherein the first file uploading request carries a unique device identifier which is used for associating APPs installed on the same terminal device, file path information is determined according to the first file uploading request, when a second APP is started, the server sends the file path information to the client, and finally, the server can receive the target file sent by the client according to the file path information. Through the mode, the client associates the first APP with the second APP by using the unique equipment identifier, if the file generated by the first APP needs to be uploaded, the file can be uploaded when the second APP is started, the first APP is not required to be started again by a user, and therefore the file uploading efficiency is improved.

Optionally, on the basis of the embodiment corresponding to fig. 6, in a first optional embodiment of the method for uploading a file according to the embodiment of the present invention, before receiving the first file upload request sent by the client, the method may further include:

receiving an equipment identifier sent by a client, wherein the equipment identifier is generated by the client according to a first installation completion instruction, and the first installation completion instruction is obtained by the client after the first APP is installed;

after the second APP is installed, a second installation completion instruction sent by the client is received, wherein the second installation completion instruction carries the identifier to be identified;

the root sends file path information to the client, including:

and judging whether the identifier to be identified is consistent with the equipment identifier, if so, sending file path information to the client.

In this embodiment, when the client acquires the first installation completion instruction generated by the first APP, an only one device identifier may be generated according to the first installation completion instruction, where the device identifier is in one-to-one correspondence with the terminal device, and APPs belonging to the same terminal device all correspond to the same device identifier. The device identifier may specifically be a 32-bit string generated by the client, and may also be an identifier such as an IMEI or a MAC, which is not limited herein.

The client sends the device identification to the server. After the second APP is installed, the client generates an identifier to be identified, which is associated with the second APP, and then sends a second installation completion instruction to the server, where the identifier to be identified is carried in the second installation completion instruction. Whether the identification mark to be recognized corresponding to the second APP is consistent with the equipment identification corresponding to the first APP is judged by the server, if so, the first APP and the second APP belong to APPs installed on the same terminal equipment, and then the server can send file path information to the client.

Optionally, on the basis of the first embodiment corresponding to fig. 6 or fig. 6, in a second optional embodiment of the method for uploading a file provided in the embodiment of the present invention, after receiving the target file sent by the client according to the file path information, the method may further include:

receiving a second file uploading request sent by the client, wherein the second file uploading request carries an equipment identifier and is used for requesting a file to be uploaded;

judging whether the file to be uploaded is a target file which is uploaded or is being uploaded according to the second file uploading request;

and if the file to be uploaded is the target file which is uploaded or is being uploaded, refusing to send the file path information to the client.

In this embodiment, the client may further receive a second file upload request sent by the client in the subsequent, where the second file upload request carries the device identifier, and the server may determine, according to the second file upload request, whether the uploaded file is a target file that has been uploaded or is being uploaded, and if the target file is being uploaded or has been uploaded, the server does not issue file path information any more.

In the embodiment of the present invention, the server further receives a second file upload request sent by the client in the subsequent process, where the second file upload request carries the device identifier, and then the client determines, according to the second file upload request, whether the file to be uploaded is a target file that has been uploaded or is being uploaded, and if the file to be uploaded is the target file that has been uploaded or is being uploaded, the server refuses to send file path information to the client. By the mode, the same file can be prevented from being repeatedly uploaded, so that transmission resources are saved, the transmission efficiency is improved, and the operability of the scheme is enhanced.

For convenience of understanding, how the client uploads the file will be described below with reference to a specific flowchart, please refer to fig. 7, where fig. 7 is a schematic flowchart of a process for uploading a file by the client in an application scenario of the present invention, as shown in the figure:

in step a1, first, a user starts an APP on a terminal device;

in step a2, initializing the APP, wherein in the initialization process, a client integrated with the APP can call files generated by other APPs installed on the same terminal device;

in step A3, after initializing APPs, the client may determine whether X files generated by other APPs need to be uploaded to the server, if so, go to step a4, otherwise, go to step a 7;

in the step A4, the client judges whether the X file starts to be uploaded, if so, the client jumps to the step A7, otherwise, the client enters the step A5;

in step A5, the client establishes an upload connection with the server;

in step a6, if the server receives the complete X file, it indicates that the upload was successful;

in step a7, if the client determines that no X file needs to be uploaded, no processing may be performed;

in step A8, after establishing the communication connection between the client and the server, if the upload fails, the upload may be retried N times, where N is an integer greater than or equal to 1, and after all N attempts fail, the upload is not continued.

Referring to fig. 8, fig. 8 is a schematic flow chart illustrating how a server receives a file according to an application scenario of the present invention, where:

in step B1, the server may configure a file of a certain terminal device, for example, configure terminal device No. 1 to upload an X file;

in step B2, the server receives a file upload request from terminal device No. 1;

in step B3, the server issues an instruction to upload an X file to the client, so that the client uploads the generated X file according to the instruction;

in step B4, the server provides the client with an upload address, that is, file path information, so that the client can upload the X file to the server according to the upload address.

The scheme provides a file uploading scheme based on equipment representation, and a new strategy is provided for uploading files of APP or SDK by relying on mass mobile phone coverage of about 9 hundred million of 'Midas' SDK, so that files needing to be uploaded by inactive APP can be uploaded through active APP, and the success rate of file uploading is greatly improved.

Referring to fig. 9, fig. 9 is a schematic diagram of an embodiment of a client according to the present invention, where the client 30 includes:

a sending module 301, configured to send a file upload request to a server if a first application APP generates a target file to be uploaded, where the file upload request carries a unique device identifier, and the device identifier is used to associate APPs installed on the same terminal device;

a receiving module 302, configured to receive file path information sent by the server when a second APP is started if the second APP and the first APP are APPs on the same terminal device, where the file path information is determined by the server according to the file upload request sent by the sending module 301;

an uploading module 303, configured to upload the target file to the server according to the file path information received by the receiving module 302.

In this embodiment, if a first application APP generates a target file to be uploaded, the sending module 301 sends a file upload request to a server, where the file upload request carries a unique device identifier, the device identifier is used to associate APPs installed on the same terminal device, and if a second APP is the same as the first APP on the terminal device, when the second APP is started, the receiving module 302 receives file path information sent by the server, where the file path information is determined by the server according to the file upload request sent by the sending module 301, and the upload module 303 uploads the target file to the server according to the file path information received by the receiving module 302.

The embodiment of the invention provides a client for uploading files, wherein if a first application program APP generates a target file to be uploaded, the client sends a file uploading request to a server, wherein the file uploading request carries a unique device identifier which is used for associating the APPs installed on the same terminal device, when a second APP is started, the client can receive file path information sent by the server, the file path information is determined by the server according to the file uploading request, and finally, the client uploads the target file to the server according to the file path information. Through the mode, the client associates the first APP with the second APP by using the unique equipment identifier, if the file generated by the first APP needs to be uploaded, the file can be uploaded when the second APP is started, the first APP is not required to be started again by a user, and therefore the file uploading efficiency is improved.

Optionally, on the basis of the embodiment corresponding to fig. 9, please refer to fig. 10, in another embodiment of the client 30 provided in the embodiment of the present invention, the client 30 further includes a generating module 304;

the generating module 304 is configured to generate the device identifier according to the first installation completion instruction of the first APP obtained before the sending module 301 sends the file upload request to the server;

the sending module 301 is further configured to send the device identifier generated by the generating module 304 to the server;

after the second APP is installed, sending a second installation completion instruction to the server, wherein the second installation completion instruction carries an identifier to be identified;

the sending module 301 is specifically configured to receive the file path information sent by the server if the server determines that the identifier to be identified is consistent with the device identifier.

Optionally, on the basis of the embodiment corresponding to fig. 9, in another embodiment of the client 30 provided in the embodiment of the present invention,

the sending module 301 is further configured to send an application identifier to the server when a second APP is started if the second APP is the same as the first APP on the terminal device, so that the server determines that the target file belongs to the first APP according to the application identifier, where the application identifier and the first APP have a unique corresponding relationship.

Secondly, in the embodiment of the present invention, the client receives the application identifier sent by the server, so that the server determines that the target file belongs to the first APP according to the application identifier, wherein the application identifier and the first APP have a unique corresponding relationship. By means of the method, different APPs can be visually represented by the application identifiers, so that background operators can acquire the APP to which the file belongs more quickly, and the practicability and feasibility of the scheme are improved.

Optionally, on the basis of the embodiment corresponding to fig. 9, please refer to fig. 11, in another embodiment of the client 30 provided in the embodiment of the present invention, the client 30 further includes a determining module 305 and a verifying module 306;

the determining module 305 is configured to determine whether the target file is successfully uploaded after the uploading module 303 uploads the target file to the server according to the file path information;

the verifying module 306 is configured to perform integrity verification on the target file if the determining module 305 determines that the target file is successfully uploaded;

the uploading module 303 is further configured to, if the determining module 305 determines that the target file fails to be uploaded, upload the target file again according to a file retransmission rule.

Optionally, on the basis of the embodiment corresponding to fig. 11, in another embodiment of the client 30 provided in the embodiment of the present invention,

the uploading module 303 is specifically configured to stop uploading the target file to the server if the uploading frequency of the target file reaches a preset uploading frequency;

and if the uploading frequency of the target file does not reach the preset uploading frequency, continuing to upload the target file to the server.

the generating module 304 is further configured to generate first signature information corresponding to the target file before the uploading module 303 uploads the target file to the server according to the file path information;

the verification module 306 is specifically configured to receive second signature information sent by the server, where the second signature information is generated by the server according to the target file;

if the second signature information is consistent with the first signature information, determining that the target file belongs to an integrity file;

and if the second signature information is inconsistent with the first signature information, determining that the target file belongs to a non-integrity file.

Optionally, on the basis of the embodiments corresponding to fig. 9, fig. 10, or fig. 11, referring to fig. 12, in another embodiment of the client 30 provided in the embodiment of the present invention, the client 30 further includes an obtaining module 307;

the determining module 305 is further configured to determine whether the first APP has an abnormal condition before the sending module 301 sends a file upload request to a server, and if yes, trigger a file generation instruction, where the file generation instruction is used to instruct the first APP to generate the target file;

or the like, or, alternatively,

the obtaining module 307 is configured to obtain an optional file from the storage area of the terminal device before the sending module 301 sends a file upload request to a server, where the optional file carries a first identifier, and if the first identifier is matched with the second identifier, it is determined that the first APP generates the target file, and the second identifier and the target file have a corresponding relationship.

Having described the client in the present invention in detail, the server in the present invention will be described in detail below, referring to fig. 13, where fig. 13 is a schematic diagram of an embodiment of the server in the embodiment of the present invention, and the server 40 includes:

a receiving module 401, configured to receive a first file upload request sent by a client if a first application APP generates a target file to be uploaded, where the first file upload request carries a unique device identifier, and the device identifier is used to associate APPs installed on the same terminal device;

a determining module 402, configured to determine file path information according to the first file upload request received by the receiving module 401;

a sending module 403, configured to send the file path information determined by the determining module 402 to the client when a second APP is started if the second APP and the first APP are APPs on the same terminal device;

the receiving module 401 is further configured to receive the target file sent by the client according to the file path information.

In this embodiment, if a first application APP generates a target file to be uploaded, a receiving module 401 receives a first file upload request sent by a client, where the first file upload request carries a unique device identifier, the device identifier is used to associate APPs installed on the same terminal device, a determining module 402 determines file path information according to the first file upload request received by the receiving module 401, and if a second APP and the first APP are the same APP on the terminal device, a sending module 403 sends the file path information determined by the determining module 402 to the client when the second APP is started, and the receiving module 401 is further used to receive the target file sent by the client according to the file path information.

The embodiment of the invention provides a file uploading server, wherein if a first application program APP generates a target file to be uploaded, the server receives a first file uploading request sent by a client, wherein the first file uploading request carries a unique device identifier which is used for associating the APPs installed on the same terminal device, file path information is determined according to the first file uploading request, when a second APP is started, the server sends the file path information to the client, and finally, the server can receive the target file sent by the client according to the file path information. Through the mode, the client associates the first APP with the second APP by using the unique equipment identifier, if the file generated by the first APP needs to be uploaded, the file can be uploaded when the second APP is started, the first APP is not required to be started again by a user, and therefore the file uploading efficiency is improved.

Optionally, on the basis of the embodiment corresponding to fig. 13, in another embodiment of the server 40 provided in the embodiment of the present invention,

the receiving module 401 is further configured to receive an equipment identifier sent by a client before receiving a first file upload request sent by the client, where the equipment identifier is generated by the client according to a first installation completion instruction, and the first installation completion instruction is obtained by the client after the first APP is installed;

after the second APP is installed, receiving a second installation completion instruction sent by the client, wherein the second installation completion instruction carries an identifier to be identified;

the sending module 403 is specifically configured to determine whether the identifier to be identified is consistent with the device identifier, and if so, send the file path information to the client.

Optionally, on the basis of the embodiment corresponding to fig. 13, please refer to fig. 14, in another embodiment of the server 40 provided in the embodiment of the present invention, the server 40 further includes a determining module 404 and a rejecting module 405;

the receiving module 401 is further configured to receive a second file upload request sent by the client after receiving the target file sent by the client according to the file path information, where the second file upload request carries the device identifier, and the second file upload request is used to request a file to be uploaded;

the determining module 404 is configured to determine, according to the second file uploading request received by the receiving module 401, whether the file to be uploaded is the target file that has been uploaded or is being uploaded;

the rejecting module 405 is configured to reject to send the file path information to the client if the determining module 404 determines that the file to be uploaded is the target file that is already uploaded or is being uploaded.

As shown in fig. 15, for convenience of description, only the parts related to the embodiment of the present invention are shown, and details of the specific technology are not disclosed, please refer to the method part of the embodiment of the present invention. The client deploys and the terminal device, and the terminal device may be any terminal device including a mobile phone, a tablet computer, a Personal Digital Assistant (PDA), a point of sale (POS), a vehicle-mounted computer, and the like, taking the terminal as the mobile phone as an example:

fig. 15 is a block diagram showing a partial structure of a cellular phone related to a terminal provided by an embodiment of the present invention. Referring to fig. 15, the cellular phone includes: radio Frequency (RF) circuitry 510, memory 520, input unit 530, display unit 540, sensor 550, audio circuitry 560, wireless fidelity (WiFi) module 570, processor 580, and power supply 590. Those skilled in the art will appreciate that the handset configuration shown in fig. 15 is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.

The following describes each component of the mobile phone in detail with reference to fig. 15:

RF circuit 510 may be used for receiving and transmitting signals during information transmission and reception or during a call, and in particular, for processing downlink information of a base station after receiving the downlink information to processor 580; in addition, the data for designing uplink is transmitted to the base station. In general, RF circuit 510 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a Low Noise Amplifier (LNA), a duplexer, and the like. In addition, RF circuit 510 may also communicate with networks and other devices via wireless communication. The wireless communication may use any communication standard or protocol, including but not limited to global system for mobile communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), email, Short Message Service (SMS), etc.

The memory 520 may be used to store software programs and modules, and the processor 580 executes various functional applications and data processing of the mobile phone by operating the software programs and modules stored in the memory 520. The memory 520 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 520 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The input unit 530 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the cellular phone. Specifically, the input unit 530 may include a touch panel 531 and other input devices 532. The touch panel 531, also called a touch screen, can collect touch operations of a user on or near the touch panel 531 (for example, operations of the user on or near the touch panel 531 by using any suitable object or accessory such as a finger or a stylus pen), and drive the corresponding connection device according to a preset program. Alternatively, the touch panel 531 may include two parts, a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, and sends the touch point coordinates to the processor 580, and can receive and execute commands sent by the processor 580. In addition, the touch panel 531 may be implemented by various types such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. The input unit 530 may include other input devices 532 in addition to the touch panel 531. In particular, other input devices 532 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like.

The display unit 540 may be used to display information input by the user or information provided to the user and various menus of the mobile phone. The display unit 540 may include a display panel 541, and optionally, the display panel 541 may be configured in the form of a Liquid Crystal Display (LCD), an organic light-emitting diode (OLED), or the like. Further, the touch panel 531 may cover the display panel 541, and when the touch panel 531 detects a touch operation on or near the touch panel 531, the touch panel is transmitted to the processor 580 to determine the type of the touch event, and then the processor 580 provides a corresponding visual output on the display panel 541 according to the type of the touch event. Although the touch panel 531 and the display panel 541 are shown as two separate components in fig. 15 to implement the input and output functions of the mobile phone, in some embodiments, the touch panel 531 and the display panel 541 may be integrated to implement the input and output functions of the mobile phone.

The handset may also include at least one sensor 550, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display panel 541 according to the brightness of ambient light, and the proximity sensor may turn off the display panel 541 and/or the backlight when the mobile phone is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally, three axes), can detect the magnitude and direction of gravity when stationary, and can be used for applications of recognizing the posture of a mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer and tapping), and the like; as for other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which can be configured on the mobile phone, further description is omitted here.

Audio circuitry 560, speaker 561, and microphone 562 may provide an audio interface between a user and a cell phone. The audio circuit 560 may transmit the electrical signal converted from the received audio data to the speaker 561, and convert the electrical signal into a sound signal by the speaker 561 for output; on the other hand, the microphone 562 converts the collected sound signals into electrical signals, which are received by the audio circuit 560 and converted into audio data, which are then processed by the audio data output processor 580, and then passed through the RF circuit 510 to be sent to, for example, another cellular phone, or output to the memory 520 for further processing.

WiFi belongs to short distance wireless transmission technology, and the mobile phone can help the user to send and receive e-mail, browse web pages, access streaming media, etc. through the WiFi module 570, which provides wireless broadband internet access for the user. Although fig. 15 shows the WiFi module 570, it is understood that it does not belong to the essential constitution of the handset, and may be omitted entirely as needed within the scope not changing the essence of the invention.

The processor 580 is a control center of the mobile phone, connects various parts of the entire mobile phone by using various interfaces and lines, and performs various functions of the mobile phone and processes data by operating or executing software programs and/or modules stored in the memory 520 and calling data stored in the memory 520, thereby performing overall monitoring of the mobile phone. Alternatively, processor 580 may include one or more processing units; optionally, processor 580 may integrate an application processor, which handles primarily the operating system, user interface, applications, etc., and a modem processor, which handles primarily the wireless communications. It will be appreciated that the modem processor described above may not be integrated into processor 580.

The handset also includes a power supply 590 (e.g., a battery) for powering the various components, which may optionally be logically connected to the processor 580 via a power management system, such that the power management system may be used to manage charging, discharging, and power consumption.

Although not shown, the mobile phone may further include a camera, a bluetooth module, etc., which are not described herein.

In the embodiment of the present invention, the processor 580 included in the terminal further has the following functions:

Optionally, the processor 580 is further configured to perform the following steps:

after a first installation completion instruction of the first APP is acquired, generating the equipment identifier according to the acquired first installation completion instruction;

sending the device identification to the server;

processor 580 is specifically configured to perform the following steps:

and if the server determines that the identifier to be identified is consistent with the equipment identifier, receiving the file path information sent by the server.

and sending an application identifier to a server so that the server determines that the target file belongs to the first APP according to the application identifier, wherein the application identifier and the first APP have a unique corresponding relationship.

judging whether the target file is uploaded successfully or not;

and if the target file is failed to be uploaded, the target file is uploaded again according to a file retransmission rule.

Optionally, the processor 580 is specifically configured to perform the following steps:

generating first signature information corresponding to the target file;

processor 580 is specifically configured to perform the following steps:

judging whether the first APP is abnormal or not, if so, triggering a file generation instruction, wherein the file generation instruction is used for indicating the first APP to generate the target file;

or the like, or, alternatively,

and acquiring an optional file from a storage area of the terminal device, wherein the optional file carries a first identifier, and if the first identifier is matched with the second identifier, determining that the first APP generates the target file, and the second identifier and the target file have a corresponding relationship.

Fig. 16 is a schematic diagram of a server structure provided by an embodiment of the present invention, where the server 600 may have a relatively large difference due to different configurations or performances, and may include one or more Central Processing Units (CPUs) 622 (e.g., one or more processors) and a memory 632, and one or more storage media 630 (e.g., one or more mass storage devices) for storing applications 642 or data 644. Memory 632 and storage medium 630 may be, among other things, transient or persistent storage. The program stored in the storage medium 630 may include one or more modules (not shown), each of which may include a series of instruction operations for the server. Still further, the central processor 622 may be configured to communicate with the storage medium 630 and execute a series of instruction operations in the storage medium 630 on the server 600.

The server 600 may also include one or more power supplies 626, one or more wired or wireless network interfaces 650, one or more input-output interfaces 658, and/or one or more operating systems 641, such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, and so forth.

The steps performed by the server in the above embodiment may be based on the server structure shown in fig. 16.

In the embodiment of the present invention, the CPU 622 included in the server also has the following functions:

Optionally, the CPU 622 is also configured to perform the following functions:

receiving an equipment identifier sent by the client, wherein the equipment identifier is generated by the client according to a first installation completion instruction, and the first installation completion instruction is obtained by the client after the first APP is installed;

the CPU 622 is specifically configured to perform the following functions:

and judging whether the identifier to be identified is consistent with the equipment identifier, if so, sending the file path information to the client.

Optionally, the CPU 622 is also configured to perform the following functions:

receiving a second file uploading request sent by the client, wherein the second file uploading request carries the equipment identifier, and the second file uploading request is used for requesting a file to be uploaded;

judging whether the file to be uploaded is the target file which is uploaded or is being uploaded according to the second file uploading request;

Referring to fig. 17, fig. 17 is a schematic diagram of an embodiment of a file uploading system according to an embodiment of the present invention, and as shown in the figure, the file uploading system includes a client 701 and a server 702;

in this embodiment, if a first application APP generates a target file to be uploaded, the client 701 sends a file upload request to the server 702, where the file upload request carries a unique device identifier, the device identifier is used to associate APPs installed on the same terminal device, the server 702 determines file path information according to the first file upload request, and if a second APP and the first APP are the same APP on the terminal device, when the second APP is started, the server 702 sends the file path information to the client 701, and the client 701 uploads the target file to the server 702 according to the file path information.

In the embodiment of the invention, a file uploading system is provided, a client associates a first APP with a second APP by using a unique device identifier, if a file generated by the first APP needs to be uploaded, the file can be uploaded when the second APP is started, and a user does not need to wait for starting the first APP again, so that the file uploading efficiency is improved.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the embodiments provided in the present invention, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above-mentioned embodiments are only used for illustrating the technical solutions of the present invention, and not for limiting the same; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.

Claims

1. A method for uploading a file, comprising:

if the second APP and the first application program APP are APPs on the same terminal device, receiving file path information sent by the server when the second APP is started, wherein the file path information is determined by the server according to the file uploading request;

2. The method of claim 1, wherein prior to sending the file upload request to the server, the method further comprises:

after a first installation completion instruction of the first application program APP is acquired, generating the equipment identifier according to the acquired first installation completion instruction;

sending the device identification to the server;

the receiving of the file path information sent by the server includes:

3. The method of claim 1, wherein when said second APP is started, said method further comprises:

and sending an application identifier to the server so that the server determines that the target file belongs to the first application program APP according to the application identifier, wherein the application identifier and the first application program APP have a unique corresponding relationship.

4. The method of claim 1, wherein after uploading the target file to the server according to the file path information, the method further comprises:

judging whether the target file is uploaded successfully or not;

5. The method of claim 4, wherein the uploading the target file again according to the file retransmission rule comprises:

6. The method of claim 4, wherein prior to uploading the target file to the server according to the file path information, the method further comprises:

generating first signature information corresponding to the target file;

the integrity check of the target file includes:

7. The method of any of claims 1-6, wherein prior to sending the file upload request to the server, the method further comprises:

judging whether the first application program APP is abnormal or not, if so, triggering a file generation instruction, wherein the file generation instruction is used for indicating the first application program APP to generate the target file;

or the like, or, alternatively,

and acquiring an optional file from a storage area of the terminal device, wherein the optional file carries a first identifier, and if the first identifier is matched with a second identifier, determining that the first application program APP generates the target file, and the second identifier and the target file have a corresponding relationship.

8. A method for uploading a file, comprising:

if the second APP and the first application program APP are APPs on the same terminal device, when the second APP is started, the file path information is sent to the client;

9. The method of claim 8, wherein before receiving the first file upload request sent by the client, the method further comprises:

receiving an equipment identifier sent by the client, wherein the equipment identifier is generated by the client according to a first installation completion instruction, and the first installation completion instruction is obtained by the client after the installation of the first application program APP is completed;

the sending the file path information to the client includes:

10. The method according to claim 8 or 9, wherein after receiving the target file sent by the client according to the file path information, the method further comprises:

11. A client, comprising:

12. A server, comprising:

13. A client, the client comprising: a memory, a transceiver, a processor, and a bus system;

wherein the memory is used for storing programs;

uploading the target file to the server according to the file path information;

14. A server, characterized in that the server comprises: a memory, a transceiver, a processor, and a bus system;

wherein the memory is used for storing programs;

determining file path information according to the file uploading request;

if the second APP and the first application program APP are the APP on the same terminal device, the file path information is sent to the client when the second APP is started;

15. A computer-readable storage medium comprising instructions which, when executed on a computer, cause the computer to perform the method of any of claims 1 to 7, or perform the method of any of claims 8 to 10.