CN117436052A

CN117436052A - Rights management method, rights management device, electronic device, and storage medium

Info

Publication number: CN117436052A
Application number: CN202311484819.5A
Authority: CN
Inventors: 巩凯丽
Original assignee: Ping An Life Insurance Company of China Ltd
Current assignee: Ping An Life Insurance Company of China Ltd
Priority date: 2023-11-08
Filing date: 2023-11-08
Publication date: 2024-01-23

Abstract

The embodiment of the application provides a right management method, a right management device, electronic equipment and a storage medium, and belongs to the field of financial science and technology. The method comprises the following steps: receiving an access request of a target object, wherein the access request comprises object information of the target object; analyzing the object information to obtain a target authority level corresponding to the target object; acquiring permission labels of candidate controls in a target page, wherein the permission labels are used for indicating and displaying first permission grades corresponding to the candidate controls and indicating and triggering second permission grades corresponding to the candidate controls; displaying the target page, wherein the target page is provided with at least one target control, and the target control is selected from candidate controls; and responding to the triggering operation of the target object on the target page to the target control, and executing an event corresponding to the triggering operation or feeding back prompt information to the target object based on the second permission level and the target permission level. The embodiment of the application can simplify the authority management, thereby improving the flexibility of the authority management.

Description

Rights management method, rights management device, electronic device, and storage medium

Technical Field

The present disclosure relates to the field of financial science and technology, and in particular, to a rights management method, a rights management device, an electronic device, and a storage medium.

Background

In order to enhance management of the financial transaction process, a financial transaction institution often allocates different operation rights to different objects, so that each object can only access and operate various content pages within the allowed operation rights, thereby improving transaction security.

Currently, the operating rights of most transaction systems are generally controlled through the background. If the authority level of the transaction system is relatively large, the page operation is relatively complex, and frequent foreground and background interaction is often involved in the mode, so that the operation flexibility is reduced, and the normal management of the authorities is influenced.

Disclosure of Invention

The main purpose of the embodiments of the present application is to provide a rights management method, a rights management device, an electronic device, and a storage medium, which aim to simplify rights management and further improve the flexibility of rights management.

To achieve the above object, a first aspect of an embodiment of the present application proposes a rights management method, including:

receiving an access request of a target object, wherein the access request contains object information of the target object;

Analyzing the object information to obtain a target authority level corresponding to the target object;

acquiring permission labels of candidate controls in a target page, wherein the permission labels are used for indicating and displaying first permission levels corresponding to the candidate controls and indicating and triggering second permission levels corresponding to the candidate controls;

displaying the target page, wherein the target page is displayed with at least one target control, and the target control is selected from the candidate controls;

and responding to the triggering operation of the target object on the target page to the target control, and executing an event corresponding to the triggering operation or feeding back prompt information to the target object based on the second permission level and the target permission level.

In some embodiments, the executing the event corresponding to the triggering operation or feeding back the prompt information to the target object based on the second permission level and the target permission level includes:

if the second permission level is consistent with the target permission level, executing an event corresponding to the triggering operation;

and if the second permission level is not consistent with the target permission level, feeding back prompt information to the target object, wherein the prompt information is used for representing that the target object does not trigger the permission of the target control.

and if the second permission level is not consistent with the target permission level, executing an event corresponding to the triggering operation or feeding back prompt information to the target object according to a preset permission tree, wherein the permission tree is used for indicating the upper-lower relationship between the permission levels.

In some embodiments, if the second permission level does not exist and is consistent with the target permission level, executing the event corresponding to the triggering operation or feeding back the prompt information to the target object according to a preset permission tree, including:

determining the upper and lower relationship between the target authority level and the second authority level according to the authority tree;

if the upper-lower relationship is expressed in the authority tree, the target authority level is an upper node of the second authority level, and then executing an event corresponding to the triggering operation;

And if the upper-lower relationship is expressed in the authority tree, the target authority level is not an upper node of the second authority level, and the prompt information is fed back to the target object.

In some embodiments, before the target page is displayed, the method further includes selecting the target control from a plurality of candidate controls, including:

selecting a candidate control with the first permission level consistent with the target permission level from the plurality of candidate controls as a first control;

selecting a candidate control with the second permission level consistent with the target permission level from the plurality of candidate controls as a second control;

integrating the first control and the second control into the target control.

In some embodiments, the permission label is generated by:

acquiring authority configuration information of each candidate control for each candidate control;

obtaining control attribute information of the candidate control and authority levels corresponding to the candidate control based on the authority configuration information;

and integrating the control attribute information and the permission level into an array, and taking the array as the permission label.

