CN113722729B

CN113722729B - Authority management method, device, terminal, server and storage medium

Info

Publication number: CN113722729B
Application number: CN202110951406.8A
Authority: CN
Inventors: 王申远
Original assignee: Beijing Dajia Internet Information Technology Co Ltd
Current assignee: Beijing Dajia Internet Information Technology Co Ltd
Priority date: 2021-08-18
Filing date: 2021-08-18
Publication date: 2024-03-01
Anticipated expiration: 2041-08-18
Also published as: CN113722729A

Abstract

The disclosure relates to a rights management method, a device, a terminal, a server and a storage medium, and relates to the technical field of Internet. The method comprises the following steps: receiving information to be sent to a second account, which is input by a first account; in the case where it is determined that the entered information includes an identification of a target object, and in the case where the first account has the right to manage the target object, prompt information is displayed for characterizing that the second account has the right to access the target object. In the method, the terminal can accurately and effectively display whether the receiver corresponding to the information has the authority to access the target object or not, and the management and access efficiency of the target object are improved.

Description

Authority management method, device, terminal, server and storage medium

Technical Field

The disclosure relates to the technical field of internet, and in particular relates to a rights management method, a device, a terminal, a server and a storage medium.

Background

Currently, users can send their edited service data (e.g., documents, etc.) to terminals used by other users using terminals, and grant some rights to the other users so that the other users can review or process the documents using the terminals.

However, the process of granting the rights in the prior art is manually completed, which consumes a lot of manpower, and may not accurately and effectively grant the rights to the user.

Disclosure of Invention

The disclosure provides a rights management method, a device, a terminal, a server and a storage medium, which solve the technical problems that the authorization process is completed manually, a great deal of manpower is consumed, and corresponding rights cannot be granted to users accurately and effectively in the prior art.

The technical scheme of the embodiment of the disclosure is as follows:

according to a first aspect of embodiments of the present disclosure, a rights management method is provided. The method may include: receiving information to be sent to a second account, which is input by a first account; in the case where it is determined that the entered information includes an identification of a target object, and in the case where the first account has the right to manage the target object, prompt information is displayed for characterizing that the second account has the right to access the target object.

Optionally, the rights management method may further include: sending a query request to a server, wherein the query request comprises an identifier of the target object and an identifier of the first account, and the query request is used for requesting to determine whether the first account has the right of managing the target object; receiving a query response corresponding to the query request sent by the server; and determining whether the first account has the right to manage the target object according to the query response.

Optionally, the query request further includes an identifier of the second account, where the query request is further used to request that, if the first account has the right to manage the target object, an access right is allocated to the second account; in the case that the first account has the right to manage the target object, displaying the prompt information for indicating that the second account has the right to access the target object specifically includes: receiving a notification message sent by the server, wherein the notification message is used for indicating that the second account has the access right; and responding to the notification message, and displaying the prompt information.

Optionally, the rights management method may further include: responding to the permission changing operation input by the first account, canceling the permission of the second account to access the target object, or changing the permission of the second account to access the target object into other permissions; and displaying prompt information corresponding to the permission change operation.

Optionally, the rights management method may further include: in response to a withdrawal operation of the entered information, the second account is revoked of access to the target object.

According to a second aspect of embodiments of the present disclosure, there is provided a rights management method. The method may include: receiving a query request sent by a terminal, wherein the query request comprises an identification of a target object, an identification of a first account and an identification of a second account, and the query request is used for requesting to determine whether the first account has the authority for managing the target object or not, and distributing access authority for the second account under the condition that the first account has the authority for managing the target object; determining that the first account has the authority to manage the target object, and sending a query response corresponding to the query request to the terminal, wherein the query response is used for indicating that the first account has the authority to manage the target object; and distributing the access right to the second account, and sending a notification message to the terminal, wherein the notification message is used for indicating that the second account has the access right.

Optionally, the rights management method may further include: receiving a permission changing request sent by the terminal, wherein the permission changing request comprises an identifier of the target object and an identifier of the second account, and the permission changing request is used for requesting to change the access permission into other permissions; determining to change the access right to the other right; and distributing the other rights to the second account, and sending a rights change response to the terminal, wherein the rights change response is used for indicating that the second account has the other rights.

Optionally, the determining that the first account has the authority to manage the target object specifically includes: in the case that the first account is the creator of the target object or the creator of the target object has granted the right to manage the target object to the first account, it is determined that the first account has the right to manage the target object.

According to a third aspect of embodiments of the present disclosure, there is provided a rights management unit. The apparatus may include: the device comprises a receiving module and a display module; the receiving module is configured to receive information input by the first account and to be sent to the second account; the display module is configured to display prompt information for representing that the second account has the right to access the target object in the case that the input information comprises the identification of the target object and in the case that the first account has the right to manage the target object.

Optionally, the rights management device further includes a sending module and a determining module; the sending module is configured to send a query request to the server, wherein the query request comprises the identification of the target object and the identification of the first account, and the query request is used for requesting to determine whether the first account has the right of managing the target object; the receiving module is further configured to receive a query response corresponding to the query request sent by the server; the determining module is configured to determine whether the first account has the right to manage the target object according to the query response.

Optionally, the query request further includes an identifier of the second account, where the query request is further used to request that, if the first account has the right to manage the target object, an access right is allocated to the second account; the receiving module is further configured to receive a notification message sent by the server, where the notification message is used to indicate that the second account has the access right; the display module is specifically configured to display the prompt information in response to the notification message.

Optionally, the above rights management device further includes a processing module configured to cancel the right of the second account to access the target object or change the right of the second account to other rights in response to the right change operation input by the first account; the display module is further configured to display prompt information corresponding to the permission changing operation.

