Method and apparatus for resuming interrupted transmission, server and storage medium

Abstract

The application relates to the technical field of breakpoint resuming, in particular to a breakpoint resuming method and device, a server and a storage medium, wherein the method comprises the following steps: identifying whether a receiving end is replaced when a uploading end performs breakpoint resuming; if the receiving end is not replaced, uploading a file for breakpoint resuming; and if the receiving end has been replaced, uploading the file for breakpoint resuming and a file before breakpoint resuming. Therefore, the problems that the uploading end and the receiving end are fixed, the uploading function cannot be normally used when the receiving end is replaced, and the applicability is low in the prior art are solved.

Description

Technical Field

[0001] This application relates to the field of breakpoint resume technology, and in particular to a breakpoint resume method, apparatus, server and storage medium. Background Technology

[0002] Resumable downloads involve dividing the download or upload task (a file or a compressed package) into several parts, with each part being uploaded or downloaded using a separate thread. If a network failure occurs, the upload or download can resume from the already uploaded or downloaded portion, rather than starting from scratch.

[0003] In related technologies, the upload and download ends of breakpoint resume download are closely linked. When the upload and download ends are fixed, and the download end changes, the upload function may not work properly. Taking the video upload scenario of the car infotainment system as an example, the car infotainment system is the upload end and the cloud drive is the download end. If the upload entry of the car infotainment system is fixed with a certain cloud drive provider, it will be very passive in future operations. Due to the complexity of OTA upgrades of car infotainment system software, it will be difficult to adapt to the already sold car infotainment systems when changing cloud drive providers, resulting in low applicability. Summary of the Invention

[0004] This application provides a method, apparatus, server, and storage medium for resuming interrupted downloads, in order to solve the problems in related technologies where the upload and receive ends are fixed, resulting in the upload function not working properly when the receiver is replaced, and the applicability is low.

[0005] The first aspect of this application provides a method for resuming interrupted downloads. The method is applied to a server, which is located between an uploader and a receiver. The method includes the following steps: identifying whether the receiver has changed when the uploader performs a resumed download; if the receiver has not changed, uploading the file to be resumed; if the receiver has changed, uploading both the file to be resumed and the file before the resumed download.

[0006] Optionally, identifying whether the receiving end has changed when the uploading end performs a breakpoint resume includes: obtaining the current identifier of the corresponding receiving end when the uploading end performs a breakpoint resume; obtaining the current authentication identifier of the corresponding receiving end when the uploading end performs a breakpoint resume; obtaining the original authentication identifier of the corresponding receiving end before the uploading end performs a breakpoint resume, and determining whether the current authentication identifier is consistent with the original authentication identifier; if they are consistent, it is determined that the receiving end has not changed; otherwise, it is determined that the receiving end has been changed.

[0007] Optionally, before identifying whether the receiving end has changed when the uploading end performs a breakpoint resume transmission, the method further includes: obtaining the device identifier of the uploading end; authenticating the uploading end based on the device identifier, and receiving the file from the uploading end after successful authentication.

[0008] Optionally, the file to be resumed from the breakpoint and the file before the breakpoint resume are both one or more data blocks.

[0009] Optionally, the receiving end can aggregate and integrate all files uploaded by the uploading end into an original file.

[0010] A second aspect of this application provides a device for resuming interrupted downloads. The device is applied to a server, which is located between an uploader and a receiver. The device includes: an identification module for identifying whether the receiver has changed when the uploader performs a resumed download; a first upload module for uploading the resumed file if the receiver has not changed; and a second upload module for uploading both the resumed file and the file before the resumed download if the receiver has changed.

[0011] Optionally, the identification module is further configured to: obtain the current authentication identifier of the corresponding receiving end when the uploading end performs breakpoint resume; obtain the original authentication identifier of the corresponding receiving end before the uploading end performs breakpoint resume, and determine whether the current authentication identifier is consistent with the original authentication identifier; if they are consistent, determine that the receiving end has not been changed, otherwise determine that the receiving end has been changed.

[0012] Optionally, the identification module is further configured to: obtain the device identifier of the uploading end; authenticate the uploading end according to the device identifier, and after successful authentication, receive the file that was interrupted and resumed from the uploading end.

[0013] Optionally, the file to be resumed from the breakpoint and the file before the breakpoint resume are both one or more data blocks.

