WO2017177621A1 - 一种局域网内数据同步方法及其装置、用户终端 - Google Patents

一种局域网内数据同步方法及其装置、用户终端 Download PDF

Info

Publication number
WO2017177621A1
WO2017177621A1 PCT/CN2016/099901 CN2016099901W WO2017177621A1 WO 2017177621 A1 WO2017177621 A1 WO 2017177621A1 CN 2016099901 W CN2016099901 W CN 2016099901W WO 2017177621 A1 WO2017177621 A1 WO 2017177621A1
Authority
WO
WIPO (PCT)
Prior art keywords
source terminal
cloud server
data
local area
area network
Prior art date
Application number
PCT/CN2016/099901
Other languages
English (en)
French (fr)
Inventor
敖伟波
Original Assignee
乐视控股（北京）有限公司
乐视网信息技术（北京）股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 乐视控股（北京）有限公司, 乐视网信息技术（北京）股份有限公司 filed Critical 乐视控股（北京）有限公司
Publication of WO2017177621A1 publication Critical patent/WO2017177621A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
    • H04L67/5682—Policies or rules for updating, deleting or replacing the stored data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2801—Broadband local area networks

Definitions

  • the present application relates to the field of synchronization technologies, and in particular, to a data synchronization method in a local area network, a device thereof, and a user terminal.
  • Cloud synchronization can be defined as cloud-centric. Data and file data uploaded by individuals in the cloud can be shared between different devices or between devices and the cloud, and the user's data and data are permanently saved in the cloud.
  • the source terminal transmits the data to be synchronized to the cloud server through the local area network, and the synchronization terminal accesses the cloud server through the local area network, and the cloud server synchronizes the data to be synchronized to the terminal to be synchronized, thereby implementing the source terminal and the standby. Synchronize the data and files of the terminal.
  • the inventor has found that at least the following problems exist in the prior art: in the existing cloud synchronization mode, even if the terminal to be synchronized and the source terminal are located on the same local area network, the data to be synchronized needs to be synchronized by the server in the cloud. To the synchronous terminal, the drawbacks of this synchronization method are: relatively time consuming and inefficient synchronization.
  • the purpose of the present application is to provide a data synchronization method in a local area network, a device thereof, and a user terminal, which solve the problem that synchronization time and synchronization efficiency are low when each device synchronizes in the same local area network.
  • the embodiment of the present application provides the following technical solutions:
  • an embodiment of the present application provides a data synchronization method in a local area network, which is applied to a user terminal, and the method includes the following steps:
  • the method further includes:
  • the identifier information of the source terminal in the local area network that obtains the source of the updated data specifically:
  • the synchronizing the update data from the source terminal is specifically:
  • the update data is synchronously updated by the source terminal to the cloud server.
  • the identifier information of the source terminal in the local area network includes the device identifier, the application identifier, and/or the user identifier of the source terminal recorded by the cloud server.
  • the identifier information of the source terminal in the local area network that obtains the update data is specifically:
  • the synchronizing the update data from the source terminal according to the identifier information of the source terminal includes:
  • the update data is synchronized by a data connection within the local area network.
  • the embodiment of the present application further provides a data synchronization device in a local area network, including:
  • a detecting unit configured to detect whether the cloud server has updated data
  • An obtaining unit configured to acquire, from the cloud server, identification information of a source terminal in a local area network of the updated data source when detecting that the cloud server has update data;
  • a synchronization unit configured to synchronize the update data from the source terminal according to the identifier information of the source terminal.
  • the device further comprises:
  • a selection unit configured to select data to be updated from the update data
  • the acquiring unit is specifically configured to: obtain identifier information of the source terminal in the local area network of the data source to be updated;
  • the synchronization unit is specifically configured to: synchronize the to-be-updated data from the source terminal.
  • the update data is synchronously updated by the source terminal to the cloud server.
  • the identifier information of the source terminal includes:
  • the device identifier, the application identifier, and/or the user identifier of the source terminal that is recorded by the cloud server where the acquiring unit is configured to: obtain the device identifier, the application identifier, and/or the user identifier of the source terminal from the cloud server. ;
  • the updating unit is configured to: establish a data connection in the local area network with the source terminal according to the device identifier, the application identifier, and/or the user identifier of the source terminal, and synchronize the update data by using the data connection in the local area network.
  • the embodiment of the present application further provides a user terminal, including:
  • a communication unit configured to establish a data connection in the local area network with the source terminal, and establish a network connection with the cloud server;
  • a central processor configured to detect whether there is update data in the cloud server; and when detecting that the cloud server has update data, obtain, from the cloud server, identifier information of the source terminal in the local area network of the update data source; The identification information of the source terminal synchronizes the update data from the source terminal.
  • the embodiment of the present application further provides an electronic device, including:
  • At least one processor and,
  • the memory stores instructions executable by the one processor, the instructions being executed by the at least one processor to enable the at least one processor to:
  • the update data is synchronized from the source terminal according to the identification information of the source terminal.
  • the embodiment of the present application further provides a non-transitory computer readable storage medium, where computer executable instructions are stored, and the computer executable instructions are set as:
  • the embodiment of the present application further provides a computer program product, where the computer program product includes a computing program stored on a non-transitory computer readable storage medium, the computer program including program instructions, when the program When the instructions are executed by the computer, the computer is caused to perform the intra-LAN data synchronization method of any of the above embodiments.
  • the identifier information of the source terminal in the local area network of the update data source is obtained from the cloud server, and according to The identification information of the source terminal synchronizes the update data from the source terminal.
  • This process is implemented in the same local area network, which avoids the cloud server acting as an intermediary between each source terminal and each terminal to be synchronized, reduces the bandwidth load of the cloud server, and greatly shortens the data synchronization time between the terminals in the LAN, and improves synchronization. effectiveness.
  • FIG. 1 is a schematic diagram of a connection between a cloud server, a source terminal, and a terminal to be synchronized provided by an embodiment of the present application;
  • FIG. 2 is a flowchart of a data synchronization method in a local area network according to Embodiment 1 of the present application;
  • FIG. 3 is a flowchart of a data synchronization method in a local area network according to Embodiment 2 of the present application;
  • FIG. 4 is a flowchart of a data synchronization method in a local area network according to Embodiment 3 of the present application;
  • FIG. 5 is a flowchart of a data synchronization method in a local area network according to Embodiment 4 of the present application.
  • FIG. 6 is a schematic structural diagram of a data synchronization device in a local area network according to Embodiment 5 of the present application;
  • FIG. 7 is a schematic structural diagram of a user terminal according to Embodiment 6 of the present application.
  • FIG. 8 is a schematic structural diagram of hardware of an electronic device according to Embodiment 7 of the present application.
  • the local area network construction described in the following embodiments of the present application adopts Digital Living Network Alliance (DLNA) or AirPlay.
  • Devices connected to the same local area network include a source terminal and a terminal to be synchronized.
  • the cloud server in this embodiment is in the cloud, and may be one or multiple.
  • the source terminal is a device that enables the cloud server to update content after it has interacted with the cloud server.
  • the source terminal includes content to be synchronized by the terminal to be synchronized and content that the terminal to be synchronized does not need to synchronize.
  • the source terminal can be one or multiple.
  • the synchronization terminal needs to synchronize the content of the source terminal, wherein the synchronization may be selective synchronization, that is, selective synchronization of content included in the source terminal, and the selective synchronization may be synchronized with all content included in the source terminal, It can be synchronized only with a part of the source terminal. Further, the to-be-synchronized terminal can not only selectively synchronize, but also can view the content to be synchronized when synchronizing with the source terminal.
  • the terminal to be synchronized here may be one or multiple.
  • FIG. 1 is a schematic diagram of a connection between a cloud server, a source terminal, and a terminal to be synchronized provided by an embodiment of the present application.
  • the terminal devices on the same local area network side include a first source terminal 101, a second source terminal 102, a third source terminal 103, a first to-be-synchronized terminal 201, a second to-be-synchronized terminal 202, and a third to be synchronized.
  • the device on the cloud side includes the cloud server 100.
  • the cloud server 100, each source terminal, and each terminal to be synchronized are connected to each other.
  • Each source terminal and the to-be-synchronized terminal have their own device identifier, application identifier, and/or user identifier.
  • Each source terminal and to-be-synchronized terminal includes any content to be synchronized and content that does not need to be synchronized.
  • the first source terminal 101 includes contents A, B, C, and D
  • the second source terminal 102 includes contents A and B
  • the third source terminal 103 includes contents A, B, and C.
  • the first to-be-synchronized terminal 201 includes content A
  • the second to-be-synchronized terminal 202 includes content B
  • the third to-be-synchronized terminal includes A, B, and E.
  • the cloud server includes contents A, B, C, and D.
  • the content described here includes data, files, and other applications with data or information attributes.
  • FIG. 2 is a flowchart of a method for synchronizing data in a local area network according to Embodiment 1 of the present application. As shown in FIG. 2, the method includes the following steps:
  • the update data stored here in the cloud server includes content to be synchronized by the terminal to be synchronized and content that does not need to be synchronized.
  • the terminal to be synchronized can selectively update data synchronously.
  • the first to-be-synchronized terminal 201 including the content A passes through the content list of the cloud server, for example, the content list includes the contents A, B, C, and D, and the update data is known.
  • the first to-be-synchronized terminal 201 can synchronize only the content B, and can also synchronize the contents C and D, and of course, the contents B, C, and D can be synchronized.
  • the to-be-synchronized terminal accesses the cloud server according to a certain period, obtains the latest synchronization situation from the synchronization, and performs adaptive synchronization according to the latest synchronization situation.
  • the source terminal includes content to be synchronized by the terminal to be synchronized and content that the terminal to be synchronized does not need to synchronize.
  • the source terminal can be one or multiple. Further, in combination with step S21, the cloud server, the source terminal, and the terminal to be synchronized herein are connected to each other.
  • the identifier information of the source terminal in the local area network includes the device identifier, the application identifier, and/or the user identifier of the source terminal recorded by the cloud server. Therefore, the source terminal information of the local area network is obtained by acquiring the device identifier, the application identifier, and/or the user identifier of the source terminal from the cloud server.
  • the source terminal before the synchronization request is sent by the terminal to be synchronized, the source terminal has performed content interaction with the cloud server, so that the content of the cloud server is updated, and at the same time, the cloud server records the device identifier of the source terminal that is updated this time.
  • Application ID and/or user ID For example, as shown in FIG. 1 , after the first source terminal 101 , the second source terminal 102 , and the third source terminal 103 interact with the cloud server 100 , the cloud server 100 records the first source terminal 101 and the second source terminal 102 .
  • the device identifier, application identifier, and/or user identifier of the third source terminal 103 are examples of the third source terminal.
  • the cloud server when the source terminal interacts with the cloud server, the cloud server is only responsible for recording data uploading and downloading, and managing the operation record. Therefore, the cloud server service is simple and clear. Clearly, it avoids the problem that the cloud server bears extra bandwidth and affects the performance of the cloud server due to the calculation and notification of the operation of the source terminal device.
  • a data connection in the local area network is established with the source terminal according to the device identifier, the application identifier, and/or the user identifier of the source terminal, and the update data is synchronized through the data connection.
  • the device to be synchronized when the content to be synchronized is compared with the cloud server, and the content needs to be updated, the device to be synchronized obtains the device identifier and the application identifier of the source terminal that operates the current update content from the cloud server. And the user identifier, according to the device identifier, the application identifier, and/or the user identifier of the source terminal, synchronizes the update data from the source terminal through the local area network, and completes synchronization of the data and the file.
  • the terminal to be synchronized when the terminal to be synchronized is synchronized with the source terminal, the content of the source terminal to be synchronized may be viewed, and the content included in the source terminal may be selectively synchronized, where the content may be synchronized with all the content included in the source terminal, or Only synchronize with part of the source terminal.
  • the to-be-synchronized terminal issues a synchronization request to the source terminal in the same local area network.
  • the synchronous connection relationship between the terminal to be synchronized and the source terminal is a many-to-many relationship.
  • the first to-be-synchronized terminal 201 and the second to-be-synchronized terminal 202 both need to synchronize the content C, and the first to-be-synchronized terminal 201 sends a synchronization request to the first source terminal 101 according to the source terminal information.
  • the first source terminal 101 and the first to-be-synchronized terminal 201 establish a data connection, thereby implementing synchronization of the content C; at the same time, the second to-be-synchronized terminal 202 issues a synchronization to the third source terminal 103 according to the source terminal information.
  • the request, the third source terminal 103 and the second to-be-synchronized terminal 202 establish a data connection, thereby realizing the synchronization of the content C.
  • the second to-be-synchronized terminal 202 sends a synchronization request to the first source terminal 101 according to the source terminal information, and the first source terminal 101 and the second to-be-synchronized terminal 202 establish a data connection, thereby implementing synchronization of the content C;
  • the first to-be-synchronized terminal 201 issues a synchronization request to the third source terminal 103 according to the source terminal information, and the third source terminal 103 establishes a data connection with the first to-be-synchronized terminal 201, thereby realizing synchronization of the content C.
  • the first to-be-synchronized terminal 201 and the second to-be-synchronized terminal 202 are simultaneously prevented from simultaneously issuing a synchronization request to the first source terminal 101 or the third source terminal 103, thereby increasing the load of the first source terminal 101 or the third source terminal 103. Case. Therefore, the source terminal tries to avoid the situation that the load is too high. In this way, the content synchronization rate is high and the synchronization is more efficient.
  • the method provided in this embodiment further includes: selecting data to be updated from the update data. Therefore, the identifier information of the source terminal in the local area network that obtains the source of the update data is specifically: obtaining the identifier information of the source terminal in the local area network of the data source to be updated; and the synchronizing the update data from the source terminal, specifically And: synchronizing the data to be updated from the source terminal.
  • the local area network may be constructed using Digital Living Network Alliance (DLNA) or AirPlay.
  • DLNA Digital Living Network Alliance
  • AirPlay The cloud server can be one or multiple.
  • the terminal to be synchronized needs to synchronize the content of the source terminal, and the terminal to be synchronized may be one or multiple.
  • the terminal to be synchronized here has its own device identifier, application identifier and/or user identifier.
  • the identifier information of the source terminal in the local area network of the update data source is obtained from the cloud server, and according to The identification information of the source terminal synchronizes the update data from the source terminal.
  • This process is implemented in the same local area network, which avoids the cloud server acting as an intermediary for synchronization between each source terminal and each terminal to be synchronized, reduces the bandwidth load of the cloud server, and greatly shortens the data synchronization time between terminals in the local area network, thereby improving synchronization efficiency.
  • FIG. 3 is a flowchart of a data synchronization method in a local area network according to Embodiment 2 of the present application. As shown in FIG. 3, the method includes the following steps:
  • steps S31, S32, and S33 the specific implementations of steps S31, S32, and S33 are the same as steps S21, S22, and S23 described above, and need not be described herein.
  • the upload synchronization result includes a device identifier, an application identifier, and/or a user identifier of the terminal to be synchronized.
  • the cloud server records the device identifier, the application identifier, and/or the user identifier of the terminal to be synchronized, so as to expand the synchronization object of the subsequent synchronization operation. Since there are many synchronization objects, the terminal to be synchronized does not have to concentrate on the same source terminal when synchronizing, so it also improves the synchronization efficiency of data and files accordingly.
  • FIG. 4 is a flowchart of a data synchronization method in a local area network according to Embodiment 3 of the present application. As shown in FIG. 4, the method includes the following steps:
  • step S41 and step S42 the specific implementations of step S41 and step S42 are the same as steps S21 and S22 described above, and need not be described here.
  • the source terminal information includes a device identifier, an application identifier, and/or a user identifier.
  • steps S44 and S45 by checking the current synchronization state and device resources, and accepting the synchronization request or rejecting the new synchronization request or placing the synchronization request into the work queue according to the current state of the source terminal. In this way, it can ensure that the source terminal is not overloaded when it is synchronized, thereby maintaining the stability and reliability of the synchronization system, and further promoting the synchronization speed and providing synchronization efficiency.
  • step S46 is the same as step S23 described above, and need not be described here.
  • FIG. 5 is a flowchart of a data synchronization method in a local area network according to Embodiment 4 of the present application. As shown in FIG. 5, the method includes the following steps:
  • steps S51 to S56 are the same as steps S41 and S46 described above, and need not be described herein.
  • the source terminal or the to-be-synchronized terminal may upload the synchronization status to the cloud server, and mark the status of the source terminal or the to-be-synchronized terminal as being synchronized.
  • the source terminal or the terminal to be synchronized can upload the synchronization status to the cloud server, and mark the status of the source terminal or the terminal to be synchronized as synchronizable.
  • the subsequent to-be-synchronized terminal selects the device for synchronization from the source terminal labeled "Syncable" according to the synchronized device list given by the cloud server. Therefore, in this way, the efficiency of synchronizing data is improved.
  • the update data may be updated by the source terminal to the cloud server, or may be synchronously updated by the terminal to be synchronized to the cloud server, that is, the source terminal and the terminal to be synchronized.
  • the synchronization role is not static, and the role can be flexibly converted according to the synchronization requirements of each terminal.
  • FIG. 6 is a schematic structural diagram of a data synchronization apparatus in a local area network according to an embodiment of the present application. As shown in Figure 6, the device includes:
  • the detecting unit 61 is configured to detect whether the cloud server has update data.
  • the obtaining unit 62 is configured to: when detecting that the cloud server has update data, acquire, from the cloud server, identifier information of the source terminal in the local area network of the update data source;
  • the synchronization unit 63 is configured to synchronize the update data from the source terminal according to the identifier information of the source terminal.
  • the cloud server when detecting that there is update data in the cloud server, when detecting that the cloud server has update data, acquiring, by the cloud server, the identifier information of the source terminal in the local area network of the update data source, and according to The identification information of the source terminal synchronizes the update data from the source terminal.
  • This process is implemented in the same local area network, which avoids the cloud server acting as an intermediary between each source terminal and each terminal to be synchronized, reduces the bandwidth load of the cloud server, and greatly shortens the data synchronization time between the terminals in the LAN, and improves synchronization. Effect rate.
  • the update data may be updated by the source terminal to the cloud server, or may be synchronously updated by the synchronization unit 63 to the cloud server, that is, the synchronization role of the source terminal and the synchronization unit 63 is not constant.
  • the roles can be flexibly converted according to the synchronization requirements of each terminal.
  • the apparatus of this embodiment further includes a selection unit 64.
  • the selecting unit 64 is configured to select data to be updated from the update data, and therefore, the acquiring unit 62 is configured to acquire identification information of the source terminal in the local area network of the data source to be updated; the synchronization unit 63 Used to synchronize the data to be updated from the source terminal.
  • the update data stored here at the cloud server includes the content that the synchronization unit 63 needs to synchronize and the content that does not need to be synchronized.
  • Selection unit 64 can selectively update the data synchronously.
  • the local area network may be constructed using Digital Living Network Alliance (DLNA) or AirPlay.
  • DLNA Digital Living Network Alliance
  • AirPlay AirPlay
  • the cloud server can be one or multiple.
  • the data synchronization device needs to synchronize the content of the source terminal, and the data synchronization device may be one or more.
  • the data synchronization device here has its own device identification, application identification and/or user identification.
  • the data synchronization device accesses the cloud server according to a certain period, obtains the latest synchronization situation therefrom, and performs adaptive synchronization according to the latest synchronization situation.
  • the source terminal information of the local area network includes a device identifier, an application identifier, and/or a user identifier of the source terminal recorded by the cloud server. Therefore, the source terminal information of the local area network is obtained by acquiring the device identifier, the application identifier, and/or the user identifier of the source terminal from the cloud server.
  • the source terminal before the synchronization unit 63 issues the synchronization request, the source terminal has performed content interaction with the cloud server to update the content of the cloud server, and at the same time, the cloud server records the device identifier of the source terminal that is updated this time. Application ID and/or user ID.
  • the cloud server when the source terminal interacts with the cloud server, the cloud server is only responsible for recording data uploading and downloading, and managing the operation record. Therefore, the cloud server service is simple and clear, and the cloud server is prevented from calculating and notifying the source terminal device. The operation is burdened with additional bandwidth and issues affecting cloud server performance.
  • the device identifier the application identifier, and/or the user identifier of the source terminal. Establishing a data connection within the local area network with the source terminal, and synchronizing the updated data through the data connection.
  • the data synchronization device and the cloud server perform content comparison, and when the content needs to be updated and synchronized, the obtaining unit 62 acquires the device identifier, the application identifier, and the source terminal of the source terminal that operates the current update content from the cloud server. And the user identifier, according to the device identifier, the application identifier, and/or the user identifier of the source terminal, synchronizes the update data from the source terminal through the local area network, and completes synchronization of the data and the file.
  • the synchronization unit 63 can view the content to be synchronized of the source terminal, and selectively synchronize the content included in the source terminal, where the content may be synchronized with all the content included in the source terminal, or Only synchronize with part of the source terminal.
  • the synchronization unit 63 issues a synchronization request to the source terminal in the same local area network.
  • the synchronous connection relationship between the data synchronization device and the source terminal is a many-to-many relationship. In this way, the content synchronization rate is high and the synchronization is more efficient.
  • FIG. 7 is a schematic structural diagram of a user terminal according to an embodiment of the present application. As shown in FIG. 7, the user terminal includes:
  • the communication unit 71 establishes a data connection in the local area network with the source terminal, and establishes a network connection with the cloud server.
  • the central processing unit 72 is configured to detect whether there is update data in the cloud server, and when detecting that the cloud server has update data, obtain, from the cloud server, identifier information of the source terminal in the local area network of the update data source, and according to the Determining the identification information of the source terminal, synchronizing the update data from the source terminal.
  • the cloud server when detecting that there is update data in the cloud server, when detecting that the cloud server has update data, acquiring, by the cloud server, the identifier information of the source terminal in the local area network of the update data source, and according to The identification information of the source terminal synchronizes the update data from the source terminal.
  • This process is implemented in the same local area network, which avoids the cloud server acting as an intermediary between each source terminal and each terminal to be synchronized, reduces the bandwidth load of the cloud server, and greatly shortens the data synchronization time between the terminals in the LAN, and improves synchronization. Effect rate.
  • the computer software can be stored in a computer readable storage medium, which, when executed, can include the flow of an embodiment of the methods described above.
  • the storage medium may be a magnetic disk, an optical disk, a read-only storage memory, or a random storage memory.
  • the central processing unit is a control center of the user terminal, and connects various parts of the entire electronic device by using various interfaces and lines, by running or executing software programs and/or modules stored in the storage unit, and calling the storage in the storage unit. Data to perform various functions of the electronic device and/or process data.
  • the central processing unit may be composed of an integrated circuit, or may be composed of a plurality of sealing integrated chips that connect the same function or different functions. That is, the processor can be a combination of a GPU, a digital signal processor, and a control chip in the communication unit.
  • the embodiment of the present application further provides a non-transitory computer readable storage medium, where the computer readable storage medium stores computer executable instructions, which can perform data synchronization in a local area network in any of the foregoing method embodiments. method.
  • FIG. 8 is a schematic structural diagram of hardware of an electronic device according to an embodiment of the present disclosure. As shown in FIG. 8 , the electronic device 8 includes:
  • processors 81 and a memory 82 are exemplified by a processor 81 in FIG.
  • the processor 81 and the memory 82 can be connected by a bus or other means, as exemplified by a bus connection in FIG.
  • the memory 82 is a non-transitory computer readable storage medium that can be used to store non-volatile software programs, non-volatile computer executable programs, and modules, such as in the embodiment of the present application.
  • a program instruction/module corresponding to the data synchronization method in the intranet for example, the detecting unit 61, the obtaining unit 62, the synchronizing unit 63, and the selecting unit 64 shown in FIG. 6).
  • the processor 81 executes various functional applications and data processing of the electronic device by executing non-volatile software programs, instructions, and modules stored in the memory 82, that is, the data synchronization method in the local area network of the above method embodiment is implemented.
  • the memory 82 may include a storage program area and an storage data area, wherein the storage program area may store an operating system, an application required for at least one function; the storage data area may store data created according to usage of the electronic device, and the like.
  • memory 82 can include high speed random access memory, and can also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device.
  • memory 82 can optionally include memory remotely located relative to processor 81, which can be connected to the electronic device over a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • the one or more modules are stored in the memory 82, and when executed by the one or more processors 81, perform an intra-local area data synchronization method in any of the above method embodiments, for example, performing the above described map Method step S21 to step S23 in 2, method step S31 to step S34 in FIG. 3, method step S41 to step S46 in FIG. 4, and method step S51 to step S57 in FIG. 5; unit 61 in FIG. 6 is implemented -64 and the functions of units 71-71 in Figure 7.
  • the electronic device of the embodiment of the present application exists in various forms, including but not limited to:
  • Mobile communication devices These devices are characterized by mobile communication functions and are mainly aimed at providing voice and data communication.
  • Such terminals include: smart phones (such as iPhone), multimedia phones, functional phones, and low-end phones.
  • Ultra-mobile personal computer equipment This type of equipment belongs to the category of personal computers, has computing and processing functions, and generally has mobile Internet access.
  • Such terminals include: PDAs, MIDs, and UMPC devices, such as the iPad.
  • Portable entertainment devices These devices can display and play multimedia content. Such devices include: audio, video players (such as iPod), handheld game consoles, e-books, and smart toys. And portable car navigation devices.
  • the server consists of a processor, a hard disk, a memory, a system bus, etc.
  • the server is similar to a general-purpose computer architecture, but because of the need to provide highly reliable services, processing power and stability High reliability in terms of reliability, security, scalability, and manageability.
  • the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located in one place. Or it can be distributed to at least two network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本申请涉及同步技术领域，尤其涉及一种局域网内数据同步方法及其装置、用户终端。该数据同步方法包括以下步骤：检测云端服务器是否存在更新数据；当检测到所述云端服务器存在更新数据时，从所述云端服务器获取所述更新数据来源的局域网内源终端的标识信息；根据所述源终端的标识信息，从源终端同步所述更新数据。此过程在同一局域网内现实，避免了云端服务器充当各个源终端和各个待同步终端之间同步的中介，降低了云端服务器的带宽负荷，而且，大大缩短局域网内终端间数据同步时间，提高了同步效率。