Optionally, the processing module is configured to revoke the right of the second account to access the target object in response to a revocation operation of the entered information.

According to a fourth aspect of embodiments of the present disclosure, there is provided a rights management unit. The apparatus may include: the device comprises a receiving module, a determining module and a sending module; the receiving module is configured to receive a query request sent by the terminal, wherein the query request comprises an identifier of a target object, an identifier of a first account and an identifier of a second account, and the query request is used for requesting to determine whether the first account has the right to manage the target object, and allocating access right to the second account when the first account has the right to manage the target object; the determining module is configured to determine that the first account has the right to manage the target object; the sending module is configured to send a query response corresponding to the query request to the terminal, wherein the query response is used for indicating that the first account has the authority of managing the target object; the determining module is further configured to assign the access right to the second account; the sending module is further configured to send a notification message to the terminal, where the notification message is used to indicate that the second account has the access right.

Optionally, the receiving module is further configured to receive a permission change request sent by the terminal, where the permission change request includes an identifier of the target object and an identifier of the second account, and the permission change request is used to request to change the access permission into other permissions; the determining module is further configured to determine to change the access right to the other right; the determining module is further configured to assign the other rights to the second account; the sending module is further configured to send a permission change response to the terminal, where the permission change response is used to indicate that the second account has the other permission.

Optionally, the determining module is specifically configured to determine that the first account has the right to manage the target object, if the first account is the creator of the target object, or if the creator of the target object has granted the right to manage the target object to the first account.

According to a fifth aspect of embodiments of the present disclosure, there is provided a terminal, which may include: a processor and a memory configured to store processor-executable instructions; wherein the processor is configured to execute the instructions to implement any of the above-described optional rights management methods of the first aspect.

According to a sixth aspect of embodiments of the present disclosure, there is provided a server, which may include: a processor and a memory configured to store processor-executable instructions; wherein the processor is configured to execute the instructions to implement any of the above-described optional rights management methods of the second aspect.

According to a seventh aspect of embodiments of the present disclosure, there is provided a computer-readable storage medium having instructions stored thereon, which when executed by a processor of a computer, enable the computer to perform any one of the above-described first aspect, or to perform any one of the above-described second aspect, of the optional rights management method.

According to an eighth aspect of embodiments of the present disclosure, there is provided a computer program product comprising computer instructions which, when run on a processor of a computer, cause the computer to perform the optional rights management method as in any of the first aspects or the optional rights management method as in any of the second aspects.

The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:

Based on any one of the above aspects, in the present disclosure, the terminal determines whether a target object exists by determining whether information input by the first account includes an identifier of the target object, and determines whether the first account can perform operations such as editing, deleting, accessing, etc. on the target object by determining whether the first account has authority to manage the target object; when the target object is determined to exist, and the first account client performs editing, deleting, accessing and other operations on the target object, the second account is indicated to have the authority to access the target object, so that the terminal can display prompt information for representing that the second account has the authority to access the target object, whether a receiver corresponding to the information has the authority to access the target object can be accurately and effectively displayed, and the management and access efficiency of the target object are improved.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure and do not constitute an undue limitation on the disclosure.

FIG. 1 illustrates a schematic diagram of a rights management system provided by an embodiment of the present disclosure;

FIG. 2 is a flow chart of a rights management method according to an embodiment of the disclosure;

FIG. 3 illustrates a schematic diagram of an interface display provided by an embodiment of the present disclosure;

FIG. 4 is a flow chart illustrating yet another rights management method provided by an embodiment of the present disclosure;

FIG. 5 illustrates a flow diagram of yet another rights management method provided by embodiments of the present disclosure;

FIG. 6 illustrates a flow diagram of yet another rights management method provided by embodiments of the present disclosure;

FIG. 7 illustrates yet another interface display schematic provided by an embodiment of the present disclosure;

FIG. 8 illustrates yet another interface display schematic provided by an embodiment of the present disclosure;

FIG. 9 is a flow chart illustrating yet another rights management method provided by an embodiment of the present disclosure;

FIG. 10 is a flow chart illustrating yet another rights management method provided by an embodiment of the present disclosure;

FIG. 11 is a flow chart illustrating yet another rights management method provided by an embodiment of the present disclosure;

FIG. 12 is a flow chart illustrating yet another rights management method provided by an embodiment of the present disclosure;

FIG. 13 is a flow chart illustrating yet another rights management method provided by an embodiment of the present disclosure;

Fig. 14 is a schematic structural view of a rights management unit according to an embodiment of the present disclosure;

FIG. 15 is a schematic view showing the structure of a rights management unit according to still another embodiment of the present disclosure;

FIG. 16 is a schematic diagram of a configuration of a rights management unit according to an embodiment of the present disclosure;

fig. 17 is a schematic structural view of still another rights management unit according to an embodiment of the present disclosure.

Detailed Description

In order to enable those skilled in the art to better understand the technical solutions of the present disclosure, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.

It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the foregoing figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the disclosure described herein may be capable of operation in sequences other than those illustrated or described herein. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.

It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, and/or components.

The data referred to in this disclosure may be data authorized by the user or sufficiently authorized by the parties.

As described in the background art, since the process of granting rights in the prior art is manually performed, a lot of manpower is consumed, and the corresponding rights may not be accurately and effectively granted to the user.