[0014] Optionally, the receiving end can aggregate and integrate all files uploaded by the uploading end into an original file.

[0015] A third aspect of this application provides a server, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the breakpoint resume method as described in the above embodiments.

[0016] A fourth aspect of this application provides a computer-readable storage medium having a computer program stored thereon, which is executed by a processor to implement the breakpoint resume method as described in the above embodiments.

[0017] Therefore, this application has at least the following beneficial effects:

[0018] This application embodiment sets up a server between the uploading end and the receiving end, using the server as a relay station for resuming interrupted file transfers between the uploading end and the receiving end. The server can upload the current remaining interrupted file and the interrupted file cached before the interrupted transfer to the receiving end when it detects that the receiving end has changed when the uploading end starts resuming the interrupted transfer. Otherwise, it continues to upload the interrupted file. Through the interaction between the server and the uploading end and the receiving end, the uploading end and the receiving end are decoupled, so that the uploading end can adapt to different receiving ends without affecting the integrity of the interrupted file, and the applicability is high.

[0019] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0020] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein:

[0021] Figure 1 This is a flowchart illustrating the adaptation process between the vehicle-mounted system and the cloud storage according to embodiments of this application.

[0022] Figure 2 This is a flowchart of a breakpoint resume method provided according to an embodiment of this application;

[0023] Figure 3 This is a flowchart of a method for resuming interrupted transmissions to multiple receiving ends, provided according to an embodiment of this application.

[0024] Figure 4 This is a schematic diagram illustrating the decoupling of the upload and receive ends of a server according to an embodiment of this application;

[0025] Figure 5 A schematic diagram illustrating the adaptation of an uploader to a modified receiver according to an embodiment of this application;

[0026] Figure 6 This is an example diagram of a breakpoint resume device provided according to an embodiment of this application;

[0027] Figure 7 This is a schematic diagram of the structure of a server according to an embodiment of this application. Detailed Implementation

[0028] The embodiments of this application are described in detail below. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0029] like Figure 1 As shown, in existing technologies, the adaptation files for the vehicle-mounted system can be directly uploaded to the cloud storage service provider. The vehicle-mounted system and the cloud storage provider are tightly bound together. Before binding, the vehicle-mounted system and the cloud storage need to be adapted first. First, after checking that its network conditions are good, the vehicle-mounted system directly obtains the authentication identifier of the cloud storage and adapts to the cloud storage based on the authentication identifier. After receiving the interrupted and resumed file, the cloud storage aggregates and integrates it into the original file. However, the uploader and receiver are closely connected. When the uploader is fixed and the receiver's entry point changes, the upload function will not work properly, resulting in low applicability.

[0030] Therefore, this application decouples the uploader and receiver by using a server, enabling the uploader to adapt to different receivers without affecting the integrity of the file after interruption, thus making it highly applicable.

[0031] The following description, with reference to the accompanying drawings, outlines a method, apparatus, server, and storage medium for resuming interrupted downloads according to embodiments of this application. Specifically, Figure 2 This is a flowchart illustrating a breakpoint resume method provided in an embodiment of this application.

[0032] like Figure 2 As shown, this breakpoint resume method is applied to a server, which is positioned between the uploader and receiver. The method includes the following steps:

[0033] In step S101, it is identified whether the receiving end has been changed when the uploading end performs a breakpoint resume transmission.

[0034] It is understood that, through the interaction between the server and the uploading and receiving ends, the embodiments of this application can identify whether the receiving end has changed when the uploading end performs a breakpoint resume, so that the server can subsequently upload breakpoint resume files to adapt to the changes in the receiving end according to the actual situation.

[0035] In this embodiment of the application, before identifying whether the receiving end has changed when the uploading end performs a breakpoint resume, the method further includes: obtaining the device identifier of the uploading end; authenticating the uploading end based on the device identifier, and receiving the file resumed from the uploading end after successful authentication.

[0036] The device identifier can be the VIN (Vehicle Identification Number) code from the vehicle terminal or the mobile terminal, and can be adjusted according to the actual situation without specific limitations.

[0037] It is understood that in this application embodiment, the device identifier of the uploading end is obtained so that the server can authenticate the uploading end, and after successful authentication, the server can receive the endpoint resume file uploaded by the uploading end so that the server can subsequently upload the endpoint resume file to the receiving end.

