Method and apparatus for multi-device content sharing download

Abstract

The application relates to a method and device for multi-device content sharing and downloading. According to the method provided by the application, in the case that a client device logs in any account information, target downloading content input by a user can be received to generate a content downloading request and send the content downloading request to a server. After receiving the content downloading request, the server first carries out legality verification, and after the verification is passed, all client devices corresponding to the account information are acquired, and downloading metadata of the target downloading content is sent to all the client devices, so that the client devices receiving the downloading metadata start a content downloading task, thereby realizing collaborative content downloading of multiple client devices of the same account (account number), enabling the user to seamlessly switch between the multiple client devices, enjoying unified content and service experience, and saving time and energy of the user, and the user does not need to manually repeat the downloading process on each client device.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, and particularly relates to a multi-device content sharing download method and device. BACKGROUND

[0002] With the development of the Internet, a video application App (application program) has become one of indispensable entertainment ways for people. In order to facilitate users to view and enjoy the video or audio of interest at any time, the mainstream audio and video application App can realize the download of video content or audio information in the account login state. However, the current technical situation can only set the download in a single device, and cannot realize the collaborative content download in the multi-login devices of the same account. SUMMARY

[0003] The present application provides a multi-device content sharing download method and device to solve the problem that the current technical situation can only set the download in a single device, and cannot realize the collaborative content download in the multi-login devices of the same account.

[0004] In a first aspect, the present application provides a multi-device content sharing download method applied to a client device, and the method comprises the following steps.

[0005] In the case that the client device logs in any account information, a target download content input by a user from the account information is received to generate a content download request;

[0006] The content download request is sent to a server;

[0007] In the case that the server passes the legality verification of the content download request and determines all client devices corresponding to the account information, the download metadata of the target download content is sent to all client devices corresponding to the account information, and the download metadata of the target download content sent by the server is received;

[0008] A content download task is started according to the download metadata, and the download progress is synchronized to the server;

[0009] In the case that the content download task of any client device fails, a notification of the content download task failure of the client device sent by the server is received.

[0010] As an optional embodiment, the content download request is sent to the server, which comprises the following steps.

[0011] A network communication connection with the server is established through a preset request sending protocol;

[0012] sending a content download request to the server through the network communication connection.

[0013] As an optional embodiment, the method further comprises:

[0014] In case that the content download request is verified by the server, recording content download information, the content download information comprising device identification information of the client device, content identification information of the target download content, a time stamp and encryption information.

[0015] As an optional embodiment, the method further comprises:

[0016] In case that any of the client devices logs in the account information, obtaining a unique authentication identifier from the server through a preset authentication protocol to obtain login authorization authentication of the server;

[0017] sending device identification information of the client device, the account information and the corresponding unique authentication identifier to the server, so that the server stores the association of the device identification information, the account information and the corresponding unique authentication identifier.

[0018] In the second aspect, the application provides a multi-device content sharing download method applied to a server, the method comprising:

[0019] In case that any of the client devices logs in the account information, receiving a content download request from the client device, the content download request comprising target download content;

[0020] verifying the content download request for legitimacy;

[0021] After the content download request is verified, sending download metadata of the target download content to all client devices corresponding to the account information, so that all client devices corresponding to the account information start a content download task according to the download metadata;

[0022] receiving download progress of the content download task of all client devices corresponding to the account information;

[0023] In case that the content download task of any client device corresponding to the account information fails according to the download progress, sending a notification of content download task failure to all other client devices.

[0024] As an optional embodiment, the receiving a content download request from the client device in case that any of the client devices logs in the account information comprises:

[0025] In a case where any of the client devices logs in the account information, receiving a network communication connection request of the client device through a preset request sending protocol, to establish a network communication connection with the client;

[0026] Receiving a content download request of the client device through the network communication connection.

[0027] As an optional embodiment, the content download request further includes encryption information,

[0028] The legality verification of the content download request includes:

[0029] Obtaining the encryption information in the content download request;

[0030] Verifying the legality of the encryption information, to determine that the content download request is legal in a case where the encryption information is legal.

[0031] As an optional embodiment, after the content download request is verified, sending download metadata of the target download content to all client devices corresponding to the account information, includes:

[0032] After the content download request is verified, obtaining running system type information of the client device corresponding to any of the account information;

[0033] Determining a target push service protocol according to the running system type information of the client device;

[0034] Sending the download metadata of the target download content to the client device according to the target push service protocol.

[0035] As an optional embodiment, the method further includes:

[0036] In a case where any of the client devices logs in the account information, sending a unique authentication identifier to the client through a preset authentication protocol, to make the client device obtain login authorization authentication of the server;