Based on this, the embodiment of the disclosure provides a rights management method, in which a terminal receives information to be sent to a second account input by a first account, and when determining that the input information includes an identifier of a target object, and when the first account has rights to manage the target object, the terminal displays a right for representing that the second account has rights to access the target object. In the embodiment of the disclosure, when determining that the target object exists and the first account has the authority to manage the target object (specifically, the first account can grant the authority to access the target object to other accounts), the terminal displays the prompt information for representing that the second account has the authority to access the target object, so that whether the receiver corresponding to the information has the authority to access the target object can be accurately and effectively determined and displayed, and the management and access efficiency of the target object are improved.

The rights management method, the device, the terminal, the server and the storage medium provided by the embodiment of the disclosure are applied to a scene of granting a certain right (for example, access right) to a certain account (for example, a second account). When the terminal receives the information to be sent to the second account, which is input by the first account, prompt information for representing that the second account has the right to access the target object can be displayed according to the method provided by the embodiment of the disclosure.

The rights management method provided by the embodiments of the present disclosure is exemplarily described below with reference to the accompanying drawings:

fig. 1 is a schematic diagram of a rights management system according to an embodiment of the present disclosure, as shown in fig. 1, where the rights management system may include a terminal 101, a server 102, and a terminal 103, where the server 102 may establish a connection with the terminal 101 and the terminal 103 through a wired network or a wireless network, respectively.

The above-mentioned terminals (including the terminal 101 and the terminal 103) may be mobile phones, tablet computers, desktop computers, laptop computers, handheld computers, notebook computers, ultra-mobile personal computers (ultra-mobile personal computer, UMPC), netbooks, cellular phones, personal digital assistants (personal digital assistant, PDA), augmented reality (augmented reality, AR) \virtual reality (VR) devices, and the like, which may install and use the content community application, and the specific form of the terminal is not particularly limited in the present disclosure. The system can perform man-machine interaction with a user through one or more modes of a keyboard, a touch pad, a touch screen, a remote controller, voice interaction or handwriting equipment and the like.

Specifically, the terminal 101 may send a query request to the server 102, that is, a request to determine whether the first account has authority to manage the target object. When determining that the first account has the right to manage the target object, the server 102 may send (or return) a query response corresponding to the query request to the terminal 101, that is, instruct the first account to have the right to manage the target object. Optionally, the server 102 may also send a notification message to the terminal 103, i.e. indicating that the second account has the right to access the target object, so that the second account may access the target object.

As shown in fig. 2, when the rights management method is applied to the terminal 101, the rights management method may include S101-S102.

S101, the terminal receives information to be sent to a second account, which is input by a first account.

It should be understood that the first account is one of at least one account corresponding to the terminal, and the first account may input (or edit) the information to be sent in a certain application suite corresponding to the terminal. For example, the information to be sent may be chat information to be sent to the second account.

S102, when the input information is determined to comprise the identification of the target object, and when the first account has the authority to manage the target object, the terminal displays prompt information for representing that the second account has the authority to access the target object.

It may be appreciated that the terminal may store a plurality of objects and respective identities of the plurality of objects, and in the case where the input information includes the identity of a target object, the terminal may determine that the target object is present, and determine whether the first account has authority to manage the target object, which is one of the plurality of objects.

The rights of the management target object can be understood as the management rights of the target object. Specifically, when the first account has the authority to manage the target object, the first account may perform operations such as editing, deleting, accessing, etc. on the target object, and the first account may also authorize other accounts (for example, the second account), and specifically, may grant the second account the authority to access or edit the target object, that is, grant the access authority or the editing authority.

Alternatively, the object (including the target object) in the embodiment of the disclosure may be a document or a file. When the target object is a document, the identification of the target object may be a uniform resource locator (uniform resource locator, URL) link to the document.

Specifically, the first account (i.e. the sender corresponding to the input information) sends the input information to the second account (i.e. the receiver corresponding to the input information), which can be understood as notifying the second account to access the target object. It will also be appreciated that in connection with the above description of the embodiments, when the first account has the right to manage the target object, it is indicated that the second account has the right to access the target object, so that the terminal may display prompt information for indicating that the second account has the right to access the target object.

In one implementation of the embodiment of the disclosure, the terminal may also send and display the input information.

Illustratively, as shown in fig. 3, after the input information is sent to the first account, an example of the prompt information and the input information is displayed on the display interface of the terminal.

After the first account sends information, the prompt information "the second account has authority to access the document corresponding to the xxx.com/sdkla2wnb ei" is displayed in the display area of the sent information, "the xxx.com/sdkla2wnb ei" is the identification of the target object.

The technical scheme provided by the embodiment at least has the following beneficial effects: S101-S102 can know that the terminal determines whether a target object exists or not by determining whether the information input by the first account comprises the identification of the target object, and determines whether the first account can edit, delete, access and other operations on the target object or not by determining whether the first account has the authority to manage the target object or not; when the target object is determined to exist, and the first account client performs editing, deleting, accessing and other operations on the target object, the second account is indicated to have the authority to access the target object, so that the terminal can display prompt information for representing that the second account has the authority to access the target object, whether a receiver corresponding to the information has the authority to access the target object can be accurately and effectively displayed, and the management and access efficiency of the target object are improved.

As described in connection with fig. 2 and fig. 4, the rights management method provided in the embodiment of the disclosure may further include: S103-S105.

S103, the terminal sends a query request to the server.

The query request comprises the identification of the target object and the identification of the first account, and is used for requesting to determine whether the first account has the authority of managing the target object.

S104, the terminal receives a query response corresponding to the query request sent by the server.

S105, the terminal determines whether the first account has the authority of the management target object according to the query response.

It should be appreciated that the server may determine whether the first account has the right to manage the target object, and when the server determines that the first account has the right to manage the target object, the query response indicates that the first account has the right to manage the target object. Otherwise, the query response indicates that the first account does not have the right to manage the target object, i.e. when the server determines that the first account does not have the right to manage the target object.