[0038] In this embodiment of the application, identifying whether the receiving end has been changed when the uploading end performs a breakpoint resume includes: obtaining the current authentication identifier of the corresponding receiving end when the uploading end performs a breakpoint resume; obtaining the original authentication identifier of the corresponding receiving end before the uploading end performs a breakpoint resume, and checking whether the current authentication identifier is consistent with the original authentication identifier; if they are consistent, it is determined that the receiving end has not been changed, otherwise it is determined that the receiving end has been changed.

[0039] The current authentication identifier can be abc_auth+abc_date+abc_bs, which corresponds to the signature identifier, timestamp identifier, and business identifier, without specific limitations.

[0040] It is understood that, in this embodiment of the application, the current authentication identifier and the original authentication identifier of the corresponding receiving end are consistent when the uploading end performs a breakpoint resume transmission to determine whether the receiving end has been changed, so as to adapt the file to the change of the receiving end for subsequent uploading of breakpoint resume transmission according to the actual situation.

[0041] It should be noted that in practical applications, the uploading end needs to provide an authentication identifier sent by the server to the receiving end. The receiving end needs to fill in the corresponding content of the updated authentication identifier. For example, if the receiving end is cloud disk provider A, the content of the authentication identifier is: vehicle_cloud_auth+vehicle_cloud_date. If the receiving end changes, the content of the authentication identifier changes to: abc_auth+abc_date+abc_bs, so that the re-upload of files can be adapted to the changes of the receiving end according to the current actual needs of the upload endpoint.

[0042] In step S102, if the receiving end has not been changed, the file that was interrupted and resumed is uploaded.

[0043] It is understandable that, in this embodiment of the application, after determining that the receiving end has not been changed, the interrupted file continues to be uploaded to the receiving end until all interrupted files are uploaded to the receiving end, so that the receiving end can subsequently summarize and integrate all files uploaded by the uploading end into the original file.

[0044] In step S103, if the receiving end has been changed, the file that was interrupted and resumed is uploaded, along with the file before the interruption and resumed.

[0045] In this context, both the file to be resumed and the file before the resumed download consist of one or more data blocks.

[0046] It is understood that if the receiving end has been changed in this embodiment, the file to be resumed after the breakpoint and the file before the breakpoint are uploaded to ensure that the receiving end receives the complete file to be resumed after the breakpoint.

[0047] It should be noted that while receiving the resumed file from the uploader, the server caches the resumed file in the database so that when the receiving end is changed later, the file before the resumed file is directly uploaded to the receiving end.

[0048] In this embodiment of the application, the receiving end summarizes and integrates all the files uploaded by the uploading end into the original file.

[0049] It is understood that in this embodiment of the application, the receiving end summarizes and integrates all files uploaded by the uploading end into the original file to ensure the integrity of the file for resuming interrupted transmission.

[0050] It should be noted that in this application, when uploading a file that can be resumed after interruption, the uploader can bind the task number or sequence number to different data blocks so that when the receiving end summarizes the data, it can be arranged according to the order of the task number or sequence number and integrated into a complete file.

[0051] According to the breakpoint resume method proposed in the embodiments of this application, the server can upload the current remaining breakpoint resume file and the cached breakpoint resume file to the receiving end when it detects that the receiving end has changed when the uploader resumes the breakpoint. Otherwise, it continues to upload the breakpoint resume file. Through the interaction between the server and the uploader and the receiving end, the uploader can be decoupled from the receiving end, so that the uploader can adapt to different receiving ends without affecting the integrity of the breakpoint resume file, and the applicability is high.

[0052] The following will combine Figures 3 to 5 The method for resuming interrupted downloads in this application is described in detail below:

[0053] Step 1: Determine network conditions and the type of file to be uploaded.

[0054] The system monitors network status in real time. When the network is stable, it determines if there are files to be uploaded. If so, it further determines whether the file type is a resumed file or a new file. If the transmission is interrupted due to network failure or poor network conditions during the upload process, the system can resume uploading or downloading from the already uploaded or downloaded portion, without having to start uploading or downloading from the beginning again, thus ensuring transmission efficiency.

[0055] Step 2: The server interacts with both the uploader and the receiver to adapt to both the uploader and the downloader.