Description

一种局域网内数据同步方法及其装置、用户终端
相关申请的交叉参考
本申请要求于2016年04月12日提交中国专利局、申请号为201610224855.1、发明名称为“一种局域网内数据同步方法及其装置、用户终端”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及同步技术领域，尤其涉及一种局域网内数据同步方法及其装置、用户终端。
背景技术
随着互联网的快速发展以及智能终端的普及，同步与备份的概念逐渐深入到人们的工作当中。云同步可以定义为以云端为中心，个人所上传在云端的数据和文件资料可以在不同的设备之间或设备与云端之间进行资源共享，并且在云端永久保存用户的资料与数据。
对于连接同一局域网内部不同设备或者应用，源终端通过局域网将待同步数据传输到云端服务器，待同步终端通过局域网访问云端服务器，云端服务器将待同步数据同步至待同步终端，从而实现源终端和待同步终端的数据和文件的同步。
在实现本申请实施例的过程中，发明人发现现有技术至少存在如下问题：现有的云同步方式，即使待同步终端与源终端位于同一局域网，也需要通过云端的服务器将待同步数据同步至同步终端，此种同步方法存在的缺陷是：比较耗时和同步效率低下。
发明内容
为了克服上述技术问题，本申请目的旨在提供一种局域网内数据同步方法及其装置、用户终端，其解决了各个设备在同一局域网内进行同步时存在同步耗时和同步效率低下的问题。
为解决上述技术问题，本申请实施例提供以下技术方案：
第一方面，本申请实施例提供一种局域网内数据同步方法，应用于用户终端，所述方法包括以下步骤：
检测云端服务器是否存在更新数据；
当检测到所述云端服务器存在更新数据时，从所述云端服务器获取所述更新数据来源的局域网内源终端的标识信息；
根据所述源终端的标识信息，从所述源终端同步所述更新数据。
其中，所述方法还包括：
从所述更新数据中选择待更新数据，则
所述获取所述更新数据来源的局域网内源终端的标识信息，具体为：
获取所述待更新数据来源的局域网内源终端的标识信息；
所述从源终端同步所述更新数据，具体为：
从所述源终端同步所述待更新数据。
其中，所述更新数据由所述源终端同步更新数据至云端服务器。
其中，所述局域网内源终端的标识信息包括云端服务器记录的所述源终端的设备标识、应用标识和/或用户标识；
所述获取所述更新数据的局域网内源终端的标识信息，具体为：
从所述云端服务器获取所述源终端的设备标识、应用标识和/或用户标识。
其中，所述根据所述源终端的标识信息，从所述源终端同步所述更新数据，具体包括：
根据所述源终端的设备标识、应用标识和/或用户标识与源终端建立局域网内数据连接；
通过所述局域网内数据连接同步所述更新数据。
第二方面，本申请实施例还提供一种局域网内数据同步装置，包括：
检测单元，用于检测云端服务器是否存在更新数据；
获取单元，用于当检测到所述云端服务器存在更新数据时，从所述云端服务器获取所述更新数据来源的局域网内源终端的标识信息；
同步单元，用于根据所述源终端的标识信息，从所述源终端同步所述更新数据。
其中，所述装置还包括：
选择单元，用于从所述更新数据中选择待更新数据，则
所述获取单元，具体用于：获取所述待更新数据来源的局域网内源终端的标识信息；
所述同步单元，具体用于：从所述源终端同步所述待更新数据。
其中，所述更新数据由所述源终端同步更新数据至云端服务器。
其中，所述源终端的标识信息包括：
云端服务器记录的所述源终端的设备标识、应用标识和/或用户标识，所述获取单元，具体用于：从所述云端服务器获取所述源终端的设备标识、应用标识和/或用户标识；
所述更新单元，具体用于：根据所述源终端的设备标识、应用标识和/或用户标识与源终端建立局域网内数据连接，通过所述局域网内数据连接同步所述更新数据。
第三方面，本申请实施例还提供一种用户终端，包括：
通信单元，用于与源终端建立局域网内数据连接，以及与云端服务器建立网络连接；
中央处理器，用于检测云端服务器是否存在更新数据；当检测到所述云端服务器存在更新数据时，从所述云端服务器获取所述更新数据来源的局域网内源终端的标识信息；并根据所述源终端的标识信息，从源终端同步所述更新数据。
第四方面，本申请实施例还提供一种电子设备，包括：
至少一个处理器；以及，
与所述至少一个处理器通信连接的存储器；其中，
所述存储器存储有可被所述一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够：
检测云端服务器是否存在更新数据；
当检测到所述云端服务器存在更新数据时，从所述云端服务器获取所述更新数据来源的局域网内源终端的标识信息；
根据所述源终端的标识信息，从源终端同步所述更新数据。
第五方面，本申请实施例还提供了一种非暂态计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为:
检测云端服务器是否存在更新数据；
当检测到所述云端服务器存在更新数据时，从所述云端服务器获取所述更新数据来源的局域网内源终端的标识信息；
根据所述源终端的标识信息，从所述源终端同步所述更新数据。
第六方面，本申请实施例还提供了一种计算机程序产品，所述计算机程序产品包括存储在非暂态计算机可读存储介质上的计算程序，所述计算机程序包括程序指令，当所述程序指令被计算机执行时，使所述计算机执行上述任意实施例的局域网内数据同步方法。
在本申请实施例中，通过检测云端服务器是否存在更新数据，当检测到所述云端服务器存在更新数据时，从所述云端服务器获取所述更新数据来源的局域网内源终端的标识信息，并根据所述源终端的标识信息，从源终端同步所述更新数据。此过程在同一局域网内实现，避免了云端服务器充当各个源终端和各个待同步终端之间同步的中介，降低了云端服务器的带宽负荷，而且，大大缩短局域网内终端间数据同步时间，提高了同步效率。
附图说明
一个或多个实施例通过与之对应的附图中的图片进行示例性说明，这些示例性说明并不构成对实施例的限定，附图中具有相同参考数字标号的元件表示为类似的元件，除非有特别申明，附图中的图不构成比例限制。
图1是本申请实施例提供的云端服务器、源终端以及待同步终端之间连接的示意图；
图2是本申请实施例一提供的一种局域网内数据同步方法的流程图；
图3是本申请实施例二提供的一种局域网内数据同步方法的流程图；
图4是本申请实施例三提供的一种局域网内数据同步方法的流程图；
图5是本申请实施例四提供的一种局域网内数据同步方法的流程图；
图6是本申请实施例五提供的一种局域网内数据同步装置的结构示意图；
图7是本申请实施例六提供的一种用户终端的结构示意图；
图8是本申请实施例七提供的一种电子设备的硬件结构示意图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处所描述的具体实施例仅用以解释本申请，并不用于限定本申请。
此外，下面所描述的本申请各个实施方式中所涉及到的技术特征只要彼此之间未构成冲突就可以相互组合。
本申请以下各个实施例所述的局域网构建采用数字生活网络联盟(DLNA)或者AirPlay。连接同一局域网的设备包括源终端以及待同步终端。本实施例的云端服务器处于云端，其可以是一个，也可以是多个。源终端是已经和云端服务器交互后，使云端服务器更新内容的设备。源终端包括待同步终端所需要同步的内容和待同步终端不需要同步的内容。源终端可以是一个，也可以是多个。待同步终端需要同步源终端的内容，其中，该同步可以是选择性同步，即对源终端包括的内容进行选择性同步，所述选择性同步可以是与源终端包括的全部内容进行同步，也可以只和源终端其中一部分内容进行同步。进一步的，待同步终端不仅可以选择性同步，而且在和源终端同步时，可以查看待同步内容。此处的待同步终端可以是一个，也可以是多个。
请参考图1，图1是本申请实施例提供的云端服务器、源终端以及待同步终端之间连接的示意图。如图1所示，处于同一局域网侧的终端设备包括第一源终端101、第二源终端102、第三源终端103、第一待同步终端201、第二待同步终端202以及第三待同步终端203。处于云端侧的设备包括云端服务器100。此处的云端服务器100、各个源终端以及各个待同步终端是两两相互连接的。其中，每个源终端和待同步终端都有属于自己的设备标识、应用标识和/或用户标识。每个源终端和待同步终端包括任意待同步内容和不需要同步的内容。比如说，如图1，第一源终端101包括内容A、B、C以及D，第二源终端102包括内容A和B，第三源终端103包括内容A、B以及C。第一待同步终端201包括内容A，第二待同步终端202包括内容B，第三待同步终端包括A、B以及E。云端服务器包括内容A、B、C以及D。此处所述的内容包括数据、文件以及其它具有数据或信息属性的应用程序。 下面结合附图对本申请实施例作进一步阐述。
实施例一
图2是本申请实施例一提供一种局域网内数据同步方法的流程图。如图2所示，所述方法包括以下步骤：
S21、检测云端服务器是否存在更新数据；
对于待同步终端来说，此处存储在云端服务器的更新数据包括待同步终端需要同步的内容和不需要同步的内容。待同步终端可以选择性进行同步更新数据。如图1所示，包括内容A的第一待同步终端201通过云端服务器的内容列表，比如，所述内容列表包括内容A、B、C和D，了解更新数据。第一待同步终端201可以只同步内容B，也可以同步内容C和D，当然也可以同步内容B、C和D。
在本实施例中，待同步终端按照一定周期访问云端服务器，从中获取最新的同步情况，并根据最新的同步情况进行适应性同步。
S22、当检测到所述云端服务器存在更新数据时，从所述云端服务器获取所述更新数据来源的局域网内源终端的标识信息；
在本步骤中，源终端包括待同步终端所需要同步的内容和待同步终端不需要同步的内容。源终端可以是一个，也可以是多个。进一步的，结合步骤S21，此处的云端服务器、源终端以及待同步终端是两两相互连接的。
在本实施例中，所述局域网内源终端的标识信息包括云端服务器记录的所述源终端的设备标识、应用标识和/或用户标识。因此，获取所述更新数据的局域网内源终端信息具体是从所述云端服务器获取所述源终端的设备标识、应用标识和/或用户标识。
在本实施例中，在待同步终端发出同步请求之前，源终端已经和云端服务器进行内容交互，使云端服务器的内容得以更新，与此同时，云端服务器记录本次更新的源终端的设备标识、应用标识和/或用户标识。比如，如图1所示，第一源终端101、第二源终端102、第三源终端103均与云端服务器100交互后，云端服务器100均记录第一源终端101、第二源终端102以及第三源终端103的设备标识、应用标识和/或用户标识。
在本实施例中，源终端和云端服务器交互时，云端服务器只负责记录数据上传和下载，以及操作记录的管理，因此，云端服务器的服务简单清 晰，避免了云端服务器因计算和通知源终端设备的操作而负担额外的带宽和影响云端服务器性能的问题。
S23、根据所述源终端的标识信息，从所述源终端同步所述更新数据。
在本步骤中，根据所述源终端的设备标识、应用标识和/或用户标识与源终端建立局域网内数据连接，通过所述数据连接同步所述更新数据。
在本实施例中，待同步终端和云端服务器进行内容对比，发现有内容需要更新同步时，待同步终端从云端服务器会获取到对本次更新内容进行操作的源终端的设备标识、应用标识和/或用户标识，根据源终端的设备标识、应用标识和/或用户标识，通过局域网从源终端同步所述更新数据，完成数据和文件的同步。此处，待同步终端在和源终端同步时，可以查看源终端的待同步内容，并对源终端包括的内容进行选择性同步，此处可以是与源终端包括的全部内容进行同步，也可以只和源终端其中一部分内容进行同步。
在本实施例中，待同步终端向处于同一局域网的源终端发出同步请求。其中，待同步终端和源终端的同步连接关系是多对多关系。比如，如图1所示，第一待同步终端201和第二待同步终端202均需要同步内容C，则第一待同步终端201根据所述源终端信息，向第一源终端101发出同步请求，第一源终端101和第一待同步终端201建立数据连接，从而实现了内容C的同步；与此同时，第二待同步终端202根据所述源终端信息，向第三源终端103发出同步请求，第三源终端103和第二待同步终端202建立数据连接，从而实现了内容C的同步。
或者，第二待同步终端202根据所述源终端信息，向第一源终端101发出同步请求，第一源终端101和第二待同步终端202建立数据连接，从而实现了内容C的同步；与此同时，第一待同步终端201根据所述源终端信息，向第三源终端103发出同步请求，第三源终端103和第一待同步终端201建立数据连接，从而实现了内容C的同步。因此，从而避免第一待同步终端201和第二待同步终端202同时向第一源终端101或第三源终端103发出同步请求，从而增加了第一源终端101或第三源终端103的负载的情况。因此源终端尽量避免负载过高的情况发生。采用此种方式，其内容同步速率高，同步更加有效率。
本实施例提供的方法还包括：从所述更新数据中选择待更新数据。因此，所述获取所述更新数据来源的局域网内源终端的标识信息，具体为：获取所述待更新数据来源的局域网内源终端的标识信息；所述从源终端同步所述更新数据，具体为：从所述源终端同步所述待更新数据。
在本实施例中，局域网构建可以采用数字生活网络联盟(DLNA)或者AirPlay。云端服务器可以是一个，也可以是多个。待同步终端需要同步源终端的内容，待同步终端可以是一个，也可以是多个。此处的待同步终端有属于自己的设备标识、应用标识和/或用户标识。
在本申请实施例中，通过检测云端服务器是否存在更新数据，当检测到所述云端服务器存在更新数据时，从所述云端服务器获取所述更新数据来源的局域网内源终端的标识信息，并根据所述源终端的标识信息，从源终端同步所述更新数据。此过程在同一局域网内实现，避免了云端服务器充当各个源终端和各个待同步终端之间同步的中介，降低了云端服务器的带宽负荷而且，大大缩短局域网内终端间数据同步时间，提高了同步效率。
实施例二
图3是本申请实施例二提供的一种局域网内数据同步方法的流程图。如图3所示，所述方法包括以下步骤：
S31、检测云端服务器是否存在更新数据；
S32、当检测到所述云端服务器存在更新数据时，从所述云端服务器获取所述更新数据来源的局域网内源终端的标识信息；
S33、根据所述源终端的标识信息，从所述源终端同步所述更新数据；
在步骤S31、S32以及S33中，步骤S31、S32以及S33的具体实施方式同上述所述的步骤S21、S22以及S23一样，在此不必赘述。
S34、同步完成后，上传同步结果至所述云端服务器。
在步骤S34中，所述上传同步结果包括待同步终端的设备标识、应用标识和/或用户标识。云端服务器记录待同步终端的设备标识、应用标识和/或用户标识，以便扩大后续同步操作的同步对象。由于同步对象多，同步时待同步终端不必过多集中同一源终端，因此其相应地也提高了数据、文件的同步效率。
实施例三
图4是本申请实施例三提供的一种局域网内数据同步方法的流程图。如图4所示，所述方法包括以下步骤：
S41、检测云端服务器是否存在更新数据；
S42、当检测到所述云端服务器存在更新数据时，从所述云端服务器获取所述更新数据来源的局域网内源终端的标识信息；
在步骤S41和步骤S42中，步骤S41和步骤S42的具体实施方式同上述所述的步骤S21和S22一样，在此不必赘述。
S43、根据所述源终端的标识信息，对所述源终端发出同步请求；
在本步骤中，所述源终端信息包括设备标识、应用标识和/或用户标识。
S44、所述源终端接收到多个同步请求时，检查当前同步状态和设备资源；
S45、如果所述源终端不能提供服务，拒绝新同步请求或者将同步请求放入工作队列；
结合步骤S44和S45，通过检查当前同步状态和设备资源，并根据源终端当前状态，接受同步请求或者拒绝新同步请求或者将同步请求放入工作队列。采用此种方式，其能够保证源终端同步时，不会负载过高，从而维护了同步系统的稳定和可靠，也进一步促进同步速度和提供同步效率。
S46、从源终端同步所述更新数据。
步骤S46的具体实施方式同上述所述的步骤S23一样，在此不必赘述。
实施例四
图5是本申请实施例四提供的一种局域网内数据同步方法的流程图。如图5所示，所述方法包括以下步骤：
S51、检测云端服务器是否存在更新数据；
S52、当检测到所述云端服务器存在更新数据时，从所述云端服务器获取所述更新数据来源的局域网内源终端的标识信息；
S53、根据所述源终端的标识信息，对所述源终端发出同步请求；
S54、所述源终端接收到多个同步请求时，检查当前同步状态和设备资源；
S55、如果所述源终端不能提供服务，拒绝新同步请求或者将同步请求放入工作队列；
S56、从源终端同步所述更新数据；
在本实施例中，步骤S51至S56的具体实施方式同上述所述的步骤S41和S46一样，在此不必赘述。
S57、根据云端服务器给出的已同步设备列表，按照一定时间间隔依次发起同步请求直到开始数据或文件同步，同时也会按照一定周期向云端服务器获取最新的同步情况。
在本实施例中，数据或文件同步时，源终端或待同步终端可以上传同步状态至云端服务器，将源终端或待同步终端的状态标记为同步中。数据或文件同步完成后，源终端或待同步终端可以上传同步状态至云端服务器，将源终端或待同步终端的状态标记为可同步。后续的待同步终端根据云端服务器给出的已同步设备列表，从标记为“可同步”的源终端选择设备进行同步。因此，采用此种方式，从而提高了同步数据的效率。
在本申请所提供的各个方法实施例中，所述更新数据可以由源终端同步更新数据至云端服务器，也可以由待同步终端同步更新数据至云端服务器，即此处的源终端和待同步终端的同步角色不是一成不变的，可以根据各个终端的同步需求灵活转换角色的。
实施例五
图6是本申请实施例提供的一种局域网内数据同步装置的结构示意图。如图6所示，该装置包括：
检测单元61，用于检测云端服务器是否存在更新数据；
获取单元62，用于当检测到所述云端服务器存在更新数据时，从所述云端服务器获取所述更新数据来源的局域网内源终端的标识信息；
同步单元63，用于根据所述源终端的标识信息，从所述源终端同步所述更新数据。
在本发明实施例中，通过检测云端服务器是否存在更新数据，当检测到所述云端服务器存在更新数据时，从所述云端服务器获取所述更新数据来源的局域网内源终端的标识信息，并根据所述源终端的标识信息，从源终端同步所述更新数据。此过程在同一局域网内实现，避免了云端服务器充当各个源终端和各个待同步终端之间同步的中介，降低了云端服务器的带宽负荷，而且，大大缩短局域网内终端间数据同步时间，提高了同步效 率。
在本实施例中，所述更新数据可以由源终端同步更新数据至云端服务器，也可以由同步单元63同步更新数据至云端服务器，即此处的源终端和同步单元63的同步角色不是一成不变的，可以根据各个终端的同步需求灵活转换角色的。
本实施例的装置还包括选择单元64。该选择单元64用于从所述更新数据中选择待更新数据，因此，具体的，所述获取单元62用于获取所述待更新数据来源的局域网内源终端的标识信息；所述同步单元63用于从所述源终端同步所述待更新数据。
在本实施例中，对于同步单元63来说，此处存储在云端服务器的更新数据包括同步单元63需要同步的内容和不需要同步的内容。选择单元64可以选择性进行同步更新数据。
在本实施例中，局域网构建可以采用数字生活网络联盟(DLNA)或者AirPlay。云端服务器可以是一个，也可以是多个。数据同步装置需要同步源终端的内容，数据同步装置可以是一个，也可以是多个。此处的数据同步装置有属于自己的设备标识、应用标识和/或用户标识。
在本实施例中，数据同步装置按照一定周期访问云端服务器，从中获取最新的同步情况，并根据最新的同步情况进行适应性同步。
在本实施例中，所述局域网内源终端信息包括云端服务器记录的所述源终端的设备标识、应用标识和/或用户标识。因此，获取所述更新数据的局域网内源终端信息具体是从所述云端服务器获取所述源终端的设备标识、应用标识和/或用户标识。
在本实施例中，在同步单元63发出同步请求之前，源终端已经和云端服务器进行内容交互，使云端服务器的内容得以更新，与此同时，云端服务器记录本次更新的源终端的设备标识、应用标识和/或用户标识。
在本实施例中，源终端和云端服务器交互时，云端服务器只负责记录数据上传和下载，以及操作记录的管理，因此，云端服务器的服务简单清晰，避免了云端服务器因计算和通知源终端设备的操作而负担额外的带宽和影响云端服务器性能的问题。
在本实施例中，根据所述源终端的设备标识、应用标识和/或用户标识 与源终端建立局域网内数据连接，通过所述数据连接同步所述更新数据。
在本实施例中，数据同步装置和云端服务器进行内容对比，发现有内容需要更新同步时，获取单元62从云端服务器会获取到对本次更新内容进行操作的源终端的设备标识、应用标识和/或用户标识，根据源终端的设备标识、应用标识和/或用户标识，通过局域网从源终端同步所述更新数据，完成数据和文件的同步。此处，同步单元63在和源终端同步时，可以查看源终端的待同步内容，并对源终端包括的内容进行选择性同步，此处可以是与源终端包括的全部内容进行同步，也可以只和源终端其中一部分内容进行同步。
在本实施例中，同步单元63向处于同一局域网的源终端发出同步请求。其中，数据同步装置和源终端的同步连接关系是多对多关系。采用此种方式，其内容同步速率高，同步更加有效率。
本领域的技术人员应当这样认为：本实施例提供的数据同步装置是与上述所述的各个方法实施例基于相同构思的，方法实施例中的相应内容适用于装置实施例，此处不再赘述。
实施例六
图7是本申请实施例提供的一种用户终端的结构示意图。如图7所示，该用户终端包括：
通信单元71，与源终端建立局域网内数据连接，以及与云端服务器建立网络连接，
中央处理器72，用于检测云端服务器是否存在更新数据，当检测到所述云端服务器存在更新数据时，从所述云端服务器获取所述更新数据来源的局域网内源终端的标识信息，并根据所述源终端的标识信息，从源终端同步所述更新数据。
在本发明实施例中，通过检测云端服务器是否存在更新数据，当检测到所述云端服务器存在更新数据时，从所述云端服务器获取所述更新数据来源的局域网内源终端的标识信息，并根据所述源终端的标识信息，从源终端同步所述更新数据。此过程在同一局域网内实现，避免了云端服务器充当各个源终端和各个待同步终端之间同步的中介，降低了云端服务器的带宽负荷，而且，大大缩短局域网内终端间数据同步时间，提高了同步效 率。
在本申请的上述实施例中阐述的技术方案不仅适用于基于局域网内的云同步，还可以适用于互联网上的服务器之间的同步。
专业人员应该还可以进一步意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。所述的计算机软件可存储于计算机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。其中，所述的存储介质可为磁碟、光盘、只读存储记忆体或随机存储记忆体等。
中央处理器为该用户终端的控制中心，利用各种接口和线路连接整个电子设备的各个部分，通过运行或执行存储在存储单元内的软件程序和/或模块，以及调用存储在存储单元内的数据，以执行电子设备的各种功能和/或处理数据。所述中央处理器可以由集成电路组成，也可以由连接多颗相同功能或不同功能的封表集成芯片而组成。即处理器可以是GPU、数字信号处理器、及通信单元中的控制芯片的组合。
实施例七
本申请实施例还提供了一种非暂态计算机可读存储介质，所述计算机可读存储介质存储有计算机可执行指令，该计算机可执行指令可执行上述任意方法实施例中的局域网内数据同步方法。
图8为本申请实施例提供的一种电子设备的硬件结构示意图，如图8所示，该电子设备8包括：
一个或多个处理器81以及存储器82，图8中以一个处理器81为例。
处理器81和存储器82可以通过总线或者其他方式连接，图8中以通过总线连接为例。
存储器82作为一种非暂态计算机可读存储介质，可用于存储非易失性软件程序、非易失性计算机可执行程序以及模块，如本申请实施例中的局 域网内数据同步方法对应的程序指令/模块(例如，附图6所示的检测单元61、获取单元62、同步单元63和选择单元64)。处理器81通过运行存储在存储器82中的非易失性软件程序、指令以及模块，从而执行电子设备的各种功能应用以及数据处理，即实现上述方法实施例局域网内数据同步方法。
存储器82可以包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需要的应用程序；存储数据区可存储根据该电子设备的使用所创建的数据等。此外，存储器82可以包括高速随机存取存储器，还可以包括非暂态存储器，例如至少一个磁盘存储器件、闪存器件、或其他非暂态固态存储器件。在一些实施例中，存储器82可选包括相对于处理器81远程设置的存储器，这些远程存储器可以通过网络连接至电子设备。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
所述一个或者多个模块存储在所述存储器82中，当被所述一个或者多个处理器81执行时，执行上述任意方法实施例中的局域网内数据同步方法，例如，执行以上描述的图2中的方法步骤S21至步骤S23、图3中的方法步骤S31至步骤S34、图4中的方法步骤S41至步骤S46和图5中的方法步骤S51至步骤S57；实现图6中的单元61-64和图7中的单元71-71的功能。
上述产品可执行本申请实施例所提供的方法，具备执行方法相应的功能模块和有益效果。未在本实施例中详尽描述的技术细节，可参见本申请实施例所提供的方法。
本申请实施例的电子设备以多种形式存在，包括但不限于：
(1)移动通信设备：这类设备的特点是具备移动通信功能，并且以提供话音、数据通信为主要目标。这类终端包括:智能手机(例如iPhone)、多媒体手机、功能性手机，以及低端手机等。
(2)超移动个人计算机设备：这类设备属于个人计算机的范畴，有计算和处理功能，一般也具备移动上网特性。这类终端包括:PDA、MID和UMPC设备等，例如iPad。
(3)便携式娱乐设备：这类设备可以显示和播放多媒体内容。该类设备包括:音频、视频播放器(例如iPod)，掌上游戏机，电子书，以及智能玩具 和便携式车载导航设备。
(4)服务器：提供计算服务的设备，服务器的构成包括处理器、硬盘、内存、系统总线等，服务器和通用的计算机架构类似，但是由于需要提供高可靠的服务，因此在处理能力、稳定性、可靠性、安全性、可扩展性、可管理性等方面要求较高。
(5)其他具有数据交互功能的电子装置。
以上所描述的设备实施例仅仅是示意性的，其中作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到至少两个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到各实施方式可借助软件加通用硬件平台的方式来实现，当然也可以通过硬件。基于这样的理解，上述技术方案本质上或者说对相关技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品可以存储在计算机可读存储介质中，如ROM/RAM、磁碟、光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行各个实施例或者实施例的某些部分所述的方法。
最后应说明的是：以上各实施例仅用以说明本申请的技术方案，而非对其限制；在本申请的思路下，以上实施例或者不同实施例中的技术特征之间也可以进行组合，步骤可以以任意顺序实现，并存在如上所述的本申请的不同方面的许多其它变化，为了简明，它们没有在细节中提供；尽管参照前述各实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分或者全部技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的范围。