In some embodiments, the obtaining the permission label of each candidate control in the target page includes:

acquiring a storage path of a configuration file storing the permission label, inquiring the configuration file based on the storage path, and extracting the permission label of the candidate control from the configuration file;

or,

and calling a query interface, and acquiring authority labels of candidate controls in the target page based on the query interface.

To achieve the above object, a second aspect of the embodiments of the present application proposes a rights management device, the device including:

an access request acquisition module, configured to receive an access request of a target object, where the access request includes object information of the target object;

the analysis module is used for analyzing the object information to obtain a target authority level corresponding to the target object;

the label acquisition module is used for acquiring authority labels of all candidate controls in the target page, wherein the authority labels are used for indicating and displaying first authority levels corresponding to the candidate controls and indicating and triggering second authority levels corresponding to the candidate controls;

the display module is used for displaying the target page, wherein the target page is provided with at least one target control, and the target control is selected from the candidate controls;

And the triggering module is used for responding to the triggering operation of the target object on the target page on the target control, executing an event corresponding to the triggering operation or feeding back prompt information to the target object based on the second permission level and the target permission level.

To achieve the above object, a third aspect of the embodiments of the present application proposes an electronic device, which includes a memory, a processor, where the memory stores a computer program, and the processor implements the method described in the first aspect when executing the computer program.

To achieve the above object, a fourth aspect of the embodiments of the present application proposes a computer-readable storage medium storing a computer program that, when executed by a processor, implements the method of the first aspect.

The authority management method, the authority management device, the electronic equipment and the storage medium are characterized by receiving an access request of a target object, wherein the access request comprises object information of the target object; and analyzing the object information to obtain the target authority level corresponding to the target object, so that the control operation authorities of all the target objects can be conveniently determined. Further, acquiring permission labels of all candidate controls in the target page, wherein the permission labels are used for indicating and displaying first permission grades corresponding to the candidate controls and indicating and triggering second permission grades corresponding to the candidate controls; and displaying the target page, wherein the target page is provided with at least one target control, and the target control is selected from candidate controls, so that the controls displayed on the target page can be controlled conveniently, and the accuracy of control display is improved. Finally, responding to the triggering operation of the target object on the target page to the target control, executing an event corresponding to the triggering operation or feeding back prompt information to the target object based on the second permission level and the target permission level, judging whether to execute the corresponding triggering event according to the permission of the target object and the permission required by the triggering control, simplifying the permission management, and further effectively improving the flexibility of the permission management.

Drawings

FIG. 1 is a flow chart of a rights management method provided by an embodiment of the present application;

fig. 2 is a flowchart of step S103 in fig. 1;

FIG. 3 is another flow chart of a rights management method provided by an embodiment of the present application;

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

fig. 5 is a flowchart of step S105 in fig. 1;

fig. 6 is another flowchart of step S105 in fig. 1;

fig. 7 is a flowchart of step S602 in fig. 6;

FIG. 8 is a schematic diagram of a rights management unit according to an embodiment of the present application;

fig. 9 is a schematic hardware structure of an electronic device according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.

It should be noted that although functional block division is performed in a device diagram and a logic sequence is shown in a flowchart, in some cases, the steps shown or described may be performed in a different order than the block division in the device, or in the flowchart. The terms first, second and the like in the description and in the claims and in the above-described figures, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of the present application only and is not intended to be limiting of the present application.

First, several nouns referred to in this application are parsed:

artificial intelligence (artificial intelligence, AI): is a new technical science for researching and developing theories, methods, technologies and application systems for simulating, extending and expanding the intelligence of people; artificial intelligence is a branch of computer science that attempts to understand the nature of intelligence and to produce a new intelligent machine that can react in a manner similar to human intelligence, research in this field including robotics, language recognition, image recognition, natural language processing, and expert systems. Artificial intelligence can simulate the information process of consciousness and thinking of people. Artificial intelligence is also a theory, method, technique, and application system that utilizes a digital computer or digital computer-controlled machine to simulate, extend, and expand human intelligence, sense the environment, acquire knowledge, and use knowledge to obtain optimal results.

Natural language processing (natural language processing, NLP): NLP is a branch of artificial intelligence that is a interdisciplinary of computer science and linguistics, and is often referred to as computational linguistics, and is processed, understood, and applied to human languages (e.g., chinese, english, etc.). Natural language processing includes parsing, semantic analysis, chapter understanding, and the like. Natural language processing is commonly used in the technical fields of machine translation, handwriting and print character recognition, voice recognition and text-to-speech conversion, information intent recognition, information extraction and filtering, text classification and clustering, public opinion analysis and opinion mining, and the like, and relates to data mining, machine learning, knowledge acquisition, knowledge engineering, artificial intelligence research, linguistic research related to language calculation, and the like.