[0037] Receiving device identifier information, the account information and the corresponding unique authentication identifier sent by the client device;

[0038] Establishing an association relationship of the device identifier information, the account information and the corresponding unique authentication identifier, to store the association relationship.

[0039] In a third aspect, the application provides a multi-device content sharing and downloading device applied to a client device, the device includes:

[0040] The first receiving module is configured to receive target download content input by a user from any account information of the client device to generate a content download request when the client device logs in the account information;

[0041] The first sending module is configured to send the content download request to a server;

[0042] The second receiving module is configured to receive download metadata of the target download content sent by the server when the server verifies the content download request and determines all client devices corresponding to the account information;

[0043] The progress synchronization module is configured to start a content download task according to the download metadata and synchronize a download progress to the server;

[0044] The third receiving module is configured to receive a notification of a content download task failure of any client device from the server when the content download task of the client device fails.

[0045] In a fourth aspect, the present application provides a device for multi-device content sharing and downloading, applied to a server, and the device comprises:

[0046] The fourth receiving module is configured to receive a content download request from the client device when the client device logs in any account information, and the content download request comprises target download content;

[0047] The legality verification module is configured to verify the legality of the content download request;

[0048] The second sending module is configured to send download metadata of the target download content to all client devices corresponding to the account information to enable all client devices corresponding to the account information to start a content download task according to the download metadata when the content download request is verified;

[0049] The fifth receiving module is configured to receive a download progress of the content download task of all client devices corresponding to the account information;

[0050] The third sending module is configured to send a notification of a content download task failure to all other client devices when the content download task of any client device corresponding to the account information fails according to the download progress.

[0051] Fifthly, this application provides an electronic device, comprising: at least one communication interface; at least one bus connected to the at least one communication interface; at least one processor connected to the at least one bus; and at least one memory connected to the at least one bus, wherein the processor is configured to:

[0052] When the client device is logged into any account information, it receives the target download content input by the user of that account information to generate a content download request;

[0053] Send the content download request to the server;

[0054] After the server verifies the legitimacy of the content download request and identifies all client devices corresponding to the account information, it sends the download metadata of the target download content to all client devices corresponding to the account information, and receives the download metadata of the target download content sent by the server.

[0055] The download task is initiated based on the download metadata, and the download progress is synchronized to the server.

[0056] If the content download task fails on any of the client devices, a notification of the content download task failure on that client device is received from the server.

[0057] or,

[0058] When the client device is logged into any account information, a content download request is received from the client device, and the content download request includes the target download content;

[0059] The legality of the content download request is verified;

[0060] After the content download request is verified, download metadata of the target download content is sent to all client devices corresponding to the account information, so that all client devices corresponding to the account information can start the content download task according to the download metadata;

[0061] Receive the download progress of the content download task from all client devices corresponding to the account information;

[0062] If, based on the download progress, it is determined that the content download task for any client device corresponding to any account information has failed, a notification of content download task failure is sent to all other client devices.

[0063] In a sixth aspect, the present application also provides a computer storage medium storing computer executable instructions for executing the method of multi-device content sharing download according to any one of the preceding aspects.

[0064] Compared with the prior art, the above technical solution provided by the embodiments of the present application has the following advantages: in the method provided by the embodiments of the present application, in the case that the client device logs in any account information, the target download content input by the user can be received to generate a content download request and send to the server. After receiving the content download request, the server first performs a legality verification, and after the verification is passed, all client devices corresponding to the account information are acquired, and the download metadata of the target download content is sent to all client devices, so that the client devices receiving the download metadata start the content download task, thereby realizing the collaborative content download of multiple client devices of the same account (account number). The user can seamlessly switch between multiple client devices to enjoy unified content and service experience, and the user can also save time and effort without manually repeating the download process on each client device. For enterprise users, it can ensure that the work materials are synchronized on all client devices to improve work efficiency and team collaboration. In addition, the task download progress of all client devices is synchronized to the server, which is uniformly managed by the server to update the task download progress of all client devices in time and notify the relevant client devices, so as to maintain the consistent experience of the user on all devices. BRIEF DESCRIPTION OF DRAWINGS

[0065] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and serve to explain the principles of the present application together with the specification.

[0066] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the accompanying drawings needed to be used in the embodiments or prior art description will be briefly introduced. Obviously, for those skilled in the art, other drawings can also be obtained based on these drawings without creative labor.

[0067] One or more embodiments are exemplarily illustrated by the pictures in the drawings corresponding thereto, and these exemplary illustrations do not constitute a limitation on the embodiments. Elements with the same reference numerals in the drawings represent similar elements, unless otherwise specified. The drawings in the drawings do not constitute a proportional limitation.