The technical scheme provided by the embodiment at least has the following beneficial effects: as known from S103-S105, the terminal may determine whether the first account has the authority to manage the target object by sending a query request to the server, and return a corresponding query response to the terminal. Because the query response may indicate whether the first account has the right to manage the target object, the terminal may determine whether the first account has the right to manage the target object. Whether the first account has the authority for managing the target object can be reasonably determined, and whether the prompt information needs to be displayed can be reasonably determined.

In an implementation manner of the embodiment of the present disclosure, the query request further includes an identifier of a second account, where the query request is further used to request that, if the first account has the right to manage the target object, an access right is allocated to the second account. Based on this, as shown in fig. 5 in conjunction with fig. 4, in the case where the first account has the right to manage the target object, the terminal displays the prompt information for indicating that the second account has the right to access the target object, and may specifically include S1021-S1022.

S1021, the terminal receives the notification message sent by the server.

The notification message is used for indicating that the second account has access rights.

It should be understood that the access right is the right to access the target object.

S1022, the terminal responds to the notification message and displays the prompt information.

It can be understood that the prompt information is the prompt information used for indicating that the second account has the right to access the target object.

When the server determines that the first account has the authority to manage the target object, the server may allocate the access authority to the second account, and before (after or simultaneously with) allocating the access authority to the second account, the server may further send the notification message to the terminal, that is, instruct the second account to have the access authority, so that the terminal may determine that the second account has the access authority, and then display the prompt message.

In one case, the terminal may also assign access rights to the second account in the event that the server determines that the first account has rights to manage the target object. Specifically, after the terminal receives the query response and determines that the first account has the authority to manage the target object, the access authority may be allocated to the second account, so as to display the prompt information.

In one implementation of the embodiments of the present disclosure, a plurality of objects and correspondence of respective identifications of the plurality of objects may be stored in a terminal. When the terminal receives the query response, the terminal may determine a target object from the plurality of objects based on the identification of the target object, and assign access rights to the second account if the first account is provided with the function of managing the target object.

The technical scheme provided by the embodiment at least has the following beneficial effects: as known from S1021-S1022, the terminal may receive a notification message sent by the server, where the notification message is used to instruct the second account to have the right to access the target object, and display prompt information for indicating that the second account has the right to access the target object. Since the notification message is sent before (after, or simultaneously with) the server assigning the access right to the second account, the notification message can truly and effectively reflect whether the second account has the access right. Furthermore, the terminal can accurately display the prompt information.

Referring to fig. 2, as shown in fig. 6, the rights management method provided in the embodiment of the present disclosure further includes steps S106 to S107.

And S106, responding to the permission changing operation input by the first account, and canceling the permission of the second account to access the target object by the terminal or changing the permission of the second account to access the target object into other permissions.

It should be understood that the rights change operation is to change the access rights of the second account. Specifically, canceling the right of the second account to access the target object indicates that the second account does not have the right to access the target object. And changing the authority of the second account for accessing the target object into other authorities, namely indicating that the second account has other authorities. Optionally, the other rights include editing rights or deleting rights.

S107, the terminal displays prompt information corresponding to the permission change operation.

Specifically, when the terminal cancels the right of the second account to access the target object, the terminal may display prompt information for indicating that the second account does not have the right to access the target object. When the terminal changes the right of the second account to access the target object to other rights (for example, editing rights), the terminal can display prompt information for representing that the second account has the right to edit the target object.

Optionally, a permission change control is included in the display interface (or display area) of the terminal.

In one case, the terminal may respond to a trigger operation for the rights change control that corresponds to the rights change operation described above.

For example, as shown in fig. 7 in conjunction with fig. 3, a permission change control (i.e., "cancel" in fig. 7) may be further included on the display interface of the terminal, and after the terminal responds to the triggering operation for "cancel", the terminal may cancel the permission of the second account to access the target object, i.e., the terminal should display "the second account does not have the permission to access the document corresponding to xxx.

In another case, the terminal may respond to the triggering operation for the permission change control to display a box, where the box may include multiple permission options, such as cancellation permission, editing permission, deletion permission, comment permission, management permission, and the like, where the first account is based on a confirmation operation of which permission (e.g. editing permission) is to trigger the permission change operation, specifically, changing the permission of accessing the target object by the second account to the permission of editing the target object, that is, changing the access permission to the editing permission.

Illustratively, in connection with fig. 7, as shown in fig. 8, is one example of a bullet box displayed on the terminal. After the triggering operation for the "cancel", an option box including "edit", "delete", "comment" and "manage" can be obtained. For example, the terminal may change the authority of accessing the target object to the authority of commenting the target object, i.e., change the access authority to the commentary authority, based on the confirmation operation of "commentary".

The technical scheme provided by the embodiment at least has the following beneficial effects: the S106-S107 can know that the terminal can cancel or modify the access rights (specifically, the rights of the second account to access the target object) based on the rights change operation input by the first account, so that the related rights of the second account can be quickly and effectively canceled or modified, various different types of rights can be allocated to the second account, and the diversity of the account authorization is improved.

Referring to fig. 2, as shown in fig. 9, the rights management method provided in the embodiment of the disclosure further includes step S108.

S108, responding to the withdrawal operation of the input information, and canceling the authority of the second account to access the target object by the terminal.

In connection with the above description of the embodiments, it should be understood that the input information includes an identification of the target object, and the first account may send the input information to the second account. When the terminal (e.g., the first terminal) responds to the withdrawal operation of the input information, it is indicated that the receiving end device (e.g., the second terminal) cannot receive and display the input information, and further the second account cannot access the target object based on the identification of the target object, so that the terminal can cancel the authority of the second account to access the target object.