Claims (13)

  1. 一种局域网内数据同步方法，所述方法应用于用户终端，其特征在于，包括：
    检测云端服务器是否存在更新数据；
    当检测到所述云端服务器存在更新数据时，从所述云端服务器获取所述更新数据来源的局域网内源终端的标识信息；
    根据所述源终端的标识信息，从所述源终端同步所述更新数据。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    从所述更新数据中选择待更新数据，则
    所述获取所述更新数据来源的局域网内源终端的标识信息，具体为：
    获取所述待更新数据来源的局域网内源终端的标识信息；
    所述从源终端同步所述更新数据，具体为：
    从所述源终端同步所述待更新数据。
  3. 根据权利要求1或2所述的方法，其特征在于，所述更新数据由所述源终端同步更新数据至云端服务器。
  4. 根据权利要求3所述的方法，其特征在于，所述局域网内源终端的标识信息包括云端服务器记录的所述源终端的设备标识、应用标识和/或用户标识；
    所述获取所述更新数据的局域网内源终端的标识信息，具体为：
    从所述云端服务器获取所述源终端的设备标识、应用标识和/或用户标识。
  5. 根据权利要求4所述的方法，其特征在于，所述根据所述源终端的标识信息，从所述源终端同步所述更新数据，具体包括：
    根据所述源终端的设备标识、应用标识和/或用户标识与源终端建立局域网内数据连接；
    通过所述局域网内数据连接同步所述更新数据。
  6. 一种局域网内数据同步装置，其特征在于，包括：
    检测单元，用于检测云端服务器是否存在更新数据；
    获取单元，用于当检测到所述云端服务器存在更新数据时，从所述云 端服务器获取所述更新数据来源的局域网内源终端的标识信息；
    同步单元，用于根据所述源终端的标识信息，从所述源终端同步所述更新数据。
  7. 根据权利要求6所述的装置，其特征在于，所述装置还包括：
    选择单元，用于从所述更新数据中选择待更新数据，则
    所述获取单元，具体用于：获取所述待更新数据来源的局域网内源终端的标识信息；
    所述同步单元，具体用于：从所述源终端同步所述待更新数据。
  8. 根据权利要求6或7所述的装置，其特征在于，所述更新数据由所述源终端同步更新数据至云端服务器。
  9. 根据权利要求8所述的装置，所述源终端的标识信息包括：
    云端服务器记录的所述源终端的设备标识、应用标识和/或用户标识，所述获取单元，具体用于：从所述云端服务器获取所述源终端的设备标识、应用标识和/或用户标识；
    所述更新单元，具体用于：根据所述源终端的设备标识、应用标识和/或用户标识与源终端建立局域网内数据连接，通过所述局域网内数据连接同步所述更新数据。
  10. 一种用户终端，其特征在于，包括：
    通信单元，用于与源终端建立局域网内数据连接，以及与云端服务器建立网络连接；
    中央处理器，用于检测云端服务器是否存在更新数据；当检测到所述云端服务器存在更新数据时，从所述云端服务器获取所述更新数据来源的局域网内源终端的标识信息；并根据所述源终端的标识信息，从源终端同步所述更新数据。
  11. 一种电子设备，其特征在于，包括：
    至少一个处理器；以及，
    与所述至少一个处理器通信连接的存储器；其中，
    所述存储器存储有可被所述一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够：
    检测云端服务器是否存在更新数据；
    当检测到所述云端服务器存在更新数据时，从所述云端服务器获取所述更新数据来源的局域网内源终端的标识信息；
    根据所述源终端的标识信息，从源终端同步所述更新数据。
  12. 一种非暂态计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有计算机可执行指令，所述计算机可执行指令用于使计算机执行权利要求1-5任一项所述的方法。
  13. 一种计算机程序产品，其特征在于，所述计算机程序产品包括存储在非暂态计算机可读存储介质上的计算机程序，所述计算机程序包括程序指令，当所述程序指令被计算机执行时，使所述计算机执行权利要求1-5任一项所述的方法。
