Method and device for sharing and downloading contents of multiple devices

Abstract

The invention relates to a multi-device content sharing downloading method and device, through the method provided by the embodiment of the invention, under the condition 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 the content downloading request is sent to a server; after receiving the content downloading request, the server firstly performs legality verification, obtains all client devices corresponding to the account information after the verification is passed, and sends downloading metadata of the target downloading content to all the client devices, so that the client devices receiving the downloading metadata start a content downloading task; therefore, collaborative content downloading of a plurality of client devices of the same account (account) is realized, a user can seamlessly switch among the plurality of client devices and enjoy unified content and service experience, time and energy can be saved for the user, and the downloading process does not need to be manually repeated on each client device.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a method and apparatus for sharing and downloading content on multiple devices. Background Art

[0002] With the development of the Internet, video application Apps (Applications) have become one of the indispensable entertainment methods for people. In order to facilitate users to view and enjoy videos or audios of their interest at any time, mainstream video and audio application Apps can now download video content or audio information when the account is logged in. However, the current technical status can only perform download settings on a single device, and cannot achieve collaborative content downloads on multiple devices logged in with the same account. Summary of the invention

[0003] The present application provides a method and apparatus for shared downloading of content on multiple devices, in order to solve the problem that the current technical status quo can only perform download settings on a single device, and cannot realize collaborative content downloading on multiple devices logged in with the same account.

[0004] In a first aspect, the present application provides a method for multi-device content sharing and downloading, which is applied to a client device, and the method includes:

[0005] In the case where the client device logs in to any account information, receiving target download content input by a user of the account information to generate a content download request;

[0006] Sending the content download request to the server;

[0007] After the server verifies the legitimacy of the content download request and determines all the client devices corresponding to the account information, in the case where the server sends the download metadata of the target download content to all the client devices corresponding to the account information, receiving the download metadata of the target download content sent by the server;

[0008] Initiate a content download task according to the download metadata, and synchronize the download progress to the server;

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

[0010] As an optional embodiment, sending the content download request to the server includes:

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

[0012] A content download request is sent to the server via the network communication connection.

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

[0014] In the case that the server successfully verifies the content download request, content download information is recorded, where the content download information includes the device identification information of the client device, the content identification information of the target download content, a timestamp, and encryption information.

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

[0016] When any of the client devices logs in to the account information, a unique authentication identifier is obtained from the server through a preset authentication protocol to obtain login authorization authentication from the server;

[0017] 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 relationship among the device identification information, the account information and the corresponding unique authentication identifier.

[0018] In a second aspect, the present application provides a method for multi-device content sharing and downloading, which is applied to a server, and the method includes:

[0019] In the case where the client device logs in to any account information, receiving a content download request from the client device, the content download request including target download content;

[0020] Performing legitimacy verification on the content download request;

[0021] 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, so that all client devices corresponding to the account information start the content download task according to the download metadata;

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

[0023] When it is determined according to the download progress that the content download task of any client device corresponding to the account information fails, a notification of content download task failure is sent to all other client devices.

[0024] As an optional embodiment, when the client device logs in any account information, receiving a content download request from the client device includes:

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

[0026] A content download request from the client device is received via the network communication connection.

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

[0028] The verifying the legitimacy of the content download request includes:

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

[0030] By verifying the legality of the encrypted information, if it is determined that the encrypted information is legal, it is determined that the content download request is legal.

[0031] As an optional embodiment, after the content download request is verified, sending the 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 the operating system type information of the client device corresponding to any of the account information;

[0033] Determine the target push service protocol according to the operating system type information of the client device;

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

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

[0036] 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 obtains login authorization authentication from the server;

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

[0038] An association relationship between the device identification information, the account information and the corresponding unique authentication identification is established to store the association relationship.

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

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

[0041] A first sending module, used for sending the content download request to the server;

[0042] A second receiving module is used to receive the download metadata of the target download content sent by the server when the server sends the download metadata of the target download content to all the client devices corresponding to the account information after the server passes the legitimacy verification of the content download request and determines all the client devices corresponding to the account information;

