WO2019052153A1 - 一种数据存取方法及系统 - Google Patents

一种数据存取方法及系统 Download PDF

Info

Publication number
WO2019052153A1
WO2019052153A1 PCT/CN2018/081232 CN2018081232W WO2019052153A1 WO 2019052153 A1 WO2019052153 A1 WO 2019052153A1 CN 2018081232 W CN2018081232 W CN 2018081232W WO 2019052153 A1 WO2019052153 A1 WO 2019052153A1
Authority
WO
WIPO (PCT)
Prior art keywords
storage device
client
private cloud
account
cloud platform
Prior art date
Application number
PCT/CN2018/081232
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 WO2019052153A1 publication Critical patent/WO2019052153A1/zh

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1446Point-in-time backing up or restoration of persistent data
    • G06F11/1448Management of the data involved in backup or backup restore
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1446Point-in-time backing up or restoration of persistent data
    • G06F11/1458Management of the backup or restore process
    • G06F11/1464Management of the backup or restore process for networked environments
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/02Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]

Definitions

  • the invention relates to a data access method and system, and belongs to the technical field of data access using a storage device.
  • An object of the present invention is to provide a data access method and system, which can effectively solve the problems existing in the prior art, and in particular, cannot directly read data of a storage device or directly back up data to a storage device by a client.
  • a data access method including the following steps:
  • the ID of the storage device is bound to the client account; wherein the storage device and the client both run a private cloud platform;
  • the client accesses the private cloud platform by using the account, and accesses the storage device by using the private cloud platform. After the verification is passed, the data in the storage device is read or stored in the storage device.
  • the storage device may be a solid state hard disk or a mechanical hard disk.
  • the step S1 includes: the client sends a broadcast, and the storage device in the same local area network feeds back the ID information of the user, and the client binds the ID of the storage device to the client account according to the ID information.
  • the client sends a broadcast
  • the storage device in the same local area network feeds back the ID information of the user
  • the client binds the ID of the storage device to the client account according to the ID information.
  • the search efficiency is very high, and the interference is less, and the binding efficiency is improved.
  • the client has a WIFI module.
  • step S1 when the client contacts the storage device, the ID of the storage device is transmitted to the client through the NFC module in the storage device, and the client receives the ID and the ID of the storage device and the client.
  • the account is bound, so that the client and the storage device can be bound simply and quickly.
  • the step S1 further includes: establishing a plurality of independent accounts by using the LDAP technology, and respectively binding the IDs of the storage devices, and at the same time, allocating independent storage spaces corresponding to the respective independent accounts in the storage device; or setting the primary account and The sub-accounts respectively establish a binding relationship between the primary account and the sub-account and the storage device ID.
  • establishing a plurality of independent accounts by using the LDAP technology and respectively binding the IDs of the storage devices, and at the same time, allocating independent storage spaces corresponding to the respective independent accounts in the storage device; or setting the primary account and The sub-accounts respectively establish a binding relationship between the primary account and the sub-account and the storage device ID.
  • step S2 includes:
  • the client and the storage device are in different networks, the client logs in to the private cloud platform by using the account, and uses the private cloud platform to send a data access request to the private cloud server; the storage device uses the external network to pass the private cloud platform.
  • the domain name is sent to the private cloud server;
  • the private cloud server feeds back the domain name of the corresponding storage device to the client according to the binding relationship between the user account and the ID information of the storage device.
  • the client accesses the storage device through the private cloud platform according to the domain name of the storage device, performs remote data reading, or remotely stores the data into the storage device.
  • the client can remotely access data, which is convenient and fast, and at the same time ensures the security of data access.
  • the step S1 further includes: when the client sends a binding request of the user account and the storage device ID through the private cloud platform, the private cloud platform of the storage device determines whether the storage device ID is bound, if If the binding is complete, the binding request is rejected. If the binding is not bound, the binding request is granted.
  • the client and the storage device save the binding relationship. Update the corresponding binding relationship list between the user account and the storage device ID, thereby avoiding illegal access to the data of the storage device, ensuring the security of the data, and also reflecting the privacy of the storage device.
  • Step S2 of the present invention further includes: when the client accesses the storage device by using the private cloud platform (including when the client accesses the storage device by using the IP address of the storage device, or when the client accesses the storage device by using the domain name of the storage device)
  • the private cloud platform automatically identifies whether there is an automatic backup identifier. If there is, the Rsync technology automatically backs up the incremental data in the client to the storage device, thereby effectively avoiding repeated backup of data and improving data backup. effectiveness.
  • the invention realizes the privatization of the cloud disk, and converts the storage function of the public cloud into the private storage device, so that the storage device has the function of storing data, and can be bound to the user account externally, thereby making the data of the proximity or the remote. Intelligent access is possible while ensuring data security.
  • a data access system comprising:
  • a binding module configured to bind the ID of the storage device to the client account; wherein the storage device and the client both run a private cloud platform;
  • a client access module configured for the client to log in to the private cloud platform by using the account, and accessing the storage device by using the private cloud platform;
  • the data reading module is configured to read the data in the storage device or store the data in the storage device after the verification is passed.
  • the binding module includes:
  • a broadcast sending module configured to send a broadcast by the client
  • An ID information feedback module configured to return back to the ID information of the storage device in the same local area network
  • the A binding module is configured to bind the ID of the storage device to the client account according to the ID information.
  • the binding module includes:
  • the B binding module is configured to transmit the ID of the storage device to the client through the NFC module in the storage device when the client contacts the storage device, and the client stores the ID of the device and the client account after receiving the ID. Bind.
  • the binding module further includes:
  • the multi-account binding module is configured to establish multiple independent accounts by using the LDAP technology and bind the IDs of the storage devices respectively;
  • a storage space allocation module configured to store, by the device, an independent storage space corresponding to each independent account
  • the primary account and the sub-account binding module are used to establish a binding relationship between the primary account and the sub-account and the storage device ID.
  • the data reading module includes:
  • a client remote access module configured to: when the client and the storage device are in different networks, the client uses the account to log in to the private cloud platform, and uses the private cloud platform to send a data access request to the private cloud server;
  • a storage device access module configured to use the external network to send the domain name to the private cloud server through the private cloud platform;
  • the domain name feedback module is configured to feed back the domain name of the corresponding storage device to the client according to the binding relationship between the user account and the ID information of the storage device;
  • the remote data access module is configured to: the client accesses the storage device through the private cloud platform according to the domain name of the storage device, performs remote data reading, or remotely stores the data into the storage device.
  • the above data access system further includes:
  • a judging module configured to: when the client sends a binding request of the user account and the storage device ID through the private cloud platform, the private cloud platform of the storage device determines whether the storage device ID is bound; if it has been bound Rejecting the binding request; if not bound, agreeing to the binding request;
  • the binding relationship storage module is configured to: after the user account is bound to the storage device ID, the client and the storage device save the binding relationship;
  • the binding relationship list update module is configured to: after the user account is bound to the storage device ID, the private cloud server updates the corresponding binding relationship list of the user account and the storage device ID.
  • the above data access system further includes:
  • the automatic backup identifier identifying module is used when the client accesses the storage device by using the private cloud platform (including when the client accesses the storage device by using the IP address of the storage device, or when the client accesses the storage device by using the domain name of the storage device) ), the private cloud platform automatically identifies the presence or absence of an automatic backup;
  • the data reading module further includes:
  • the incremental data automatic backup module is used to automatically back up the incremental data in the client to the storage device by using Rsync technology if there is an automatic backup identifier.
  • the present invention has the following advantages:
  • the invention realizes the privatization of the cloud disk, and converts the storage function of the public cloud into the private storage device, so that the storage device has the function of storing data, and can be bound to the user account externally, thereby making the proximity or remote Intelligent access to data is possible while ensuring data security;
  • the client sends a broadcast, and the storage device in the same local area network feeds back its own ID information, and the client binds the ID of the storage device to the client account according to the ID information, (compared to UPNP, etc.) Therefore, the search can be performed by setting certain fields, the search efficiency is very high, and the interference is less, and the binding efficiency is improved;
  • the invention obtains the domain name of the storage device by using the private cloud server, thereby realizing remote data reading or remotely storing the data into the storage device, which is convenient and fast; and at the same time, ensures the security of data access;
  • the private cloud platform of the storage device determines whether the storage device ID is bound, if it has been bound. The binding request is rejected. If the binding is not bound, the binding request is granted. After the user account is bound to the storage device ID, the client and the storage device save the binding relationship, and the private cloud server updates the user. The corresponding binding relationship list between the account and the storage device ID, thereby avoiding illegal access to the data of the storage device, ensuring the security of the data, and also reflecting the privacy of the storage device.
  • the invention uses the LDAP technology to establish multiple independent accounts and binds them respectively with the ID of the storage device, and at the same time, allocates independent storage spaces corresponding to the individual accounts in the storage device; or sets the primary account and the sub-account respectively. Establishing a binding relationship between the primary account and the sub-account and the storage device ID; thereby implementing secure access to data of the same storage device that is equal to multiple people or has different rights;
  • the private cloud platform automatically identifies whether there is an automatic backup identifier. If there is, the Rsync technology automatically backs up the incremental data in the client to the storage device, which is convenient and quick.
  • FIG. 1 is a flow chart of a method of an embodiment of the present invention.
  • Embodiment 1 of the present invention includes the following steps:
  • the ID of the storage device is bound to the client account; wherein the storage device and the client both run a private cloud platform;
  • the client accesses the private cloud platform by using the account, and accesses the storage device by using the private cloud platform. After the verification is passed, the data in the storage device is read or stored in the storage device.
  • Step S1 includes: the client sends a broadcast, and the storage device in the same local area network feeds back its own ID information, and the client binds the ID of the storage device to the client account according to the ID information.
  • LDAP technology can be used to establish multiple independent accounts and bind to the ID of the storage device respectively, and at the same time, the storage device is allocated and The independent storage space corresponding to each independent account; or the primary account and the sub-account are respectively set up to establish a binding relationship between the primary account and the sub-account and the storage device ID.
  • Step S2 includes:
  • the client and the storage device are in different networks, the client logs in to the private cloud platform by using the account, and uses the private cloud platform to send a data access request to the private cloud server; the storage device uses the external network to pass the private cloud platform.
  • the domain name is sent to the private cloud server;
  • the private cloud server feeds back the domain name of the corresponding storage device to the client according to the binding relationship between the user account and the ID information of the storage device.
  • the client accesses the storage device through the private cloud platform according to the domain name of the storage device, performs remote data reading, or remotely stores the data into the storage device.
  • the step S1 further includes: when the client sends a binding request of the user account and the storage device ID through the private cloud platform, the private cloud platform of the storage device determines whether the storage device ID is bound, if it has been bound. The binding request is rejected. If the binding is not bound, the binding request is granted. After the user account is bound to the storage device ID, the client and the storage device save the binding relationship, and the private cloud server updates the user account. A list of binding relationships with the storage device ID.
  • the client accesses the storage device by using the private cloud platform (including when the client accesses the storage device by using the IP address of the storage device, or the client uses the storage device)
  • the private cloud platform automatically identifies whether there is an automatic backup identifier, and if so, uses the Rsync technology to automatically back up the incremental data in the client to the storage device.
  • a data access system comprising:
  • a binding module configured to bind the ID of the storage device to the client account; wherein the storage device and the client both run a private cloud platform;
  • a client access module configured for the client to log in to the private cloud platform by using the account, and accessing the storage device by using the private cloud platform;
  • the data reading module is configured to read the data in the storage device or store the data in the storage device after the verification is passed.
  • the binding module includes:
  • a broadcast sending module configured to send a broadcast by the client
  • An ID information feedback module configured to return back to the ID information of the storage device in the same local area network
  • the A binding module is configured to bind the ID of the storage device to the client account according to the ID information.
  • the binding module further includes:
  • the multi-account binding module is configured to establish multiple independent accounts by using the LDAP technology and bind the IDs of the storage devices respectively;
  • a storage space allocation module configured to store, by the device, an independent storage space corresponding to each independent account
  • the primary account and the sub-account binding module are used to establish a binding relationship between the primary account and the sub-account and the storage device ID.
  • the data reading module includes:
  • a client remote access module configured to: when the client and the storage device are in different networks, the client uses the account to log in to the private cloud platform, and uses the private cloud platform to send a data access request to the private cloud server;
  • a storage device access module configured to use the external network to send the domain name to the private cloud server through the private cloud platform;
  • the domain name feedback module is configured to feed back the domain name of the corresponding storage device to the client according to the binding relationship between the user account and the ID information of the storage device;
  • the remote data access module is configured to: the client accesses the storage device through the private cloud platform according to the domain name of the storage device, performs remote data reading, or remotely stores the data into the storage device.
  • a judging module configured to: when the client sends a binding request of the user account and the storage device ID through the private cloud platform, the private cloud platform of the storage device determines whether the storage device ID is bound; if it has been bound Rejecting the binding request; if not bound, agreeing to the binding request;
  • the binding relationship storage module is configured to: after the user account is bound to the storage device ID, the client and the storage device save the binding relationship;
  • the binding relationship list update module is configured to: after the user account is bound to the storage device ID, the private cloud server updates the corresponding binding relationship list of the user account and the storage device ID.
  • the above data access system further includes:
  • the automatic backup identifier identifying module is used when the client accesses the storage device by using the private cloud platform (including when the client accesses the storage device by using the IP address of the storage device, or when the client accesses the storage device by using the domain name of the storage device) ), the private cloud platform automatically identifies the presence or absence of an automatic backup;
  • the data reading module further includes:
  • the incremental data automatic backup module is used to automatically back up the incremental data in the client to the storage device by using Rsync technology if there is an automatic backup identifier.
  • Embodiment 2 A data access method, comprising the following steps:
  • the ID of the storage device is bound to the client account; wherein the storage device and the client both run a private cloud platform;
  • the client accesses the private cloud platform by using the account, and accesses the storage device by using the private cloud platform. After the verification is passed, the data in the storage device is read or stored in the storage device.
  • step S1 when the client contacts the storage device, the ID of the storage device is transmitted to the client through the NFC module in the storage device, and the client binds the ID of the storage device to the client account after receiving the ID. .
  • Step S2 includes:
  • the client and the storage device are in different networks, the client logs in to the private cloud platform by using the account, and uses the private cloud platform to send a data access request to the private cloud server; the storage device uses the external network to pass the private cloud platform.
  • the domain name is sent to the private cloud server;
  • the private cloud server feeds back the domain name of the corresponding storage device to the client according to the binding relationship between the user account and the ID information of the storage device.
  • the client accesses the storage device through the private cloud platform according to the domain name of the storage device, performs remote data reading, or remotely stores the data into the storage device.
  • the step S1 further includes: when the client sends a binding request of the user account and the storage device ID through the private cloud platform, the private cloud platform of the storage device determines whether the storage device ID is bound, if it has been bound. The binding request is rejected. If the binding is not bound, the binding request is granted. After the user account is bound to the storage device ID, the client and the storage device save the binding relationship, and the private cloud server updates the user account. A list of binding relationships with the storage device ID.
  • a data access system comprising:
  • a binding module configured to bind the ID of the storage device to the client account; wherein the storage device and the client both run a private cloud platform;
  • a client access module configured for the client to log in to the private cloud platform by using the account, and accessing the storage device by using the private cloud platform;
  • the data reading module is configured to read the data in the storage device or store the data in the storage device after the verification is passed.
  • the binding module includes:
  • the B binding module is configured to transmit the ID of the storage device to the client through the NFC module in the storage device when the client contacts the storage device, and the client stores the ID of the device and the client account after receiving the ID. Bind.
  • the data reading module includes:
  • a client remote access module configured to: when the client and the storage device are in different networks, the client uses the account to log in to the private cloud platform, and uses the private cloud platform to send a data access request to the private cloud server;
  • a storage device access module configured to use the external network to send the domain name to the private cloud server through the private cloud platform;
  • the domain name feedback module is configured to feed back the domain name of the corresponding storage device to the client according to the binding relationship between the user account and the ID information of the storage device;
  • the remote data access module is configured to: the client accesses the storage device through the private cloud platform according to the domain name of the storage device, performs remote data reading, or remotely stores the data into the storage device.
  • a judging module configured to: when the client sends a binding request of the user account and the storage device ID through the private cloud platform, the private cloud platform of the storage device determines whether the storage device ID is bound; if it has been bound Rejecting the binding request; if not bound, agreeing to the binding request;
  • the binding relationship storage module is configured to: after the user account is bound to the storage device ID, the client and the storage device save the binding relationship;
  • the binding relationship list update module is configured to: after the user account is bound to the storage device ID, the private cloud server updates the corresponding binding relationship list of the user account and the storage device ID.
  • Embodiment 3 A data access method, comprising the following steps:
  • binding the ID of the storage device to the client account (for example, binding by using a two-dimensional code); wherein the storage device and the client both run a private cloud platform;
  • the client accesses the private cloud platform by using the account, and accesses the storage device by using the private cloud platform. After the verification is passed, the data in the storage device is read or stored in the storage device.
  • a data access system comprising:
  • a binding module configured to bind the ID of the storage device to the client account; wherein the storage device and the client both run a private cloud platform;
  • a client access module configured for the client to log in to the private cloud platform by using the account, and accessing the storage device by using the private cloud platform;
  • the data reading module is configured to read the data in the storage device or store the data in the storage device after the verification is passed.
  • Zhang San has a mobile hard disk.
  • the ID of the mobile hard disk and the client account are first used. Binding (for example, the client can send a broadcast, the mobile hard disk in the same local area network feeds back its own ID information, and the client binds the ID of the mobile hard disk to the client account according to the ID information; or utilizes the client
  • the NFC module in the mobile terminal and the mobile hard disk implements the binding between the client and the mobile hard disk. After the binding, the client and the mobile hard disk store the binding relationship; when the client needs to access the mobile hard disk, the client will be the client.
  • the binding relationship with the mobile hard disk is sent to the mobile hard disk, and the mobile hard disk is verified and fed back to the client, and the client sends a connection request to establish a connection with the mobile hard disk, and then the data in the storage device can be read or the data can be saved. Into the storage device.
  • the client can connect to the WIFI of the storage device, and then use the account to log in to the private cloud platform on the client, and the storage device verifies the account and storage. If the authentication is passed, the private cloud platform of the client is connected.
  • the storage device can be connected to the LAN through the private cloud platform.
  • the storage device can serve as an AP, so that the client can also connect.
  • LAN you can perform data access operations in the LAN. Users access data directly through the private cloud platform on the client.
  • the client and the storage device are in different networks (that is, the client and the storage device are not together, for example, the storage device is at home, the client is outdoors, the user travels with the client, and wants to store the photos and videos of the tour directly at home.
  • the private cloud platform on the client needs to send the binding relationship to the private cloud server storage, and the private cloud server also verifies whether the storage device ID is Bind, if it is bound, the binding relationship is not stored. If it is not bound, the binding relationship is stored.
  • the client logs in to the private cloud platform through the user account and sends a request to the private cloud server to access data from the storage device;
  • the storage device accesses the private cloud through an external network (such as a wireless network at home)
  • the server sends the domain name to the private cloud server through the private cloud platform;
  • the private cloud server binds the user account to the ID information of the storage device (for example, discovers the user account that is in the private cloud server and is being accessed). If the storage device has a binding relationship, the domain name of the corresponding storage device is fed back to the client through the private cloud platform; the client accesses the storage device according to the domain name of the storage device, performs remote data reading, or remotely stores the data.
  • the storage device uses 3G, 4G, 5G, etc.
  • the private cloud platform determines the client. Whether the signal sent by the terminal contains the identifier of the automatic backup, and if so, the Rsync technology is used to automatically back up the incremental data in the Zhangsan client.
  • Zhang has three mobile hard disks
  • the data access principle is the same as above, and the user account is bound to the three mobile hard disks respectively.
  • the private cloud server will use the private cloud platform to map the domain names of the three mobile hard disks. Both are fed back to the client, and the client selectively accesses it.
  • Zhang San wants to use the mobile hard disk with his family, he can use LDAP technology to establish multiple independent accounts and bind them to the ID of the storage device respectively, and at the same time, allocate independent storage space corresponding to each independent account in the mobile hard disk; Or, by setting a primary account and a sub-account, respectively establishing a binding relationship between the primary account and the sub-account and the storage device ID; thereby realizing secure access to data of the same storage device by multiple people or having different rights. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Storage Device Security (AREA)
  • Information Transfer Between Computers (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

本发明公开了一种数据存取方法及系统,所述方法包括以下步骤:S1,将存储设备的ID与客户端账号进行绑定;其中,所述的存储设备和客户端上均运行有私有云平台;S2,客户端利用账号登陆私有云平台,利用所述的私有云平台访问存储设备,验证通过后,读取存储设备中的数据或将数据存入存储设备中。本发明实现了客户端直接对存储设备的数据进行读取或直接备份数据至存储设备中;本发明通过私有云服务器获取存储设备的域名,从而实现了远程数据读取或远程将数据存入存储设备中,方便快捷;而且同时保证了数据访问的安全性。

Description

一种数据存取方法及系统 技术领域
本发明涉及一种数据存取方法及系统,属于利用存储设备进行数据存取技术领域。
背景技术
现有技术中,进行数据备份及读取存储设备中的数据都很不方便,比如备份客户端的数据时,需要先将客户端数据导入电脑,然后电脑连接存储设备,将数据导入存储设备中;当需要读取存储设备中的数据时,也需要利用电脑连接存储设备,然后通过电脑读取存储设备中的数据,因而无法实现客户端直接对存储设备的数据进行读取或直接备份数据至存储设备中;也无法实现数据的自动备份或读取。
另外,人们出游时一般都会拍摄很多照片、视频,但是又受限于客户端内存小,而且存储起来也不方便,所以无法尽兴的随意拍摄;另外,人们闲暇时喜欢看看电影或电视剧,但是由于客户端内存小,所以一般都无法下载大量的电影或电视剧在客户端中。而现有的存储设备,虽然空间大,但是无法直接进行数据读取或存储,更无法实现数据的远程存储或读取,因而使用起来仍然很不方便。
发明内容
本发明的目的在于,提供一种数据存取方法及系统,它可以有效解决现有技术中存在的问题,尤其是无法实现客户端直接对存储设备的数据进行读取或直接备份数据至存储设备中的问题。
为解决上述技术问题,本发明采用如下的技术方案:一种数据存取方法,包括以下步骤:
S1,将存储设备的ID与客户端账号进行绑定;其中,所述的存储设备和客户端上均运行有私有云平台;
S2,客户端利用账号登陆私有云平台,利用所述的私有云平台访问存储设备,验证通过后,读取存储设备中的数据或将数据存入存储设备中。
所述的存储设备可以是固态硬盘或机械硬盘。
优选的,步骤S1包括:客户端发出广播,处于同一局域网的存储设备反馈回自身的ID信息,客户端根据所述的ID信息,将存储设备的ID与客户端账号进行绑定,(相比于UPNP等方式)从而可以通过设定某些字段来进行搜索,搜索效率非常高,而且干扰较少,提高了绑定效率。
所述的客户端具有WIFI模块。
或者优选的,步骤S1中,当客户端和存储设备接触时,通过存储设备中的NFC模块将存储设备的ID传输给客户端,客户端接收到所述ID后将存储设备的ID与客户端账号进行绑定,从而可以实现客户端与存储设备简单、快捷的进行绑定。
优选的,步骤S1还包括:利用LDAP技术建立多个独立账号并分别与存储设备的ID进行绑定,同时使得存储设备中分配与各个独立账号对应的独立的存储空间;或者通过设置主账号及子账号,分别建立所述主账号及子账号与存储设备ID的绑定关系。从而实现了多人平等的或具有不同权限的对同一个存储设备的数据进行安全存取。
前述的数据存取方法中,步骤S2包括:
S21,若客户端与存储设备处于不同的网络中,客户端利用账号登陆私有云平台,利用所述的私有云平台向私有云服务器发送数据存取请求;存储设备利用外部网络通过私有云平台将其域名发送至私有云服务器;
S22,私有云服务器根据用户账号与存储设备的ID信息的对应绑定关系,将相应的存储设备的域名反馈给客户端;
S23,客户端根据所述的存储设备的域名通过私有云平台访问存储设备,进行远程数据读取或远程将数据存入存储设备中。
通过以上方法,从而可以实现客户端远程的存取数据,方便快捷;而且同时保证了数据访问的安全性。
优选的,步骤S1还包括:当客户端通过私有云平台发送用户账号与存储设备ID的绑定请求时,存储设备的私有云平台判断所述的存储设备ID是否被绑定过,如果已被绑定过,则拒绝该绑定请求;如果未被绑定过,则同意该绑定请求;用户账号与存储设备ID进行绑定后,客户端、存储设备保存该绑定关系,私有云服务器更新用户账号与存储设备ID的对应绑定关系列表,从而避免了非法访问存储设备的数据,保证了数据的安全性,同时也体现了存储设备的私有性。
本发明的步骤S2还包括:客户端利用所述的私有云平台访问存储设备时(包括客户端通过利用存储设备的IP地址访问存储设备时,或者客户端通过利用存储设备的域名访问存储设备时),私有云平台自动识别有无自动备份的标识,若有,则利用Rsync技术自动将客户端中的增量数据备份至存储设备中,从而有效避免了数据的重复备份,提高了数据备份的效率。
本发明实现云盘私有化,即将公有云的存储功能转化至私有存储设备中,从而使得存储设备既具有存储数据的功能,又可以对外与用户账号进行绑定,从而使得近距离或远程 的数据智能存取成为可能,同时可以保证数据的安全性。
一种数据存取系统,包括:
绑定模块,用于将存储设备的ID与客户端账号进行绑定;其中,所述的存储设备和客户端上均运行有私有云平台;
客户端访问模块,用于客户端利用账号登陆私有云平台,利用所述的私有云平台访问存储设备;
数据读取模块,用于验证通过后,客户端读取存储设备中的数据或将数据存入存储设备中。
优选的,所述的绑定模块包括:
广播发送模块,用于客户端发出广播;
ID信息反馈模块,用于处于同一局域网的存储设备反馈回自身的ID信息;
A绑定模块,用于客户端根据所述的ID信息,将存储设备的ID与客户端账号进行绑定。
或者优选的,所述的绑定模块包括:
B绑定模块,用于当客户端和存储设备接触时,通过存储设备中的NFC模块将存储设备的ID传输给客户端,客户端接收到所述ID后将存储设备的ID与客户端账号进行绑定。
优选的,所述的绑定模块还包括:
多账号绑定模块,用于利用LDAP技术建立多个独立账号并分别与存储设备的ID进行绑定;
存储空间分配模块,用于存储设备分配与各个独立账号对应的独立的存储空间;
或者包括:
主账号及子账号绑定模块,用于建立主账号及子账号与存储设备ID的绑定关系。
本发明的数据存取系统中,所述的数据读取模块包括:
客户端远程访问模块,用于若客户端与存储设备处于不同的网络中,客户端利用账号登陆私有云平台,利用所述的私有云平台向私有云服务器发送数据存取请求;
存储设备访问模块,用于存储设备利用外部网络通过私有云平台将其域名发送至私有云服务器;
域名反馈模块,用于私有云服务器根据用户账号与存储设备的ID信息的对应绑定关系,将相应的存储设备的域名反馈给客户端;
远程数据存取模块,用于客户端根据所述的存储设备的域名通过私有云平台访问存储设备,进行远程数据读取或远程将数据存入存储设备中。
上述的数据存取系统中,还包括:
判断模块,用于当客户端通过私有云平台发送用户账号与存储设备ID的绑定请求时,存储设备的私有云平台判断所述的存储设备ID是否被绑定过;如果已被绑定过,则拒绝该绑定请求;如果未被绑定过,则同意该绑定请求;
绑定关系存储模块,用于用户账号与存储设备ID进行绑定后,客户端、存储设备保存该绑定关系;
绑定关系列表更新模块,用于用户账号与存储设备ID进行绑定后,私有云服务器更新用户账号与存储设备ID的对应绑定关系列表。
上述的数据存取系统,还包括:
自动备份标识识别模块,用于客户端利用所述的私有云平台访问存储设备时(包括客户端通过利用存储设备的IP地址访问存储设备时,或者客户端通过利用存储设备的域名访问存储设备时),私有云平台自动识别有无自动备份的标识;
所述的数据读取模块还包括:
增量数据自动备份模块,用于若有自动备份的标识,则利用Rsync技术自动将客户端中的增量数据备份至存储设备中。
与现有技术相比,本发明具有以下优点:
1、通过将存储设备的ID与客户端账号进行绑定;客户端利用账号登陆私有云平台,利用所述的私有云平台访问存储设备,验证通过后,读取存储设备中的数据或将数据存入存储设备中,从而实现了客户端直接对存储设备的数据进行读取或直接备份数据至存储设备中;
2、本发明实现云盘私有化,即将公有云的存储功能转化至私有存储设备中,从而使得存储设备既具有存储数据的功能,又可以对外与用户账号进行绑定,从而使得近距离或远程的数据智能存取成为可能,同时可以保证数据的安全性;
3、客户端发出广播,处于同一局域网的存储设备反馈回自身的ID信息,客户端根据所述的ID信息,将存储设备的ID与客户端账号进行绑定,(相比于UPNP等方式)从而可以通过设定某些字段来进行搜索,搜索效率非常高,而且干扰较少,提高了绑定效率;
4、本发明通过利用私有云服务器获取存储设备的域名,从而实现了远程数据读取或远程将数据存入存储设备中,方便快捷;而且同时保证了数据访问的安全性;
5、本发明中,当客户端通过私有云平台发送用户账号与存储设备ID的绑定请求时,存储设备的私有云平台判断所述的存储设备ID是否被绑定过,如果已被绑定过,则拒绝该 绑定请求;如果未被绑定过,则同意该绑定请求;用户账号与存储设备ID进行绑定后,客户端、存储设备保存该绑定关系,私有云服务器更新用户账号与存储设备ID的对应绑定关系列表,从而避免了非法访问存储设备的数据,保证了数据的安全性,同时也体现了存储设备的私有性
6、本发明利用LDAP技术建立多个独立账号并分别与存储设备的ID进行绑定,同时使得存储设备中分配与各个独立账号对应的独立的存储空间;或者通过设置主账号及子账号,分别建立所述主账号及子账号与存储设备ID的绑定关系;从而实现了多人平等的或具有不同权限的对同一个存储设备的数据进行安全存取;
7、本发明客户端利用所述的私有云平台访问存储设备时(包括客户端通过利用存储设备的IP地址访问存储设备时,或者客户端通过利用存储设备的域名访问存储设备时),私有云平台自动识别有无自动备份的标识,若有,则利用Rsync技术自动将客户端中的增量数据备份至存储设备中,方便快捷。
附图说明
图1是本发明的一种实施例的方法流程图。
下面结合附图和具体实施方式对本发明作进一步的说明。
具体实施方式
本发明的实施例1:一种数据存取方法,如图1所示,包括以下步骤:
S1,将存储设备的ID与客户端账号进行绑定;其中,所述的存储设备和客户端上均运行有私有云平台;
S2,客户端利用账号登陆私有云平台,利用所述的私有云平台访问存储设备,验证通过后,读取存储设备中的数据或将数据存入存储设备中。
步骤S1包括:客户端发出广播,处于同一局域网的存储设备反馈回自身的ID信息,客户端根据所述的ID信息,将存储设备的ID与客户端账号进行绑定。
为了实现多人平等的或具有不同权限的对同一个存储设备的数据进行安全存取,可以利用LDAP技术建立多个独立账号并分别与存储设备的ID进行绑定,同时使得存储设备中分配与各个独立账号对应的独立的存储空间;或者通过设置主账号及子账号,分别建立所述主账号及子账号与存储设备ID的绑定关系。
步骤S2包括:
S21,若客户端与存储设备处于不同的网络中,客户端利用账号登陆私有云平台,利用所述的私有云平台向私有云服务器发送数据存取请求;存储设备利用外部网络通过私有云平台 将其域名发送至私有云服务器;
S22,私有云服务器根据用户账号与存储设备的ID信息的对应绑定关系,将相应的存储设备的域名反馈给客户端;
S23,客户端根据所述的存储设备的域名通过私有云平台访问存储设备,进行远程数据读取或远程将数据存入存储设备中。
步骤S1还包括:当客户端通过私有云平台发送用户账号与存储设备ID的绑定请求时,存储设备的私有云平台判断所述的存储设备ID是否被绑定过,如果已被绑定过,则拒绝该绑定请求;如果未被绑定过,则同意该绑定请求;用户账号与存储设备ID进行绑定后,客户端、存储设备保存该绑定关系,私有云服务器更新用户账号与存储设备ID的对应绑定关系列表。
为了实现对客户端中的增量数据进行自动备份,客户端利用所述的私有云平台访问存储设备时(包括客户端通过利用存储设备的IP地址访问存储设备时,或者客户端通过利用存储设备的域名访问存储设备时),私有云平台自动识别有无自动备份的标识,若有,则利用Rsync技术自动将客户端中的增量数据备份至存储设备中。
一种数据存取系统,包括:
绑定模块,用于将存储设备的ID与客户端账号进行绑定;其中,所述的存储设备和客户端上均运行有私有云平台;
客户端访问模块,用于客户端利用账号登陆私有云平台,利用所述的私有云平台访问存储设备;
数据读取模块,用于验证通过后,客户端读取存储设备中的数据或将数据存入存储设备中。
所述的绑定模块包括:
广播发送模块,用于客户端发出广播;
ID信息反馈模块,用于处于同一局域网的存储设备反馈回自身的ID信息;
A绑定模块,用于客户端根据所述的ID信息,将存储设备的ID与客户端账号进行绑定。
所述的绑定模块还包括:
多账号绑定模块,用于利用LDAP技术建立多个独立账号并分别与存储设备的ID进行绑定;
存储空间分配模块,用于存储设备分配与各个独立账号对应的独立的存储空间;
或者包括:
主账号及子账号绑定模块,用于建立主账号及子账号与存储设备ID的绑定关系。
所述的数据读取模块包括:
客户端远程访问模块,用于若客户端与存储设备处于不同的网络中,客户端利用账号登陆私有云平台,利用所述的私有云平台向私有云服务器发送数据存取请求;
存储设备访问模块,用于存储设备利用外部网络通过私有云平台将其域名发送至私有云服务器;
域名反馈模块,用于私有云服务器根据用户账号与存储设备的ID信息的对应绑定关系,将相应的存储设备的域名反馈给客户端;
远程数据存取模块,用于客户端根据所述的存储设备的域名通过私有云平台访问存储设备,进行远程数据读取或远程将数据存入存储设备中。
还包括:
判断模块,用于当客户端通过私有云平台发送用户账号与存储设备ID的绑定请求时,存储设备的私有云平台判断所述的存储设备ID是否被绑定过;如果已被绑定过,则拒绝该绑定请求;如果未被绑定过,则同意该绑定请求;
绑定关系存储模块,用于用户账号与存储设备ID进行绑定后,客户端、存储设备保存该绑定关系;
绑定关系列表更新模块,用于用户账号与存储设备ID进行绑定后,私有云服务器更新用户账号与存储设备ID的对应绑定关系列表。
上述的数据存取系统,还包括:
自动备份标识识别模块,用于客户端利用所述的私有云平台访问存储设备时(包括客户端通过利用存储设备的IP地址访问存储设备时,或者客户端通过利用存储设备的域名访问存储设备时),私有云平台自动识别有无自动备份的标识;
所述的数据读取模块还包括:
增量数据自动备份模块,用于若有自动备份的标识,则利用Rsync技术自动将客户端中的增量数据备份至存储设备中。
实施例2:一种数据存取方法,包括以下步骤:
S1,将存储设备的ID与客户端账号进行绑定;其中,所述的存储设备和客户端上均运行有私有云平台;
S2,客户端利用账号登陆私有云平台,利用所述的私有云平台访问存储设备,验证通过后,读取存储设备中的数据或将数据存入存储设备中。
步骤S1中,当客户端和存储设备接触时,通过存储设备中的NFC模块将存储设备的ID传输给客户端,客户端接收到所述ID后将存储设备的ID与客户端账号进行绑定。
步骤S2包括:
S21,若客户端与存储设备处于不同的网络中,客户端利用账号登陆私有云平台,利用所述的私有云平台向私有云服务器发送数据存取请求;存储设备利用外部网络通过私有云平台将其域名发送至私有云服务器;
S22,私有云服务器根据用户账号与存储设备的ID信息的对应绑定关系,将相应的存储设备的域名反馈给客户端;
S23,客户端根据所述的存储设备的域名通过私有云平台访问存储设备,进行远程数据读取或远程将数据存入存储设备中。
步骤S1还包括:当客户端通过私有云平台发送用户账号与存储设备ID的绑定请求时,存储设备的私有云平台判断所述的存储设备ID是否被绑定过,如果已被绑定过,则拒绝该绑定请求;如果未被绑定过,则同意该绑定请求;用户账号与存储设备ID进行绑定后,客户端、存储设备保存该绑定关系,私有云服务器更新用户账号与存储设备ID的对应绑定关系列表。
一种数据存取系统,包括:
绑定模块,用于将存储设备的ID与客户端账号进行绑定;其中,所述的存储设备和客户端上均运行有私有云平台;
客户端访问模块,用于客户端利用账号登陆私有云平台,利用所述的私有云平台访问存储设备;
数据读取模块,用于验证通过后,客户端读取存储设备中的数据或将数据存入存储设备中。
所述的绑定模块包括:
B绑定模块,用于当客户端和存储设备接触时,通过存储设备中的NFC模块将存储设备的ID传输给客户端,客户端接收到所述ID后将存储设备的ID与客户端账号进行绑定。
所述的数据读取模块包括:
客户端远程访问模块,用于若客户端与存储设备处于不同的网络中,客户端利用账号登陆私有云平台,利用所述的私有云平台向私有云服务器发送数据存取请求;
存储设备访问模块,用于存储设备利用外部网络通过私有云平台将其域名发送至私有云服务器;
域名反馈模块,用于私有云服务器根据用户账号与存储设备的ID信息的对应绑定关系,将相应的存储设备的域名反馈给客户端;
远程数据存取模块,用于客户端根据所述的存储设备的域名通过私有云平台访问存储设备,进行远程数据读取或远程将数据存入存储设备中。
还包括:
判断模块,用于当客户端通过私有云平台发送用户账号与存储设备ID的绑定请求时,存储设备的私有云平台判断所述的存储设备ID是否被绑定过;如果已被绑定过,则拒绝该绑定请求;如果未被绑定过,则同意该绑定请求;
绑定关系存储模块,用于用户账号与存储设备ID进行绑定后,客户端、存储设备保存该绑定关系;
绑定关系列表更新模块,用于用户账号与存储设备ID进行绑定后,私有云服务器更新用户账号与存储设备ID的对应绑定关系列表。
实施例3:一种数据存取方法,包括以下步骤:
S1,将存储设备的ID与客户端账号进行绑定(比如可以采用二维码的方式进行绑定);其中,所述的存储设备和客户端上均运行有私有云平台;
S2,客户端利用账号登陆私有云平台,利用所述的私有云平台访问存储设备,验证通过后,读取存储设备中的数据或将数据存入存储设备中。
一种数据存取系统,包括:
绑定模块,用于将存储设备的ID与客户端账号进行绑定;其中,所述的存储设备和客户端上均运行有私有云平台;
客户端访问模块,用于客户端利用账号登陆私有云平台,利用所述的私有云平台访问存储设备;
数据读取模块,用于验证通过后,客户端读取存储设备中的数据或将数据存入存储设备中。
本发明的一种实施例的工作原理:
比如张三有一个移动硬盘,为了实现张三可以直接通过客户端访问该移动硬盘(所述的移动硬盘和客户端中均运行有私有云平台),则首先将移动硬盘的ID与客户端账号进行绑定(比如可以利用客户端发出广播,处于同一局域网的移动硬盘反馈回自身的ID信息,客户端根据所述的ID信息,将移动硬盘的ID与客户端账号进行绑定;或者利用客户端和移动硬盘中的NFC模块实现客户端与移动硬盘的绑定);绑定之后,客户端及移动硬盘均存储 该绑定关系;下次客户端需要访问该移动硬盘时,会将客户端和移动硬盘的绑定关系发送给移动硬盘,移动硬盘进行核实之后反馈给客户端,客户端再发出连接请求,从而与移动硬盘建立连接,然后即可读取存储设备中的数据或将数据存入存储设备中了。
具体的说,若客户端与存储设备在一起,比如都在家或都在公司等,客户端可以通过存储设备的WIFI联网,然后利用账号登陆客户端上的私有云平台,存储设备验证账号与存储设备ID的绑定关系,若验证通过,则客户端的私有云平台显示已连接;此时可以通过私有云平台可以设置存储设备连接局域网,这时候存储设备可以作为一个AP,使得客户端也连入局域网,可以在局域网中进行数据存取操作了。用户直接通过客户端上的私有云平台进行数据存取操作。
若客户端与存储设备处于不同的网络中(即客户端与存储设备不在一起,比如存储设备在家,客户端在户外,用户带着客户端旅游,并想将旅游的照片、视频直接存入家里的存储设备中),则客户端账号与存储设备ID绑定之后,需要客户端上的私有云平台将该绑定关系发送至私有云服务器存储,私有云服务器同时会验证该存储设备ID是否被绑定过,如果被绑定过则不存储该绑定关系,如果未被绑定过,则存储该绑定关系。然后客户端(可利用3G、4G、5G等)通过用户账号登陆私有云平台并向私有云服务器发送从存储设备存取数据的请求;存储设备通过外部网络(比如家中的无线网络)访问私有云服务器,并将其域名通过其上的私有云平台发送至私有云服务器;私有云服务器根据用户账号与存储设备的ID信息的对应绑定关系(比如发现私有云服务器中存在与正在访问的用户账号存在绑定关系的存储设备),则将相应的存储设备的域名通过私有云平台反馈给客户端;客户端根据所述的存储设备的域名访问存储设备,进行远程数据读取或远程将数据存入存储设备中。
在张三的客户端账号与移动硬盘ID建立连接时(包括客户端通过利用移动硬盘的IP地址访问移动硬盘时,或者客户端通过利用移动硬盘的域名访问移动硬盘时),私有云平台判断客户端发送的信号是否包含自动备份的标识,若有,则利用Rsync技术对张三客户端中的增量数据进行自动备份。
如果张三有3个移动硬盘,则进行数据存取原理同上,将用户账号与3个移动硬盘分别进行绑定,当远程访问时,私有云服务器会通过私有云平台将3个移动硬盘的域名都反馈给客户端,客户端选择性的进行访问。
如果张三想与家人共同使用该移动硬盘,则可以利用LDAP技术建立多个独立账号并分别与存储设备的ID进行绑定,同时使得移动硬盘中分配与各个独立账号对应的独立的存 储空间;或者通过设置主账号及子账号,分别建立所述主账号及子账号与存储设备ID的绑定关系;从而实现了多人平等的或具有不同权限的对同一个存储设备的数据进行安全存取。

Claims (10)

  1. 一种数据存取方法,其特征在于,包括以下步骤:
    S1,将存储设备的ID与客户端账号进行绑定;其中,所述的存储设备和客户端上均运行有私有云平台;
    S2,客户端利用账号登陆私有云平台,利用所述的私有云平台访问存储设备,验证通过后,读取存储设备中的数据或将数据存入存储设备中。
  2. 根据权利要求1所述的数据存取方法,其特征在于,步骤S1包括:客户端发出广播,处于同一局域网的存储设备反馈回自身的ID信息,客户端根据所述的ID信息,将存储设备的ID与客户端账号进行绑定;或者当客户端和存储设备接触时,通过存储设备中的NFC模块将存储设备的ID传输给客户端,客户端接收到所述ID后将存储设备的ID与客户端账号进行绑定;或者利用LDAP技术建立多个独立账号并分别与存储设备的ID进行绑定,同时使得存储设备中分配与各个独立账号对应的独立的存储空间;或者通过设置主账号及子账号,分别建立所述主账号及子账号与存储设备ID的绑定关系。
  3. 根据权利要求1所述的数据存取方法,其特征在于,步骤S2包括:
    S21,若客户端与存储设备处于不同的网络中,客户端利用账号登陆私有云平台,利用所述的私有云平台向私有云服务器发送数据存取请求;存储设备利用外部网络通过私有云平台将其域名发送至私有云服务器;
    S22,私有云服务器根据用户账号与存储设备的ID信息的对应绑定关系,将相应的存储设备的域名反馈给客户端;
    S23,客户端根据所述的存储设备的域名通过私有云平台访问存储设备,进行远程数据读取或远程将数据存入存储设备中。
  4. 根据权利要求1或3所述的数据存取方法,其特征在于,步骤S1还包括:当客户端通过私有云平台发送用户账号与存储设备ID的绑定请求时,存储设备的私有云平台判断所述的存储设备ID是否被绑定过,如果已被绑定过,则拒绝该绑定请求;如果未被绑定过,则同意该绑定请求;用户账号与存储设备ID进行绑定后,客户端、存储设备保存该绑定关系,私有云服务器更新用户账号与存储设备ID的对应绑定关系列表。
  5. 根据权利要求1所述的数据存取方法,其特征在于,步骤S2还包括:客户端利用所述的私有云平台访问存储设备时,私有云平台自动识别有无自动备份的标识,若有,则利用Rsync技术自动将客户端中的增量数据备份至存储设备中。
  6. 一种数据存取系统,其特征在于,包括:
    绑定模块,用于将存储设备的ID与客户端账号进行绑定;其中,所述的存储设备和客户端 上均运行有私有云平台;
    客户端访问模块,用于客户端利用账号登陆私有云平台,利用所述的私有云平台访问存储设备;
    数据读取模块,用于验证通过后,客户端读取存储设备中的数据或将数据存入存储设备中。
  7. 根据权利要求6所述的数据存取系统,其特征在于,所述的绑定模块包括:
    广播发送模块,用于客户端发出广播;
    ID信息反馈模块,用于处于同一局域网的存储设备反馈回自身的ID信息;
    A绑定模块,用于客户端根据所述的ID信息,将存储设备的ID与客户端账号进行绑定;
    或者所述的绑定模块包括:
    B绑定模块,用于当客户端和存储设备接触时,通过存储设备中的NFC模块将存储设备的ID传输给客户端,客户端接收到所述ID后将存储设备的ID与客户端账号进行绑定。
    或者所述的绑定模块包括:
    多账号绑定模块,用于利用LDAP技术建立多个独立账号并分别与存储设备的ID进行绑定;
    存储空间分配模块,用于存储设备分配与各个独立账号对应的独立的存储空间;
    或者所述的绑定模块包括:
    主账号及子账号绑定模块,用于建立主账号及子账号与存储设备ID的绑定关系。
  8. 根据权利要求6所述的数据存取系统,其特征在于,所述的数据读取模块包括:
    客户端远程访问模块,用于若客户端与存储设备处于不同的网络中,客户端利用账号登陆私有云平台,利用所述的私有云平台向私有云服务器发送数据存取请求;
    存储设备访问模块,用于存储设备利用外部网络通过私有云平台将其域名发送至私有云服务器;
    域名反馈模块,用于私有云服务器根据用户账号与存储设备的ID信息的对应绑定关系,将相应的存储设备的域名反馈给客户端;
    远程数据存取模块,用于客户端根据所述的存储设备的域名通过私有云平台访问存储设备,进行远程数据读取或远程将数据存入存储设备中。
  9. 根据权利要求6所述的数据存取系统,其特征在于,还包括:
    判断模块,用于当客户端通过私有云平台发送用户账号与存储设备ID的绑定请求时,存储设备的私有云平台判断所述的存储设备ID是否被绑定过;如果已被绑定过,则拒绝该绑定 请求;如果未被绑定过,则同意该绑定请求;
    绑定关系存储模块,用于用户账号与存储设备ID进行绑定后,客户端、存储设备保存该绑定关系;
    绑定关系列表更新模块,用于用户账号与存储设备ID进行绑定后,私有云服务器更新用户账号与存储设备ID的对应绑定关系列表。
  10. 根据权利要求6所述的数据存取系统,其特征在于,还包括:
    自动备份标识识别模块,用于客户端利用所述的私有云平台访问存储设备时,私有云平台自动识别有无自动备份的标识;
    所述的数据读取模块还包括:
    增量数据自动备份模块,用于若有自动备份的标识,则利用Rsync技术自动将客户端中的增量数据备份至存储设备中。
PCT/CN2018/081232 2017-09-14 2018-03-30 一种数据存取方法及系统 WO2019052153A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710828511.6 2017-09-14
CN201710828511.6A CN107766176A (zh) 2017-09-14 2017-09-14 一种数据存取方法及系统

Publications (1)

Publication Number Publication Date
WO2019052153A1 true WO2019052153A1 (zh) 2019-03-21

Family

ID=61265539

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/081232 WO2019052153A1 (zh) 2017-09-14 2018-03-30 一种数据存取方法及系统

Country Status (2)

Country Link
CN (1) CN107766176A (zh)
WO (1) WO2019052153A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11283805B2 (en) 2018-07-16 2022-03-22 Alibaba Group Holding Limited Cloud device account configuration method, apparatus and system, and data processing method

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107766176A (zh) * 2017-09-14 2018-03-06 北京春鸿科技有限公司 一种数据存取方法及系统
CN108966209A (zh) * 2018-07-16 2018-12-07 佛山长意云信息技术有限公司 一种数据存储方法、装置及移动存储设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120233678A1 (en) * 2011-03-10 2012-09-13 Red Hat, Inc. Securely and automatically connecting virtual machines in a public cloud to corporate resource
CN103379144A (zh) * 2012-04-18 2013-10-30 爱国者电子科技有限公司 云存储移动装置及云存储数据的云存储方法
CN103442053A (zh) * 2013-08-23 2013-12-11 深圳市奥尼视讯技术有限公司 基于云服务平台实现远程访问存储终端的方法及系统
CN107104958A (zh) * 2017-04-14 2017-08-29 深圳市先河系统技术有限公司 管理私有云设备的方法、私有云和公有云设备及存储装置
CN107766176A (zh) * 2017-09-14 2018-03-06 北京春鸿科技有限公司 一种数据存取方法及系统

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2013178665A (ja) * 2012-02-28 2013-09-09 Keepdata Ltd バックアップシステム
CN202662003U (zh) * 2012-06-01 2013-01-09 湖南国安思科计算机系统有限公司 无线私有安全云存储设备
CN203773533U (zh) * 2014-01-13 2014-08-13 万国科技股份有限公司 移动式数据处理装置
CN104038544A (zh) * 2014-06-07 2014-09-10 深圳市人人云技术有限公司 一种远程访问和远程共享无线存储的方法和系统
CN104378410A (zh) * 2014-09-30 2015-02-25 东莞市联讯系统科技有限公司 一种微型私有云存储、传输的系统及方法
CN104883393A (zh) * 2015-04-28 2015-09-02 深圳市美贝壳科技有限公司 家庭云存储方法
CN105204964B (zh) * 2015-09-28 2019-06-25 北京奇虎科技有限公司 基于云盘的数据备份方法及装置
CN106843757B (zh) * 2017-01-11 2020-01-07 上海斐讯数据通信技术有限公司 基于多功能移动硬盘的数据同步方法及多功能移动硬盘
CN107071039B (zh) * 2017-04-24 2017-12-12 深圳至上移动科技有限公司 一种私有数据云存储系统及私有数据云存储方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120233678A1 (en) * 2011-03-10 2012-09-13 Red Hat, Inc. Securely and automatically connecting virtual machines in a public cloud to corporate resource
CN103379144A (zh) * 2012-04-18 2013-10-30 爱国者电子科技有限公司 云存储移动装置及云存储数据的云存储方法
CN103442053A (zh) * 2013-08-23 2013-12-11 深圳市奥尼视讯技术有限公司 基于云服务平台实现远程访问存储终端的方法及系统
CN107104958A (zh) * 2017-04-14 2017-08-29 深圳市先河系统技术有限公司 管理私有云设备的方法、私有云和公有云设备及存储装置
CN107766176A (zh) * 2017-09-14 2018-03-06 北京春鸿科技有限公司 一种数据存取方法及系统

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11283805B2 (en) 2018-07-16 2022-03-22 Alibaba Group Holding Limited Cloud device account configuration method, apparatus and system, and data processing method

Also Published As

Publication number Publication date
CN107766176A (zh) 2018-03-06

Similar Documents

Publication Publication Date Title
CN111045690B (zh) 区块链节点服务部署方法、装置、系统、计算设备及介质
CN110505606B (zh) 蓝牙Mesh网络及其配网鉴权方法、设备和存储介质
US9386445B2 (en) Electronic device, personal cloud apparatus, personal cloud system and method for registering personal cloud apparatus in user portal server thereof
JP2019511141A5 (zh)
US11057234B2 (en) Device control method and apparatus
CN105100052B (zh) 服务器、手机终端及其帐号与设备绑定执行、控制方法
US10812572B2 (en) Cloud-based data sharing
WO2019052153A1 (zh) 一种数据存取方法及系统
KR20110042711A (ko) 개인 네트워크를 이용한 서비스 제공 방법 및 장치
CN106685947A (zh) 一种智能电视私有云设备的访问方法及系统
KR20140135080A (ko) 무선 통신시스템에서의 UEs간 통신 방법
JP2014501469A (ja) アプリケーション識別子の割当
CN102571798A (zh) 一种公安网络系统
CN109756915A (zh) 一种无线网络管理方法及系统
US10075989B2 (en) Network system and network connecting method
CN101800686A (zh) 业务实现方法、装置和系统
CN105338089A (zh) 一种远程内容共享方法、服务器及终端
CN106603992A (zh) 一种监控系统
KR101325025B1 (ko) 셋톱박스 기반의 클라우드 서비스 방법 및 이를 위한 컴퓨터로 판독가능한 기록매체
CN107592360B (zh) 一种基于混合云的物联网数据聚合方法及系统
WO2019071924A1 (zh) 一种智能影音播放方法及系统
CN103391527B (zh) 无线接入热点设备中功能共享的实现方法、设备及系统
JP2018028724A (ja) クラウドシステム、及びアプリケーション実行装置の遠隔操作方法、並びにその課金方法
CN102694879A (zh) 业务识别方法、设备和系统
CN205829695U (zh) 一种新的基于网络存储设备的权限认证系统

Legal Events

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

Ref document number: 18856246

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 10.09.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18856246

Country of ref document: EP

Kind code of ref document: A1