PCT/CN2016/099901 2016-04-12 2016-09-23 一种局域网内数据同步方法及其装置、用户终端 WO2017177621A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610224855.1 2016-04-12
CN201610224855.1A CN105933393A (zh) 2016-04-12 2016-04-12 一种局域网内数据同步方法及其装置、用户终端

Publications (1)

Publication Number Publication Date
WO2017177621A1 true WO2017177621A1 (zh) 2017-10-19

Family

ID=56838036

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/099901 WO2017177621A1 (zh) 2016-04-12 2016-09-23 一种局域网内数据同步方法及其装置、用户终端

Country Status (2)

Country Link
CN (1) CN105933393A (zh)
WO (1) WO2017177621A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107613024A (zh) * 2017-10-31 2018-01-19 维沃移动通信有限公司 一种数据同步方法及移动终端
CN112163042A (zh) * 2020-09-24 2021-01-01 杭州安恒信息技术股份有限公司 多变数据同步方法、装置、电子装置及存储介质
CN112860721A (zh) * 2021-03-12 2021-05-28 云知声智能科技股份有限公司 一种智慧园区的云端数据更新方法、装置和系统
CN113765985A (zh) * 2021-01-15 2021-12-07 北京京东拓先科技有限公司 用于同步消息的方法和装置
CN113923230A (zh) * 2020-06-22 2022-01-11 华为技术有限公司 数据同步方法、电子设备和计算机可读存储介质

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105933393A (zh) * 2016-04-12 2016-09-07 乐视控股（北京）有限公司 一种局域网内数据同步方法及其装置、用户终端
CN109167756B (zh) * 2018-07-30 2020-09-04 腾讯科技（深圳）有限公司 一种用户数据的同步方法、装置及存储介质
CN109067913A (zh) * 2018-09-19 2018-12-21 量子云未来（北京）信息科技有限公司 一种维持数据同步的方法及装置
CN112202864B (zh) * 2020-09-24 2022-12-09 建信金融科技有限责任公司 一种上下文切换系统、方法、装置、设备及介质
CN114301929B (zh) * 2021-12-10 2024-03-08 阿里巴巴（中国）有限公司 云端剪贴板数据同步方法、装置、云服务器和系统
CN117201510A (zh) * 2022-05-30 2023-12-08 华为技术有限公司 一种文件同步方法、装置、设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103108051A (zh) * 2013-02-27 2013-05-15 上海够快网络科技有限公司 一种从云端服务器同步共享文件的方法
CN103327037A (zh) * 2012-03-20 2013-09-25 中兴通讯股份有限公司 数据同步方法及装置
CN103873451A (zh) * 2012-12-17 2014-06-18 中国移动通信集团公司 一种数据同步的方法、设备和系统
CN104660706A (zh) * 2015-03-09 2015-05-27 陈健强 一种局域网内多终端数据交互方法及其系统
CN105933393A (zh) * 2016-04-12 2016-09-07 乐视控股（北京）有限公司 一种局域网内数据同步方法及其装置、用户终端

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2787696B1 (en) * 2012-11-15 2016-10-26 Huawei Device Co., Ltd. Method and device for transferring web real-time communication session
CN103491137A (zh) * 2013-09-02 2014-01-01 用友软件股份有限公司 数据同步系统和数据同步方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103327037A (zh) * 2012-03-20 2013-09-25 中兴通讯股份有限公司 数据同步方法及装置
CN103873451A (zh) * 2012-12-17 2014-06-18 中国移动通信集团公司 一种数据同步的方法、设备和系统
CN103108051A (zh) * 2013-02-27 2013-05-15 上海够快网络科技有限公司 一种从云端服务器同步共享文件的方法
CN104660706A (zh) * 2015-03-09 2015-05-27 陈健强 一种局域网内多终端数据交互方法及其系统
CN105933393A (zh) * 2016-04-12 2016-09-07 乐视控股（北京）有限公司 一种局域网内数据同步方法及其装置、用户终端

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107613024A (zh) * 2017-10-31 2018-01-19 维沃移动通信有限公司 一种数据同步方法及移动终端
CN113923230A (zh) * 2020-06-22 2022-01-11 华为技术有限公司 数据同步方法、电子设备和计算机可读存储介质
CN112163042A (zh) * 2020-09-24 2021-01-01 杭州安恒信息技术股份有限公司 多变数据同步方法、装置、电子装置及存储介质
CN112163042B (zh) * 2020-09-24 2024-01-23 杭州安恒信息技术股份有限公司 多变数据同步方法、装置、电子装置及存储介质
CN113765985A (zh) * 2021-01-15 2021-12-07 北京京东拓先科技有限公司 用于同步消息的方法和装置
CN112860721A (zh) * 2021-03-12 2021-05-28 云知声智能科技股份有限公司 一种智慧园区的云端数据更新方法、装置和系统