The technical scheme provided by the embodiment at least has the following beneficial effects: as shown in S108, in response to the withdrawal operation of the input information, the terminal may cancel the permission of the second account to access the target object, and may determine, based on the withdrawal operation, that the receiving end device cannot receive and display the input information, thereby canceling the access permission of the second account, and improving the accuracy of terminal display.

As shown in fig. 10, a rights management method is applied to the server 102, and the rights management method may include S201 to S203.

S201, the server receives a query request sent by the terminal.

The query request includes an identifier of a target object, an identifier of a first account, and an identifier of a second account, and is used for requesting to determine whether the first account has the right to manage the target object, and allocating access rights to the second account when the first account has the right to manage the target object.

S202, the server determines that the first account has the authority to manage the target object, and sends a query response corresponding to the query request to the terminal.

The query response is used for indicating that the first account has the authority of managing the target object.

In an implementation manner of the embodiment of the present disclosure, when the server determines that the first account does not have the authority to manage the target object, the server may also send a query response to the terminal, where the query response is used to indicate that the first account does not have the authority to manage the target object.

S203, the server allocates access rights to the second account and sends notification messages to the terminal.

The notification message is used for indicating that the second account has the access right.

It should be understood that the explanation in S201-S203 can be referred to the descriptions in S103-S105 and S1021-S1022, and will not be repeated here.

Note that, the embodiment of the present disclosure does not limit the order of execution of the above S203 and the transmission of the query response corresponding to the query request to the terminal in S202. For example, the step S203 may be performed after the inquiry response corresponding to the inquiry request is transmitted to the terminal, the step S203 may be performed before the inquiry response corresponding to the inquiry request is transmitted to the terminal, or the step S203 may be performed while the inquiry response corresponding to the inquiry request is transmitted to the terminal.

The technical scheme provided by the embodiment at least has the following beneficial effects: as known from S201 to S203, the server may send a query response to the terminal when determining that the first account has the authority to manage the target object, where the query response is used to indicate that the first account has the authority to manage, so that the terminal may determine that the first account has the authority to manage; and the server may assign access rights to the second account and send a notification message to the terminal indicating that the first account has access rights. Therefore, the terminal not only can determine that the first account has the management authority, but also can determine that the second account has the access authority, and can accurately and effectively determine whether different accounts have the corresponding authorities corresponding to the target object, so that the management and access efficiency of the target object are improved.

In connection with fig. 10, as shown in fig. 11, the rights management method provided by the present disclosure may further include S204-S206.

S204, the server receives the permission change request sent by the terminal.

The permission change request comprises the identification of the target object and the identification of the second account, and is used for requesting to change the access permission into other permission.

It can be understood that the terminal may change the access right to other rights in response to the right change operation input by the first account, or may send the right change request to the server in response to the right change operation, and the server determines to change the access right to other rights.

In connection with the description of the above embodiments, it should be understood that the other rights may include editing rights, deleting rights, managing rights, and the like.

For example, if the other rights are editing rights, the rights change request is for requesting that the rights of the second account to access the target object be changed to the rights of the editing target object.

S205, the server determines to change the access rights to other rights.

S206, the server allocates other rights for the second account and sends a right changing response to the terminal.

Wherein the rights change response is used to indicate that the second account is provided with the other rights.

The technical scheme provided by the embodiment at least has the following beneficial effects: as known from S204-S206, in the case that the terminal needs to change the corresponding rights of the second account, a rights change request may be sent to the server; after receiving the permission change request and determining to change the access permission to other permission, the server may allocate the other permission to the second account and return a change response, so that the terminal may display prompt information for indicating that the second account has other permission. The server can determine that the access rights are changed into other rights of various types, so that the efficiency of account related rights change can be improved; and further, the terminal can display prompt information of other authorities of more types, and the accuracy of information display is improved.

Referring to fig. 10, as shown in fig. 12, in an implementation manner of the embodiment of the disclosure, the determining that the first account has the authority to manage the target object specifically includes S2021.

S2021, in a case where the first account is the creator of the target object, or the creator of the target object has granted the authority to manage the target object to the first account, the server determines that the first account has the authority to manage the target object.

It should be appreciated that in one instance, the first account may be the creator of the target object, such that the server may determine that the first account has the right to manage the target object.

In another case, the creator of the target object may be another account (e.g., a third account) that has granted the right to manage the target object to the first account, so the first account may have the right to manage the target object.

The technical scheme provided by the embodiment at least has the following beneficial effects: as known from S2021, in a case where the first account is the creator of the target object, or the creator of the target object has granted the right to manage the target object to the first account, the server may determine that the first account has the right to manage the target object. In the embodiment of the disclosure, when the first account is the creator of the target object, it is indicated that the first account already has the management authority of the target object. In addition, when the creator of the target object grants the management right to any account (for example, the first account), it is explained that any account also has the management right of the target object. In this way, the server can determine whether the first account has the authority to manage the target object by determining whether the first account is the creator of the target object or has been granted the management authority by the creator, so that whether the first account has the management authority can be accurately and effectively determined.

As shown in fig. 13, the rights management method is applied to a process based on the interaction of the respective devices in the rights management system shown in fig. 1, and may include S301 to S307.

S301, the terminal receives information to be sent to a second account, which is input by a first account.

S302, the terminal sends a query request to the server.

S303, the server receives a query request sent by the terminal.

S304, the server determines that the first account has the authority to manage the target object, and sends a query response corresponding to the query request to the terminal.

S305, the terminal receives a query response corresponding to the query request sent by the server.