[0068] Figure 1 An interaction example diagram of the client device and the server provided by the embodiments of the present application;

[0069] Figure 2 One of the flowcharts of the method of multi-device content sharing download provided by the embodiments of the present application;

[0070] Figure 3 Fig. 2 is a flowchart illustrating a method for sharing and downloading content among multiple devices according to an embodiment of the present application;

[0071] Figure 4 Fig. 3 is a flowchart illustrating a method for sharing and downloading content among multiple devices according to an embodiment of the present application;

[0072] Figure 5 Fig. 4 is a flowchart illustrating a method for sharing and downloading content among multiple devices according to an embodiment of the present application;

[0073] Figure 6 Fig. 5 is a block diagram illustrating a device for sharing and downloading content among multiple devices according to an embodiment of the present application;

[0074] Figure 7 Fig. 6 is a block diagram illustrating a device for sharing and downloading content among multiple devices according to an embodiment of the present application;

[0075] Figure 8 Fig. 7 is a block diagram illustrating an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0076] In order to make the objects, technical solutions, and advantages of the embodiments of the present application clearer, the following will be used in conjunction with the accompanying drawings for a clear and complete description of the technical solutions of the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application and not all the embodiments. Based on the embodiments of the present application, all other embodiments obtained by a person of ordinary skill in the art without creative work fall within the scope of protection of the present application.

[0077] The following disclosure provides many different embodiments, or examples, for implementing different structures of the present application. For the purpose of simplification, the components and arrangements of the specific examples are described in the following. Of course, they are only examples and are not intended to limit the present application. In addition, reference numbers and / or letters can be repeated in different examples. Such repetition is for the purpose of simplification and clarity, and does not itself indicate a relationship between the various embodiments and / or arrangements discussed.

[0078] To solve the technical problem that only download setting can be performed on a single device in the prior art and the same account multiple login devices cannot realize collaborative content download, the application provides a multi-device content sharing download method and device, which can realize collaborative content download of multiple client devices of the same account (account), so that users can seamlessly switch between multiple client devices, enjoy unified content and service experience, save time and effort for users, and do not need to manually repeat the download process on each client device, and for enterprise users, work materials can be ensured to be synchronized on all client devices, improving work efficiency and team collaboration.

[0079] To enable those skilled in the art to clearly and accurately understand the technical solutions of the embodiments of the application, the technical solutions of the embodiments of the application are described in detail below with reference to the drawings.

[0080] Figure 1 An interactive example diagram of the client device and the server provided by the embodiments of the application.

[0081] In the embodiments of the application, a user can use one account information to log in to different client devices, for example, a mobile phone client, a tablet client or a personal computer, etc., such as client device 1 to client device n as shown in Figure 1 The account information logged in all client devices can be authenticated and managed by the server. When any client device (for example, client device 1) logs in the account information and performs content download, the server can determine all client devices logged in by the account information after receiving the content download request sent by the client device, and send download metadata to all client devices to start the download task, so as to realize collaborative content download of multiple client devices of the same account (account).

[0082] Figure 2 One of the flowcharts of the multi-device content sharing download method provided by the embodiments of the application. As shown in Figure 2 The multi-device content sharing download method provided by the embodiments of the application can be applied to a client device, and can specifically include the following steps:

[0083] Step 201, in the case that any account information is logged in on the client device, receiving target download content input by a user from the account information to generate a content download request.

[0084] The client device can be any smart electronic device such as a mobile phone, a tablet, a personal computer, etc., and each smart electronic device is installed with a client application. When any client device needs to download content, the corresponding account information can be logged in the client device, and a user graphical interface can be provided for the user to input the selection of target download content. After the client device receives the user input of the target download content, the client device can generate a content download request.

[0085] The content download request can include content identification information, device identification information, a timestamp, encryption information, etc.

[0086] Step 202, sending the content download request to the server.

[0087] The client device can establish a network communication connection with the server through a preset request sending protocol, such as the WebSocket protocol. After the network communication connection is established, the content download request is sent to the server.

[0088] Step 203, receiving the download metadata of the target download content sent by the server in the case that the server verifies the legality of the content download request and determines all client devices corresponding to the account information, and sends the download metadata of the target download content to all client devices corresponding to the account information.

[0089] After the server completes the legality verification of the content download request, the server determines all client devices corresponding to the account information, and all client devices receive the download metadata of the target download content sent by the server. The download metadata can include download links, file identifiers, download addresses (URL), etc.