[0056] The uploading end uploads the authentication identifier and device identifier to the server. The server forwards them to the receiving end and receives the device identifier and authentication identifier content sent by the receiving end. If the authentication identifier is changed, it means that the receiving end has been changed, and the server confirms the compatible uploading end and receiving end based on the changed authentication identifier. If the authentication identifier is not changed, it means that the current receiving end has not been changed.

[0057] It should be noted that the adaptation service interacts with the file receiving service, providing the upload entry information and authentication identifier required by the uploader, as follows: Upload entry parameter: needDealUrl; Part size parameter: partSize; Upload task number: uploadId; Signature identifier parameter to be added to the authentication request header: vehicle_cloud_auth; Timestamp identifier parameter to be added to the authentication request header: vehicle_cloud_date; The uploader preloads the upload entry information and header authentication identifier before uploading, and the adaptation service obtains the signature and timestamp values ​​from the receiving end.

[0058] Specifically, such as Figure 4 and Figure 5 As shown, when cloud disk vendor A is the receiving end, the authentication identifier is vehicle_cloud_auth+vehicle_cloud_date. However, when the receiving end is changed from cloud disk vendor A to cloud disk vendor B, the authentication identifier changes to abc_auth+abc_date+abc_bs. Therefore, the authentication identifier is used to determine whether the receiving end has changed.

[0059] Step 3: Upload the file to be uploaded to the receiving end.

[0060] If the file to be uploaded is a new file, it will be divided into chunks according to the chunk size in the entry information, and the chunks will be bound to the corresponding task numbers in sequence. The server will then forward the file to the receiving end. After receiving the file, the receiving end will check whether all chunks have been uploaded completely by checking the task numbers, and then aggregate all the files into the original file. It should be noted that during the process of forwarding the file upload, the server also caches the uploaded file data in the local database to prevent the need to re-upload the file if the network is interrupted.

[0061] If the file to be uploaded is a file that can be resumed after interruption, the server needs to determine the remaining files that can be resumed after interruption, and retrieve the previously cached files that can be resumed after interruption from the local database. These files are then merged and uploaded to the receiving end, where they are summarized.

[0062] Next, the interrupted transmission resume device proposed according to the embodiments of this application is described with reference to the accompanying drawings.

[0063] Figure 6 This is a block diagram of the breakpoint resume device according to an embodiment of this application.

[0064] like Figure 6 As shown, the interrupted resume transmission device 10 is applied to a server, which is located between the uploading end and the receiving end. The device includes: an identification module 100, a first uploading module 200, and a second uploading module 300.

[0065] The identification module 100 is used to identify whether the receiving end has changed when the uploading end performs a resume upload; the first uploading module 200 is used to upload the resumed file if the receiving end has not changed; the second uploading module 300 is used to upload both the resumed file and the file before the resume upload if the receiving end has changed.

[0066] In this embodiment of the application, the identification module is further used to: obtain the current identifier of the corresponding receiving end when the uploading end performs breakpoint resume; obtain the original identifier of the corresponding receiving end before the uploading end performs breakpoint resume, and determine whether the current identifier is consistent with the original identifier; if they are consistent, it is determined that the receiving end has not been changed, otherwise it is determined that the receiving end has been changed.

[0067] In this embodiment of the application, the identification module is further used to: obtain the correspondence between the upload end and the receiver; determine the receiver corresponding to the upload end according to the correspondence, and identify the current identifier of the corresponding receiver.

[0068] In this embodiment of the application, the identification module is further configured to: obtain the authentication identifier of the uploader; authenticate the uploader according to the authentication identifier, and after successful authentication, receive the file that was interrupted and resumed from the uploader.

[0069] In this embodiment of the application, the file to be resumed after a breakpoint and the file before the breakpoint resume are both one or more data blocks.

[0070] In this embodiment of the application, the receiving end summarizes and integrates all the files uploaded by the uploading end into the original file.

[0071] It should be noted that the foregoing explanation of the breakpoint resume method embodiment also applies to the breakpoint resume device of this embodiment, and will not be repeated here.

[0072] According to the breakpoint resume transmission device proposed in the embodiments of this application, the server can upload the current remaining breakpoint resume transmission file and the cached breakpoint resume transmission file to the receiving end when it detects that the receiving end has changed when the upload end resumes the transmission. Otherwise, it continues to upload the breakpoint resume transmission file. Through the interaction between the server and the upload end and the receiving end, the upload end can be decoupled from the receiving end, so that the upload end can adapt to different receiving ends without affecting the integrity of the breakpoint resume transmission file, and the applicability is high.