S306, the terminal determines whether the first account has the authority of the management target object according to the query response.

S307, when the input information is determined to comprise the identification of the target object, and when the first account has the authority to manage the target object, the terminal displays prompt information for representing that the second account has the authority to access the target object.

It should be understood that the explanation in S301 to S307 may be referred to the description in the above embodiment, and will not be repeated here.

The technical scheme provided by the embodiment at least has the following beneficial effects: as can be seen from S301 to S307, the terminal may send a query request to the server, and determine whether the first account has the authority to manage the target object based on a query response sent by the server and corresponding to the query request; in the case that it is determined that the input information (i.e., the information input by the first account to be transmitted to the second account) includes the identification of the target object, and in the case that the first account has the right to manage the target object, prompt information for indicating that the second account has the right to access the target object is displayed. In the embodiment of the disclosure, the terminal determines whether a target object exists by determining whether information input by a first account includes an identifier of the target object, and determines whether the first account can edit, delete, access and other operations on the target object by determining whether the first account has the authority to manage the target object; when the target object is determined to exist, and the first account client performs editing, deleting, accessing and other operations on the target object, the second account is indicated to have the authority to access the target object, so that the terminal can display the prompt information, whether the receiver corresponding to the information has the authority to access the target object can be accurately and effectively displayed, and the management and access efficiency of the target object are improved.

It will be appreciated that, in actual implementation, the terminal/server according to the embodiments of the present disclosure may include one or more hardware structures and/or software modules for implementing the corresponding rights management method described above, where the executing hardware structures and/or software modules may constitute a terminal/server. Those of skill in the art will readily appreciate that the algorithm steps of the examples described in connection with the embodiments disclosed herein may be implemented as hardware or a combination of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

Based on such understanding, the embodiment of the present disclosure further correspondingly provides a rights management device, and fig. 14 shows a schematic structural diagram of the rights management device provided by the embodiment of the present disclosure. As shown in fig. 14, the rights management unit 20 may include: a receiving module 201 and a display module 202.

The receiving module 201 is configured to receive information to be sent to the second account, which is input by the first account.

The display module 202 is configured to display prompt information for indicating that the second account has the right to access the target object in a case where it is determined that the input information includes the identification of the target object and in a case where the first account has the right to manage the target object.

Optionally, the rights management device 20 may further include a sending module 203 and a determining module 204.

The sending module 203 is configured to send a query request to the server, where the query request includes the identifier of the target object and the identifier of the first account, and the query request is used to request to determine whether the first account has the right to manage the target object.

The receiving module 201 is further configured to receive a query response corresponding to the query request sent by the server.

A determining module 204 is configured to determine, based on the query response, whether the first account has rights to manage the target object.

Optionally, the query request further includes an identifier of the second account, where the query request is further used to request that the second account be assigned access rights if the first account has rights to manage the target object.

The receiving module 201 is further configured to receive a notification message sent by the server, where the notification message is used to indicate that the second account has the access right.

The display module 202 is specifically configured to display the prompt information in response to the notification message.

Optionally, the rights management device further includes a processing module 205.

The processing module 205 is configured to cancel the right of the second account to access the target object or change the right of the second account to other rights in response to the right change operation input by the first account.

The display module 202 is further configured to display a prompt message corresponding to the rights change operation.

Optionally, the processing module 205 is configured to revoke the right of the second account to access the target object in response to a revocation operation of the entered information.

As described above, the embodiments of the present disclosure may divide functional modules of a rights management apparatus according to the above-described method examples. The integrated modules may be implemented in hardware or in software functional modules. In addition, it should be further noted that the division of the modules in the embodiments of the present disclosure is merely a logic function division, and other division manners may be implemented in practice. For example, each functional module may be divided corresponding to each function, or two or more functions may be integrated in one processing module.

The specific manner in which each module performs the operation and the beneficial effects of the rights management device in the foregoing embodiment are described in detail in the foregoing method embodiment, and are not described herein again.

Fig. 15 is a schematic structural view of another rights management unit provided in the present disclosure. As shown in fig. 15, the rights management unit 30 may include at least one processor 301 and a memory 303 for storing processor-executable instructions. Wherein the processor 301 is configured to execute instructions in the memory 303 to implement the rights management method in the above-described embodiments.

In addition, the rights management device 30 may also include a communication bus 302 and at least one communication interface 304.

The processor 301 may be a processor (central processing units, CPU), microprocessor unit, ASIC, or one or more integrated circuits for controlling the execution of the programs of the present disclosure.

Communication bus 302 may include a path to transfer information between the above components.

Communication interface 304, using any transceiver-like device for communicating with other devices or communication networks, such as ethernet, radio access network (radio access network, RAN), wireless local area network (wireless local area networks, WLAN), etc.

The memory 303 may be, but is not limited to, a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (random access memory, RAM) or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), a compact disc read-only memory (compact disc read-only memory) or other optical disc storage, a compact disc storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory may be stand alone and be connected to the processing unit by a bus. The memory may also be integrated with the processing unit.

The memory 303 is used for storing instructions for executing the disclosed aspects, and is controlled by the processor 301 for execution. The processor 301 is configured to execute instructions stored in the memory 303 to perform the functions of the methods of the present disclosure.

In a particular implementation, as one embodiment, processor 301 may include one or more CPUs, such as CPU0 and CPU1 of FIG. 15.

In a specific implementation, as an embodiment, the rights management unit 30 may include a plurality of processors, such as the processor 301 and the processor 307 in fig. 15. Each of these processors may be a single-core (single-CPU) processor or may be a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