[0043] A progress synchronization module, used to start the content download task according to the download metadata, and synchronize the download progress to the server;

[0044] The third receiving module is used for receiving a notification of failure of the content downloading task of any of the client devices sent by the server when the content downloading task of the client device fails.

[0045] In a fourth aspect, the present application provides a device for sharing and downloading content on multiple devices, which is applied to a server, and the device includes:

[0046] A fourth receiving module, configured to receive a content download request from a client device when the client device logs in to any account information, wherein the content download request includes target download content;

[0047] A legality verification module, used to verify the legality of the content download request;

[0048] A 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 start the content download task according to the download metadata;

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

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

[0051] In a fifth aspect, the present 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; at least one memory connected to the at least one bus, wherein the processor is configured to:

[0052] In the case where the client device logs in to any account information, receiving target download content input by a user of the account information to generate a content download request;

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

[0054] After the server verifies the legitimacy of the content download request and determines all the client devices corresponding to the account information, in the case where the server sends the download metadata of the target download content to all the client devices corresponding to the account information, receiving the download metadata of the target download content sent by the server;

[0055] Initiate a content download task according to the download metadata, and synchronize the download progress to the server;

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

[0057] or,

[0058] In the case where the client device logs in to any account information, receiving a content download request from the client device, the content download request including target download content;

[0059] Performing legitimacy verification on the content download request;

[0060] 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, so that all client devices corresponding to the account information start the content download task according to the download metadata;

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

[0062] When it is determined according to the download progress that the content download task of any client device corresponding to the account information fails, a notification of content download task failure is sent to all other client devices.

[0063] In a sixth aspect, the present application further provides a computer storage medium storing computer executable instructions, wherein the computer executable instructions are used to execute the method for multi-device content sharing and downloading as described in any one of the above items of the present application.

[0064] The above technical solution provided by the embodiment of the present application has the following advantages over the prior art: the method provided by the embodiment of the present application, when the client device logs in to any account information, can receive the target download content input by the user to generate a content download request and send it to the server. After receiving the content download request, the server will first perform a legitimacy verification, and after the verification is passed, 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 device that receives the download metadata starts the content download task, thereby realizing the collaborative content download of multiple client devices of the same account (account number), so that users can seamlessly switch between multiple client devices and enjoy a unified content and service experience, and can also save time and energy for users, without having to manually repeat the download process on each client device, and for enterprise users, it can ensure that work materials are synchronized on all client devices, 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, and the task download progress of all client devices is updated in time and the relevant client devices are notified to ensure that users have a consistent experience on all devices. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0066] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0067] One or more embodiments are exemplarily described by pictures in the corresponding drawings, and these exemplified descriptions do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings represent similar elements, and unless otherwise stated, the figures in the drawings do not constitute proportional limitations.

[0068] Figure 1 An example diagram of the interaction between a client device and a server provided in an embodiment of the present application;

[0069] Figure 2 One of the flowcharts of a method for sharing and downloading content on multiple devices provided in an embodiment of the present application;

[0070] Figure 3 A second flowchart of a method for sharing and downloading content on multiple devices provided in an embodiment of the present application;

[0071] Figure 4 A third flowchart of a method for sharing and downloading content on multiple devices provided in an embodiment of the present application;

[0072] Figure 5 A fourth flowchart of a method for sharing and downloading content on multiple devices provided in an embodiment of the present application;

[0073] Figure 6 One of the structural block diagrams of an apparatus for sharing and downloading content on multiple devices provided in an embodiment of the present application;

[0074] Figure 7 A second structural block diagram of an apparatus for sharing and downloading content on multiple devices provided in an embodiment of the present application;