[0090] Since the operating systems of each client device can be different, such as Android operating systems and IOS systems, different systems can establish a connection with the server through different protocols to receive the download metadata sent by the server. For example, for client devices with IOS systems, the Apple Push Notification Service (APNS) protocol can be used to receive the download metadata, and for client devices without IOS systems, the Firebase Cloud Messaging (FCM) protocol can be used to receive the download metadata.

[0091] In some embodiments, the client device further records the content download information after the server verifies the legality of the client device, wherein the content download information comprises device identification information of the client device, content identification information of the target download content, a timestamp and encryption information, so as to store and manage the content download information.

[0092] Step 204, starting the content download task according to the download metadata and synchronizing the download progress to the server.

[0093] After receiving the download metadata, the client device can start a local content download task according to the download metadata, download the file content matching the file identifier from the download address URL (such as a CDN (Content Delivery Network) or a cloud storage service), record the download progress, and synchronize the download progress to the server, so that the server can uniformly manage the download progress of all client devices.

[0094] Step 205, in the case that the content download task of any client device fails, receiving a notification of the content download task failure of the client device sent from the server.

[0095] In the case that the download progress of a certain client device stops or stops for more than a certain time range, it can be judged that the content download task of the client device fails, and a notification of the content download task failure of the client device sent from the server can be received.

[0096] In some embodiments, the server can uniformly manage the download status of each client device according to the download progress, including download creation, execution, suspension and cancellation, and synchronize the download status to each client device. The client device synchronizes the download status through the server, so as to keep the user consistent download experience on all client devices.

[0097] In some embodiments, the server can uniformly manage the download status of each client device according to the download progress, including download creation, execution, suspension and cancellation, and synchronize the download status to each client device. The client device synchronizes the download status through the server, so as to keep the user consistent download experience on all client devices. Figure 2 Based on the method embodiment shown in the figure, the present application further provides another optional embodiment. Figure 3 A flowchart of another method for multi-device content sharing download provided by an embodiment of the present application is shown in FIG. 6. As shown in the figure, the method for multi-device content sharing download provided by an embodiment of the present application can be applied to a client device and can specifically include the following steps: Figure 3 As shown in the figure, the method for multi-device content sharing download provided by an embodiment of the present application can be applied to a client device and can specifically include the following steps:

[0098] Step 301, in the case that any client device logs in the account information, obtaining a unique authentication identifier from the server through a preset authentication protocol to obtain the login authorization authentication of the server.

[0099] When logging in the same account information on each client device, the device identification information of the client device is registered and associated to the account information, and a unique authentication identifier is obtained from the server through a preset authentication protocol. For example, a unique Token authentication identifier can be obtained from the server using the JWT (JSON Web Tokens) protocol, so as to obtain the login authorization authentication of the server and ensure the login security of the client device.

[0100] In step 302, the device identification information of the client device, the account information, and the corresponding unique authentication identifier are sent to the server.

[0101] After obtaining the login authorization authentication of the server, the client device sends the device identification information, the account information, and the corresponding unique authentication identifier to the server, and the server stores and manages the association relationship among the device identification information, the account information, and the corresponding unique authentication identifier.

[0102] In step 303, the target download content input by the user from the account information is received to generate a content download request.

[0103] After the client device successfully logs in the account information, the target download content input by the user is received to generate a content download request. For details, refer to step 202 shown in Figure 2 For brevity, details are not repeated here.

[0104] In step 304, the content download request is sent to the server.

[0105] For details, refer to step 202 shown in Figure 2 For brevity, details are not repeated here.

[0106] In step 305, after the server verifies the legality of the content download request and determines all client devices corresponding to the account information, the download metadata of the target download content is received, which is sent by the server under the condition that the download metadata of the target download content is sent to all client devices corresponding to the account information.

[0107] After the client device is verified by the server, the server can determine all client devices corresponding to the account information through the association relationship among the device identification information, the account information, and the corresponding unique authentication identifier stored by the server, and send the download metadata. The client device receives the download metadata. For details, refer to step 203 shown in Figure 2 For brevity, details are not repeated here.

[0108] In step 306, the content download task is started according to the download metadata, and the download progress is synchronized to the server.

[0109] For details, refer toFigure 2 As shown in step 204, for brevity, details are not described herein.

[0110] Step 307, in case of failure of content download task of any client device, receiving the notification of failure of content download task of the client device sent from the server.

[0111] For details, please refer to Figure 2 As shown in step 205, for brevity, details are not described herein.