In a specific implementation, as an embodiment, the rights management unit 30 may further include an output device 305 and an input device 306. The output device 305 communicates with the processor 301 and may display information in a variety of ways. For example, the output device 305 may be a liquid crystal display (liquid crystal display, LCD), a light emitting diode (light emitting diode, LED) display device, a Cathode Ray Tube (CRT) display device, or a projector (projector), or the like. The input device 306 communicates with the processor 301 and may accept user input in a variety of ways. For example, the input device 306 may be a mouse, keyboard, touch screen device, or sensing device, among others.

Fig. 16 is a diagram showing a result example of another rights management unit provided in the present disclosure. As shown in fig. 16, the rights management unit 40 may include: a receiving module 401, a determining module 402 and a transmitting module 403.

The receiving module 401 is configured to receive a query request sent by a terminal, where the query request includes an identifier of a target object, an identifier of a first account, and an identifier of a second account, where the query request is used to request to determine whether the first account has a right to manage the target object, and allocate an access right to the second account if the first account has a right to manage the target object.

A determination module 402 is configured to determine that the first account has rights to manage the target object.

A sending module 403, configured to send a query response corresponding to the query request to the terminal, where the query response is used to instruct the first account to have rights to manage the target object.

The determination module 402 is further configured to assign the access right to the second account.

The sending module 403 is further configured to send a notification message to the terminal, where the notification message is used to indicate that the second account has the access right.

Optionally, the receiving module 401 is further configured to receive a permission modification request sent by the terminal, where the permission modification request includes an identifier of the target object and an identifier of the second account, and the permission modification request is used to request to modify the access permission into other permissions.

The determining module 402 is further configured to determine to change the access right to the other right.

The determination module 402 is further configured to assign the other rights to the second account.

The sending module 403 is further configured to send a permission modification response to the terminal, where the permission modification response is used to indicate that the second account has the other permission.

Optionally, the determining module 402 is specifically configured to determine that the first account has the right to manage the target object, in case the first account is the creator of the target object, or the creator of the target object has granted the right to manage the target object to the first account.

Fig. 17 is a schematic structural view of another rights management unit provided in the present disclosure. As shown in fig. 17, the rights management unit 50 may include at least one processor 501 and a memory 503 for storing processor-executable instructions. Wherein the processor 501 is configured to execute instructions in the memory 503 to implement the rights management method in the above-described embodiments.

In addition, the rights management device 50 may also include a communication bus 502 and at least one communication interface 504.

The processor 501 may be a CPU, microprocessor, ASIC, or one or more integrated circuits for controlling the execution of programs in accordance with aspects of the present disclosure.

Communication bus 502 may include a path to transfer information between the aforementioned components.

Communication interface 504 uses any transceiver-like device for communicating with other devices or communication networks, such as ethernet, RAN, WLAN, etc.