Information extraction (Information Extraction, NER): extracting the fact information of the appointed type of entity, relation, event and the like from the natural language text, and forming the text processing technology of the structured data output. Information extraction is a technique for extracting specific information from text data. Text data is made up of specific units, such as sentences, paragraphs, chapters, and text information is made up of small specific units, such as words, phrases, sentences, paragraphs, or a combination of these specific units. The noun phrase, the name of a person, the name of a place, etc. in the extracted text data are all text information extraction, and of course, the information extracted by the text information extraction technology can be various types of information.

Based on this, the embodiment of the application provides a rights management method, a rights management device, an electronic device and a storage medium, which aim to simplify rights management and further improve the flexibility of rights management.

The rights management method and apparatus, electronic device and storage medium provided in the embodiments of the present application are specifically described through the following embodiments, and the rights management method in the embodiments of the present application is first described.

The embodiment of the application can acquire and process the related data based on the artificial intelligence technology. Among these, artificial intelligence (Artificial Intelligence, AI) is the theory, method, technique and application system that uses a digital computer or a digital computer-controlled machine to simulate, extend and extend human intelligence, sense the environment, acquire knowledge and use knowledge to obtain optimal results.

Artificial intelligence infrastructure technologies generally include technologies such as sensors, dedicated artificial intelligence chips, cloud computing, distributed storage, big data processing technologies, operation/interaction systems, mechatronics, and the like. The artificial intelligence software technology mainly comprises a computer vision technology, a robot technology, a biological recognition technology, a voice processing technology, a natural language processing technology, machine learning/deep learning and other directions.

The embodiment of the application provides a right management method, which relates to the technical field of digital medical treatment. The authority management method provided by the embodiment of the application can be applied to the terminal, the server side and software running in the terminal or the server side. In some embodiments, the terminal may be a smart phone, tablet, notebook, desktop, etc.; the server side can be configured as an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, and a cloud server for providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs, basic cloud computing services such as big data and artificial intelligent platforms and the like; the software may be an application or the like that implements the rights management method, but is not limited to the above form.

The subject application is operational with numerous general purpose or special purpose computer system environments or configurations. For example: personal computers, server computers, hand-held or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like. The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

In the various embodiments of the present application, when related processing is required according to data related to identity or characteristics of an object, such as object information, object behavior data, object history data, and object position information, permission or consent of the object is obtained first, and related laws and regulations and standards are complied with for collection, use, processing, and the like of the data. In addition, when the personal information of the object needs to be acquired in the embodiment of the application, the independent permission or independent consent of the object is acquired through a popup window or a jump to a confirmation page or the like, and after the independent permission or independent consent of the object is explicitly acquired, the necessary object related data for enabling the embodiment of the application to normally operate is acquired.

Fig. 1 is an optional flowchart of a rights management method provided in an embodiment of the present application, where the method in fig. 1 may include, but is not limited to, steps S101 to S105.

Step S101, receiving an access request of a target object, wherein the access request contains object information of the target object;

step S102, analyzing the object information to obtain a target authority level corresponding to the target object;

step S103, obtaining permission labels of all candidate controls in a target page, wherein the permission labels are used for indicating and displaying first permission grades corresponding to the candidate controls and indicating and triggering second permission grades corresponding to the candidate controls;

step S104, displaying a target page, wherein the target page is provided with at least one target control, and the target control is selected from candidate controls;

step S105, responding to the triggering operation of the target object on the target page to the target control, and executing an event corresponding to the triggering operation or feeding back prompt information to the target object based on the second permission level and the target permission level.

Step S101 to step S105 illustrated in the embodiment of the present application, by receiving an access request of a target object, where the access request includes object information of the target object; and analyzing the object information to obtain the target authority level corresponding to the target object, so that the control operation authorities of all the target objects can be conveniently determined. Further, acquiring permission labels of all candidate controls in the target page, wherein the permission labels are used for indicating and displaying first permission grades corresponding to the candidate controls and indicating and triggering second permission grades corresponding to the candidate controls; and displaying the target page, wherein the target page is provided with at least one target control, and the target control is selected from candidate controls, so that the controls displayed on the target page can be controlled conveniently, and the accuracy of control display is improved. Finally, responding to the triggering operation of the target object on the target page to the target control, executing an event corresponding to the triggering operation or feeding back prompt information to the target object based on the second permission level and the target permission level, judging whether to execute the corresponding triggering event according to the permission of the target object and the permission required by the triggering control, simplifying the permission management, and further effectively improving the flexibility of the permission management.