[0112] Correspondingly, the present application also provides related embodiments on the server side. Figure 4 A flowchart of a method for multi-device content sharing download provided by an embodiment of the present application is shown in Figure 3. As shown in Figure 3, the method for multi-device content sharing download provided by an embodiment of the present application can be applied to a server, and the method can include the following steps: Figure 4 As shown in Figure 3, the method for multi-device content sharing download provided by an embodiment of the present application can be applied to a server, and the method can include the following steps:

[0113] Step 401, in case of login of any account information of a client device, receiving the content download request from the client device.

[0114] As described above, the content download request can include target download content, such as content identification information of the target download content, and can also include device identification information, time stamp, encryption information, etc.

[0115] As an optional embodiment, a network communication connection request of a client device through a preset request sending protocol can be received to establish a network communication connection with the client, and the content download request of the client device can be received through the network communication connection. For example, the preset request sending protocol can be a WebSocket protocol.

[0116] Step 402, verifying the legality of the content download request.

[0117] The server can obtain the encryption information in the content download request, and verify the legality of the content download request through the legality verification of the encryption information. As understood by those skilled in the art, the client device and the server can be provided with matched encryption information, and the legality of the content download request can be confirmed through the matching confirmation of the encryption information.

[0118] In still other embodiments, in addition to the legality verification of the encryption information, it can also be verified whether the client device is authorized, such as whether the client device is legal through the identification information of the client device, and the legality of the download content can also be verified, and details are not described herein.

[0119] Step 403, after the content download request is verified, the download metadata of the target download content is sent to all client devices corresponding to the account information.

[0120] After the server confirms that the content download request is legal, it can find all client devices corresponding to the client. For example, it can push all client devices that have logged in the account information to the client device that sent the content download request, so that the user can select and determine to obtain more accurate client devices corresponding to the account information. Alternatively, the server can check the stored client devices and account information to confirm all client devices corresponding to the account information. The present application embodiment does not limit here.

[0121] After confirming all client devices that want to download the content, the system type information of each client device can be obtained, such as Android system, IOS system, etc. Then, the target push service protocol is determined according to the system type information of the client device, for example, Firebase Cloud Messaging (FCM) or Apple Push Notification Service (APNS). Firebase Cloud Messaging (FCM) can be used for the push of download metadata of client devices of non- IOS system, while Apple Push Notification Service (APNS) is used for the push of download metadata of client devices of IOS system.

[0122] Step 404, receive the download progress of the content download task of all client devices corresponding to the account information.

[0123] After the server sends the download metadata to all client devices, each client device will start a content download task (for example, download a content file from a URL address, such as accessing a CDN or a cloud storage service to obtain a content file) according to the download metadata, and start a download process. The server will receive the download process of each client device, and update the download status of all client devices according to the download process.

[0124] Step 405, in the case that the content download task of any client device corresponding to the account information fails according to the download progress, a notification of the failure of the content download task is sent to all other client devices.

[0125] The server can confirm the content download status of the client device according to the download progress, and for some download errors (progress stops or progress has stopped for a period of time), it can be judged that the content download task of the client device fails, and then the current download status (content download task fails) of the client device is notified to other client devices to keep the user consistent experience on all devices.

[0126] In Figure 4 Based on the method embodiment shown, the application embodiment further provides another method embodiment. Figure 5 A flowchart of a fourth method of multi-device content sharing download provided by the application embodiment. As Figure 5 The method of multi-device content sharing download of the application embodiment is applied to a server, which can include the following steps:

[0127] Step 501, in the case of logging in account information on any client device, a unique authentication identifier is sent to the client through a preset authentication protocol, so that the client device obtains the login authorization authentication of the server.

[0128] The preset authentication protocol is, for example, the JWT (JSON Web Tokens) protocol. The server can implement user (account information) authentication and authorization to ensure operation security. For example, the server can receive Token authentication (i.e. unique authentication identifier) of user account information login by using the JWT protocol, and when the user account information Token authentication is successful, the client device is successfully logged in and authorized, and the login authorization authentication of the client device is completed.

[0129] Step 502, receiving device identification information, account information and corresponding unique authentication identifier sent by the client device.

[0130] After completing the login authorization authentication of the client device, the client device and the server can be connected through communication, so that the server can receive the device identification information, account information and corresponding unique authentication identifier sent by the client device.

[0131] Step 503, establishing the association relationship of the device identification information, account information and corresponding unique authentication identifier, and storing the association relationship.