[0075] Figure 8 A structural block diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0076] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0077] The disclosure below provides many different embodiments or examples to realize the different structures of the present application. In order to simplify the disclosure of the present application, the parts and settings of specific examples are described below. Of course, they are only examples, and the purpose is not to limit the present application. In addition, the present application can repeat reference numbers and / or letters in different examples. This repetition is for the purpose of simplification and clarity, and does not itself indicate the relationship between the various embodiments and / or settings discussed.

[0078] In order to solve the technical problem that the prior art can only perform download settings on a single device and cannot achieve collaborative content downloading on multiple login devices with the same account, the present application provides a method and apparatus for multi-device content shared downloading, which can achieve collaborative content downloading on multiple client devices of the same account (account number), allowing users to seamlessly switch between multiple client devices and enjoy a unified content and service experience. It can also save users time and energy without having to manually repeat the download process on each client device. For enterprise users, it can ensure that work data is synchronized on all client devices, thereby improving work efficiency and team collaboration.

[0079] In order to enable those skilled in the art to clearly and accurately understand the technical solutions of the embodiments of the present application, the technical solutions of the embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0080] Figure 1 An example diagram of the interaction between a client device and a server provided in an embodiment of the present application.

[0081] In the embodiment of the present application, a user can use one account information to log in to different client devices, and the different client devices can be, for example, a mobile client, a tablet client, or a personal computer, etc. Figure 1 The client devices 1 to n shown in the figure, and all client devices that have been logged in by the account information can be authenticated and managed by the server. When any client device (such as client device 1) logs in the account information and downloads content, the server can determine all client devices that have been 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, so that all client devices start the download task, thereby realizing collaborative content download by multiple client devices of the same account (account number).

[0082] Figure 2 This is one of the flow charts of a method for sharing and downloading content on multiple devices provided in an embodiment of the present application. Figure 2 As shown, a method for sharing and downloading content on multiple devices in an embodiment of the present application is applied to a client device and may specifically include the following steps:

[0083] Step 201 : When a client device logs in to any account information, a target download content input by a user of the account information is received to generate a content download request.

[0084] The client device can be any intelligent electronic device such as a mobile phone, a tablet, a personal computer, etc., and each intelligent electronic device has a client application installed on it. When any client device needs to download content, the corresponding account information can be logged in on the client device, and a user graphical interface is provided for the user to input and select the target download content. After receiving the target download content input by the user, the client device can generate a content download request.

[0085] The content download request may include, for example, content identification information, device identification information, a timestamp, encryption information, and the like.

[0086] Step 202: Send a content download request to the server.

[0087] The client device may establish a network communication connection with the server through a preset request sending protocol, wherein the preset request sending protocol may be, for example, the WebSocket protocol, and after the network communication connection is established, send a content download request to the server.

[0088] Step 203, after the server verifies the legitimacy of the content download request and determines 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.

[0089] After the server completes the legality verification of the content download request, and after the server determines all the client devices corresponding to the account information, all the client devices receive the download metadata sent by the server for the target download content. The download metadata may include, for example, the download link, file identifier, download address URL (Uniform Resource Locator) and other information.

[0090] Since the operating system of each client device may be different, for example, some are Android operating systems, and some are IOS systems, different systems establish connections with the server through different protocols to receive the download metadata sent by the server. For example, for client devices of the IOS system, the download metadata is received through the Apple Push Notification Service (APNS) protocol, and for non-IOS system clients, the download metadata can be received through the Firebase Cloud Messaging (FCM) protocol.

[0091] In other embodiments, after the server verifies its legitimacy, the client device also needs to record content download information, wherein the content download information includes the device identification information of the client device, the 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: Start the content download task according to the download metadata, and synchronize the download progress to the server.