In step S101 of some embodiments, an access request for a target object is received.

Wherein the access request contains object information of the target object, and the access request is a request generated when the target object wants to access a certain content page. The target object refers to a network user, a web page maintainer, etc., without limitation. The object information is used for indicating the identity, the owned authority level and other information of the target object.

In the embodiment, when the target object wants to access a certain system, the target object first inputs object information such as its own object name, login password, etc. on a login page of the system, and sends an access request to the system based on the input object information. Then, the system server receives the object information input by the target object in response to the access request of the target object.

In step S102 of some embodiments, the object information is parsed to obtain a target authority level corresponding to the target object.

The target authority level refers to an authority level possessed by the target object. The authority levels are represented as R1, R2, R3 and R4, wherein the priority of the R1 authority level is smaller than the R2 authority level, the priority of the R2 authority level is smaller than the R3 authority level, and the priority of the R3 authority level is smaller than the R4 authority level. The higher the priority of the rights level of an object, the greater the operability of the object in the system.

When the embodiment is specifically implemented, the preset computer code program is utilized to analyze the object information, identify the specific content in the object information, compare the identified specific content with the object registration information pre-stored in the object database, and obtain the identity information of the target object based on the object registration information consistent with the specific content. Further, according to the mapping relation between the object registration information and the authority configuration, the specific operation authority owned by the target object is determined. Further, according to the specific operation authority possessed by the target object, a target authority level corresponding to the target object is obtained.

The mapping relationship between the object registration information and the authority configuration is set according to practical situations, for example, different authorities are given to the object according to the department and the job level of the object in the object registration information, and the object is restricted to have certain authorities.

For example, assume that the R3 permission level is capable of clicking on control 1. When the target object has the click operation authority of the control 1 on the content page, the target authority level of the target object on the control 1 is considered to be the R3 authority level.

Referring to fig. 2, in some embodiments, step S103 may include, but is not limited to including step S201 or step S202:

Step S201, a storage path of a configuration file storing permission labels is obtained, the configuration file is queried based on the storage path, and the permission labels of candidate controls are extracted from the configuration file;

or,

step S202, a query interface is called, and permission labels of candidate controls in the target page are obtained based on the query interface.

Step S201 and step S202 are described in detail below.

In step S201 of some embodiments, a storage path of a configuration file storing permission labels is acquired, and the configuration file is queried based on the storage path, and permission labels of candidate controls are extracted from the configuration file.

The permission label is used for indicating a first permission level corresponding to the display candidate control and a second permission level corresponding to the trigger candidate control. The candidate controls are interactable controls for layout on the content page.

The configuration file refers to a computer file, and the configuration file contains configuration parameters of a system, configuration parameters of each control, permission labels and the like.

The storage path is used for indicating the storage position of the configuration file.

In this embodiment, since the file attribute of the configuration file often indicates the storage path thereof, the storage path of the configuration file storing the permission label is obtained from the file attribute of the configuration file based on this. And then, inquiring the folders layer by layer according to the acquired storage path to obtain the configuration file. And finally, extracting the permission labels of the candidate controls from the configuration file according to the parameter types in the configuration file.

For example, the tab configuration 2 of a certain candidate control 1 is "show= 'show arr'"; the permission label of the candidate control 1 in the configuration file is expressed as showarr= [ 'R1', 'R2', 'R4' ]; i.e., an object that possesses the authority level of R1, R2, R4 can see the candidate control 1 on the content page.

In step S202 of some embodiments, a query interface is invoked and permission labels for each candidate control in the target page are obtained based on the query interface.

When the embodiment is specifically implemented, a query interface AP I is called, a related server is associated by utilizing the query interface, and permission labels of all candidate controls in a target page are obtained from the related server, wherein the related server stores the permission labels of all candidate controls. The permission label is stored by the third-party server, so that the storage pressure of the system server can be reduced.

The permission labels can be flexibly acquired through the step S201 and the step S202, so that the diversity of acquiring the permission labels is improved, and the acquisition efficiency of the permission labels is improved.

Referring to fig. 3, in some embodiments, the process of generating the permission label may include, but is not limited to, steps S301 to S303:

step S301, acquiring authority configuration information of each candidate control for each candidate control;

Step S302, obtaining control attribute information of the candidate control and authority levels corresponding to the candidate control based on the authority configuration information;

step S303, integrating the attribute information of the control and the authority level into an array, and taking the array as an authority label.

Step S301 to step S303 are described in detail below.

In step S301 of some embodiments, for each candidate control, permission configuration information of the candidate control is acquired.