[0132] The server receives device identification information, account information, and unique authentication information sent by client devices for managing client devices. In one embodiment, the server can store device identification information and account information in a newly created database table named `user_device`. When a client device logs in with this account information, an association is established between the client device's device identification information and the account information, and this association is stored. In another embodiment, the server can store device identification information, account information, and a unique authentication identifier in a newly created database table named `user_device`. When a client device logs in with this account information and completes login authorization authentication through the server, an association is established between the device identification information, account information, and the corresponding unique authentication identifier, and this association is stored.

[0133] Step 504: Receive a content download request from the client device.

[0134] For details, please refer to [link / reference]. Figure 4 Step 401 shown will not be repeated here for the sake of brevity.

[0135] Step 505: Verify the legitimacy of the content download request.

[0136] For details, please refer to [link / reference]. Figure 4 Step 402 shown will not be repeated here for the sake of brevity.

[0137] Step 506: After the content download request is verified, send the download metadata of the target content to all client devices corresponding to the account information.

[0138] In one embodiment of this application, the server can obtain the association between device identification information, account information, and the corresponding unique authentication identifier by manipulating the user_device database table, thereby determining all client devices corresponding to the account information. Then, based on the client device, communication connection, etc., the server sends download metadata to the client device.

[0139] For more details, please refer to [link / reference]. Figure 4 Step 403 shown will not be repeated here for the sake of brevity.

[0140] Step 507: Receive the download progress of content download tasks for all client devices corresponding to the account information.

[0141] For details, please refer to [link / reference]. Figure 4 Step 404 shown will not be repeated here for the sake of brevity.

[0142] Step 508: If the download task for any client device corresponding to any account information fails based on the download progress, send a notification of content download task failure to all other client devices.

[0143] Specifically, see Figure 4 As shown in step 405, for brevity, it will not be repeated here.

[0144] It should be noted that the server in the embodiments of the present application can be a server device integrated with multiple functions, such as client device login authorization authentication, client device download request verification, responding to client device download request to provide download content file, etc. Alternatively, the server can also be multiple server devices, which respectively implement the functions of client device login authorization authentication, client device download request verification, responding to client device download request to provide download content file, etc. The embodiments of the present application do not limit this.

[0145] In summary, the method embodiment provided by the embodiments of the present application can receive the target download content input by the user to generate a content download request and send it to the server in the case that the client device logs in any account information. After receiving the content download request, the server will first perform a legality verification, and after the verification is passed, it will obtain all client devices corresponding to the account information and send the download metadata of the target download content to all client devices, so that the client devices receiving the download metadata start the content download task, thereby realizing the collaborative content download of multiple client devices of the same account (account number). The user can seamlessly switch between multiple client devices to enjoy unified content and service experience, and it also saves time and effort for the user, without the need to manually repeat the download process on each client device. For enterprise users, it can ensure that the work materials are synchronized on all client devices to improve work efficiency and team collaboration. In addition, all client devices synchronize the task download progress to the server, which is uniformly managed by the server to update the task download progress of all client devices in time and notify the relevant client devices, so as to maintain consistent experience for the user on all devices.

[0146] Correspondingly, the embodiments of the present application also provide device embodiments corresponding to the method embodiments. Figure 6 One of the structural block diagrams of a device for multi-device content sharing download provided by the embodiments of the present application is shown in FIG. 6. Figure 6 As shown in FIG. 6, the device for multi-device content sharing download provided by the embodiments of the present application is applied to a client device, which can include:

[0147] The first receiving module 601 is configured to receive the target download content input by the user from the account information to generate a content download request in the case that the client device logs in any account information.

[0148] The first sending module 602 is configured to send the content download request to the server.

[0149] The second receiving module 603 is configured to receive the download metadata of the target download content sent by the server in the case that the server determines that all the client devices corresponding to the account information after the server verifies the legality of the content download request, and sends the download metadata of the target download content to all the client devices corresponding to the account information.

[0150] The progress synchronization module 604 is configured to start a content download task according to the download metadata, and synchronize the download progress to the server.

[0151] The third receiving module 605 is configured to receive the notification of the content download task failure of the client device sent by the server in the case that the content download task of any one of the client devices fails.

[0152] Figure 7 FIG. 1 is a structural block diagram of one of the devices for multi-device content sharing and downloading provided by the embodiments of the present application. As shown in the figure, the device for multi-device content sharing and downloading provided by the embodiments of the present application is applied to a server, and the device can include: Figure 7

[0153] The fourth receiving module 701 is configured to receive the content download request from the client device in the case that the client device logs in any account information, and the content download request includes target download content.

[0154] The legality verification module 702 is configured to verify the legality of the content download request.

[0155] The second sending module 703 is configured to send the download metadata of the target download content to all the client devices corresponding to the account information after the content download request is verified, so that all the client devices corresponding to the account information start a content download task according to the download metadata.

