CN112152967A - Data storage management method and related device - Google Patents
Data storage management method and related device Download PDFInfo
- Publication number
- CN112152967A CN112152967A CN201910568950.7A CN201910568950A CN112152967A CN 112152967 A CN112152967 A CN 112152967A CN 201910568950 A CN201910568950 A CN 201910568950A CN 112152967 A CN112152967 A CN 112152967A
- Authority
- CN
- China
- Prior art keywords
- account
- data
- authority
- authority relationship
- relationship
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 42
- 238000013500 data storage Methods 0.000 title claims abstract description 39
- 238000000034 method Methods 0.000 claims abstract description 42
- 230000004048 modification Effects 0.000 claims description 43
- 238000012986 modification Methods 0.000 claims description 43
- 238000012545 processing Methods 0.000 claims description 10
- 238000004590 computer program Methods 0.000 claims description 2
- 238000010586 diagram Methods 0.000 description 14
- 238000013461 design Methods 0.000 description 12
- 238000012795 verification Methods 0.000 description 7
- 230000008569 process Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/604—Tools and structures for managing or administering access control systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
- G06F21/6245—Protecting personal data, e.g. for financial or medical purposes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/28—Restricting access to network management systems or functions, e.g. using authorisation function to access network configuration
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- General Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Medical Informatics (AREA)
- Automation & Control Theory (AREA)
- Computing Systems (AREA)
- Storage Device Security (AREA)
Abstract
The embodiment of the application discloses a method and a related device for data storage management, wherein the authority relationship between a second device account and a first device is determined through an operation request sent by the second device account, then the operation on the first device data is executed according to the authority relationship, the operation on the first device data under the authority limit can be ensured, if the authority does not exist, the first device data cannot be operated, so that the operation on the first device data stored in a server is subjected to authority authentication, the data safety of a user is guaranteed, the data leakage is effectively prevented, the management is facilitated, and the management is clearer and more definite.
Description
Technical Field
The present application relates to the field of data processing technologies, and in particular, to a method for managing data storage and a related apparatus.
Background
In the big data era, people pay attention to the storage and management of data. Data is typically generated in the terminal device, stored in the terminal device or uploaded to a server for storage. For smart speakers, the most important data are voice conversation history data and the user's address book.
The voice conversation history data refers to voice messages generated by voice conversation with the smart sound box when the user uses the smart sound box. The voice conversation history data includes important privacy of the user and safety information of the user. If the voice conversation history data is leaked out, the lawless person may be informed of some past situations of the user.
If the voice conversation history data is simply stored in the server, the security of the user information is difficult to be guaranteed, and the privacy security of the user is threatened.
Disclosure of Invention
The embodiment of the application provides a data storage management method and a related device, which are used for solving the technical problem that the user information safety is difficult to guarantee.
A first aspect of an embodiment of the present application provides a method for data storage management, including:
acquiring an operation request sent by a second device account, wherein the operation request comprises operation on first device data, the first device data is data uploaded to a server database by first devices, and the first devices and the second device account have authority relationship;
determining the authority relationship between the second equipment account and the first equipment according to the operation request;
and executing the operation on the first device data according to the authority relationship.
In one possible design, in an implementation manner of the first aspect of the embodiment of the present application, the operation on the first device data includes at least one of operations of querying the device data, reading the device data, modifying the device data, and deleting the device data.
In one possible design, in another implementation manner of the first aspect of the embodiment of the present application, the determining, according to the operation request, the authority relationship between the second device account and the first device includes:
acquiring an authority relationship set of the first equipment or an authority relationship set of the second equipment account according to the operation request;
and acquiring the authority relationship between the first device and the second device account from the authority relationship set of the first device or the authority relationship set of the second device account.
In a possible design, in another implementation manner of the first aspect of the embodiment of the present application, the authority relationship between the first device and the second device account is an administrator authority relationship or a general member authority relationship;
the executing the operation on the first device data according to the authority relationship comprises: and if the authority relationship between the first device and the second device account is the administrator authority relationship, executing the operation on the first device data.
In a possible design, in another implementation manner of the first aspect of the embodiment of the present application, before the obtaining of the operation request sent by the second device account, the method further includes:
acquiring two-dimensional code data sent through a second device account, wherein the two-dimensional code data is acquired from the first device through the second device account;
and establishing the authority relationship between the first device and the second device account according to the two-dimensional code data.
In one possible design, in another implementation manner of the first aspect of the embodiment of the present application, after establishing the authority relationship between the first device and the second device account according to the two-dimensional code data, the method further includes:
acquiring a permission modification request sent by a second device account, wherein the permission modification request comprises modification operation on permission between first device and the second device account;
acquiring the authority relationship between the first device and the second device account according to the authority modification request;
and if the authority relationship between the first device and the second device account is the administrator authority relationship, executing modification operation.
In one possible design, in another implementation manner of the first aspect of the embodiment of the present application, after establishing the authority relationship between the first device and the second device account according to the two-dimensional code data, the method further includes:
and sending the authority relationship between the first device and the second device account to the second device account, so that the second device account displays an interface according to the authority relationship between the first device and the second device account.
A second aspect of the embodiments of the present application provides an apparatus for data storage management, including:
the acquisition unit is used for acquiring an operation request sent by a second device account, wherein the operation request comprises operation on first device data, the first device data is data uploaded to a server database by the first device, and the first device and the second device account have an authority relationship;
the processing unit is used for determining the authority relationship between the second equipment account and the first equipment according to the operation request;
and the execution unit is used for executing the operation on the first equipment data according to the authority relationship.
In one possible design, in one implementation of the second aspect of the embodiment of the present application, the operation on the first device data includes at least one of querying the device data, reading the device data, modifying the device data, and deleting the device data.
In one possible design, in another implementation manner of the second aspect of the embodiment of the present application, the processing unit is further configured to:
acquiring an authority relationship set of the first equipment or an authority relationship set of the second equipment account according to the operation request;
and acquiring the authority relationship between the first device and the second device account from the authority relationship set of the first device or the authority relationship set of the second device account.
In one possible design, in another implementation manner of the second aspect of the embodiment of the present application, the authority relationship between the first device and the second device account is an administrator authority relationship or a general member authority relationship;
the execution unit is further to: and if the authority relationship between the first device and the second device account is the administrator authority relationship, executing the operation on the first device data.
In one possible design, in another implementation manner of the second aspect of the embodiment of the present application, the apparatus further includes:
the binding unit is used for acquiring the two-dimensional code data sent by the second equipment account, and the two-dimensional code data is acquired from the first equipment by the second equipment account;
the binding unit is further used for establishing an authority relationship between the first device and the second device account according to the two-dimensional code data.
In one possible design, in another implementation manner of the second aspect of the embodiment of the present application, the apparatus further includes:
the permission modification unit is used for acquiring a permission modification request sent by the second equipment account, and the permission modification request comprises modification operation on permission between the first equipment account and the second equipment account;
the authority modifying unit is also used for acquiring the authority relationship between the first equipment and the second equipment account according to the authority modifying request; and if the authority relationship between the first device and the second device account is the administrator authority relationship, executing modification operation.
In one possible design, in another implementation manner of the second aspect of the embodiment of the present application, the apparatus further includes:
and the sending unit is used for sending the authority relationship between the first equipment and the second equipment account to the second equipment account so that the second equipment account displays an interface according to the authority relationship between the first equipment and the second equipment account.
A third aspect of the present application provides a server comprising: a memory, a transceiver, a processor, and a bus system;
wherein, the memory is used for storing programs;
the processor is used for executing the program in the memory and comprises the following steps:
acquiring an operation request sent by a second device account, wherein the operation request comprises operation on first device data, the first device data is data uploaded to a server database by first devices, and the first devices and the second device account have authority relationship;
determining the authority relationship between the second equipment account and the first equipment according to the operation request;
and executing the operation on the first device data according to the authority relationship.
The bus system is used for connecting the memory and the processor so as to enable the memory and the processor to communicate.
A fourth aspect of the present application provides a computer-readable storage medium having stored therein instructions, which when run on a computer, cause the computer to perform the method of any of the above aspects.
A fifth aspect of the application provides a computer program product comprising instructions which, when run on a computer or processor, cause the computer or processor to perform the method of any of the above aspects.
According to the technical scheme, the embodiment of the application has the following advantages:
according to the method and the device, the authority relationship between the second device account and the first device is determined through the operation request sent by the second device account, then the operation on the first device data is executed according to the authority relationship, the first device data operation under the authority limit can be guaranteed, if the authority does not exist, the first device data operation cannot be operated, the first device data operation stored in the server is enabled to be authenticated, the data safety of a user is guaranteed, the data leakage is effectively prevented, the management is facilitated, the management is enabled to be clearer and more definite.
Drawings
FIG. 1 is a system architecture diagram of a method for data storage management in an embodiment of the present application;
FIG. 2 is a diagram illustrating an embodiment of a method for data storage management according to an embodiment of the present application;
FIG. 3 is a diagram illustrating an embodiment of an apparatus for data storage management according to an embodiment of the present application;
FIG. 4 is a diagram of another embodiment of an apparatus for data storage management according to an embodiment of the present application;
FIG. 5 is a diagram of another embodiment of an apparatus for data storage management according to an embodiment of the present application;
FIG. 6 is a diagram illustrating another embodiment of an apparatus for data storage management according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of a server according to an embodiment of the present application.
Detailed Description
The embodiment of the application provides a data storage management method and a related device, which are used for solving the technical problem that the user information safety is difficult to guarantee.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims of the present application and in the drawings described above, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "corresponding" and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
It should be understood that data is shared among multiple devices, typically stored in a server, and then accessed and read by the devices to the server. Fig. 1 is a system architecture diagram of a data storage management method in an embodiment of the present application, please refer to fig. 1, when multiple devices access a server, and query, read, modify, or delete data in the server, in the embodiment of the present application, the server performs permission verification on the accessed devices, and if the permission verification is passed, the device is allowed to perform corresponding operations.
In this application embodiment, the system architecture includes first equipment and second equipment, and first equipment is smart devices, for example smart audio amplifier, intelligent wrist-watch bracelet, smart television etc. can be connected with the server to upload the server with data. The data uploaded to the server may be voice conversation history records of the user and the intelligent device, address book data, or photos, and is not limited in practical application. The second device is a terminal device, and the terminal device includes but is not limited to a mobile phone, a desktop computer, a tablet computer, a notebook computer, and a palm computer. The terminal equipment is provided with a client, and the terminal equipment can access the server through the client. The request is sent via the second device account, i.e. the request is sent via the second device with the identity of the second device account. And scanning the two-dimensional code through the second equipment account, namely scanning the two-dimensional code through the second equipment by using the identity of the second equipment account.
It will be appreciated that the first device and the second device account may establish a rights relationship. When a user uses the first device for the first time, the two-dimensional code is displayed on the first device. The user can scan the two-dimensional code through the second device account to obtain the two-dimensional code data, the two-dimensional code data comprises the information of the first device, therefore, after the two-dimensional code data are sent to the server through the second device account, the server can bind the first device with the second device account according to the information of the first device in the two-dimensional code data to establish an authority relationship, and the authority relationship can be an administrator authority relationship or a general member authority relationship.
When the first device is bound with the terminal device for the first time, the first device defaults to an administrator authority relationship. When the first device is bound again, the two-dimension code can be set on a setting interface of the first device, after a user opens the setting interface of the first device to find the two-dimension code, the two-dimension code is scanned by a second device account to be bound, and the second device account bound with the first device is defaulted to be a general member authority relationship when the second device account bound with the first device.
In this embodiment of the application, the authority relationship between the first device and the second device account may be an authority relationship between the first device identifier and the second device account identifier, or an authority relationship between the first device identifier and the second device account, which is not limited herein.
After the authority relationship between the first device and the second device account can be established, the second device account can access the first device data in the server, the first device data is uploaded to the server by the first device, and when the second device account accesses the first device data in the server, the authority verification of the server is needed. A method for data storage management provided by an embodiment of the present application will be described in detail below.
Fig. 2 is a schematic diagram of an embodiment of a method for data storage management in an embodiment of the present application, and referring to fig. 2, an embodiment of a method for data storage management in an embodiment of the present application includes:
201. acquiring an operation request sent by a second device account, wherein the operation request comprises operation on first device data, the first device data is data uploaded to a server database by first devices, and the first devices and the second device account have authority relationship;
the operation request may be an operation on the first device data, including at least one of querying the device data, reading the device data, modifying the device data, and deleting the device data. The operation request may include an identifier of the second device account indicating that the operation request is issued by the second device account, an identifier of the first device indicating that the operation is performed on the data of the first device, an operation identifier indicating what operation is performed, and a location code of the data indicating a location of the data where the operation is performed in the server.
It should be noted that the first device data is data uploaded to the server database by the first device, for example, when the smart speaker generates a voice conversation history record during a conversation with a user, the voice conversation history record is uploaded to the server database and stored. Or the intelligent watch sets alarm clock data and uploads the alarm clock data to the server database. It should be understood that the server database stores corresponding first device data according to each first device, for example, stores corresponding device data of smart speaker a according to smart speaker a, and stores corresponding device data of smart speaker B according to smart speaker B, wherein the device data of smart speaker a is bound to the identifier of smart speaker a, the device data of smart speaker B is bound to the identifier of smart speaker B, and the device data of smart speaker a is not bound to the device data of smart speaker B.
In practical application, other authority relationships may be set, such as a family member authority relationship, a visitor authority relationship, an a-level member authority relationship, and the like, and different authority relationships may perform different operations on the first device data, such as limiting the visitor authority relationship to only perform query operations, and the like, which is not limited herein.
202. Determining the authority relationship between the second equipment account and the first equipment according to the operation request;
after the operation request sent by the second device account is obtained, the authority relationship between the second device account and the first device needs to be determined according to the operation request. The authority relationship between the second device account and the first device is preset and stored in a database of the server.
In this embodiment of the application, the authority relationship associated with the second device account may be queried in the database of the server according to the identifier of the second device account in the operation request, and then the authority relationship between the second device account and the first device may be obtained through querying from the authority relationships. Or inquiring the authority relationship associated with the first device in a database of the server according to the identifier of the first device in the operation request, and then inquiring the authority relationship between the second device account and the first device from the authority relationships. In practical application, the authority relationship between the second device account and the first device may also be determined by other search methods, which is not limited herein.
203. And executing the operation on the first device data according to the authority relationship.
It can be understood that the operation allowed to be performed on the first device data by the second device account may be determined according to the authority relationship between the second device account and the first device, for example, if the authority relationship between the second device account and the first device is an administrator authority relationship, it may be determined that the second device account can perform operations of querying the device data, reading the device data, modifying the device data, and deleting the device data on the first device data; for another example, the authority relationship between the second device account and the first device is a general member authority relationship, and the second device account only has the simple authority of voice call, video call and exiting from the bound device, and does not have the authority of modifying the data of the first device. The authority relationship between the second device account and the first device and the permission operation corresponding to the authority relationship are recorded in a database of the server, the administrator authority relationship corresponds to inquiring device data, reading device data, modifying device data and deleting device data, and if the authority relationship between the second device account and the first device is the administrator authority relationship, the operation can be searched according to the administrator authority relationship.
In an embodiment of the present application, the operation request includes an operation on the first device data, for example, the operation request includes a query operation on the first device data. After the authority relationship between the second device account and the first device is determined according to the operation request, the operation on the data of the first device can be executed according to the authority relationship. For example, the operation on the first device data in the operation request is an operation of querying the first device data, the authority relationship between the second device account and the first device is an administrator authority relationship, and the administrator authority relationship includes an operation of querying the device data, so that the operation of querying the first device data can be executed.
It can be understood that, if the operation on the first device data in the operation request is an operation of querying the first device data, and the authority relationship between the second device account and the first device is a general membership relationship, and the operation of querying the device data is not included in the general membership relationship, the operation of querying the first device data is not executed, and information of "no operation authority" may be returned.
Optionally, on the basis of the foregoing embodiments corresponding to fig. 2, in an optional embodiment of the data storage management method provided in the embodiment of the present application, the determining, according to the operation request, the authority relationship between the second device account and the first device includes:
acquiring an authority relationship set of the first equipment or an authority relationship set of the second equipment account according to the operation request;
and acquiring the authority relationship between the first device and the second device account from the authority relationship set of the first device or the authority relationship set of the second device account.
In the embodiment of the present application, the above description includes two implementation manners, one of which is: acquiring an authority relation set of the first equipment according to the operation request; and acquiring the authority relationship between the first device and the account of the second device from the authority relationship set of the first device. The other realization mode is as follows: acquiring an authority relationship set of a second device account according to the operation request; and acquiring the authority relationship between the first device and the second device account from the authority relationship set of the second device account. The specific implementation mode can be selected according to the storage mode of the authority relationship between the first device and the second device account in the database in the server. Other implementation manners are also available, as long as the authority relationship between the first device and the second device account can be searched from the database of the server.
It will be appreciated that the operation request may include an identification of the first device and an identification of the second device account. The permission relationship set of the first device may be first obtained through the identifier of the first device, and then the permission relationship between the first device and the second device account may be obtained from the permission relationship set of the first device according to the identifier of the second device account. Or, the authority relationship set of the second device account may be first obtained through the identifier of the second device account, and then the authority relationship between the first device and the second device account may be obtained from the authority relationship set of the second device account.
Optionally, on the basis of the embodiments corresponding to fig. 2, in an optional embodiment of the data storage management method provided in the embodiment of the present application, the authority relationship between the first device and the second device account is an administrator authority relationship or a general member authority relationship;
the executing the operation on the first device data according to the authority relationship comprises: and if the authority relationship between the first device and the second device account is the administrator authority relationship, executing the operation on the first device data.
It can be understood that, when the authority relationship between the first device and the second device account is the administrator authority relationship, the operations that the server obtains the administrator authority relationship from the database may perform are querying the device data, reading the device data, modifying the device data and deleting the device data, and the operation on the first device data in the operation request is one of the operations, and may perform the operation.
In the embodiment of the application, more authority relationships can be set so as to perform more detailed authority limitation on the operation request.
Optionally, on the basis of the foregoing embodiments corresponding to fig. 2, in an optional embodiment of the data storage management method provided in this embodiment of the application, before the obtaining of the operation request sent by the second device account, the method further includes:
acquiring two-dimensional code data sent through a second device account, wherein the two-dimensional code data is acquired from the first device through the second device account;
and establishing the authority relationship between the first device and the second device account according to the two-dimensional code data.
It is understood that the authority relationship of the first device and the second device account is established in advance in a database of the server. The establishment mode can be binding through a two-dimension code. The case of binding the first use of the first device will be described as follows:
when the first equipment is used for the first time, a screen of the first equipment displays a two-dimensional code, wherein the two-dimensional code comprises information of the first equipment; the two-dimensional code on the screen of the first device is scanned through the second device account, the two-dimensional code data can be obtained, and then the second device account sends the two-dimensional code data to the server, so that the server establishes the authority relation between the first device and the second device account according to the two-dimensional code data. When the second device account sends the two-dimensional code data to the server, the second device account can also be provided with an identifier of the second device account, namely the identifier of the second device account, so that the server can know that the two-dimensional code data is sent by the second device account. Or the server knows that the two-dimensional code data is sent by the second device account by detecting the source of the data packet (i.e. detecting the source of the two-dimensional code data). In practical application, other manners may also be set to obtain the relationship between the two-dimensional code data and the second device account, which is not described herein again.
The server establishes an authority relationship between the first device and the second device account according to the two-dimensional code data, the two-dimensional code data sent by the server from the second device account can acquire information of the first device and information of the second device account, which can be identifiers of the first device and the second device account, and then the first device is bound according to the two-dimensional code data, and the authority relationship between the first device and the second device account is set in a database of the server to be an administrator authority relationship. The server may then send the relevant data to the first device and the second device account, so that the first device and the second device account confirm that the binding is successful and perform the corresponding procedure. For example, the first device can be used normally after being bound successfully, the two-dimensional code is not displayed on a starting screen, the two-dimensional code is placed in a setting interface, corresponding changes are made to the two-dimensional code, and the binding frequency information in the two-dimensional code data can be modified to be non-first-time binding. And after the second device account receives the data successfully bound by the server, the information of the first device can be displayed on an interface of the second device account, and the first device can be operated.
The case where the first device is not first bound will be described below.
It can be understood that after the first device has finished the first binding, the two-dimensional code will not be displayed on the startup picture, but the interface of the home page is displayed, and the first device can be normally used. If the first device needs to be bound with other second device accounts, the two-dimensional code for binding can be found on the setting interface, then the two-dimensional code is scanned by the second device account and uploaded to the server, so that the server binds the first device with the second device account, and the authority relationship between the first device and the second device account is established. The process of establishing the authority relationship between the first device and the second device account is similar to the first binding, but the difference is that after the server receives the two-dimensional code data of the second device account, the server can know that the binding is not the first binding from the two-dimensional code data, or the server searches a database of the server according to the first device identifier in the two-dimensional code data to obtain that the first device is bound with other second device accounts, so that the binding is determined to be not the first binding. And when the server determines that the binding is not the first binding, the authority relationship between the first device and the second device account is set as a general member relationship by default and is stored in a database of the server. The relevant information is then sent to the first device and the second device account.
It should be noted that, if the first device that has finished the first binding wants to perform binding again, the first device may be reset, so that the first device is restored to the state before the first device is not bound.
Optionally, on the basis of the foregoing embodiments corresponding to fig. 2, in an optional embodiment of the data storage management method provided in this embodiment of the application, after the authority relationship between the first device and the second device account is established according to the two-dimensional code data, the method further includes:
acquiring a permission modification request sent by a second device account, wherein the permission modification request comprises modification operation on permission between first device and the second device account;
acquiring the authority relationship between the first device and the second device account according to the authority modification request;
and if the authority relationship between the first device and the second device account is the administrator authority relationship, executing modification operation.
In the embodiment of the application, after the authority relationship between the first device and the second device account is established, the authority relationship can be modified, including operations such as querying, modifying, deleting, newly adding the authority relationship and the like. The following describes in detail the case of modifying the relationship of rights.
In the embodiment of the application, the operation of modifying the authority between the first device and the second device account comprises the operation of modifying the authority relationship between the first device and the second device account and the operation authority between the first device and the second device account.
When the user wants to modify the authority relationship, the user may send a request for modifying the authority via the second device account. The modification permission request comprises a modification operation on the permission relationship between the first device and the second device account, for example, a modification operation for modifying the administrator permission relationship into a general member permission relationship, and the modification permission request also comprises an identification of the first device and an identification of the second device account, which are used for indicating the modified permission relationship is the permission relationship of which devices.
It should be understood that, in the embodiment of the present application, after the authority relationship between the first device and the second device account is established, the administrator may also modify the operation authority of the general member, including modifying the operation authority of the general member on the first device, such as a voice call, a video call, and the like. The following describes in detail the case of modifying the operating permissions between the first device and the second device account.
When the administrator can modify the operation permission of the general member, the modification permission request sent by the second device account is a request for modifying the operation permission of the general member, for example, the operation permission of the general member a is a function of performing voice call and video call through the smart speaker, the operation permission of the general member a needs to be modified to a function of performing voice call only through the smart speaker, and the modification permission request sent by the second device account is a request for modifying the operation permission of the general member a to a function of performing voice call only through the smart speaker. And after the server acquires the permission modification request, firstly, performing permission verification on a second equipment account initiating the request, acquiring the permission relation between the first equipment and the second equipment account, and if the second equipment account is an administrator, modifying the operation permission of a general member A (another second equipment account) on the first equipment into a function of performing voice call only through the intelligent loudspeaker box.
It should be noted that, after receiving the permission modification request, the server needs to perform permission verification on the second device account initiating the permission modification request, specifically, to perform permission verification on the permission relationship between the first device and the second device account, if the permission relationship between the first device and the second device account is the administrator permission relationship, the permission modification request may be executed, and if the permission relationship between the first device and the second device account is the general member permission relationship, the permission modification request is rejected.
After the authority relationship between the first device and the second device account is established, an authority relationship may be added, and the case of the added authority relationship is described in detail below.
When a user wants to add a new authority relationship, the user may send a new authority relationship request through a second device account bound with a first device, where the new authority relationship request may include an identifier of the first device, an identifier of a third device account, and an authority relationship between the first device and the third device account, and the third device account is similar to the second device account. After receiving the new authority relationship request, the server may perform authority verification according to the authority relationship between the bound first device and the second device account, and if the authority relationship between the first device and the second device account is the administrator authority relationship, the authority relationship between the first device and the third device account may be newly added in the database of the server, and is defaulted to be a general member authority relationship, and specific setting may be performed according to the new authority relationship request, which is not limited herein.
In this embodiment of the present application, a blacklist may also be set, for example, if the relationship between the first device a and the second device account X is set as a blacklist relationship, the second device account X cannot be bound with the first device a.
In this embodiment of the application, when the second device communicates with the server, the corresponding interface implementation of the server is called, for example, when the second device changes an administrator, the change administrator interface implementation of the server may be called.
It is understood that, in general, a first device has only one administrator, i.e., the second device account bound to the first device, and only one second device account is an administrator account, i.e., only one authority relationship between the first device and the second device account is an administrator authority relationship. When other second device accounts are upgraded to the administrator authority relationship through the second device account, the original second device account can be downgraded to the general member authority relationship.
Optionally, on the basis of the foregoing embodiments corresponding to fig. 2, in an optional embodiment of the data storage management method provided in this embodiment of the application, after the authority relationship between the first device and the second device account is established according to the two-dimensional code data, the method further includes:
and sending the authority relationship between the first device and the second device account to the second device account, so that the second device account displays an interface according to the authority relationship between the first device and the second device account.
In this embodiment of the present application, the server sends, to the second device account, the authority relationship between the first device and the second device account, which may be an administrator authority relationship, or a general member authority relationship, for example, a manager field in the second device account sent by the server is yes, which indicates that the authority relationship between the first device and the second device account is the administrator authority relationship. When the second device account receives the administrator authority relationship, the corresponding interface can be displayed according to the administrator authority relationship, the interface is provided with a query message recording button, a delete message recording button, a change administrator option button and the like, and the interface corresponding to the general member authority relationship is not provided with the buttons because the general member authority relationship is only provided with the authorities.
It should be noted that the server database may be one database, or may be a combination of multiple databases to implement different data storage, and is specifically set according to an actual application, and is not limited herein.
The above is a detailed description of an embodiment of a method for data storage management in an embodiment of the present application, and the following is a detailed description of an embodiment of an apparatus for data storage management in an embodiment of the present application.
Fig. 3 is a schematic diagram of an embodiment of an apparatus for data storage management in an embodiment of the present application, referring to fig. 3, an embodiment of an apparatus for data storage management in an embodiment of the present application, specifically a server 300, including:
an obtaining unit 301, configured to obtain an operation request sent by a second device account, where the operation request includes an operation on first device data, the first device data is data uploaded by a first device to a server database, and the first device and the second device account have an authority relationship;
the processing unit 302 is configured to determine, according to the operation request, an authority relationship between the second device account and the first device;
an executing unit 303, configured to execute an operation on the first device data according to the authority relationship.
Optionally, on the basis of the foregoing embodiments corresponding to fig. 3, in an optional embodiment of the data storage management apparatus provided in this embodiment of the application, the operation on the first device data includes at least one of operations of querying the device data, reading the device data, modifying the device data, and deleting the device data.
Optionally, on the basis of the foregoing embodiments corresponding to fig. 3, in an optional embodiment of the data storage management apparatus provided in this embodiment of the present application, the processing unit 302 is further configured to:
acquiring an authority relationship set of the first equipment or an authority relationship set of the second equipment account according to the operation request;
and acquiring the authority relationship between the first device and the second device account from the authority relationship set of the first device or the authority relationship set of the second device account.
Optionally, on the basis of the foregoing embodiments corresponding to fig. 3, in an optional embodiment of the data storage management apparatus provided in this embodiment of the application, the authority relationship between the first device and the second device account is an administrator authority relationship or a general member authority relationship;
the execution unit 303 is further configured to: and if the authority relationship between the first device and the second device account is the administrator authority relationship, executing the operation on the first device data.
Fig. 4 is a schematic diagram of another embodiment of a data storage management apparatus in an embodiment of the present application, and optionally, on the basis of the foregoing embodiments corresponding to fig. 3, referring to fig. 4, in an optional embodiment of the data storage management apparatus provided in the embodiment of the present application, the apparatus further includes:
the binding unit 304 is configured to acquire two-dimensional code data sent through a second device account, where the two-dimensional code data is acquired from a first device through the second device account;
the binding unit 304 is further configured to establish an authority relationship between the first device and the second device account according to the two-dimensional code data.
Fig. 5 is a schematic diagram of another embodiment of a data storage management apparatus in an embodiment of the present application, and optionally, on the basis of the foregoing embodiments corresponding to fig. 3, referring to fig. 5, in an optional embodiment of the data storage management apparatus provided in the embodiment of the present application, the apparatus further includes:
a permission modification unit 305, configured to obtain a permission modification request sent by the second device account, where the permission modification request includes a permission modification operation between the first device and the second device account;
the permission modification unit 305 is further configured to obtain a permission relationship between the first device and the second device account according to the permission modification request; and if the authority relationship between the first device and the second device account is the administrator authority relationship, executing modification operation.
Fig. 6 is a schematic diagram of another embodiment of a data storage management apparatus in an embodiment of the present application, and optionally, on the basis of the foregoing embodiments corresponding to fig. 3, referring to fig. 6, in an optional embodiment of the data storage management apparatus provided in the embodiment of the present application, the apparatus further includes:
the sending unit 306 is configured to send the authority relationship between the first device and the second device account to the second device account, so that the second device account displays an interface according to the authority relationship between the first device and the second device account.
Fig. 7 is a schematic diagram of a server structure according to an embodiment of the present disclosure, where the server 700 may have a relatively large difference due to different configurations or performances, and may include one or more Central Processing Units (CPUs) 722 (e.g., one or more processors) and a memory 732, and one or more storage media 730 (e.g., one or more mass storage devices) for storing applications 742 or data 744. Memory 732 and storage medium 730 may be, among other things, transient storage or persistent storage. The program stored in the storage medium 730 may include one or more modules (not shown), each of which may include a series of instruction operations for the server. Further, the central processor 722 may be configured to communicate with the storage medium 730, and execute a series of instruction operations in the storage medium 730 on the server 700.
The server 700 may also include one or more power supplies 726, one or more wired or wireless network interfaces 750, one or more input-output interfaces 758, and/or one or more operating systems 741, such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, and so forth.
The steps performed by the server in the above embodiments may be based on the server structure shown in fig. 7.
In the embodiment of the present application, the CPU722 is configured to perform the following steps:
acquiring an operation request sent by a second device account, wherein the operation request comprises operation on first device data, the first device data is data uploaded to a server database by first devices, and the first devices and the second device account have authority relationship;
determining the authority relationship between the second equipment account and the first equipment according to the operation request;
and executing the operation on the first device data according to the authority relationship.
Optionally, the operation on the first device data includes at least one of querying the device data, reading the device data, modifying the device data, and deleting the device data.
In the embodiment of the present application, the CPU722 is further configured to perform the following steps:
acquiring an authority relationship set of the first equipment or an authority relationship set of the second equipment account according to the operation request;
and acquiring the authority relationship between the first device and the second device account from the authority relationship set of the first device or the authority relationship set of the second device account.
Optionally, the authority relationship between the first device and the second device account is an administrator authority relationship or a general member authority relationship;
in the embodiment of the present application, the CPU722 is further configured to perform the following steps:
and if the authority relationship between the first device and the second device account is the administrator authority relationship, executing the operation on the first device data.
In the embodiment of the present application, the CPU722 is further configured to perform the following steps:
acquiring two-dimensional code data sent through a second device account, wherein the two-dimensional code data is acquired from the first device through the second device account;
and establishing the authority relationship between the first device and the second device account according to the two-dimensional code data.
In the embodiment of the present application, the CPU722 is further configured to perform the following steps:
acquiring a permission modification request sent by a second device account, wherein the permission modification request comprises modification operation on permission between first device and the second device account;
acquiring the authority relationship between the first device and the second device account according to the authority modification request;
and if the authority relationship between the first device and the second device account is the administrator authority relationship, executing modification operation.
In the embodiment of the present application, the CPU722 is further configured to perform the following steps:
and sending the authority relationship between the first device and the second device account to the second device account, so that the second device account displays an interface according to the authority relationship between the first device and the second device account.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
Claims (10)
1. A method of data storage management, comprising:
acquiring an operation request sent by a second device account, wherein the operation request comprises operation on first device data, the first device data is data uploaded to a server database by first devices, and the first devices and the second device account have authority relationship;
determining the authority relationship between the second equipment account and the first equipment according to the operation request;
and executing the operation on the first equipment data according to the authority relation.
2. The method of claim 1, wherein the operation on the first device data comprises at least one of querying device data, reading device data, modifying device data, and deleting device data.
3. The method of claim 1, wherein determining the authority relationship of the second device account with the first device according to the operation request comprises:
acquiring the authority relationship set of the first equipment or the authority relationship set of the second equipment account according to the operation request;
and acquiring the authority relationship between the first device and the second device account from the authority relationship set of the first device or the authority relationship set of the second device account.
4. The method of claim 1, wherein the authority relationship between the first device and the second device account is an administrator authority relationship or a general member authority relationship;
executing the operation on the first device data according to the authority relationship comprises: and if the authority relationship between the first equipment and the second equipment account is an administrator authority relationship, executing the operation on the first equipment data.
5. The method of claim 1, wherein before the obtaining the operation request sent by the second device account, the method further comprises:
acquiring two-dimensional code data sent through the second equipment account, wherein the two-dimensional code data is acquired from the first equipment through the second equipment account;
and establishing the authority relationship between the first device and the second device account according to the two-dimensional code data.
6. The method of claim 5, wherein after establishing the authority relationship between the first device and the second device account according to the two-dimensional code data, the method further comprises:
acquiring a modification permission request sent by the second device account, wherein the modification permission request comprises modification operation on permission between the first device and the second device account;
acquiring the authority relationship between the first equipment and the second equipment account according to the authority modification request;
and if the authority relationship between the first equipment and the second equipment account is an administrator authority relationship, executing the modification operation.
7. The method of claim 5, wherein after establishing the authority relationship between the first device and the second device account according to the two-dimensional code data, the method further comprises:
and sending the authority relationship between the first device and the second device account to the second device account, so that the second device account displays an interface according to the authority relationship between the first device and the second device account.
8. An apparatus for data storage management, comprising:
the device comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring an operation request sent by a second device account, the operation request comprises operation on first device data, the first device data is data uploaded to a server database by a first device, and the first device and the second device account have authority relationship;
the processing unit is used for determining the authority relationship between the second equipment account and the first equipment according to the operation request;
and the execution unit is used for executing the operation on the first equipment data according to the authority relation.
9. A computer-readable storage medium comprising instructions which, when executed on a computer, cause the computer to perform the method of any one of claims 1 to 7.
10. A computer program product comprising instructions which, when run on a computer or processor, cause the computer or processor to perform the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910568950.7A CN112152967A (en) | 2019-06-27 | 2019-06-27 | Data storage management method and related device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910568950.7A CN112152967A (en) | 2019-06-27 | 2019-06-27 | Data storage management method and related device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112152967A true CN112152967A (en) | 2020-12-29 |
Family
ID=73868728
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910568950.7A Pending CN112152967A (en) | 2019-06-27 | 2019-06-27 | Data storage management method and related device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112152967A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113341929A (en) * | 2021-06-18 | 2021-09-03 | 中国第一汽车股份有限公司 | Electronic control unit calibration data management system, method, device and equipment |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105450691A (en) * | 2014-08-21 | 2016-03-30 | 阿里巴巴集团控股有限公司 | Service-processing method and device, and server |
| CN107734155A (en) * | 2017-09-27 | 2018-02-23 | 维沃移动通信有限公司 | A kind of data processing method and device |
| CN108959939A (en) * | 2018-04-18 | 2018-12-07 | 腾讯科技（深圳）有限公司 | A kind of system permission open method, device, system and storage medium |
| CN109587113A (en) * | 2018-10-30 | 2019-04-05 | 歌尔科技有限公司 | A kind of equipment correlating method, equipment and storage medium |
| US20190121999A1 (en) * | 2017-10-24 | 2019-04-25 | Mastercard International Incorporated | Method and system for securely controlling access to data |
-
2019
- 2019-06-27 CN CN201910568950.7A patent/CN112152967A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105450691A (en) * | 2014-08-21 | 2016-03-30 | 阿里巴巴集团控股有限公司 | Service-processing method and device, and server |
| CN107734155A (en) * | 2017-09-27 | 2018-02-23 | 维沃移动通信有限公司 | A kind of data processing method and device |
| US20190121999A1 (en) * | 2017-10-24 | 2019-04-25 | Mastercard International Incorporated | Method and system for securely controlling access to data |
| CN108959939A (en) * | 2018-04-18 | 2018-12-07 | 腾讯科技（深圳）有限公司 | A kind of system permission open method, device, system and storage medium |
| CN109587113A (en) * | 2018-10-30 | 2019-04-05 | 歌尔科技有限公司 | A kind of equipment correlating method, equipment and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113341929A (en) * | 2021-06-18 | 2021-09-03 | 中国第一汽车股份有限公司 | Electronic control unit calibration data management system, method, device and equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8126506B2 (en) | System and method for securely managing data stored on mobile devices, such as enterprise mobility data | |
| EP2975821B1 (en) | Network connection method and apparatus | |
| US9843930B2 (en) | Trusted execution environment initialization method and mobile terminal | |
| TWI761385B (en) | Device configuration method, device, and system | |
| EP3386167B1 (en) | Cloud operation interface sharing method, related device and system | |
| CN109831441B (en) | Identity authentication method, system and related components | |
| KR20170126388A (en) | Method, device and system for executing business process | |
| US11488428B2 (en) | Enabling distribution of a mobile key | |
| JP2018506754A (en) | Method, apparatus, program, and recording medium for acquiring certification material | |
| CN106022027B (en) | A kind of unlocking method and a device of mobile device | |
| CN104579665B (en) | Method for authenticating and device | |
| WO2017097258A1 (en) | Spam blocking method and apparatus, computer program, and readable medium | |
| CN107766743B (en) | Method and device for setting file access authority, terminal equipment and storage medium | |
| CN113312669B (en) | Password synchronization method, device and storage medium | |
| CN112152967A (en) | Data storage management method and related device | |
| CN107526960B (en) | System and method for protecting mobile contact information | |
| CN112395020B (en) | Safety protection method of intranet, client, target server and storage medium | |
| CN112286632A (en) | Cloud platform, cloud platform management method and device, electronic equipment and storage medium | |
| CN111132131A (en) | Number copying method, terminal and storage medium | |
| CN111753268A (en) | Single sign-on method, device, storage medium and mobile terminal | |
| CN106330899A (en) | Private cloud device account management method and system, electronic device and server | |
| WO2023280009A1 (en) | Access control method and apparatus, device, and storage medium | |
| CN107633180B (en) | Data query method and system of public security system | |
| CN114827060A (en) | Interaction method and device and electronic equipment | |
| CN108076084B (en) | Resource sharing method, device and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20201229 |