The authority configuration information refers to functions of each candidate control determined in the page design stage, authority required for triggering an object, and the like.

When the embodiment is specifically implemented, for each candidate control, extracting configuration codes of the candidate control in a page design stage, and then, carrying out code analysis on the configuration codes to obtain authority configuration information of the candidate control.

In step S302 of some embodiments, control attribute information of the candidate control and a permission level corresponding to the candidate control are obtained based on the permission configuration information.

The control attribute information is used for indicating the functions of the candidate controls and triggering events corresponding to the candidate controls.

When the embodiment is specifically implemented, the permission configuration information is subjected to information analysis, so that the control attribute information of the candidate control and the permission level corresponding to the candidate control are obtained.

In step S303 of some embodiments, the control attribute information and the permission level are integrated into an array, and the array is used as a permission label.

When the embodiment is specifically implemented, firstly, the attribute information and the authority level of the control are integrated into an array according to a preset format; then, the array is used as a permission label.

For example, for a candidate control M for implementing the query function, the candidate control M is only displayed for the objects with authority levels R1, R2 and R4, and the query function is only directed to the objects with authority levels R1, R2. The rights label for this candidate control M is showarr= [ 'R1', 'R2', 'R4',select arr= [ 'R1', 'R2'.

The control attribute information and the permission level can be integrated more conveniently through the steps S301 to S303, and the permission label of each candidate control is constructed in a fixed format, so that the permission label is simpler and more standardized, and the permission management process is facilitated to be simplified.

Referring to fig. 4, prior to step S104 in some embodiments, the rights management method may include, but is not limited to, steps S401 to S403:

step S401, selecting a candidate control with the first authority level consistent with the target authority level from a plurality of candidate controls as a first control;

Step S402, selecting a candidate control with the second authority level consistent with the target authority level from a plurality of candidate controls as a second control;

step S403, integrating the first control and the second control into a target control.

Steps S401 to S403 are described in detail below.

In step S401 of some embodiments, a candidate control having a first permission level consistent with the target permission level is selected as a first control from a plurality of candidate controls.

In a specific implementation of this embodiment, for each candidate control, a comparison is made as to whether the first permission level of the candidate control is consistent with the target permission level. And if the first permission level of the candidate control is consistent with the target permission level, taking the candidate control as the first control.

For example, the first permission level of candidate control A is { R2, R4}, indicating that candidate control A will be displayed to an object whose permission level is R2 and whose permission level is R4. And if the target permission level is R2, taking the candidate control as a first control.

In step S402 of some embodiments, a candidate control having a second permission level consistent with the target permission level is selected as the second control from the plurality of candidate controls.

In a specific implementation of this embodiment, for each candidate control, a comparison is made as to whether the second permission level of the candidate control is consistent with the target permission level. And if the second permission level of the candidate control is consistent with the target permission level, taking the candidate control as the second control.

For example, the first permission level of candidate control A is { R2, R4}, the second permission level is { R4}, indicating that candidate control A will be displayed for objects with permission levels of R2 and R4, but that candidate control A only allows objects with permission levels of R4 to trigger. And if the target permission level is R4, taking the candidate control as a second control, displaying a candidate control A on the page, and enabling the target object to trigger the candidate control A. And if the target permission level is R2, taking the candidate control as a first control, and displaying the candidate control A on the page, wherein the target object is not allowed to trigger the candidate control A.

In step S403 of some embodiments, the first control and the second control are integrated into a target control.

In a specific implementation of this embodiment, first the first control and the second control are brought into the same set; then, the candidate controls of the set are de-duplicated so that each candidate control appears only once. Finally, each control in the heavy set is taken as a target control.

The control displayed to the target object can be screened from the plurality of candidate controls according to the authority possessed by the target object through the steps S401 to S403 to serve as the target control, so that the accuracy and the comprehensiveness of control display are improved.

In step S104 of some embodiments, when the target page is displayed according to the object information input by the target object, the target page is generated on the target control layout page according to the object information, and the target page is displayed to the target object. The target page is provided with at least one target control, and the target control is selected from candidate controls.

Referring to fig. 5, in some embodiments, step S105 may include, but is not limited to, steps S501 to S502:

step S501, if the second authority level is consistent with the target authority level, executing an event corresponding to the triggering operation;

step S502, if the second permission level is not consistent with the target permission level, a prompt message is fed back to the target object, wherein the prompt message is used for representing that the target object does not trigger the permission of the target control.

Step S501 to step S502 are described in detail below.

In step S501 of some embodiments, if there is a second permission level consistent with the target permission level, an event corresponding to the trigger operation is performed.

In the specific implementation of this embodiment, if the second permission level is consistent with the target permission level, the target object is considered to have the permission to trigger the target control, and therefore, in response to the triggering operation of the target object, the event corresponding to the triggering operation is executed.

In step S502 of some embodiments, if there is no second permission level consistent with the target permission level, a hint information is fed back to the target object.

In the embodiment, if the second permission level is not consistent with the target permission level, the target object is considered to have no permission to trigger the target control, and therefore, prompt information "no permission" is fed back to the target object in response to the triggering operation of the target object.

Through the steps S501 to S502, whether the target object has the authority for triggering the target control can be conveniently judged according to the consistency of the second authority level and the target authority level, so that corresponding feedback is performed according to the judgment condition, and the simplicity of page operation and the simplicity of authority management are improved.

Referring to fig. 6, in some embodiments, step S105 further includes, but is not limited to, steps S601 to S602:

step S601, if the second authority level is consistent with the target authority level, executing an event corresponding to the triggering operation;

step S602, if the second permission level is not consistent with the target permission level, executing an event corresponding to the triggering operation or feeding back prompt information to the target object according to a preset permission tree, wherein the permission tree is used for indicating the upper-lower relationship between the permission levels.

The following describes step S601 to step S602 in detail.

In step S601 of some embodiments, if there is a second permission level consistent with the target permission level, an event corresponding to the trigger operation is performed.

In step S602 of some embodiments, if the second permission level does not exist and is consistent with the target permission level, according to the preset permission tree, an event corresponding to the triggering operation is executed or a prompt message is fed back to the target object.

In the embodiment, first, the upper-lower relationship between the target authority level and the second authority level is determined according to the authority tree. And then, judging the upper and lower relationship between the target authority level and the second authority level in the authority tree. If the upper-lower relationship is expressed in the authority tree, executing an event corresponding to the triggering operation, wherein the target authority level is an upper node of the second authority level; if the upper and lower relationship is expressed in the authority tree, the target authority level is not the upper node of the second authority level, and prompt information is fed back to the target object.

Through steps S601 to S602, whether the target object has the authority for triggering the target control can be conveniently judged according to the consistency between the second authority level and the target authority level, and further, the embodiment introduces the concept of the authority tree, so that the upper authority level has the authority of the lower authority level, and the accuracy and the rationality of authority management can be further improved.

Referring to fig. 7, in some embodiments, step S602 may include, but is not limited to, steps S701 to S703:

step S701, determining the upper and lower relationship between the target authority level and the second authority level according to the authority tree;

step S702, if the upper-lower relationship indicates that the target authority level is the upper node of the second authority level in the authority tree, executing an event corresponding to the triggering operation;

in step S703, if the upper-lower relationship indicates that the target authority level is not the upper node of the second authority level in the authority tree, the prompt information is fed back to the target object.

Step S701 to step S703 are described in detail below.

In step S701 of some embodiments, a superior-inferior relationship of the target authority level and the second authority level is determined according to the authority tree.

The rights tree often takes the form of a binary tree in which a higher level node has rights possessed by a lower level node.

When the embodiment is specifically implemented, traversing the authority tree, and inquiring the upper-lower relationship between the target authority level and the second authority level.

In step S702 of some embodiments, if the upper-lower relationship indicates that the target authority level is an upper node of the second authority level in the authority tree, an event corresponding to the trigger operation is performed.

In the embodiment, if the upper-lower relationship indicates that the target authority level is an upper node of the second authority level in the authority tree, which indicates that the target authority level has the authority of the second authority level, then an event corresponding to the trigger operation is executed in response to the trigger operation of the target object.

For example, in the authority tree, the authority level R3 is an upper node of the authority level R1, the target authority level is R3, and the second authority level is R1, where if the target object is considered to have the authority to trigger the target control, then the event corresponding to the triggering operation is executed in response to the triggering operation of the target object.

In step S703 of some embodiments, if the upper-lower relationship indicates that the target authority level is not an upper node of the second authority level in the authority tree, a hint information is fed back to the target object.

In the embodiment, if the upper-lower relationship indicates that the target authority level is not an upper node of the second authority level in the authority tree, it is indicated that the target authority level does not have the authority of the second authority level, and therefore, in response to the trigger operation of the target object, the prompt information "no authority" is fed back to the target object.

Through the steps S701 to S703, whether the target object has the authority for triggering the target control can be judged by using the upper and lower relationships of the authority levels in the authority tree, so that corresponding feedback is performed, and the accuracy and the high efficiency of the authority management can be improved.

According to the authority management method, an access request of a target object is received, wherein the access request contains object information of the target object; and analyzing the object information to obtain the target authority level corresponding to the target object, so that the control operation authorities of all the target objects can be conveniently determined. Further, acquiring permission labels of all candidate controls in the target page, wherein the permission labels are used for indicating and displaying first permission grades corresponding to the candidate controls and indicating and triggering second permission grades corresponding to the candidate controls; and displaying the target page, wherein the target page is provided with at least one target control, and the target control is selected from candidate controls, so that the controls displayed on the target page can be controlled conveniently, and the accuracy of control display is improved. Finally, responding to the triggering operation of the target object on the target page to the target control, executing an event corresponding to the triggering operation or feeding back prompt information to the target object based on the second permission level and the target permission level, judging whether to execute the corresponding triggering event according to the permission of the target object and the permission required by the triggering control, simplifying the permission management, and further effectively improving the flexibility of the permission management.

Referring to fig. 8, an embodiment of the present application further provides a rights management apparatus, which may implement the rights management method, where the apparatus includes:

an access request obtaining module 801, configured to receive an access request of a target object, where the access request includes object information of the target object;

the parsing module 802 is configured to parse the object information to obtain a target authority level corresponding to the target object;

the tag obtaining module 803 is configured to obtain permission tags of candidate controls in the target page, where the permission tags are used to indicate a first permission level corresponding to the display candidate controls and indicate a second permission level corresponding to the trigger candidate controls;

the display module 804 is configured to display a target page, where the target page displays at least one target control, and the target control is selected from candidate controls;

and the triggering module 805 is configured to respond to a triggering operation of the target object on the target page on the target control, and execute an event corresponding to the triggering operation or feed back prompt information to the target object based on the second permission level and the target permission level.

In some embodiments, the tag acquisition module 803 is specifically configured to:

Or,

and calling a query interface, and acquiring authority labels of all candidate controls in the target page based on the query interface.

In some embodiments, the permission label is generated by:

acquiring authority configuration information of candidate controls aiming at each candidate control;

and integrating the attribute information and the permission level of the control into an array, and taking the array as a permission label.

In some embodiments, the rights management device further comprises a screening module (not shown), in particular for:

selecting a candidate control with the first permission level consistent with the target permission level from a plurality of candidate controls as a first control;

and integrating the first control and the second control into a target control.

In some embodiments, the triggering module 805 is specifically configured to:

if the second permission level is not consistent with the target permission level, a prompt message is fed back to the target object, wherein the prompt message is used for representing that the target object does not trigger the permission of the target control.

In some embodiments, the triggering module 805 specifically includes:

a first execution unit (not shown) for executing an event corresponding to the trigger operation if there is a second authority level consistent with the target authority level;

and the second execution unit (not shown) is used for executing an event corresponding to the triggering operation or feeding back prompt information to the target object according to a preset authority tree if the second authority level is not consistent with the target authority level, wherein the authority tree is used for indicating the upper-lower relationship between the authority levels.

In some embodiments, a second execution unit (not shown) is specifically configured to:

if the upper-lower relationship is expressed in the authority tree, executing an event corresponding to the triggering operation, wherein the target authority level is an upper node of the second authority level;

if the upper and lower relationship is expressed in the authority tree, the target authority level is not the upper node of the second authority level, and prompt information is fed back to the target object.

The specific implementation of the rights management device is basically the same as the specific embodiment of the rights management method described above, and will not be described here again.

The embodiment of the application also provides electronic equipment, which comprises: the system comprises a memory, a processor, a program stored on the memory and capable of running on the processor, and a data bus for realizing connection communication between the processor and the memory, wherein the program realizes the authority management method when being executed by the processor. The electronic equipment can be any intelligent terminal including a tablet personal computer, a vehicle-mounted computer and the like.

Referring to fig. 9, fig. 9 illustrates a hardware structure of an electronic device according to another embodiment, the electronic device includes:

the processor 901 may be implemented by a general purpose CPU (central processing unit), a microprocessor, an application specific integrated circuit (ApplicationSpecificIntegratedCircuit, ASIC), or one or more integrated circuits, etc. for executing related programs to implement the technical solutions provided by the embodiments of the present application;

the memory 902 may be implemented in the form of read-only memory (ReadOnlyMemory, ROM), static storage, dynamic storage, or random access memory (RandomAccessMemory, RAM). The memory 902 may store an operating system and other application programs, and when the technical solutions provided in the embodiments of the present application are implemented by software or firmware, relevant program codes are stored in the memory 902, and the processor 901 invokes the rights management method to execute the embodiments of the present application;

An input/output interface 903 for inputting and outputting information;

the communication interface 904 is configured to implement communication interaction between the device and other devices, and may implement communication in a wired manner (e.g. USB, network cable, etc.), or may implement communication in a wireless manner (e.g. mobile network, WIFI, bluetooth, etc.);

a bus 905 that transfers information between the various components of the device (e.g., the processor 901, the memory 902, the input/output interface 903, and the communication interface 904);

wherein the processor 901, the memory 902, the input/output interface 903 and the communication interface 904 are communicatively coupled to each other within the device via a bus 905.

The embodiment of the application also provides a computer readable storage medium, wherein the computer readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to realize the rights management method.

The memory, as a non-transitory computer readable storage medium, may be used to store non-transitory software programs as well as non-transitory computer executable programs. In addition, the memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory optionally includes memory remotely located relative to the processor, the remote memory being connectable to the processor through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The embodiment of the application provides a rights management method, a rights management device, an electronic device and a computer readable storage medium, which are used for receiving an access request of a target object, wherein the access request comprises object information of the target object; and analyzing the object information to obtain the target authority level corresponding to the target object, so that the control operation authorities of all the target objects can be conveniently determined. Further, acquiring permission labels of all candidate controls in the target page, wherein the permission labels are used for indicating and displaying first permission grades corresponding to the candidate controls and indicating and triggering second permission grades corresponding to the candidate controls; and displaying the target page, wherein the target page is provided with at least one target control, and the target control is selected from candidate controls, so that the controls displayed on the target page can be controlled conveniently, and the accuracy of control display is improved. Finally, responding to the triggering operation of the target object on the target page to the target control, executing an event corresponding to the triggering operation or feeding back prompt information to the target object based on the second permission level and the target permission level, judging whether to execute the corresponding triggering event according to the permission of the target object and the permission required by the triggering control, simplifying the permission management, and further effectively improving the flexibility of the permission management.

The embodiments described in the embodiments of the present application are for more clearly describing the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application, and as those skilled in the art can know that, with the evolution of technology and the appearance of new application scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

It will be appreciated by those skilled in the art that the solutions shown in fig. 1-7 are not limiting to embodiments of the present application and may include more or fewer steps than shown, or certain steps may be combined, or different steps.

The above described apparatus embodiments are merely illustrative, wherein the units illustrated as separate components may or may not be physically separate, i.e. may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

Those of ordinary skill in the art will appreciate that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof.

The terms "first," "second," "third," "fourth," and the like in the description of the present application and in the above-described figures, if any, 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 embodiments of the present application described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," 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 in this application, "at least one" means one or more, and "a plurality" means two or more. "and/or" for describing the association relationship of the association object, the representation may have three relationships, for example, "a and/or B" may represent: only a, only B and both a and B are present, wherein a, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b or c may represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", wherein a, b, c may be single or plural.

In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the above-described division of units is merely a logical function division, and there may be another division manner in actual implementation, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described above as separate components may or may not be physically separate, and components shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in part or all of the technical solution or in part in the form of a software product stored in a storage medium, including multiple instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods of the various 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 (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing a program.

Preferred embodiments of the present application are described above with reference to the accompanying drawings, and thus do not limit the scope of the claims of the embodiments of the present application. Any modifications, equivalent substitutions and improvements made by those skilled in the art without departing from the scope and spirit of the embodiments of the present application shall fall within the scope of the claims of the embodiments of the present application.

Claims

1. A rights management method, the method comprising:

2. The rights management method according to claim 1, wherein the executing the event corresponding to the trigger operation or feeding back the hint information to the target object based on the second rights level and the target rights level comprises:

3. The rights management method according to claim 1, wherein the executing the event corresponding to the trigger operation or feeding back the hint information to the target object based on the second rights level and the target rights level comprises:

4. A rights management method according to claim 3, wherein if the second rights level is not present and is consistent with the target rights level, executing the event corresponding to the trigger operation or feeding back the prompt information to the target object according to a preset rights tree, includes:

5. The rights management method of claim 1, wherein prior to said displaying said target page, said method further comprises screening out said target control from a plurality of candidate controls, comprising:

integrating the first control and the second control into the target control.

6. The rights management method of claim 1, wherein the rights label is generated by:

7. The rights management method according to any one of claims 1 to 6, wherein the obtaining the rights label of each candidate control in the target page includes:

or,

8. A rights management unit, the unit comprising:

9. An electronic device comprising a memory storing a computer program and a processor implementing the rights management method of any of claims 1 to 7 when the computer program is executed by the processor.

10. A computer readable storage medium storing a computer program, characterized in that the computer program, when executed by a processor, implements the rights management method of any one of claims 1 to 7.