[0156] The fifth receiving module 704 is configured to receive the download progress of the content download task of all the client devices corresponding to the account information.

[0157] The third sending module 705 is configured to send the notification of the content download task failure to all the other client devices in the case that the content download task of any one of the client devices corresponding to the account information fails according to the download progress.

[0158] ​In summary, the device embodiment provided by the embodiment of the application can receive the target download content input by the user to generate a content download request and send the content download request to the server in the case that the client device logs in any account information. The server performs legality verification after receiving the content download request, and obtains all client devices corresponding to the account information and sends the download metadata of the target download content to all client devices after the verification is passed, so that the client devices receiving the download metadata start the content download task, thereby realizing the collaborative content download of multiple client devices of the same account (account number), enabling the user to seamlessly switch between multiple client devices, enjoying unified content and service experience, saving time and energy for the user, and eliminating the need for the user to manually repeat the download process on each client device. For enterprise users, the working materials can be synchronized on all client devices to improve work efficiency and team collaboration. In addition, the task download progress of all client devices is synchronized to the server, which is uniformly managed by the server to update the task download progress of all client devices and notify the relevant client devices in a timely manner, so as to maintain the consistent experience of the user on all devices.

[0159] As shown in Figure 8 The embodiment of the application provides an electronic device, which comprises a processor 801, a communication interface 802, a memory 803 and a communication bus 804, wherein the processor 801, the communication interface 802 and the memory 803 complete mutual communication through the communication bus 804,

[0160] The memory 803 is used for storing a computer program.

[0161] In an embodiment of the application, the processor 801 is used for executing the program stored in the memory 803 to implement the method for sharing and downloading content of multiple devices provided by any one of the preceding method embodiments, which comprises the following steps.

[0162] In the case that the client device logs in any account information, the target download content input by the user from the account information is received to generate a content download request.

[0163] The content download request is sent to the server.

[0164] In the case that the server performs legality verification on the content download request and determines all client devices corresponding to the account information, the download metadata of the target download content sent by the server is received in the case that the download metadata of the target download content is sent to all client devices corresponding to the account information.

[0165] The content download task is started according to the download metadata, and the download progress is synchronized to the server.

[0166] In case that the content downloading task of any of the client devices fails, a notification of the content downloading task failure of the client device is received from the server.

[0167] Or comprising:

[0168] In case that the client device logs in any of the account information, a content downloading request is received from the client device, the content downloading request comprising target downloading content;

[0169] The content downloading request is verified for legitimacy;

[0170] After the content downloading request is verified, downloading metadata of the target downloading content is sent to all the client devices corresponding to the account information, so that all the client devices corresponding to the account information start content downloading tasks according to the downloading metadata;

[0171] The downloading progress of the content downloading tasks of all the client devices corresponding to the account information is received;

[0172] In case that the content downloading task of any of the client devices corresponding to the account information fails according to the downloading progress, a notification of the content downloading task failure is sent to all the other client devices.

[0173] The embodiment of the application further provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the steps of the method for multi-device content sharing and downloading provided by any one of the foregoing method embodiments.

[0174] The apparatus embodiments described above are merely illustrative, wherein the units described as separate components can or can not be physically separate, and the components displayed as units can or can not be physical units, i.e., can be located in one place, or can be distributed on multiple network units. Part or all of the modules can be selected according to actual needs to achieve the purpose of the embodiment scheme.

[0175] Through the description of the foregoing embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus a general hardware platform, and of course can also be implemented by hardware. Based on such understanding, the foregoing technical solutions essentially or in other words the part that contributes to the related art can be embodied in the form of a software product, which can be stored in a computer readable storage medium, such as a ROM / RAM, a magnetic disk, an optical disk, etc., and includes a plurality of instructions to make a computer device (which can be a personal computer, a server, or a network device, etc.) execute the methods described in each embodiment or some parts of the embodiments.

[0176] It is to be understood that the terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The terms "comprises", "comprising", "includes", "including" and "has" are inclusive and therefore specify the presence of stated features, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof. The method steps, processes, and operations described herein are not to be construed as necessarily requiring their performance in the particular order

[0177] The above description is that of current embodiments of the application. Various modifications and changes can be made thereto without departing from the spirit and scope of the application as set forth. The scope of the application is not to be limited to the specific illustrative embodiments therein but only by the claims.

Claims