Also Published As

Publication number Publication date
CN105933393A (zh) 2016-09-07

Similar Documents

Publication Publication Date Title
WO2017177621A1 (zh) 一种局域网内数据同步方法及其装置、用户终端
US11533220B2 (en) Network-assisted consensus protocol
US10560261B1 (en) Systems and techniques for capture of trusted media data
US20170163479A1 (en) Method, Device and System of Renewing Terminal Configuration In a Memcached System
JP6385336B2 (ja) クラウド同期システムのためのテレメトリ・システム
US10110538B2 (en) Method and apparatus for message transmission
JP2021504847A (ja) クロスブロックチェーンインタラクション方法、装置、システム、および電子デバイス
WO2017107542A1 (zh) 视频节目获取方法、设备及系统
WO2017028779A1 (zh) 物联网协议转换功能的配置方法、装置、非易失性计算机存储介质和电子设备
US20170163478A1 (en) Method,electronic device and system for updating client configuration in key-value pair database
US9774642B2 (en) Method and device for pushing multimedia resource and display terminal
US11249796B2 (en) Method and apparatus for enhanced assertion management in cloud media processing
GB2490759A (en) Initiation, failure recovery and setting sharing in video and teleconferences
US10673931B2 (en) Synchronizing method, terminal, and server
US10623450B2 (en) Access to data on a remote device
WO2017092311A1 (zh) 视频数据的获取方法、装置及系统
US20170171571A1 (en) Push Video Documentation Methods and Appliances
US20170155740A1 (en) Method, Electronic Device and System for Acquiring Video Data
CN104737580B (zh) 用于移动蜂窝网络中受控数据上传的方法和设备
US20170187800A1 (en) File synchronization method, electronic device
WO2016155363A1 (zh) 多媒体文件播放器的播放列表的维护方法及装置
US20150281317A1 (en) Requesting media content segments via multiple network connections
WO2017088294A1 (zh) 用于建立无线连接的方法与设备
US10313469B2 (en) Method, apparatus and system for processing user generated content
US20170063956A1 (en) Coordinating state changes among multiple media devices

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16898435

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 16898435

Country of ref document: EP

Kind code of ref document: A1