[0073] Figure 7 A schematic diagram of the structure of a server provided in an embodiment of this application. The server may include:

[0074] The memory 701, the processor 702, and the computer program stored on the memory 701 and executable on the processor 702.

[0075] When the processor 702 executes the program, it implements the breakpoint resume method provided in the above embodiments.

[0076] Furthermore, the vehicle also includes:

[0077] Communication interface 703 is used for communication between memory 701 and processor 702.

[0078] The memory 701 is used to store computer programs that can run on the processor 702.

[0079] The memory 701 may include high-speed RAM (Random Access Memory) memory, and may also include non-volatile memory, such as at least one disk storage.

[0080] If the memory 701, processor 702, and communication interface 703 are implemented independently, then the communication interface 703, memory 701, and processor 702 can be interconnected via a bus to complete communication between them. The bus can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 7 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0081] Optionally, in a specific implementation, if the memory 701, processor 702, and communication interface 703 are integrated on a single chip, then the memory 701, processor 702, and communication interface 703 can communicate with each other through an internal interface.

[0082] The processor 702 may be a CPU (Central Processing Unit), an ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement the embodiments of this application.

[0083] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the above-described breakpoint resume method.

[0084] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0085] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "N" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0086] Any process or method described in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or N executable instructions for implementing custom logic functions or processes, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0087] It should be understood that the various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, the N steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or more of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (FPGAs), field-programmable gate arrays (FPGAs), etc.

[0088] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0089] Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of this application.

Claims

1. A method for resuming interrupted downloads, characterized in that, The method is applied to a server, which is positioned between the uploading end and the receiving end. The method includes the following steps: The method for identifying whether the receiving end has changed when the uploading end performs a breakpoint resume transmission includes: obtaining the current authentication identifier of the corresponding receiving end when the uploading end performs a breakpoint resume transmission; obtaining the original authentication identifier of the corresponding receiving end before the uploading end performs a breakpoint resume transmission, and comparing whether the current authentication identifier is consistent with the original authentication identifier; if they are consistent, it is determined that the receiving end has not changed; otherwise, it is determined that the receiving end has been changed. If the receiving end has not been changed, then upload the file that was interrupted and resumed. If the receiving end has been changed, upload the file that was interrupted and resumed, as well as the file before the interruption and resumed.

2. The method according to claim 1, characterized in that, Before identifying whether the receiving end has changed when the uploading end performs a resume download, the process also includes: Obtain the device identifier of the upload end; The uploader is authenticated based on the device identifier, and the file is received from the uploader after interruption and resumption upon successful authentication.

3. The method according to claim 1, characterized in that, The file to be resumed from the breakpoint and the file before the breakpoint resume are both one or more data blocks.

4. The method according to claim 1, characterized in that, The receiving end aggregates and integrates all files uploaded by the uploading end into the original file.

5. A device for resuming interrupted downloads, characterized in that, The device is applied to a server, which is positioned between the uploading end and the receiving end, wherein the device includes: An identification module is used to identify whether the receiving end has been changed when the uploading end performs a breakpoint resume transmission. The identification module is further used to: obtain the current authentication identifier of the corresponding receiving end when the uploading end performs a breakpoint resume transmission; obtain the original authentication identifier of the corresponding receiving end before the uploading end performs a breakpoint resume transmission, and determine whether the current authentication identifier is consistent with the original authentication identifier; if they are consistent, it is determined that the receiving end has not been changed; otherwise, it is determined that the receiving end has been changed. The first upload module is used to upload files that can be resumed from interruption if the receiving end has not been changed. The second upload module is used to upload the file that was interrupted and resumed, as well as the file before the interruption and resumed, if the receiving end has been changed.

6. The apparatus according to claim 5, characterized in that, The identification module is further used for: Obtain the device identifier of the upload end; The uploader is authenticated based on the device identifier, and the file is received from the uploader after interruption and resumption upon successful authentication.

7. A server, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, the processor executing the program to implement the breakpoint resume method as described in any one of claims 1-4.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, The program is executed by the processor to implement the breakpoint resume method as described in any one of claims 1-4.

Images