The memory 503 may be, but is not limited to, a ROM or other type of static storage device that can store static information and instructions, a RAM or other type of dynamic storage device that can store information and instructions, an EEPROM, a CD-ROM or other optical disk storage, optical disk storage (including compact discs, laser discs, optical disks, digital versatile discs, blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory may be stand alone and be connected to the processing unit by a bus. The memory may also be integrated with the processing unit.

Wherein the memory 503 is used to store instructions for performing the disclosed aspects and is controlled for execution by the processor 501. The processor 501 is configured to execute instructions stored in the memory 503 to implement the functions in the methods of the present disclosure.

In a particular implementation, as one embodiment, processor 501 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 17.

In a specific implementation, as an embodiment, the rights management unit 50 may include a plurality of processors, such as processor 501 and processor 507 in fig. 17. Each of these processors may be a single-core (single-CPU) processor or may be a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

In a specific implementation, as an embodiment, the rights management unit 50 may further include an output device 505 and an input device 506. The output device 505 communicates with the processor 501 and may display information in a variety of ways. For example, the output device 505 may be a liquid crystal display (liquid crystal display, LCD), a light emitting diode (light emitting diode, LED) display device, a Cathode Ray Tube (CRT) display device, or a projector (projector), or the like. The input device 506 communicates with the processor 501 and may accept user input in a variety of ways. For example, the input device 506 may be a mouse, a keyboard, a touch screen device, a sensing device, or the like.

It will be appreciated by those skilled in the art that the structure shown in fig. 15 or 17 described above is not limiting of the rights management unit and may include more or less components than illustrated, or may combine some components, or may employ a different arrangement of components.

In addition, the present disclosure also provides a computer-readable storage medium comprising instructions that, when executed by a processor, cause the processor to perform the rights management method as provided by the above embodiments.

In addition, the present disclosure also provides a computer program product comprising instructions which, when executed by a processor, cause the processor to perform the rights management method as provided by the above embodiments.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any adaptations, uses, or adaptations of the disclosure following the general principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

Claims

1. A rights management method applied to a terminal, comprising:

receiving information to be sent to a second account, which is input by a first account;

displaying prompt information for representing that a second account has the right to access the target object under the condition that the input information comprises the identification of the target object and the first account has the right to manage the target object, displaying the prompt information in a display area of the transmitted information after the first account transmits the information, wherein the display area of the transmitted information of the terminal comprises a right change control;

responding to the permission changing operation input by the first account, canceling the permission of the second account to access the target object, or changing the permission of the second account to access the target object into other permissions;

and displaying prompt information corresponding to the permission change operation.

2. The rights management method of claim 1, wherein the method further comprises:

sending a query request to a server, wherein the query request comprises an identifier of the target object and an identifier of the first account, and the query request is used for requesting to determine whether the first account has the authority for managing the target object;

Receiving a query response corresponding to the query request sent by the server;

and determining whether the first account has the authority for managing the target object according to the query response.

3. The rights management method according to claim 2, wherein the query request further includes an identifier of the second account, and the query request is further used for requesting that access rights be allocated to the second account if the first account has rights to manage the target object;

and displaying prompt information for representing that a second account has the right to access the target object when the first account has the right to manage the target object, wherein the prompt information comprises the following components:

receiving a notification message sent by the server, wherein the notification message is used for indicating that the second account has the access right;

and responding to the notification message, and displaying the prompt information.

4. A rights management method according to any of claims 1-3, wherein the method further comprises:

and in response to a withdrawal operation of the input information, canceling the right of the second account to access the target object.

5. A rights management method applied to a server, comprising:

receiving a query request sent by a terminal, wherein the query request comprises an identifier of a target object, an identifier of a first account and an identifier of a second account, the query request is used for requesting to determine whether the first account has the authority to manage the target object, and allocating access authority to the second account when the first account has the authority to manage the target object, after the first account sends information, prompt information is displayed in a display area of the sent information of the terminal, and the display area of the sent information of the terminal comprises an authority change control;

determining that the first account has the authority to manage the target object, and sending a query response corresponding to the query request to the terminal, wherein the query response is used for indicating that the first account has the authority to manage the target object;

distributing the access right to the second account, and sending a notification message to the terminal, wherein the notification message is used for indicating that the second account has the access right;

receiving a permission changing request sent by the terminal, wherein the permission changing request comprises an identifier of the target object and an identifier of the second account, and the permission changing request is used for requesting to change the access permission into other permissions;

Determining to change the access rights to the other rights;

and distributing the other rights to the second account, and sending a rights change response to the terminal, wherein the rights change response is used for indicating that the second account has the other rights.

6. The rights management method of claim 5, wherein the determining that the first account has rights to manage the target object comprises:

and determining that the first account has the right to manage the target object under the condition that the first account is the creator of the target object or the creator of the target object has granted the right to manage the target object to the first account.

7. A rights management unit, comprising: the device comprises a receiving module, a display module and a processing module;

the receiving module is configured to receive information input by the first account and to be sent to the second account;

the display module is configured to display prompt information for representing that a second account has the right to access the target object when the input information comprises the identification of the target object and the first account has the right to manage the target object, the prompt information is displayed in a display area of the transmitted information after the first account transmits the information, and a right change control is included in the display area of the transmitted information of the terminal;

The processing module is configured to respond to the permission changing operation input by the first account, cancel the permission of the second account to access the target object or change the permission of the second account to access the target object into other permissions;

the display module is further configured to display prompt information corresponding to the permission change operation.

8. The rights management device of claim 7, further comprising a transmitting module and a determining module;

the sending module is configured to send a query request to a server, wherein the query request comprises an identifier of the target object and an identifier of the first account, and the query request is used for requesting to determine whether the first account has the authority for managing the target object;

the receiving module is further configured to receive a query response corresponding to the query request, which is sent by the server;

the determining module is configured to determine whether the first account has the right to manage the target object according to the query response.

9. The rights management unit of claim 8, wherein the query request further includes an identification of the second account, the query request further requesting that access rights be assigned to the second account if the first account has rights to manage the target object;

The receiving module is further configured to receive a notification message sent by the server, where the notification message is used to indicate that the second account has the access right;

the display module is specifically configured to respond to the notification message and display the prompt information.

10. Rights management unit according to any of the claims 7-9, characterized in that,

the processing module is further configured to revoke the right of the second account to access the target object in response to a revocation operation of the entered information.

11. A rights management unit, comprising: the device comprises a receiving module, a determining module and a sending module;

the receiving module is configured to receive a query request sent by a terminal, where the query request includes an identifier of a target object, an identifier of a first account, and an identifier of a second account, where the query request is used to request to determine whether the first account has a right to manage the target object, and allocate an access right to the second account if the first account has a right to manage the target object, and after the first account sends information, prompt information is displayed in a display area of the sent information of the terminal, and the display area of the sent information of the terminal includes a right change control;

The determining module is configured to determine that the first account has the right to manage the target object;

the sending module is configured to send a query response corresponding to the query request to the terminal, wherein the query response is used for indicating that the first account has the authority to manage the target object;

the determining module is further configured to allocate the access rights to the second account;

the sending module is further configured to send a notification message to the terminal, where the notification message is used to indicate that the second account has the access right;

the receiving module is further configured to receive a permission changing request sent by the terminal, wherein the permission changing request comprises an identifier of the target object and an identifier of the second account, and the permission changing request is used for requesting to change the access permission into other permissions;

the determining module is further configured to determine to change the access right to the other right;

the determining module is further configured to allocate the other rights to the second account;

the sending module is further configured to send a permission change response to the terminal, where the permission change response is used to indicate that the second account has the other permission.

12. The rights management unit of claim 11, wherein,

the determining module is specifically configured to determine that the first account has the right to manage the target object, if the first account is the creator of the target object or the creator of the target object has granted the right to manage the target object to the first account.

13. A rights management system, characterized in that the rights management system comprises a terminal and a server;

the terminal being adapted to perform the rights management method of any of the preceding claims 1-4;

the server is configured to perform the rights management method of claim 5 or 6.

14. A terminal, the terminal comprising:

a processor;

a memory configured to store the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement the rights management method of any of claims 1-4.

15. A server, the server comprising:

a processor;

a memory configured to store the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement the rights management method of claim 5 or 6.

16. A computer readable storage medium having instructions stored thereon, which when executed by a processor of a computer, cause the computer to perform the rights management method of any of claims 1-4 or the rights management method of claim 5 or 6.