[0093] After receiving the download metadata, the client device can start a local content download task based on the download metadata, download the file content matching the file identifier from the download address URL (such as CDN (Content Delivery Network) or 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: When the content download task of any client device fails, a notification of the failure of the content download task of the client device sent by the server is received.

[0095] When the download progress of a certain client device stops or stops for more than a certain time range, it can be determined that the content download task of the client device has failed, and a notification of the failure of the content download task of the client device sent by 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, thereby maintaining a consistent download experience for the user on all client devices.

[0097] exist Figure 2 Based on the method embodiment shown, the present application also provides another optional embodiment. Figure 3 The second flowchart of a method for sharing and downloading content on multiple devices provided in an embodiment of the present application is shown in FIG. Figure 3 As shown, a method for sharing and downloading content on multiple devices in an embodiment of the present application is applied to a client device and may specifically include the following steps:

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

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

[0100] Step 302: Send the device identification information, account information and corresponding unique authentication identifier of the client device to the server.

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

[0102] Step 303: receiving target download content input by the user from the account information to generate a content download request.

[0103] After the client device successfully logs in the account information, it receives the target download content entered by the user, thereby generating a content download request. Figure 2 For the sake of brevity, step 201 is not described again here.

[0104] Step 304: Send a content download request to the server.

[0105] For details, please refer to Figure 2 For the sake of brevity, step 202 is not described again here.

[0106] Step 305: After the server verifies the legitimacy of the content download request and determines all client devices corresponding to the account information, the server 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.

[0107] After the client device verifies the legitimacy of the content download request through the server, the server can determine all client devices corresponding to the account information through the association between the device identification information, account information and the corresponding unique authentication identifier stored in it, and send the download metadata. The client device receives the download metadata. For details, please refer to Figure 2 Step 203 is shown and will not be described again for the sake of brevity.

[0108] Step 306: Start the content download task according to the download metadata, and synchronize the download progress to the server.

[0109] For details, please refer to Figure 2 Step 204 is shown and will not be described again for the sake of brevity.

[0110] Step 307: When the content download task of any client device fails, a notification of the failure of the content download task of the client device sent by the server is received.

[0111] For details, please refer to Figure 2 Step 205 is shown and will not be described again for the sake of brevity.

[0112] Correspondingly, the embodiments of the present application also provide relevant embodiments on the server side. Figure 4 The third flowchart of a method for sharing and downloading content on multiple devices provided in an embodiment of the present application is shown in FIG. Figure 4 As shown, a method for sharing and downloading content on multiple devices in an embodiment of the present application is applied to a server, and the method may include the following steps:

[0113] Step 401: When the client device logs in to any account information, a content download request from the client device is received.

[0114] As mentioned above, the content download request may include target download content, such as content identification information of the target download content, and may also include device identification information, timestamp, encryption information, etc.

[0115] As an optional embodiment, a network communication connection request from a client device via a preset request sending protocol may be received to establish a network communication connection with the client, and then a content download request from the client device may be received via the network communication connection. The preset request sending protocol may be, for example, the WebSocket protocol.

[0116] Step 402: Verify the legitimacy of the content download request.

[0117] The server can obtain the encrypted information in the content download request and determine the legitimacy of the content download request by verifying the legitimacy of the encrypted information. It can be understood by those skilled in the art that matching encrypted information can be set in the client device and the server, and the legitimacy of the content download request can be confirmed by matching confirmation of the encrypted information.

[0118] In some other embodiments, in addition to verifying the legitimacy of encrypted information, it is also possible to verify whether the client device has obtained authentication authorization, such as confirming whether the client device is legitimate through the identification information of the client device, and the legitimacy of the downloaded content can also be verified, which will not be repeated here.

[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 confirming that the content download request is legitimate, the server can search for all client devices corresponding to the client. For example, the server can push all client devices that have been logged in by the account information history to the client device that sent the content download request for the user to select and confirm, so as to obtain the client device corresponding to the more accurate account information. Optionally, the server can check the stored client device and account information to confirm all client devices corresponding to the account information. The embodiments of the present application are not limited here.

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

[0122] Step 404: Receive the download progress of the content download tasks 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 the content download task (for example, download the content file from the URL address, such as accessing the CDN or cloud storage service to obtain the content file) according to the download metadata, and start the download process. The server will receive the download progress of each client device and update the download status of all client devices according to the download progress.

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

[0125] The server can confirm the content download status of the client device based on the download progress. For some download errors (progress stops or the progress has been stopped for a period of time), it may be determined that the content download task of the client device has failed, and then the current download status of the client device (content download task failure) is notified to other client devices to ensure that the user has a consistent experience on all devices.

[0126] exist Figure 4 Based on the method embodiment shown, the embodiment of the present application also provides another method embodiment. Figure 5 The fourth flowchart of a method for sharing and downloading content on multiple devices provided in an embodiment of the present application is shown in FIG. Figure 5 As shown, a method for sharing and downloading content on multiple devices in an embodiment of the present application is applied to a server, and the method may include the following steps:

[0127] Step 501: When any client device 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 obtains login authorization authentication from 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 operational security. For example, the server can use the JWT protocol to receive the token authentication (i.e., unique authentication identifier) ​​of the user account information login. When the user account information token authentication is successful, the client device is successfully logged in and authorized, completing the login authorization authentication of the client device.

[0129] Step 502: Receive device identification information, account information and a corresponding unique authentication identifier sent from a 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: Establish an association relationship between the device identification information, the account information and the corresponding unique authentication identification to store the association relationship.

[0132] The server receives the device identification information, account information and unique authentication information sent by the client device for managing the client device. As an embodiment of the present application, the server can create a new database table user_device to store the device identification information and account information. When the account information has a client device logged in, the device identification information of the client device is associated with the account information and stored. As another embodiment of the present application, the server can create a new database table user_device to store the device identification information, account information and unique authentication identifier. When the account information has a client device logged in and the server login authorization authentication is performed, the association relationship between the device identification information, account information and the corresponding unique authentication identifier is established to store the association relationship.

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

[0134] For details, please refer to Figure 4 Step 401 shown is not described again for the sake of brevity.

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

[0136] For details, please refer to Figure 4 Step 402 is shown and will not be described again for the sake of brevity.

[0137] Step 506: 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.

[0138] As an embodiment of the present application, the server can obtain the association between device identification information, account information and the corresponding unique authentication identifier by operating the database table user_device, thereby determining all client devices corresponding to the account information, and then send download metadata to the client device according to the client device, communication connection, etc.

[0139] For other details, see Figure 4 Step 403 is shown and will not be described again for the sake of brevity.

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

[0141] For details, please refer to Figure 4 Step 404 is shown and will not be described again for the sake of brevity.

[0142] Step 508: When it is determined according to the download progress that the content download task of any client device corresponding to the account information fails, a notification of content download task failure is sent to all other client devices.

[0143] For details, please refer to Figure 4 Step 405 is shown and will not be described again for the sake of brevity.

[0144] It should be noted that the server in the embodiment of the present application can be a server device that integrates multiple functions, such as client device login authorization authentication, client device download request verification, responding to client device download request to provide download content files, etc. Optionally, the server can also be multiple server devices that respectively implement client device login authorization authentication, client device download request verification, responding to client device download request to provide download content files, etc. The embodiment of the present application does not limit this.

[0145] In summary, the method embodiment provided in the embodiment of the present application can receive the target download content input by the user when the client device logs in to any account information to generate a content download request and send it to the server. After receiving the content download request, the server will first perform a legitimacy verification, and after the verification is passed, 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 device that receives the download metadata starts the content download task, thereby realizing the collaborative content download of multiple client devices of the same account (account number), so that users can seamlessly switch between multiple client devices and enjoy a unified content and service experience, and can also save time and energy for users, without having to manually repeat the download process on each client device, and for enterprise users, it can ensure that work materials are synchronized on all client devices, 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, and the task download progress of all client devices is updated in time and the relevant client devices are notified to ensure that users have a consistent experience on all devices.

[0146] Correspondingly, the embodiments of the present application also provide embodiments of devices corresponding to the method embodiments. Figure 6 This is one of the structural block diagrams of a device for sharing and downloading content on multiple devices provided in an embodiment of the present application. Figure 6 As shown, a device for sharing and downloading content on multiple devices in an embodiment of the present application is applied to a client device, and the device may include:

[0147] The first receiving module 601 is used to receive target download content input by a user from any account information when the client device logs in to the account information, so as to generate a content download request;

[0148] A first sending module 602, configured to send the content download request to a server;

[0149] The second receiving module 603 is used to receive the download metadata of the target download content sent by the server when the server sends the download metadata of the target download content to all the client devices corresponding to the account information after the server verifies the legitimacy of the content download request and determines all the client devices corresponding to the account information;

[0150] A progress synchronization module 604 is used to start the 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 a notification of failure of the content downloading task of any of the client devices sent by the server when the content downloading task of the client device fails.

[0152] Figure 7 This is one of the structural block diagrams of a device for sharing and downloading content on multiple devices provided in an embodiment of the present application. Figure 7 As shown, a device for sharing and downloading content on multiple devices in an embodiment of the present application is applied to a server, and the device may include:

[0153] The fourth receiving module 701 is used to receive a content download request from a client device when the client device logs in any account information, wherein the content download request includes target download content;

[0154] A legality verification module 702, used to verify the legality of the content download request;

[0155] The second sending module 703 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 start the content download task according to the download metadata;

[0156] A fifth receiving module 704, configured to receive the download progress of the content download task of all client devices corresponding to the account information;

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

[0158] In summary, the device embodiment provided by the embodiment of the present application can receive the target download content input by the user when the client device logs in to any account information to generate a content download request and send it to the server. After receiving the content download request, the server will first perform a legitimacy verification, and after the verification is passed, 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 device that receives the download metadata starts the content download task, thereby realizing the collaborative content download of multiple client devices of the same account (account number), so that users can seamlessly switch between multiple client devices and enjoy a unified content and service experience, and can also save time and energy for users, without having to manually repeat the download process on each client device. For enterprise users, it can ensure that work materials are synchronized on all client devices, 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, and the task download progress of all client devices is updated in time and the relevant client devices are notified to ensure that users have a consistent experience on all devices.

[0159] like Figure 8 As shown, an embodiment of the present application provides an electronic device, including 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 communicate with each other through the communication bus 804.

[0160] Memory 803, used for storing computer programs;

[0161] In one embodiment of the present application, the processor 801 is configured to execute a program stored in the memory 803 to implement any one of the aforementioned method embodiments to provide a method for sharing and downloading content on multiple devices, including:

[0162] In the case where the client device logs in to any account information, receiving target download content input by a user of the account information to generate a content download request;

[0163] Sending the content download request to the server;

[0164] After the server verifies the legitimacy of the content download request and determines all the client devices corresponding to the account information, in the case where the server sends the download metadata of the target download content to all the client devices corresponding to the account information, receiving the download metadata of the target download content sent by the server;

[0165] Initiate a content download task according to the download metadata, and synchronize the download progress to the server;

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

[0167] Or include:

[0168] In the case where the client device logs in to any account information, receiving a content download request from the client device, the content download request including target download content;

[0169] Performing legitimacy verification on the content download request;

[0170] 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, so that all client devices corresponding to the account information start the content download task according to the download metadata;

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

[0172] When it is determined according to the download progress that the content download task of any client device corresponding to the account information fails, a notification of content download task failure is sent to all other client devices.

[0173] An embodiment of the present application also provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps of a method for multi-device content sharing and downloading provided by any of the aforementioned method embodiments are implemented.

[0174] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0175] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a general hardware platform, and of course, by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the relevant technology can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

[0176] It should be understood that the terms used herein are only for the purpose of describing specific example embodiments and are not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms "one", "an" and "said" as used herein may also be meant to include plural forms. The terms "include", "comprise", "contain", and "have" are inclusive, and therefore specify the existence of stated features, steps, operations, elements and / or parts, but do not exclude the existence or addition of one or more other features, steps, operations, elements, parts, and / or combinations thereof. The method steps, processes, and operations described herein are not interpreted as necessarily requiring them to be performed in the specific order described or illustrated, unless the execution order is clearly indicated. It should also be understood that additional or alternative steps may be used.

[0177] The above description is only a specific implementation of the present application, so that those skilled in the art can understand or implement the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest range consistent with the principles and novel features applied for herein.

Claims

1. A method for sharing and downloading content on multiple devices, characterized in that: Applied to a client device, the method comprises: In the case where the client device logs in to any account information, receiving target download content input by a user of the account information to generate a content download request; Sending the content download request to the server; After the server verifies the legitimacy of the content download request and determines all the client devices corresponding to the account information, in the case where the server sends the download metadata of the target download content to all the client devices corresponding to the account information, receiving the download metadata of the target download content sent by the server; Initiate a content download task according to the download metadata, and synchronize the download progress to the server; In the case that the content download task of any of the client devices fails, a notification of the failure of the content download task of the client device sent by the server is received.

2. The method according to claim 1, characterized in that The sending the content download request to the server includes: Establishing a network communication connection with the server through 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 comprises: In the case that the server successfully verifies the content download request, content download information is recorded, where the content download information 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 comprises: When any of the client devices logs in to the account information, 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 relationship among the device identification information, the account information and the corresponding unique authentication identifier.

5. A method for sharing and downloading content on multiple devices, characterized in that: Applied to a server, the method comprises: In the case where the client device logs in to any account information, receiving a content download request from the client device, the content download request including target download content; Performing legitimacy verification on the content download request; 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, so that all client devices corresponding to the account information start the content download task according to the download metadata; receiving the download progress of the content download task of all client devices corresponding to the account information; When it is determined according to the download progress that the content download task of any client device corresponding to the account information fails, 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 a client device when the client device logs in any account information includes: In the case where the client device logs in to any account information, receiving a network communication connection request from the client device through a preset request sending protocol to establish a network communication connection with the client; A content download request from the client device is received via the network communication connection.

7. The method according to claim 5, characterized in that The content download request also includes encryption information. The verifying the legitimacy of the content download request includes: Obtaining encryption information in the content download request; By verifying the legality of the encrypted information, if it is determined that the encrypted information is legal, it is determined that the content download request is legal.

8. The method according to claim 5, characterized in that After the content download request is verified, sending the download metadata of the target download content to all client devices corresponding to the account information includes: After the content download request is verified, obtaining the operating system type information of the client device corresponding to any of the account information; Determine the target push service protocol according to the operating system type information of the client device; The download metadata of the target download content is sent to the client device according to the target push service protocol.

9. The method according to claim 5, characterized in that The method further comprises: 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 obtains login authorization authentication from the server; Receiving device identification information, the account information and the corresponding unique authentication identifier sent from the client device; An association relationship between the device identification information, the account information and the corresponding unique authentication identification is established to store the association relationship.

10. A device for sharing and downloading content on multiple devices, characterized in that: Applied to a client device, the device comprises: A first receiving module, configured to receive target download content input by a user of any account information when the client device logs in to the account information, so as to generate a content download request; A first sending module, used for sending the content download request to the server; A second receiving module is used to receive the download metadata of the target download content sent by the server when the server sends the download metadata of the target download content to all the client devices corresponding to the account information after the server passes the legitimacy verification of the content download request and determines all the client devices corresponding to the account information; A progress synchronization module, used to start the content download task according to the download metadata, and synchronize the download progress to the server; The third receiving module is used for receiving a notification of failure of the content downloading task of any of the client devices sent by the server when the content downloading task of the client device fails.

11. A device for sharing and downloading content on multiple devices, characterized in that: Applied to a server, the device comprises: A fourth receiving module, configured to receive a content download request from a client device when the client device logs in to any account information, wherein the content download request includes target download content; A legality verification module, used to verify the legality of the content download request; A 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 start the content download task according to the download metadata; A fifth receiving module, configured 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 when it is determined according to the download progress that the content download task of any client device corresponding to the account information fails.

Images