1. A method for multi-device content sharing and downloading, characterized in that, Applied to a client device, the method includes: When the client device is logged into any account information, it receives the target download content input by the user of that account information to generate a content download request; Send the content download request to the server; After the server verifies the legitimacy of the content download request and identifies all client devices corresponding to the account information, it sends the download metadata of the target download content to all client devices corresponding to the account information. In this case, the server receives the download metadata of the target download content sent by the server, wherein all client devices corresponding to all account information receive the download metadata sent by the server and start the content download task. The download task is initiated based on the download metadata, and the download progress is synchronized to the server. If the content download task of any of the client devices fails, a notification of the content download task failure of that client device is received from the server, wherein the download status of all client devices corresponding to the account information remains consistent.

2. The method according to claim 1, characterized in that, Sending the content download request to the server includes: A network communication connection is established with the server using a preset request sending protocol; A content download request is sent to the server via the network communication connection.

3. The method according to claim 1, characterized in that, The method further includes: If the server verifies the content download request, it records the content download information, which includes the device identification information of the client device, the content identification information of the target download content, a timestamp, and encryption information.

4. The method according to claim 1, characterized in that, The method further includes: When the account information is logged in on any of the client devices, a unique authentication identifier is obtained from the server through a preset authentication protocol to obtain login authorization authentication from the server; The device identification information of the client device, the account information, and the corresponding unique authentication identifier are sent to the server so that the server stores the association between the device identification information, the account information, and the corresponding unique authentication identifier.

5. A method for multi-device content sharing and downloading, characterized in that, Applied to a server, the method includes: When the client device is logged into any account information, a content download request is received from the client device, and the content download request includes the target download content; The legality of the content download request is verified; After the content download request is verified, download metadata of the target download content is sent to all client devices corresponding to the account information, so that all client devices corresponding to the account information can start the content download task according to the download metadata; Receive the download progress of the content download task from all client devices corresponding to the account information; If, based on the download progress, it is determined that the content download task for any client device corresponding to any account information has failed, a notification of content download task failure is sent to all other client devices.

6. The method according to claim 5, characterized in that, The step of receiving a content download request from the client device when any account information is logged in on the client device includes: When the client device logs in to any account information, it receives a network communication connection request from the client device through a preset request sending protocol in order to establish a network communication connection with the client. The network communication connection is used to receive content download requests from the client device.

7. The method according to claim 5, characterized in that, The content download request also includes encrypted information. The legality verification of the content download request includes: Obtain the encrypted information from the content download request; By verifying the legitimacy of the encrypted information, the content download request can be determined to be legitimate if the encrypted information is found to be legitimate.

8. The method according to claim 5, characterized in that, After the content download request is verified, the download metadata of the target download content is sent to all client devices corresponding to the account information, including: After the content download request is verified, obtain the operating system type information of the client device corresponding to any of the account information; The target push service protocol is determined based on the operating system type information of the client device; Download metadata of the target download content is sent to the client device in accordance with the target push service protocol.

9. The method according to claim 5, characterized in that, The method further includes: When any of the client devices logs in to the account information, a unique authentication identifier is sent to the client through a preset authentication protocol so that the client device can obtain login authorization authentication from the server; Receive device identification information, account information, and the corresponding unique authentication identifier from the client device; Establish an association between the device identification information, the account information, and the corresponding unique authentication identifier, and store the association.

10. A device for multi-device content sharing and downloading, characterized in that, Applied to a client device, the device includes: The first receiving module is used to receive the target download content input by the user of any account information when the client device is logged in, so as to generate a content download request; The first sending module is used to send the content download request to the server; The second receiving module is configured to receive the download metadata of the target download content sent by the server after the server has verified the legality of the content download request and determined all client devices corresponding to the account information, and then sends the download metadata of the target download content to all client devices corresponding to the account information. In this case, all client devices corresponding to all account information receive the download metadata sent by the server and start the content download task. The progress synchronization module is used to start a content download task based on the download metadata and synchronize the download progress to the server; The third receiving module is used to receive a notification from the server that the content download task of any of the client devices has failed, wherein the download status of all client devices corresponding to the account information remains consistent.

11. A device for multi-device content sharing and downloading, characterized in that, Applied to a server, the device includes: The fourth receiving module is used to receive a content download request from the client device when the client device is logged into any account information, the content download request including the target download content; The legitimacy verification module is used to verify the legitimacy of the content download request; The second sending module is used to send the download metadata of the target download content to all client devices corresponding to the account information after the content download request is verified, so that all client devices corresponding to the account information can start the content download task according to the download metadata; The fifth receiving module is used to receive the download progress of the content download task of all client devices corresponding to the account information; The third sending module is used to send a notification of content download task failure to all other client devices if the content download task of any client device corresponding to any account information fails based on the download progress.

Images