CN116954788A

CN116954788A - Information management method, apparatus, device, medium, and program product

Info

Publication number: CN116954788A
Application number: CN202310641649.0A
Authority: CN
Inventors: 杨云祥
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2023-05-31
Filing date: 2023-05-31
Publication date: 2023-10-27

Abstract

The application discloses an information management method, an information management device, an information management equipment, an information management medium and an information management program product, and relates to the technical field of computers. The method comprises the following steps: displaying a statement management interface; receiving, for a first application in an application platform, a flow configuration operation for at least one information protection claim among a plurality of candidate information protection claims; and in response to the flow configuration operation, configuring a signing flow of at least one information protection statement in an account verification flow corresponding to the first application program. The information protection declarations corresponding to the plurality of applications on the application platform are uniformly managed through the display declaration management interface, so that the management efficiency of the information protection declarations is improved; in addition, different information protection statements are configured for each application program in the statement management interface, so that a method for configuring the information protection statements in a plurality of applications is realized more conveniently, and the configuration efficiency of the information protection statements is improved.

Description

Information management method, apparatus, device, medium, and program product

Technical Field

Embodiments of the present application relate to the field of computer technologies, and in particular, to an information management method, an information management device, an information management apparatus, an information management medium, and a program product.

Background

With the development and popularization of internet technology, the application on the internet is increasing. Because of the requirements of personal information protection laws, each application related to the personal information of the object needs the object to sign the designated information protection statement, so that the data compliance of the application when using the personal information is ensured.

In the related art, an application implements a declaration management system for managing information protection declarations provided to objects at the time of development.

However, the claim management systems carried by different applications tend to be different, that is, each application has its own method of claim management. Then, in the case where an administrator manages a plurality of applications, it is necessary to manage information protection statements for different applications separately, resulting in a low management efficiency of the information protection statements.

Disclosure of Invention

The embodiment of the application provides an information management method, an information management device, an information management medium and an information management program product, which can improve the management efficiency of information protection statement, and the technical scheme is as follows:

in one aspect, there is provided an information management method, the method including:

displaying a statement management interface, wherein the statement management interface is used for managing information protection statements corresponding to applications on an application platform, the information protection statements are protocol files to be agreed between application service users and application service providers, and the statement management interface comprises a plurality of candidate information protection statements;

Receiving, for a first application program in the application platform, a flow configuration operation for at least one information protection statement in the plurality of candidate information protection statements, where the flow configuration operation is used to configure the at least one information protection statement in an account verification flow corresponding to the first application program;

and responding to the flow configuration operation, and configuring the signing flow of the at least one information protection statement in the account verification flow corresponding to the first application program.

In another aspect, there is provided an information management apparatus including:

the display module is used for displaying a statement management interface, wherein the statement management interface is used for managing information protection statements corresponding to applications on an application platform, the information protection statements are protocol files to be agreed between application service users and application service providers, and the statement management interface comprises a plurality of candidate information protection statements;

the receiving module is used for receiving a flow configuration operation of at least one information protection statement in the plurality of candidate information protection statements aiming at a first application program in the application platform, wherein the flow configuration operation is used for configuring the at least one information protection statement in an account verification flow corresponding to the first application program;

And the configuration module is used for responding to the flow configuration operation and configuring the signing flow of the at least one information protection statement in the account verification flow corresponding to the first application program.

In another aspect, a computer device is provided, the computer device including a processor and a memory having stored therein at least one instruction, at least one program, a set of codes, or a set of instructions, the at least one instruction, the at least one program, the set of codes, or the set of instructions being loaded and executed by the processor to implement the information management method as in any of the above embodiments.

In another aspect, a computer readable storage medium having stored therein at least one instruction, at least one program, a set of codes, or a set of instructions loaded and executed by a processor to implement an information management method as in any of the above embodiments is provided.

In another aspect, a computer program product or computer program is provided, the computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions so that the computer device performs the information management method described in any of the above embodiments.

The technical scheme provided by the embodiment of the application has the beneficial effects that at least:

the information protection declarations corresponding to the plurality of applications on the application platform are uniformly managed through the display declaration management interface, so that the management efficiency of the information protection declarations is improved; in addition, aiming at the appointed application program on the application platform, when the terminal receives the configuration operation of the appointed information protection statement, the signing flow of at least one information protection statement is configured in the account verification flow corresponding to the appointed application program, namely, different information protection statements are configured for each application program in the statement management interface, so that the method for configuring the information protection statement in a plurality of applications is realized more conveniently, and the configuration efficiency of the information protection statement is improved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a schematic illustration of an implementation environment provided by an exemplary embodiment of the present application;

FIG. 2 is a flow chart of a method of information management provided by an exemplary embodiment of the present application;

FIG. 3 is an interface diagram of a claim management interface provided by an exemplary embodiment of the present application;

FIG. 4 is an interface diagram of an application flow configuration interface provided by an exemplary embodiment of the present application;

FIG. 5 is an interface diagram of a registration interface provided by an exemplary embodiment of the present application;

FIG. 6 is an interface diagram of a protocol details interface provided by an exemplary embodiment of the present application;

fig. 7 is a flowchart of an information management method provided by another exemplary embodiment of the present application;

FIG. 8 is an interface diagram of a claim management interface provided by another exemplary embodiment of the present application;

FIG. 9 is an interface diagram of a declarative new interface provided by an exemplary embodiment of the present application;

FIG. 10 is an interface diagram of a version management interface provided by an exemplary embodiment of the present application;

FIG. 11 is a version edit interface of a plain text type statement provided by an exemplary embodiment of the application;

FIG. 12 is a version editing interface for a document type declaration provided by an exemplary embodiment of the present application;

FIG. 13 is a version editing interface of a page link type declaration provided by an exemplary embodiment of the present application;

fig. 14 is a flowchart of an information management method provided by yet another exemplary embodiment of the present application;

FIG. 15 is an interface diagram of a claim logging interface provided by an exemplary embodiment of the present application;

FIG. 16 is a schematic diagram of a module architecture of an account air control platform according to an exemplary embodiment of the present application;

FIG. 17 is a version state flowchart of an consent claim provided by an exemplary embodiment of the present application;

FIG. 18 is a flow chart for validating expiration of a version to be validated provided by an exemplary embodiment of the present application;

FIG. 19 is a flowchart of an update flow time consent claim check provided by an exemplary embodiment of the present application;

FIG. 20 is a flowchart of an application service user viewing a consent claim provided by an exemplary embodiment of the present application;

FIG. 21 is a flowchart of the generation of an application service user consent check and consent record provided by an exemplary embodiment of the present application;

FIG. 22 is a schematic diagram of a status update relationship of an consent record provided by an exemplary embodiment of the present application;

FIG. 23 is a flow chart of consent record expiration destruction provided by an exemplary embodiment of the present application;

Fig. 24 is a schematic structural view of an information management apparatus provided in an exemplary embodiment of the present application;

fig. 25 is a schematic structural view of an information management apparatus provided in another exemplary embodiment of the present application;

fig. 26 is a schematic diagram of a computer device according to an exemplary embodiment of the present application.

Detailed Description

For the purpose of promoting an understanding of the principles and advantages of the application, reference will now be made in detail to the embodiments of the application, some but not all of which are illustrated in the accompanying drawings. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

The terms "first," "second," and the like in this disclosure are used for distinguishing between similar elements or items having substantially the same function and function, and it should be understood that there is no logical or chronological dependency between the terms "first," "second," and no limitation on the amount or order of execution.

With the development and popularization of internet technology, the application on the internet is increasing. Because of the requirements of personal information protection laws, each application related to the personal information of the object needs the object to sign the designated information protection statement, so that the data compliance of the application when using the personal information is ensured. In the related art, an application implements a declaration management system for managing information protection declarations provided to objects at the time of development. However, the claim management systems carried by different applications tend to be different, that is, each application has its own method of claim management. Then, in the case where an administrator manages a plurality of applications, it is necessary to manage information protection statements for different applications separately, resulting in a low management efficiency of the information protection statements.

The embodiment of the application provides an information management method, which is used for uniformly managing information protection statements corresponding to a plurality of applications on an application platform through a display statement management interface, so that the management efficiency of the information protection statements is improved; in addition, aiming at the appointed application program on the application platform, when the terminal receives the configuration operation of the appointed information protection statement, the signing flow of at least one information protection statement is configured in the account verification flow corresponding to the appointed application program, namely, different information protection statements are configured for each application program in the statement management interface, so that the method for configuring the information protection statement in a plurality of applications is realized more conveniently, and the configuration efficiency of the information protection statement is improved.

Fig. 1 is a schematic diagram of an implementation environment provided by an exemplary embodiment of the present application, as shown in fig. 1, where the implementation environment includes a terminal 100 and a server 110, and the terminal 100 includes a tenant terminal 101 and a user (i.e., an application service user) terminal 102, where the terminal 100 and the server 110 are connected through a communication network 120. Alternatively, the tenant terminal 101 and the user terminal 102 may be the same terminal or different terminals, which is not limited in the embodiment of the present application.

In the embodiment of the present application, a second application program is installed in the tenant terminal 101, where the second application program is provided with an information protection declaration management function, and the second application program may be at least one of a financial management application program, an employee management application program, an enterprise management application program, an instant messaging application program, a medical health application program, a ticket purchasing application program, an order management application program, and a shopping application program.

The user terminal 102 is provided with a first application, which is any application requiring signing of information protection statements. The embodiment of the application does not limit the specific type of the first application program. Alternatively, the first application and the second application may be installed in the same terminal, and illustratively, the first application and the second application are installed in the tenant terminal 101.

Illustratively, a second application program installed on the tenant terminal 101 displays a declaration management interface, where the declaration management interface is used to manage information protection declarations corresponding to applications (including the first application program) on the application platform, and the declaration management interface includes multiple candidate information protection declarations; receiving, on the tenant terminal 101, a flow configuration operation for a target information protection declaration among a plurality of candidate information protection declarations, for a first application program; in response to the flow configuration operation, configuring a signing flow of the target information protection statement in an account verification flow corresponding to the first application program, for example: when the flow configuration of the application program is carried out, the signing flow of the target information protection statement is configured in the registration flow of the application program.

Optionally, while the tenant terminal 101 increases the signing flow of the target information protection statement, the tenant terminal 101 sends a flow configuration request to the server 110, and after receiving the flow configuration request, the server 110 configures the signing flow of the target protection statement in the account verification flow corresponding to the first application program; subsequently, after the user terminal 102 updates the first application or reinstalls the first application, the signing process of the target protection statement is configured in the account verification process running in the user terminal 102, and when the application service user initiates the account verification process, the application service user needs to agree with the target information protection statement to perform the next process.

In some embodiments, terminal 100 is a smart phone, tablet, notebook, desktop, smart home, smart car terminal, smart speaker, etc., but is not limited thereto.

It should be noted that the server 110 can be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, and can also be a cloud server that provides cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs (Content Delivery Network, content delivery networks), and basic cloud computing services such as big data and artificial intelligence platforms.

Cloud Technology (Cloud Technology) refers to a hosting Technology that unifies serial resources such as hardware, software, network and the like in a wide area network or a local area network to realize calculation, storage, processing and sharing of data. The cloud technology is based on the general names of network technology, information technology, integration technology, management platform technology, application technology and the like applied by the cloud computing business model, can form a resource pool, and is flexible and convenient as required. Cloud computing technology will become an important support. Background services of technical networking systems require a large amount of computing, storage resources, such as video websites, picture-like websites, and more portals. Along with the high development and application of the internet industry, each article possibly has an own identification mark in the future, the identification mark needs to be transmitted to a background system for logic processing, data with different levels can be processed separately, and various industry data needs strong system rear shield support and can be realized only through cloud computing. Optionally, the server 110 may also be implemented as a node in a blockchain system.

It should be noted that, in the present application, before and during the process of collecting the related data of the object, a prompt interface, a popup window or output voice prompt information may be displayed, where the prompt interface, popup window or voice prompt information is used to prompt the object to collect the related data currently, so that the present application only starts to execute the related step of obtaining the related data of the object after obtaining the confirmation operation of the object to the prompt interface or popup window, otherwise (i.e. when the confirmation operation of the object to the prompt interface or popup window is not obtained), the related step of obtaining the related data of the object is finished, i.e. the related data of the object is not obtained. In other words, all object data collected by the present application is collected with the object agreeing and signed, and the collection, use and processing of related object data requires compliance with related laws and regulations and standards of the related region.

In connection with the above description and implementation environment, fig. 2 is a flowchart of an information management method according to an embodiment of the present application, where the method is applied to a tenant terminal as shown in fig. 1 for illustration, and the method includes:

step 201, a claim management interface is displayed.

The declaration management interface is used for managing information protection declarations corresponding to the applications on the application platform, wherein the information protection declarations refer to protocol files to be agreed between application service users and application service providers, and the declaration management interface comprises a plurality of candidate information protection declarations.

Illustratively, the information protection declaration may be implemented as a consent declaration, such as: terms of service, object agreements, information protection rules, etc. require application of agreement files signed (i.e., agreed) by the service user.

In some embodiments, the application platform includes a plurality of applications, and the claim management interface performs unified management on information protection claims corresponding to the plurality of applications.

Optionally, managing the information protection statement includes: at least one of creating an information protection statement, deleting an information protection statement, updating an information protection statement, configuring an information protection statement (i.e., configuring a signing procedure of an information protection statement in an application), etc., which is not limited in the embodiment of the present application.

In some embodiments, the declaration management interface includes a declaration new control and a declaration list, where the declaration new control is used to add candidate information protection declaration, and the declaration list is used to display the candidate information protection declaration; clicking the statement new control can add a candidate information protection statement in the statement list.

Optionally, in response to receiving a trigger operation on the claim newly created control, displaying a claim editing interface; receiving a new operation of protecting the statement against the first candidate information at the statement editing interface; the first candidate information protection claim is displayed in a claim list.

Optionally, the editing object of the declaration editing interface includes: declaration names, declaration identifications, declaration contents, declaration types, declaration file types, declaration record retention times, etc., to which embodiments of the present application are not limited.

The declaration name is the name of the user definition of the tenant for information protection declaration; the claim identification can be a unique identification allocated by the system for information protection claim; the declaration content is specific declaration details of the information protection declaration (namely, file content of a corresponding protocol file); the declaration type is a protocol type of information protection declaration, such as: terms of service, object agreements, information protection rules, etc.

The declaration file type is used to determine in which form the information protection declaration is to be presented to the object, and the declaration file type includes at least one of plain text, document, page link, and the like. Illustratively, in the case that the type of the declaration file is implemented as a plain text, the declaration content is an information protection declaration embodied in a plain text form, that is, the consent declaration content displayed by the object is plain text information; in the case where the declaration file type is implemented as a document, the declaration content is an information protection declaration embodied in the document, for example: uploading a PDF format agreement statement file by a tenant, and displaying the PDF when the object views the statement details; in the case that the declaration file type is implemented as a page link, the declaration content is an information protection declaration embodied in the form of a page link.

Optionally, in the case where the declaration file type is implemented as a page link, after the application portal clicks on the consent declaration, the object will jump to the specified page link, and the object agrees to the page link, and the account wind control platform does not check the content of the page link.

The above statement record keeping time refers to the signing record keeping time of the information protection statement by the management application service user. Optionally, the information protection claim's claim record has a shelf life limit, such as: the maximum period is 12 months; when a claim record exceeds the corresponding claim record shelf life, the claim record will be destroyed.

Optionally, the information management method provided by the embodiment of the application can be implemented through a Multi-tenant technology (Multi-tenancy Technology), the Multi-tenant technology is a software architecture technology based on a cloud technology, the cloud platform provides the instance to an external tenant through the Multi-tenant technology, and each tenant can perform personalized configuration on the rented instance according to own requirements.

In some embodiments, the claim management interface refers to an interface displayed in an account management platform.

The account wind control platform is an example rented by the tenant. Illustratively, after the tenant logs in the account wind control platform, the management module of the account wind control platform can manage the information protection statements of a plurality of applications.

Illustratively, after the management module of the account management platform builds an information protection statement, the account management platform sends basic information (such as a statement identifier, a statement type, a statement file type, a statement identifier and the like) of the built information protection statement to a universal module of the account management platform for storage, wherein the universal module can be used for storing the information protection statement built by the tenant. Alternatively, the general-purpose module may be implemented as a module mounted on a server.

Referring to FIG. 3, an interface diagram of a claim management interface is schematically shown. The declaration management interface 300 includes a new declaration control 301 and a declaration list display area 302, where an information protection declaration a and an information protection declaration B displayed in the declaration list display area 302 are obtained by triggering the new declaration control 301 to edit.

As shown in fig. 3, in the statement list display area 302, there are displayed: declaration names, such as: an information protection statement A; declarative identifications, such as: the unique identification number (Identity Document, ID) of the information protection claim a is 001; declaration type, such as: the declaration type of the information protection declaration A is other protocol types inconvenient to classify; declaring file types, such as: the file type of the information protection statement A is URL page link; declaring record save time, such as: the statement record preservation time of the information protection statement A is 6 months; declaring the recorded content, such as: the page link of the uniform resource locator (Uniform Resource Locator, URL) corresponding to the information protection statement A [ http:// hh1.Hhhh. Com ], and the content detail of the information protection statement A can be checked by clicking the link to enter the URL page.

Step 202, for a first application in an application platform, receiving a flow configuration operation for at least one information protection claim among a plurality of candidate information protection claims.

The flow configuration operation is used for configuring at least one information protection statement in the account verification flow corresponding to the first application program.

The account verification process includes a login process, a registration process, and the like, which require an application service user to sign an information protection statement.

In some embodiments, the account wind control platform further includes a process configuration interface of the first application program, where the process configuration module may configure a signing process of the information protection statement of the first application program.

Illustratively, after a plurality of candidate information protection claims are newly created, the designated application program and the designated information protection claims need to be associated, so that the account verification process of the designated application program includes a signing process for the designated information protection certificate.

Optionally, displaying a flow configuration interface of an account verification flow corresponding to the first application program, where the flow configuration interface includes a first enabling control, and the first enabling control is used to open a signing flow of the information protection statement in the account verification flow corresponding to the first application program; in response to receiving an opening operation on the first enabling control, displaying a declaration configuration area, wherein the declaration configuration area is used for inputting a declaration identifier corresponding to a candidate information protection declaration to be configured; and receiving a determining operation of the declaration identification corresponding to at least one information protection declaration in the declaration configuration area, and taking the determining operation as a flow configuration operation.

Optionally, the declaration identifier corresponding to the at least one information protection declaration is a unique identifier number automatically allocated by the system when the information protection declaration is newly built.

Referring to FIG. 4, an interface diagram of an application flow configuration interface 400 is shown for indicating a registration flow of a first application, in which clicking on an agreements declaration enablement control 401 configures at least one agreements declaration for the registration flow of the first application from a plurality of agreements declarations (including: protocol A/003, protocol B/004, and protocol C/005).

As shown in fig. 4, after the consent-claim enabling control 401 is turned on, the claim configuration area 402 is displayed, where the claim configuration area 402 includes content input boxes, each content input box corresponds to one consent claim that is visible to the object of the first application program, each content input box may be checked so as to select (e.g., the content input box 403 corresponds to the checked box 404) whether to fill, if so, the object must agree in the registration procedure to the consent claim corresponding to the content input box to perform the next step, otherwise, whether the object agrees to all the consent claims that do not affect the application to perform the next step.

In fig. 4, a declaration description related to protocol a (name)/003 (ID) is input in a content input box 403 in a declaration configuration area 402, that is, protocol a can be configured in a registration flow of a first application program; clicking the delete control 405 after the content input box 403, the configuration of protocol a may be deleted; clicking on the configuration control 406 configures other consent claims in the registration flow of the first application.

Optionally, based on the determining operation of the claim identifier corresponding to the at least one information protection claim in the claim configuration area, determining a hyperlink corresponding to the claim identifier corresponding to the at least one information protection claim, where the hyperlink is used to display the claim content of the at least one information protection claim.

In fig. 4, the declaration description format entered in content input box 403 uses a flexible concatenation form, i.e., literal + { consent declaration ID }, such as: {003} has been read and agreed in detail; finally, when the portal presentation is applied, the { consent statement ID } is replaced by a name hyperlink of a corresponding consent statement, such as: having read and agreed to agreement a in detail, clicking on the name "agreement a" of the agreement statement will reveal the agreement content details of agreement a.

Optionally, the number of information protection statements configured in the account verification process of the first application is limited. For example: the registration procedure of the first application supports configuration of at most 4 consent claims. Optionally, in the first application program, the number of information protection statement supporting configuration by different account verification processes is the same; alternatively, the number of information protection statements that support configuration is different for different account verification flows.

In step 203, in response to the flow configuration operation, a signing flow of at least one information protection statement is configured in an account verification flow corresponding to the first application program.

Illustratively, referring to FIG. 4, after clicking the confirmation control 407, the signing processes corresponding to the protocols A/003, B/004 and C/005 are added to the registration process corresponding to the first application.

Referring to fig. 5, an interface diagram of a registration interface is shown, where the registration interface is an application portal interface that is displayed by a first application program when an object performs account registration.

Each consent claim configured in the registration flow of the first application will be displayed in a bar, text portion directly, and { consent claim ID } will be replaced with a name hyperlink for the consent claim, which will be presented when clicked.

As shown in fig. 5, when the signing flows corresponding to the protocols a/003, B/004 and C/005 are configured in the registration flow of the first application program, a signing area 501 is displayed in the registration interface 500, and a hook is performed in the signing area 501, so that the corresponding protocols are agreed. If all three agreements need to be agreed upon during configuration, if the object does not sign up for agreement a, clicking on the registration control 502 will display a prompt "please read and agree with agreement a first", thereby prompting the user that the user needs to sign up for agreement a before proceeding to the next step.

Optionally, the consent claims presentation means of the different sound text types are different: when the declaration file type is a URL page link, clicking the name and then directly jumping to the configured URL address, and displaying declaration content on the URL page; in the case that the declaration file type is a document, clicking on the name will jump to the customized domain name address of the tenant, and then displaying the declaration content in the form of a portable file format (Portable Document Forma, PDF) document; in the case where the declaration file type is plain text, clicking on the name will reveal the declaration content in plain text form in the form of a pop-up box.

Illustratively, for "self has read and agreed to protocol B" shown in the signature area 501 in fig. 5, assuming that the declaration file type of protocol B is of plain text type, referring to fig. 6 after clicking on the declaration name "protocol B", a pop-up window 600 will be displayed, and details of protocol B will be displayed in plain text form in the pop-up window 600.

In some embodiments, the account verification process may be a process for the first application.

Optionally, in response to a flow configuration operation on a registration flow corresponding to the first application, configuring a signing flow of at least one information protection claim in the registration flow; or, in response to a flow configuration operation on the login flow corresponding to the first application program, configuring a signing flow of at least one information protection statement in the login flow.

For example: when entering a specified application program, an account login process is required, and when the account login is performed, the object needs to agree with related service terms and agreements.

In other embodiments, the account verification process may be a process for a specific module in the first application program, for example: the financial application program comprises a face payment function, a face verification process is required to be carried out, and the object is required to sign and agree with a related privacy protocol before face verification is carried out.

Alternatively, for the specified candidate information protection statement, only the account verification flow corresponding to the specified application program may be associated; account verification processes corresponding to a plurality of application programs can also be associated. Schematically, as shown in fig. 3, the information protection statement a is associated with only the registration flow of the application a; the information protection declaration B is associated with the registration flows of the application a and the application B.

Optionally, the general module of the account wind control platform is further used for managing application flows of each application in the application platform.

Illustratively, after the tenant triggers the flow configuration operation of the specified information protection statement of the first application program at the management module of the account wind control platform, the management module of the account wind control platform sends a flow configuration request to the universal module of the account wind control platform, wherein the flow configuration request at least comprises a program identifier of the first application program, an application flow identifier to be configured and a statement identifier of the specified information protection statement.

After receiving a flow configuration request, a general module of the account wind control platform invokes a stored information protection statement according to a statement identification of the specified information protection statement, if the specified information protection statement corresponding to the statement identification exists, generating a signing flow code corresponding to the specified information protection statement, and adding the signing flow code in a registration flow application code corresponding to the first application program; then the subsequent application service user needs to sign the specified information protection statement when registering the first application.

In some embodiments, the claim management interface includes a second enabling control corresponding to the at least one information protection claim, where the second enabling control is configured to enable a signing process of the at least one information protection claim in an account verification process configured with the at least one information protection claim.

Optionally, in response to the flow configuration operation, in a case that the second enabling control is in an on state, configuring a signing flow of at least one information protection statement in an account verification flow corresponding to the first application program.

Illustratively, after receiving a flow configuration request, the universal module of the account wind control platform determines that a specified information protection statement corresponding to a statement identifier exists, and needs to invoke basic information of an account verification flow corresponding to a first application program, where the basic information includes enabling information for the information protection statement, and if enabling information indicates that the account verification flow corresponding to the first application program starts a signing flow for the information protection statement, generates a signing flow code corresponding to the specified information protection statement, and adds the signing flow code in a registration flow application code corresponding to the first application program.

Illustratively, as shown in fig. 3, the declaration start-stop control 303 corresponding to the information protection declaration a in the declaration management interface 300 is in a closed state, which indicates that although the information protection declaration a is configured for the registration flow and the login flow of the application a, the signing flow corresponding to the information protection declaration a is not configured in the registration flow and the login flow of the application a in practice; only when the declaration start-stop control 303 is set in the enabled state, the signing process corresponding to the information protection declaration a is configured into the registration process and the login process of the application a.

In some embodiments, when the tenant opens a signing flow of the information protection statement in an account verification flow corresponding to the first application program during information protection statement configuration, the system automatically matches the information protection statement for the first application program according to statement description information corresponding to each candidate information protection statement in the statement list.

Optionally, displaying a flow configuration interface of an account verification flow corresponding to the first application program, where the flow configuration interface includes a first enabling control, and the first enabling control is used to open a signing flow of the information protection statement in the account verification flow corresponding to the first application program; and in response to receiving an opening operation on the first enabling control, automatically configuring a signing flow of at least one information protection statement in an account verification flow corresponding to the first application program under the condition that the statement description information comprises a program identifier of the first application program.

Alternatively, the program identifier of the first application program may be used to uniquely indicate the first application program; alternatively, the program identifier of the first application program is used to indicate the packet identifier corresponding to the first application program.

Illustratively, the flow configuration request includes a program identifier of the first application program, an application flow identifier to be configured, and declaration description information corresponding to the specified information protection declaration. After receiving the flow configuration request, the universal module of the account wind control platform extracts the program identifier in the statement description information corresponding to the specified information protection statement; if the program identification is consistent with the received program identification of the first application program, generating a signing flow code corresponding to the specified information protection statement, and adding the signing flow code in a registration flow application code corresponding to the first application program.

In summary, the information management method provided by the embodiment of the application performs unified management on the information protection statements corresponding to a plurality of applications on the application platform through the display statement management interface, so that the management efficiency of the information protection statements is improved; in addition, aiming at the appointed application program on the application platform, when the terminal receives the configuration operation of the appointed information protection statement, the signing flow of at least one information protection statement is configured in the account verification flow corresponding to the appointed application program, namely, different information protection statements are configured for each application program in the statement management interface, so that the method for configuring the information protection statement in a plurality of applications is realized more conveniently, and the configuration efficiency of the information protection statement is improved.

According to the method provided by the embodiment of the application, the first enabling control is displayed on the flow configuration interface by displaying the flow configuration interface of the account verification flow corresponding to the first application program, and the declaration configuration area is displayed by triggering the first enabling control; by the confirmation operation of the declaration identification in the declaration configuration area, the signing flow of at least one information protection declaration is automatically configured in the account verification flow corresponding to the first application program, so that the configuration program of the signing flow of the information protection declaration is more simply realized, and the management efficiency of tenants on the information protection declaration is improved.

According to the method provided by the embodiment of the application, based on the determination operation of the declaration identification corresponding to at least one information protection declaration in the declaration configuration area, the corresponding hyperlink is configured for the declaration identification corresponding to at least one information protection declaration, so that the declaration content of the information protection declaration can be displayed on an application portal in a hyperlink mode, an application service user can know more declaration content of the information protection declaration conveniently, and the application experience of the application service user in the signing process of the information protection declaration is improved.

According to the method provided by the embodiment of the application, the first starting control is displayed on the flow configuration interface by displaying the flow configuration interface of the account verification flow corresponding to the first application program, and the information protection statement is automatically configured for the application program according to the statement description information of the information protection statement by triggering the first starting control, so that the efficiency of flow configuration of the information protection statement is improved.

According to the method provided by the embodiment of the application, in response to the flow configuration operation, under the condition that the second enabling control is in the enabling state, the signing flow of at least one information protection statement is configured in the account verification flow corresponding to the first application program, namely, the enabling condition of the information protection statement in all the associated application programs is controlled by the second enabling control, so that the management efficiency of the information protection statement is improved.

In some alternative embodiments, the claim management interface is further configured to manage versions of the information protection claim. Fig. 7 is a flowchart of an information management method according to an embodiment of the present application, where the method is applied to a tenant terminal as shown in fig. 1, and the method includes:

step 701, displaying a claim management interface.

The declaration management interface is used for managing information protection declarations corresponding to the applications on the application platform, wherein the information protection declarations refer to protocol files to be agreed between application service users and application service providers.

Referring to FIG. 8, an interface diagram of another claim management interface is schematically shown. Included in the claims management interface 800 are a new claims control 801 and a claims list display area 802.

As shown in fig. 8, the declaration list display area 802 includes a plurality of list items including: agreeing to a declaration name/ID, agreeing to a declaration type, declaring a file type, current version (i.e., declaring a current version), creation time (i.e., time of newly added declaration), registration flow association application, login flow association application, declaration start-stop control (i.e., second enable control), and operations.

Step 702, in response to receiving a trigger operation on the claim newly created control, displaying a claim editing interface.

Optionally, the declaration editing interface is used for editing candidate information to protect information such as declaration name, declaration type, declaration file type, declaration record save time, declaration description and the like; it should be noted that, only the candidate information protection declaration is newly added (or understood as a definition) in the declaration editing interface, the declaration content of the candidate information protection declaration is not configured, and the declaration content of the candidate information protection declaration is configured in the subsequent version management interface.

Illustratively, after clicking on the new declaration control 801 in fig. 8, that is, the declaration management interface 800 is windowed to display a declaration editing interface 900 (see fig. 9), a declaration name, a declaration type, a declaration file type, a declaration record retention time, a declaration description, and the like of a consent declaration can be edited in the declaration editing interface 900.

Wherein "×" indicates that the entry information is padding information, for example: "agree to claim name" means information that the claim name is necessary to fill at the same time; the declaration is described as custom descriptive information, to which embodiments of the application are not limited.

In response to receiving a new operation for the first candidate information protection claim at the claim editing interface, step 703, displaying the first candidate information protection claim in the claim list.

Illustratively, as shown in fig. 9, receiving a trigger operation to the "determine" control 901, that is, receiving a new addition operation to the consent statement, clicking on the "confirm" control 901, the statement management interface 800 will newly add the consent statement about "application C service clause".

After the first candidate information protection statement is newly added, the statement content of the first candidate information protection statement is also required to be configured, and the configuration of the statement content can be realized through version management of the first candidate information protection statement, namely, the new version is added, and different statement contents are configured under different versions.

Optionally, the claim list includes a version management control, where the version management control is used to perform version management on the first candidate information protection claim.

Consent declaration is to provide explicit validation and direction for objects through continuous version iterations, version presence state, need to specify the validation time of each version, if the specified validation time is today or the time before today, the version will be validated immediately, each validation will generate an incremental version number, the old version will be considered as history version no longer validated after release of the new version, and all objects of the tenant need to reconfirm the new version of the declaration when accessing the application again.

Illustratively, as shown in fig. 8, the declaration list display area 802 in the declaration management interface 800 includes an operation list item including a version management control 803, and the version management control 803 is used for performing version management on the consent declaration.

Step 704, in response to receiving a triggering operation on the version management control, displaying a version management interface corresponding to the first candidate information protection statement.

The version management interface comprises a version new control and a declaration version list, wherein the version new control is used for adding first candidate information protection declarations of different versions, and the declaration version list is used for displaying version information of the first candidate information protection declarations; and a candidate information protection statement with a designated version can be newly added into the statement version list by triggering the version newly-built control.

The version information of the candidate information protection statement comprises statement content, version state, version number, version effective time, version release time and the like of the information protection statement.

Alternatively, the declaration content of the information protection declaration is presented in plain text, document, page links, or the like.

Optionally, the version state is a state of an information protection statement of a current version, and the version state includes: history version, validation version and version to be validated. The historical version refers to a version which takes effect in a historical time period and is not currently taking effect; the effective version refers to the currently effective version, namely the information protection statement of the effective version is the information protection statement currently configured in the account verification flow of the first application program; historical versions refer to versions that are validated for some period of time in the future, and are not currently validated.

The version number refers to the version identifier allocated by the system after the information protection statement of the appointed version is validated. Optionally, the system assigns version numbers to the validated information protection assertions in turn in an incremental manner. For example: the version number of the first effective information protection statement is V1, and the version number of the second effective information protection statement is V2; the effective time is the effective time of the information protection statement of the corresponding version; the release time is the new time of the information protection statement of the corresponding version.

Referring to fig. 10, an interface schematic diagram of a version management interface is shown, and after clicking on the version management control 803 in fig. 8, a version management interface 1000 for other protocols of the application a is displayed, where the version management interface 1000 includes a "new version" control 1001, and a version list display area 1002 is declared.

In the declaration version list display area 1002, declaration contents of other protocols of application a (presented in the form of URL page links), version status, version number, version validation time and version release time, and operation list items are displayed.

The operation list item comprises a view control, an edit control and a delete control, wherein the view control is used for viewing the specific version contents of other protocols of the application A of the corresponding version; the editing control is used for editing the specific version contents of other protocols of the application A of the corresponding version; the "delete" control is used to delete the corresponding version of the application a other protocol.

Step 705, receiving a triggering operation on the version new control.

The triggering operation may be at least one of a single click operation, a double click operation, a long press operation, a sliding operation, a voice command operation, a gesture command operation, and the like, which is not limited in the embodiment of the present application.

For illustration, please refer to fig. 10, a trigger operation in the "new version" control 1001 is received, and then other protocols of the application a of the specified version can be newly added.

Step 706, based on the triggering operation, displaying the version information of the first candidate information protection declaration of the first version in the declaration version list.

Responding to the triggering operation, and displaying a version editing interface; receiving an editing operation of the first candidate information protection statement of the first version on the version editing interface, wherein the editing operation is used for editing the statement content of the first candidate information protection statement of the first version; based on the editing operation, version information of the first candidate information protection declaration of the first version is displayed in the declaration version list.

Wherein the operation object of the editing operation includes the declaration content and the validation time of the first candidate information protection declaration of the first version.

In some embodiments, a version editing interface is displayed according to the declaration file type to which the candidate information protection declaration corresponds.

Optionally, displaying a first edition editing interface under the condition that the declaration text type corresponding to the candidate information protection declaration is plain text, wherein the first edition editing interface comprises a text input box for inputting the declaration content corresponding to the candidate information protection declaration of the first edition; receiving a text input operation in the text input box for a first candidate information protection statement for the first version; based on the text input operation, version information of the first candidate information protection declaration of the first version is displayed in the declaration version list.

Optionally, the general module of the account wind control platform is further used for performing version management on the information protection statement.

Illustratively, the general module of the account wind control platform already stores basic information of the specified information protection statement, for example: and when the tenant triggers a version new operation of the specified information protection statement at the management module of the account wind control platform, the management module of the account wind control platform sends a version new request to the universal module of the account wind control platform, wherein the version new request at least comprises a statement identifier, version content and version effective time of the specified information protection statement.

After receiving the version new operation, the universal module of the account wind control platform invokes the stored information protection statement according to the statement identification of the specified information protection statement, and if the specified information protection statement corresponding to the statement identification exists, the tenant is explained to have defined the specified information protection statement. Then the general module judges whether the effective time of the version is smaller than or equal to the current time, if the effective time of the version is smaller than or equal to the current time, the general module continues to judge whether the appointed information protection statement of the effective version is stored currently; if the specified information protection statement does not exist, directly storing the version content of the received specified information protection statement, and storing version state equipment of the version content into an effective state, and adding a signing process corresponding to the specified information protection statement in a registration process application code, wherein the signing process comprises hyperlinks corresponding to the statement content; if the specified information protection statement exists, setting the version state of the specified information protection statement of an effective version as a historical version, storing the version content of the received specified information protection statement, and updating hyperlink corresponding to the statement content in the signing process corresponding to the specified information protection statement in the registration process application code;

If the effective time of the version is longer than the current time, continuing to judge whether the general module currently stores the appointed information protection statement of the version to be effective; if the version information protection statement does not exist, the version content of the received specified information protection statement is stored, version state equipment is in a state to be validated, and then the received specified information protection statement is validated under the condition that the current moment reaches the version validation time. Optionally, if the version state of the currently stored specified information protection statement of the version to be validated is the version 1 to be validated; continuing to judge whether the version effective time of the currently stored specified information protection statement is earlier than the version effective time of the received specified information protection statement, if so, setting the version state of the received specified information protection statement as a version 2 to be effective; then, after the specified information protection statement with the state of the to-be-validated version 1 is validated, the version state of the specified information protection statement with the state of the to-be-validated version 2 is updated to the to-be-validated version 1.

And when a certain version in the specified information protection statement takes effect, the universal module of the account wind control platform automatically distributes incremental version numbers for the effective specified information protection statement according to the effective sequence.

Referring to FIG. 11, a version editing interface for plain text type declarations is schematically shown, and as shown in FIG. 11, version editing interface 1100 includes a text entry box 1101 in which text of a desired specific declarative content can be entered; the version editing interface 1100 includes an effective time editing box 1102, and the effective time of the version of the other protocols of the newly-built application a can be set through the effective time editing box 1102.

After inputting the specific declaration content text and setting the effective time of the version, clicking the "publish" control 1103, i.e. publishing the application a other protocols of the current new version, and displaying the version information of the application a other protocols of the version in the declaration version list display area 1002 in the version management interface 1000.

Optionally, displaying a second edition editing interface under the condition that the declaration text type corresponding to the candidate information protection declaration is a document, wherein the second edition editing interface comprises a document uploading control, the document uploading control is used for importing a declaration document corresponding to the candidate information protection declaration, and the document content in the declaration document is the declaration content corresponding to the candidate information protection declaration; receiving a document uploading operation of a declaration document corresponding to a first candidate information protection declaration of a first version on a text uploading control; based on the document upload operation, version information of the first candidate information protection declaration of the first version is displayed in the declaration version list.

Optionally, the document uploading control is used for importing a declaration document of a specified type corresponding to the candidate information protection declaration, where the specified type of declaration document may be a PDF type, a TXT type, a DOC type, and the embodiment of the present application is not limited thereto.

Referring to fig. 12, a version editing interface of a document type declaration is shown, and as shown in fig. 12, the version editing interface 1200 includes a document upload control 1201, and a declaration file stored locally or in the cloud can be uploaded by clicking on the document upload control 1201. The version editing interface 1200 includes an effective time editing box 1202, and the effective time editing box 1202 can set the effective time of the version of the other protocols of the newly-built application a.

After uploading the declaration document agreeing to the declaration and setting the effective time of the version, clicking the "issue" control 1203 to issue the other protocols of the application a of the current new version, and displaying the version information of the other protocols of the application a of the version in the declaration version list display area 1002 in the version management interface 1000.

Optionally, displaying a third edition editing interface under the condition that the declaration text type corresponding to the candidate information protection declaration is a page link, wherein the third edition editing interface comprises a page link input box, the page link input box is used for inputting the page link corresponding to the candidate information protection declaration, and page display content in the page link is declaration content corresponding to the candidate information protection declaration; receiving an input operation of a page link corresponding to a first candidate information protection statement of a first version on a page link input box; based on the input operation, version information of the first candidate information protection declaration of the first version is displayed in the declaration version list.

Referring to fig. 13, a version editing interface of a page link type declaration is shown, and as shown in fig. 13, the version editing interface 1300 includes a page link input box 1301, in which a link address of a URL page link corresponding to a consent declaration to be added can be input; the version editing interface 1300 includes an effective time editing box 1302, and the effective time editing box 1302 can set the effective time of the version of the other protocols of the newly-built application a.

After the link address of the URL page link and the set version effective time are input, the "issue" control 1303 is clicked, that is, the other protocols of the application a of the current new version are issued, and the version information of the other protocols of the application a of the version is displayed in the declaration version list display area 1002 in the version management interface 1000.

Step 707, for a first application in the application platform, receives a flow configuration operation for at least one information protection claim of a preset version among the plurality of candidate information protection claims.

Optionally, displaying a flow configuration interface of an account verification flow corresponding to the first application program, where the flow configuration interface includes a first enabling control, and the first enabling control is used to open a signing flow of the information protection statement in the account verification flow corresponding to the first application program; responsive to receiving an open operation on the first enablement control, displaying a declarative configuration area; and receiving a determining operation of the declaration identification corresponding to at least one information protection declaration in the declaration configuration area, and taking the determining operation as a flow configuration operation.

Step 708, in response to the flow configuration operation, configures a signing flow of at least one information protection claim in an account verification flow corresponding to the first application.

According to the method provided by the embodiment of the application, the declaration editing interface is displayed by receiving the triggering operation on the declaration newly-built control; then, the first candidate information protection declaration is displayed in the declaration list by following a new operation on the first candidate information protection declaration at the declaration editing interface. And then, the appointed information protection statement is associated in the appointed application flow, and the new operation of the information protection statement and the configuration operation of the information protection statement are decoupled, so that different application programs can use the same information protection statement, and the management efficiency of the information protection statement is improved.

According to the method provided by the embodiment of the application, the version management interface corresponding to the first candidate information protection statement is displayed by receiving the triggering operation on the version management control; by receiving the triggering operation on the version newly-built control, displaying a version editing interface, and newly-building and editing information protection declarations of different versions on the version editing interface, when the information protection declarations are updated, the new information protection declarations do not need to be declared, so that application flow configuration is prevented from being carried out again; the version of the information protection statement is updated, so that the statement content of the information protection statement can be updated in each application, and the management efficiency of the information protection statement is further improved.

In some optional embodiments, the account wind control platform further includes management of a statement record corresponding to the information protection statement. Fig. 14 is a flowchart of an information management method according to an embodiment of the present application, where the method is applied to the tenant terminal shown in fig. 1, and the method includes:

step 1401, a claim management interface is displayed.

Step 1402, for a first application in an application platform, receives a flow configuration operation for at least one information protection claim among a plurality of candidate information protection claims.

Step 1403, in response to the flow configuration operation, configures a signing flow of at least one information protection claim in an account verification flow corresponding to the first application.

In step 1404, the statement record is displayed according to an account verification process initiated by the first account on the first application.

Wherein the claim record is used for recording the signing result of the first account for the at least one information protection claim.

Optionally, the statement record is displayed in a statement management interface of the account wind control platform.

Referring to fig. 15, an interface diagram of a declaration record is shown, and as shown in fig. 15, the signing result of different objects for each protocol is shown in a declaration record 1500.

Illustratively, after the object clicks to log in or registers to enter the next step, the portal will generate an agreement record according to the checked condition of the object, i.e. the authorization condition of the object for one or more agreement claims. If the object hooks a certain agreement statement, the object is considered to agree with the current release versions of all agreement statements in the agreement statement; if the object does not hook a piece of consent content, then the object is considered to be unauthorized of the content of the currently published version of all consent claims in the piece of content.

The tenant may view the declaration records of the consent claims by the objects of all application systems. The declaration record includes: the object ID of the consent operation, the application of the operation, the flow of the application, the consent claim name and ID of the object operation, the version of the consent claim of the object operation, the time of the object operation, the expiration time of the claim record, the operation result, and the like.

Wherein each consent claim configures a claim record save time, and when an object operates an effective version of a consent claim to generate a consent record, the system calculates an expiration time of the claim record according to the consent claim configured save time. When the expiration time is reached, the claim record is destroyed.

Optionally, displaying first identification information in the statement record, where the first identification information is used to indicate that the first account signs at least one information protection statement; or displaying second identification information in the statement record, wherein the second identification information is used for indicating that the first account does not sign at least one information protection statement; or displaying third identification information in the statement record, wherein the third identification information is used for indicating that the first account signs at least one information protection statement updated by version; or displaying fourth identification information in the statement record, wherein the fourth identification information is used for indicating that the first account is deleted.

In some embodiments, an operation interface of a declaration record is provided for the first account at the application portal, when the first account deletes the declaration record signed for at least one information protection declaration in the registration procedure, the declaration record of the first account displays fourth identification information, that is, the deletion of the first account is indicated at the declaration record interface of the tenant terminal; when the first account deletes the statement record of the related information protection statement signed in the login process, the statement record of the first account displays fifth identification information, namely, the signing result of the first account withdrawal on at least one information protection statement in the login process, on a statement record interface of the tenant terminal.

According to the method provided by the embodiment of the application, according to the account verification process initiated by the first account on the first application program, a statement record is displayed, and the statement record is used for recording the signing result of the first account on at least one information protection statement; the management channel for signing and recording the statement corresponding to the account is provided, and the efficiency of information protection statement management on the account is improved.

The information management method provided by the embodiment of the application is described below by taking the implementation of the information protection statement as an agreeable statement as an example. First, referring to fig. 16, a schematic diagram of a module architecture of an account wind control platform provided by the present application is shown, and as shown in fig. 16:

the account air control platform 1600 includes three main modules: management module 1610, portal module 1620, and universal module 1630.

Wherein, the management module 1610 is a module carried on the tenant end, and the management module 1610 provides the function of the management system for the tenant; the portal module 1620 is a module carried on the application, and the portal module 1620 provides functions such as login or registration for the application service user; the universal module 1630 includes management of the functional sub-modules, and the universal module 1630 includes three functional sub-modules of application, consent statement, and consent record.

The consent sound sub-module 1631 is used for defining consent claims in the account wind control platform and maintaining a version life cycle of each consent claim; the application sub-module 1632 is configured to apply configuration of a corresponding account verification procedure, where an agreement statement may be configured; consent records sub-module 1633 contains all consent records generated by the application portal.

The server at the account management platform 1600 includes both the tenant and the application service user. The tenant can perform consent statement management (i.e. configuration and management of consent statement and consent statement version), application management configuration (configuration of consent statement into account verification flow of application), consent record management (management of consent records generated by all application portals); the application service user can perform application flow reading and (i.e. by accessing the application to see the agreeing statement that the tenant configures for the application), agreeing statement version reading (see details of agreeing to the statement), statement record generation (the application service user decides whether to sign or not to go to the next step and generate the statement record).

Secondly, introducing an agreeing statement management flow carried out by the tenant:

1) Consent asserts the start-stop logic.

After the consent claims creation is completed, the tenant may start and stop specifying the consent claims. But the enable and disable consent claims require that preset conditions be met. Enabling: the enabled consent claims must possess a valid consent claim version, otherwise, the error is reported "the consent claims have no valid version, please go to version management to create a new version or modify the validation time"; and (3) stopping: when an already enabled consent claim is disabled, it must be satisfied that the claim is not associated by any application flow, otherwise an error is reported "the consent claim is referenced in the application a registration flow, cannot be closed".

2) Agreeing to claim version management.

First, there are three states for agreeing to the version of the claim: to-be-validated version, historical version. Wherein, the version to be validated: the effective time of the newly-built version is longer than today; effective version: the time of the newly-built version is smaller than or equal to the present day, or the effective time of the version to be effective is equal to the present day, and the version to be effective is automatically effective; historical version: after the release of the new version, the native version will be set to the history version.

Referring to fig. 17, a version status flow chart of a consent claim is shown, as shown in fig. 17, the flow comprising the steps of:

At step 1701, a consent claim version is created.

Illustratively, after the tenant logs in the account management platform, the latest version of the consent statement is newly built in the consent statement management module, and the consent statement management module sends the newly built latest version of the consent statement ID and the version effective time to the consent statement submodule 1631; version management is performed on the latest version of the consent claims by the consent claims submodule 1631, where version management is mainly performed on the version states of the versions of the consent claims.

Step 1702, check consent claim status.

Illustratively, the consent claim submodule 1631 starts to check the version validation time of the latest version of the consent claim after receiving the latest version of the consent claim ID and the version validation time.

Step 1703, determine if the version validation time is less than or equal to today?

Illustratively, it is determined whether the version validation time of the latest version of the consent claim is less than or equal to today.

If it is determined that the version validation time is less than or equal to today, step 1704, continuing to determine whether the first co-declaration version has a release version?

Illustratively, if the version validation time of the latest version of the consent claims is less than or equal to today, continuing to determine whether the current consent claims have a released version of the consent claims, where the released version of the consent claims refers to the consent claims currently being validated.

And 1705, if it is determined that the release version exists in the current consent statement version, setting the current effective version state as the history version.

Illustratively, if there is currently an issued version of the consent claim, since the version of the latest version of the consent claim takes effect less than or equal to today, the consent claim that takes effect today should be the latest version of the consent claim; then the status of the consent claim of the currently published version is set to the historical version.

Step 1706, an incremented version number is generated, setting the newly added version state to a live version.

Illustratively, an incremental version number is allocated to the latest version of the consent statement, and the state of the latest version of the consent statement is set to be an effective version, that is, the consent statement being effective is modified to the latest version of the consent statement, that is, the currently effective consent statement is modified to the latest version of the consent statement in the account verification process. For example: and updating the service protocol A of the version 1.0 in the registration flow to the service protocol A of the version 2.0.

Step 1707, end.

Illustratively, the update flow of the version status for each version of the consent claim is ended.

If it is determined that the release version does not exist in the current consent claim version, step 1704 is executed to step 1706.

Illustratively, if there is no consent statement of the released version currently, it indicates that the consent statement is not configured in the current account verification process, or the consent statement in the current account verification process is a consent statement of the invalid version, an incremental version number is allocated to the consent statement of the latest version, and the state of the consent statement of the latest version is set to be the valid version, that is, the consent statement that is being validated is modified to be the consent statement of the latest version, that is, the consent statement that is being validated currently is modified to be the consent statement of the latest version in the account verification process.

If the version validation time is greater than today, step 1708, continuing to determine whether the version to be validated exists in the current consent claim version?

Illustratively, if it is determined that the version validation time of the latest version of the consent claim is longer than today, continuing to determine whether there is a consent claim of the version to be validated.

Step 1709, it is determined that the current agreeing to claim version does not have a version to be validated, and the newly added version status is set as the version to be validated.

Illustratively, if it is determined that there is no consent claim of the version to be validated, the version status of the consent claim of the latest version is set as the version to be validated because it is not the time of validation of the latest version today.

Step 1707, end.

Step 1710, determining that the current agreeing statement version has a version to be validated, and throwing out an exception: there is a version to be validated and no new version can be created.

Schematically, if judging that the agreeable statement of the to-be-validated version exists, displaying abnormal information on an account wind control platform interface of the tenant terminal, wherein the abnormal information is as follows: there is already a version to be validated, no new version can be created, that is, there can currently only be one validated version and one version to be validated for the consent claims.

Step 1707, end.

Second, the meaning of the validation time corresponds to the definition of the time that the legal regulations are validated. Validation of the version in addition to immediately upon creation in fig. 17, there is another validation scenario: the release to be validated (validation time is longer than today) expires.

Referring to fig. 18, a flow chart for validating the expiration of a version to be validated is shown schematically, as shown in fig. 18, the flow chart comprising the steps of:

step 1801, issuing a timing task: performed at 0 point daily.

Illustratively, a timer is set, where the timer corresponds to a timed task, where the timed task is to check whether the version of the consent claim in the current account verification flow is expired, and the timer is set to execute the timed task at 0 point per day, that is, to check whether the version expiration time of the currently validated consent claim version is less than or equal to 0 point per day.

Step 1802, a determination is made as to whether a task lock is obtained.

Because a plurality of consent claims exist in the account wind control platform, each consent claim needs to execute the timing task, and the situation that a single consent claim executes the same timing task for a plurality of times is avoided by adopting a task lock mode.

Illustratively, when a certain consent state is acquired, the timing task is executed, and when the task lock is not acquired, the timing task is not executed; the task lock may be implemented in a manner of Zookeeper, redis, which is not limited in the embodiment of the present application.

And step 1803, if the task lock is not obtained, ending.

Illustratively, if it is determined that the task lock is not obtained by the current consent statement, the timed task is not executed.

If it is determined that the task lock is obtained, all versions of the consent claims are obtained, step 1804.

Schematically, if the current consent statement is judged to obtain the task lock, the consent statement corresponding to all the current versions is obtained, and the version states of the consent statements of all the versions are determined.

Step 1805, determine whether the version of the consent claim is a version to be validated?

Illustratively, checking the version states of the consent claims of the versions sequentially, if it is determined that the version state of the consent claim of the current version is not the version to be validated, continuing to determine whether the version state of the consent claim of the next version is the version to be validated?

If it is determined that the version of the consent claim is the version to be validated, step 1806, continuing to determine if the version expiration time is less than or equal to today?

Illustratively, if it is determined that the version status of the consent claim of the current version is the version to be validated, continuing to determine whether the version expiration time of the consent claim of the current version is less than or equal to today?

If it is determined that the version expiration time is less than or equal to today, step 1807, continuing to determine whether there is an issued version of the consent statement to which the current version belongs?

Schematically, if it is determined that the version expiration time of the consent claims of the currently to-be-validated version is less than or equal to today, continuing to determine whether the consent claims of the current version have the published version, if: and judging whether the agreeing statement A of the current to-be-validated version has the agreeing statement A being validated or not.

And step 1808, if it is determined that the release version exists in the consent statement to which the current version belongs, setting the current effective version state as the history version.

Illustratively, if it is determined that the consent claims of the currently pending version have a published version (i.e., the currently validated consent claims), the version status of the currently validated consent claims is set to the historical version.

Step 1807, generating an incremental version number, and setting the to-be-validated version state to be a valid version.

Illustratively, an incremental version number is assigned to the consent claim of the version to be validated, and the version status of the consent claim of the version to be validated is set to the validation version.

Step 1803, end.

Illustratively, the timed task for the grant declaration of the currently acquired task lock is ended, and the timed task for the grant declaration of the next acquired task lock is continued to be executed.

Step 1809, if it is determined that the consent statement to which the current version belongs does not have an issue version, step 1809 is performed.

Illustratively, if it is determined that the consent claim of the currently pending version does not have the published version (i.e., the currently validated consent claim), an incremental version number is assigned to the consent claim of the currently pending version, and the version status of the consent claim of the pending version is set to the validation version.

Step 1803, end.

3) And (5) application flow configuration.

When the reference consent claims are configured in the application flow, the input consent claim ID needs to be satisfied and is true and valid, and the consent claims have effective versions.

Referring to fig. 19, a flowchart of a consent claim checking process is shown, as shown in fig. 19, and includes the following steps:

in step 1901, the application flow is updated.

Illustratively, after the tenant logs in the account wind control platform, the tenant may enter an application flow configuration module to configure an application flow, where the application flow includes an account login flow, an account registration flow, and the like, which is not limited in this embodiment of the present application.

Step 1902, application flow basic information inspection.

Illustratively, when the tenant updates the application flow, the account wind control platform is triggered to check the application flow, for example: it is checked whether the application flow is enabled (i.e. whether the application flow is configured in the application), authentication properties of the application flow (account name, mailbox, etc.), and the opening of the consent statement.

Step 1903, determine if application flow opens consent claim?

Illustratively, it is determined whether an agreement statement is opened in the application flow, that is, whether a verification flow corresponding to the agreement statement is configured to be opened in the application flow.

If it is determined that the application process opens the consent claim, step 1904, continuing to determine whether the number of claim configuration information pieces is greater than 4?

Illustratively, if it is determined that the verification process of the consent claims is started in the application process, the configuration situation of the consent claims in the application process is continuously determined, for example: the amount of declarative configuration information added at the application flow configuration interface is checked.

The declarative configuration information is the information filled in the content input box 403 in fig. 4. A declaration configuration information is associated with a consent declaration.

If it is determined that the number of claims configuration information pieces is less than or equal to 4, step 1905, continuing to determine whether or not there is an agreement statement associated with the claims configuration information?

Illustratively, the number of consent claims configurable by a single application flow is limited, i.e., the number of claim configuration information added at the application flow configuration interface is limited. Assuming that the number of agreeable claims configurable by a single application flow is 4, if it is determined that the number of claim configuration information added in the application flow is less than or equal to 4, it is further necessary to continuously check whether the agreeable claims associated with each claim configuration information exist, for example: checking whether the declaration ID filled by the tenant in the declaration configuration information is an ID existing in the consent declaration list.

If it is determined that the consent statement associated with the statement configuration information exists, step 1906, continuing to determine whether the consent statement associated with the statement configuration information has a valid version?

Illustratively, if it is determined that the consent statement associated with the current statement configuration information exists, it is further determined whether an effective version exists in the consent statement.

If it is determined that the valid version exists in the consent statement associated with the statement configuration information, step 1907 is ended.

Illustratively, if the consent statement associated with the current statement configuration information has a valid version, the consent statement associated with the current statement configuration information can be configured into the application flow, the checking of the current statement configuration information is ended, and the checking of the consent statement associated with the next statement configuration information is continued.

And after checking all the declaration configuration information, ending the checking flow of the agreeable declaration of the current application flow.

Step 1908, if it is determined that the consent statement associated with the statement configuration information does not have a valid version, throwing an exception: the consent states that there is no validation version.

Schematically, if it is determined that the consent statement associated with the current statement configuration information does not have a valid version, displaying abnormal information on an application flow configuration interface corresponding to the tenant terminal, where the abnormal information may be: the consent states that there is no validation version.

Step 1907 ends.

Illustratively, the checking of the current claim configuration information is ended, and the checking of the consent claim associated with the next claim configuration information is continued.

Step 1909, if it is determined that the consent statement associated with the statement configuration information does not exist, throwing an exception: consent claims do not exist.

Schematically, if it is determined that the consent statement associated with the current statement configuration information does not exist, displaying abnormal information on an application flow configuration interface corresponding to the tenant terminal, where the abnormal information may be: consent claims do not exist.

Step 1907 ends.

Step 1910, if it is determined that the number of the declarative configuration information pieces is greater than 4, throwing an exception: the consent states that the content is at most 4 pieces configurable.

Schematically, if it is determined that the number of declaration configuration information added in the application flow is greater than 4, displaying abnormal information on an application flow configuration interface corresponding to the tenant terminal, where the abnormal information may be: the consent claims content can be configured up to 4 pieces to prompt the tenant that the number of consent claims currently configured exceeds the limit.

Step 1907 ends.

Illustratively, the checking flow of the consent claims for the current application flow is ended directly.

If the application flow is judged not to open the consent claim, step 1907 is ended.

Schematically, if it is determined that the current application flow does not open the consent claims, directly ending the checking flow of the consent claims of the current application flow.

Next, the usage flow of the consent claims by the application service user is introduced:

1) The application service user views the consent claims.

When the portal checks the specific content of the consent statement by clicking on the name of the consent statement, the application service user needs to perform different presentations according to the file type of the consent statement.

Referring to fig. 20, a flowchart for an application service user to view an agreement statement is shown, as shown in fig. 20, the flowchart comprising the steps of:

in step 2001, the user requests to view the consent claim content.

Illustratively, when the application service user clicks the name of the consent statement on the registration interface of the application, that is, requests to view the specific content of the consent statement, the application background sends the ID of the consent statement to the consent sound submodule 1631.

Step 2002, determining whether a consent claim ID exists?

Illustratively, after receiving the consent claim ID, consent claim submodule 1631 determines whether the consent claim associated with the consent claim ID exists, for example: whether the consent claim ID is an ID already existing in the consent claim list.

Step 2003, if it is determined that the consent claim ID exists, continuing to determine whether the consent claim has a valid version?

Illustratively, if it is determined that the consent statement associated with the consent statement ID exists, it is further determined whether an effective version exists in the consent statement.

If it is determined that the consent statement has an effective version, step 2004, continuing to determine whether the effective version is a URL link?

Illustratively, if there is an validated version of the consent claim associated with the consent claim ID, determining whether the declaration file type of the consent claim of the validated version is URL link?

In step 2005, if the validated version is not the URL link, the object storage address of the PDF is obtained.

Schematically, if the type of the declaration file of the consent declaration of the validation version is judged not to be the URL link, the object storage address of the PDF corresponding to the consent declaration of the validation version is obtained.

Step 2006, the request is proxied to the PDF object storage service address by the reverse proxy.

Illustratively, an application client to which an application service user logs in proxies a request to view consent claim content to a PDF object storage service address through a reverse proxy.

The working principle of the reverse proxy is that the proxy server receives the network access connection request of the client, then the server transmits the request to the service server which actually works in the network in a strategic way, and returns the result processed by the service server to the client which initiates the connection request on the network.

After the PDF object storage service address is obtained, the user logs in the corresponding terminal interface of the application service to jump to the PDF object storage service address, thereby displaying the specific content of the consent statement

Step 2007, end.

Illustratively, the current application service user ends the process of requesting to view the consent claim specific content.

If step 2008, it is determined that the validated version is a URL link, the request is redirected to the URL link address configured by the validated version.

Illustratively, if it is determined that the declaration file type of the consent declaration of the validation version is a URL link, the request is redirected to the URL link address of the consent declaration configuration of the validation version. That is, the user logs in the corresponding terminal interface of the application service and jumps to the URL link address, so that the specific content of the consent statement is displayed.

Step 2007, end.

Step 2009, if it is determined that the valid version does not exist in the consent statement, discarding the exception: the consent states that there is no validation version.

Schematically, if it is determined that the consent statement associated with the consent statement ID does not have a valid version, displaying abnormal information on an application registration interface of a terminal on which an application service user logs, where the abnormal information is: the consent states that there is no validation version.

Step 2007, end.

If it is determined that the consent claim ID does not exist, step 2010, an exception is thrown: consent claims do not exist.

Illustratively, if it is determined that the consent statement associated with the consent statement ID does not exist, displaying, on an application registration interface of the terminal on which the application service user logs, exception information, where the exception information is: consent claims do not exist.

Step 2007, end.

2) The application service user agrees to the declaration check.

The application service user submits the final consent result to the portal service back end through reading and confirming the consent statement displayed by the portal, and the portal service needs to check the consent condition submitted by the application service user.

Referring to fig. 21, a flowchart of the application service user consent check and consent record generation is shown, as shown in fig. 21, comprising the steps of:

step 2101, update user consent.

Illustratively, when the application service user submits an application flow (e.g., registration flow, login flow), the application background sends information to the generic module 1630 about the application service user ID, the specified consent claim ID, the specified version ID of the specified consent claim, and whether the application service user agrees.

Step 2102, determining if the user has passed the consent claim?

Illustratively, after receiving the information about the application service user ID, the specified consent claim ID, the specified version ID of the specified consent claim, and whether the application service user agrees, the universal module 1630 determines whether the application service user has passed the specified consent claim, that is, determines whether the application service user has passed the signing process corresponding to the specified consent claim through the consent record of the application service user.

If it is determined that the user has passed the consent claim, step 2103, continuing to determine whether the last version agreed by the user is greater than the current version?

Illustratively, if it is determined that the application service user passes the signing process corresponding to the specified consent claim, then it is continuously determined whether the version number of the version of the specified consent claim that the application service user last agrees is greater than the version number of the specified version of the current specified consent claim.

Step 2104, if it is determined that the last agreed version of the user is greater than the current version, discarding the exception: consent states that the versions do not match.

Schematically, if it is determined that the version number of the version of the specified consent claim that the application service user agrees last time is greater than the version number of the specified version of the current specified consent claim, displaying abnormal information on an application registration interface of the terminal that the application service user logs in, where the abnormal information is: consent states that the versions do not match.

Step 2105 ends.

Illustratively, the current checking flow for consent to the specified consent claim in the submitted application flow is ended.

If it is determined that the last version agreed by the user is not greater than the current version, step 2106 is continued to determine whether the last version agreed by the user is equal to the current version?

Illustratively, if it is determined that the version number of the version of the specified consent claim that was last agreed by the application service user is not greater than the version number of the specified version of the specified consent claim, continuing to determine whether the version number of the version of the specified consent claim that was last agreed by the application service user is equal to the version number of the specified version of the specified consent claim?

Step 2107, if it is determined that the last agreed version of the user is equal to the current version, adding an agreement record: the user agrees or does not sign a specified version of the specified agreement statement.

Illustratively, if it is determined that the version number of the version of the specified consent claim that the application service user last agrees is equal to the version number of the specified version of the specified consent claim, according to the above information about whether the application service user agrees (where the information may be agreeing or not agreeing), the application service user's corresponding consent record is newly added: the application service user agrees (i.e., signs) to the specified version of the specified consent claim; alternatively, the application service user does not authorize (i.e., does not sign) the specified version of the specified consent claim.

Step 2105 ends.

Step 2108, if it is determined that the last agreed version of the user is not equal to the current version, adding an agreement record: the user re-agrees or does not sign the specified version of the specified consent claim.

Illustratively, if it is determined that the version number of the version of the specified consent claim that the application service user last agrees is not equal to the version number of the specified version of the specified consent claim, according to the above information about whether the application service user agrees (where the information may be agreeing or not), the application service user's corresponding consent record is newly added: the application service user agrees (i.e., signs) to the specified version of the specified consent claim; alternatively, the application service user does not authorize (i.e., does not sign) the specified version of the specified consent claim.

Step 2105 ends.

Step 2109, if it is determined that the user fails the consent claim, adding a consent record: the user agrees or does not authorize to specify a specified version of the agreeing statement.

Illustratively, if it is determined that the application service user has not passed the signing process corresponding to the specified consent claim, according to the above information about whether the application service user agrees (wherein, the information may be agreeing or not agreeing), a new addition is made in the agreeing record corresponding to the application service user: the application service user agrees (i.e., signs) to the specified version of the specified consent claim; alternatively, the application service user does not authorize (i.e., does not sign) the specified version of the specified consent claim.

Step 2105 ends.

Finally, the management of application records is explained:

1) The status of the record is agreed.

The consent information submitted by the portal application service user generates consent records, and 5 kinds of consent records in different states exist in different scenes.

Consent (grant): the new application service user agrees to the validated version for the first time.

Delete (delete): the application service user is de-registered with the deletion/service plane application program interface (Application Programming Interface, API).

Update (Renewed): the application service user re-agrees after the version update.

Unsigned (NotGranted): the application service user does not sign an agreement statement on the first submission.

Withdrawal (widmdew): the service plane API removes login consent.

The service plane API deregisters and agrees to refer to that the application service user agrees to the protocol a during registration, and the application provides a management interface for the application service user, so that the application service user can delete the agreed protocol a during registration through the management interface.

Similarly, the service plane API revokes login consent means that the application service user agrees to the protocol B when logging in, and the application will provide a management interface for the application service user, so that the application service user can delete the agreed protocol B when logging in through the management interface.

Referring to fig. 22, a schematic diagram of a status update relationship of a consent record is shown, as shown in fig. 22:

(1) The first time the application service user submits, without signing the agreement, the consent record is in the "unsigned" state 2201, the application service user agrees to the validated version of the agreement for the first time, and the consent record is updated from the "unsigned" state 2201 to the "consent" state 2202.

(2) When the application service user de-registers the protocol through the API, then the consent record is updated from the "consent" state 2202 to the "revocation" state 2203. (3) After de-registering the protocol, the user is deleted, resulting in a deleted record, i.e., a consent record is updated from the "revoked" state 2203 to the "deleted" state 2204.

(4) When the application service user re-registers and signs the agreement, the consent record is updated from the "delete" state 2204 to the "consent" state 2202.

(5) When the application service user logs in again, agreeing to a new version of the agreement, then the agreement record is updated from an "agreement" state 2202 to an "updated" state 2205.

(6) If the application service user is deleted, the record is agreed to update from the "update" state 2205 to the "delete" state 2204.

(7) If the application service user de-registers the protocol through the API, the record is granted to be updated from the "update" state 2205 to the "withdraw" state 2203. (3) After de-registering the protocol, the user is deleted, resulting in a deleted record, i.e., a consent record is updated from the "revoked" state 2203 to the "deleted" state 2204.

(8) If the application service user withdraws the login protocol through the business plane API, the consent record is updated from the "consent" state 2202 to the "withdraw" state 2203.

(9) If the application service user is deleted, the consent record is updated from the "consent" state 2202 to the "delete" state 2204.

(10) When the application service user re-registers and does not sign the agreement, the consent record is updated from the "delete" state 2204 to the "unsigned" state 2201.

2) Agreeing to record the expired destruction.

Each consent claim is configured with a consent record retention time, and when an application service user operates an effective version of a consent claim to generate a consent record, the system calculates the expiration time of the record according to the consent claim configured retention time. When the expiration time is reached, the record is destroyed.

Referring to fig. 23, a flowchart of the method for agreeing to record expiration destruction is shown, and as shown in fig. 23, the method includes the following steps:

step 2301, timing tasks: performed at 0 point daily.

Schematically, a timer is set, the timer corresponds to a timing task, the timing task is to check whether the corresponding consent record of each account in the account wind control platform is expired, the timer is set to execute the timing task at 0 point per day, that is, check whether the record expiration time of the consent record is less than or equal to 0 point per day.

Step 2302, determine if task lock is obtained?

Because a plurality of accounts exist in the account wind control platform, each account needs to execute the timing task, and the situation that a single account executes the same timing task for a plurality of times is avoided by adopting a task lock mode.

Illustratively, when a task lock is acquired by an account, a timing task is executed, and when the task lock is not acquired, the timing task is not executed; the task lock may be implemented in a manner of Zookeeper, redis, which is not limited in the embodiment of the present application.

If it is determined that the task lock is obtained, a consent record with an expiration time less than or equal to the current time is queried 2303.

Schematically, if the current account is judged to obtain the task lock, all the consent records corresponding to the current account are obtained, and the record expiration time of each consent record is determined.

In step 2304, the consent record is deleted.

Illustratively, all consent records of the current account whose expiration time is less than or equal to 0 point of the day are traversed and deleted.

Step 2305, end.

Illustratively, the timed task for the account currently obtaining the task lock is ended, and the timed task for the next account obtaining the task lock is continued to be executed.

Step 2305, if it is determined that the task lock is not obtained, ending.

Schematically, if the current account does not acquire the task lock, the timing task is not executed.

Fig. 24 is a block diagram showing the structure of an information management apparatus according to an exemplary embodiment of the present application, and as shown in fig. 24, the apparatus includes:

the display module 2400 is configured to display a declaration management interface, where the declaration management interface is configured to manage an information protection declaration corresponding to an application on an application platform, where the information protection declaration is a protocol file to be agreed between an application service user and an application service provider, and the declaration management interface includes multiple candidate information protection declarations;

a receiving module 2410, configured to receive, for a first application program in the application platform, a flow configuration operation for at least one information protection claim among the plurality of candidate information protection claims, where the flow configuration operation is configured to configure the at least one information protection claim in an account verification flow corresponding to the first application program;

a configuration module 2420, configured to configure the signing process of the at least one information protection claim in the account verification process corresponding to the first application in response to the process configuration operation.

In some embodiments, referring to fig. 25, the receiving module 2410 is configured to:

responsive to receiving an opening operation on the first launch enable control, displaying a declaration configuration area, wherein the declaration configuration area is used for inputting a declaration identifier corresponding to a candidate information protection declaration to be configured;

and receiving a determining operation of a declaration identification corresponding to the at least one information protection declaration in the declaration configuration area, and taking the determining operation as the flow configuration operation.

In some embodiments, the apparatus further comprises:

a determining module 2430 is configured to configure a hyperlink corresponding to the declaration identifier corresponding to the at least one information protection declaration, based on a determining operation of the declaration identifier corresponding to the at least one information protection declaration in the declaration configuration area, where the hyperlink is used to display a declaration content of the at least one information protection declaration.

In some embodiments, the candidate information protection declaration includes declaration description information therein; the display module 2400 is configured to display a flow configuration interface of an account verification flow corresponding to the first application, where the flow configuration interface includes a first enabling control, and the first enabling control is configured to open a signing flow of an information protection statement in the account verification flow corresponding to the first application; the receiving module 2410 is configured to automatically configure a signing procedure of the at least one information protection claim in an account verification procedure corresponding to the first application program in response to receiving an opening operation on the first enabling control when the claim description information includes a program identifier of the first application program.

In some embodiments, the configuration module 2420 is configured to configure the signing procedure of the at least one information protection claim in the registration procedure in response to a procedure configuration operation for the registration procedure corresponding to the first application; or, the configuration module 2420 is configured to configure the signing process of the at least one information protection claim in the login process in response to a process configuration operation of the login process corresponding to the first application.

In some embodiments, the claim management interface includes a second start enabling control corresponding to the at least one information protection claim, where the second start enabling control is configured to start a signing process of the at least one information protection claim in an account verification process configured with the at least one information protection claim; the configuration module 2420 is configured to configure the signing process of the at least one information protection claim in the account verification process corresponding to the first application program in response to the process configuration operation when the second start enable control is in the on-enable state.

The statement management interface comprises a statement new control and a statement list, wherein the statement new control is used for newly adding the candidate information protection statement, and the statement list is used for displaying the candidate information protection statement; the receiving module 2410 is configured to:

Responding to the received triggering operation on the statement new control, and displaying a statement editing interface;

in response to receiving a new operation at the claim editing interface for a first candidate information protection claim, the first candidate information protection claim is displayed in the claim list.

In some embodiments, the claim list includes a version management control, where the version management control is configured to version manage the first candidate information protection claim; the display module 2400 is configured to display, in response to receiving a trigger operation on the version management control, a version management interface corresponding to the first candidate information protection statement, where the version management interface includes a version new control and a statement version list, the version new control is used to add the first candidate information protection statement of different versions, and the statement version list is used to display version information of the first candidate information protection statement; the receiving module 2410 is configured to receive a triggering operation on the version new control; the display module 2400 is configured to display, in the declaration version list, version information of a first candidate information protection declaration of a first version based on the triggering operation.

In some embodiments, the display module 2400 is configured to display a version editing interface in response to the triggering operation; the receiving module 2410 is configured to receive an editing operation on the first candidate information protection statement of the first version at the version editing interface, where the editing operation is used to edit the statement content of the first candidate information protection statement of the first version; the display module 2400 is configured to display, in the declaration version list, version information of a first candidate information protection declaration of the first version based on the editing operation.

In some embodiments, the display module 2400 is configured to display a statement record according to an account verification procedure initiated by a first account on the first application, where the statement record is configured to record a signing result of the first account on the at least one information protection statement.

In some embodiments, the display module 2400 is configured to:

displaying first identification information in the statement record, wherein the first identification information is used for indicating that the first account signs the at least one information protection statement;

or alternatively, the process may be performed,

displaying second identification information in the statement record, wherein the second identification information is used for indicating that the first account does not sign the at least one information protection statement;

Or alternatively, the process may be performed,

displaying third identification information in the statement record, wherein the third identification information is used for indicating that the first account signs the at least one information protection statement after version updating;

or alternatively, the process may be performed,

and displaying fourth identification information in the statement record, wherein the fourth identification information is used for indicating that the first account is deleted.

In summary, the information management device provided by the embodiment of the application performs unified management on the information protection statements corresponding to a plurality of applications on the application platform through the display statement management interface, so that the management efficiency of the information protection statements is improved; in addition, aiming at the appointed application program on the application platform, when the terminal receives the configuration operation of the appointed information protection statement, the signing flow of at least one information protection statement is configured in the account verification flow corresponding to the appointed application program, namely, different information protection statements are configured for each application program in the statement management interface, so that the method for configuring the information protection statement in a plurality of applications is realized more conveniently, and the configuration efficiency of the information protection statement is improved.

It should be noted that: the information management apparatus provided in the above embodiment is only exemplified by the division of the above functional modules, and in practical application, the above functional allocation may be performed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules, so as to perform all or part of the functions described above. In addition, the information management apparatus and the information management method embodiment provided in the foregoing embodiments belong to the same concept, and specific implementation processes thereof are detailed in the method embodiment and are not described herein again.

Fig. 26 shows a block diagram of a computer device 2600 provided by an exemplary embodiment of the present application. The computer device 2600 may be a portable mobile terminal such as: a smart phone, a tablet computer, an MP3 player (Moving Picture Experts Group Audio Layer III, motion picture expert compression standard audio plane 3), an MP4 (Moving Picture Experts Group Audio Layer IV, motion picture expert compression standard audio plane 4) player, a notebook computer, or a desktop computer. The computer device 2600 may also be referred to by other names as user devices, portable terminals, laptop terminals, desktop terminals, and the like.

Generally, the computer device 2600 includes: a processor 2601, and a memory 2602.

The processor 2601 may include one or more processing cores, such as a 4-core processor, an 8-core processor, or the like. The processor 2601 may be implemented in at least one hardware form of a DSP (Digital Signal Processing ), FPGA (Field-Programmable Gate Array, field programmable gate array), PLA (Programmable Logic Array ). The processor 2601 may also include a main processor and a coprocessor, wherein the main processor is a processor for processing data in an awake state, and is also called a CPU (Central Processing Unit ); a coprocessor is a low-power processor for processing data in a standby state. In some embodiments, the processor 2601 may be integrated with a GPU (Graphics Processing Unit, image processor) for taking care of rendering and drawing of content that the display screen needs to display. In some embodiments, the processor 2601 may also include an AI (Artificial Intelligence ) processor for processing computing operations related to machine learning.

The memory 2602 may include one or more computer-readable storage media, which may be non-transitory. Memory 2602 may also include high-speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium in memory 2602 is used to store at least one instruction for execution by processor 2601 to implement the information management methods provided by the method embodiments of the present application.

In some embodiments, computer device 2600 may optionally include other components, and those skilled in the art will appreciate that the structure illustrated in fig. 26 is not limiting of computer device 2600, and may include more or less components than illustrated, or may combine certain components, or employ a different arrangement of components.

Those of ordinary skill in the art will appreciate that all or part of the steps in the various methods of the above embodiments may be implemented by a program for instructing related hardware, and the program may be stored in a computer readable storage medium, which may be a computer readable storage medium included in the memory of the above embodiments; or may be a computer-readable storage medium, alone, that is not incorporated into the terminal. The computer readable storage medium has stored therein at least one instruction, at least one program, a set of codes, or a set of instructions, which are loaded and executed by the processor to implement the information management method of any of the above embodiments.

Alternatively, the computer-readable storage medium may include: read Only Memory (ROM), random access Memory (RAM, random Access Memory), solid state disk (SSD, solid State Drives), or optical disk, etc. The random access memory may include resistive random access memory (ReRAM, resistance Random Access Memory) and dynamic random access memory (DRAM, dynamic Random Access Memory), among others. The foregoing embodiment numbers of the present application are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.

It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program for instructing relevant hardware, where the program may be stored in a computer readable storage medium, and the storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.

The foregoing description of the preferred embodiments of the present application is not intended to limit the application, but rather, the application is to be construed as limited to the appended claims.

Claims

1. An information management method, the method comprising:

2. The method of claim 1, wherein the receiving, for a first application in the application platform, a flow configuration operation for at least one information protection claim among the plurality of candidate information protection claims comprises:

displaying a flow configuration interface of an account verification flow corresponding to the first application program, wherein the flow configuration interface comprises a first enabling control, and the first enabling control is used for starting a signing flow of an information protection statement in the account verification flow corresponding to the first application program;

In response to receiving an opening operation on the first enabling control, displaying a declaration configuration area, wherein the declaration configuration area is used for inputting a declaration identifier corresponding to a candidate information protection declaration to be configured;

3. The method according to claim 2, wherein the method further comprises:

and configuring a hyperlink corresponding to the declaration identifier corresponding to the at least one information protection declaration based on the determination operation of the declaration identifier corresponding to the at least one information protection declaration in the declaration configuration area, wherein the hyperlink is used for displaying the declaration content of the at least one information protection declaration.

4. The method of claim 1, wherein the candidate information protection declaration includes declaration description information;

the method further comprises the steps of:

And in response to receiving an opening operation on the first enabling control, automatically configuring a signing flow of the at least one information protection statement in an account verification flow corresponding to the first application program under the condition that the statement description information contains a program identifier of the first application program.

5. The method of claim 1, wherein configuring the signing process of the at least one information protection claim in the account verification process corresponding to the first application in response to the process configuration operation comprises:

in response to a flow configuration operation on a registration flow corresponding to the first application program, configuring a signing flow of the at least one information protection statement in the registration flow;

or alternatively, the process may be performed,

and in response to a flow configuration operation of a login flow corresponding to the first application program, configuring a signing flow of the at least one information protection statement in the login flow.

6. The method according to any one of claims 1 to 5, wherein the claim management interface includes a second enabling control corresponding to the at least one information protection claim, and the second enabling control is configured to open a signing procedure of the at least one information protection claim in an account verification procedure configured with the at least one information protection claim;

The step of configuring the signing process of the at least one information protection statement in the account verification process corresponding to the first application program in response to the process configuration operation includes:

and responding to the flow configuration operation, and under the condition that the second enabling control is in an enabling state, configuring the signing flow of the at least one information protection statement in the account verification flow corresponding to the first application program.

7. The method according to any one of claims 1 to 5, wherein the claim management interface includes a claim new control and a claim list, the claim new control is used for adding a candidate information protection claim, and the claim list is used for displaying the candidate information protection claim;

the method further includes, for a first application program in the application platform, before receiving a flow configuration operation for at least one information protection claim among the plurality of candidate information protection claims:

8. The method of claim 7, wherein the claim list includes a version management control, the version management control configured to version manage the first candidate information protection claim;

after the first candidate information protection statement is displayed in the statement list, the method further comprises:

responding to the triggering operation of the version management control, displaying a version management interface corresponding to the first candidate information protection statement, wherein the version management interface comprises a version new control and a statement version list, the version new control is used for adding the first candidate information protection statement of different versions, and the statement version list is used for displaying version information of the first candidate information protection statement;

receiving triggering operation on the version newly-built control;

and displaying the version information of the first candidate information protection statement of the first version in the statement version list based on the triggering operation.

9. The method of claim 8, wherein the displaying version information of the first candidate information protection declaration of the first version in the declaration version list based on the triggering operation includes:

Responding to the triggering operation, and displaying a version editing interface;

receiving an editing operation of the first candidate information protection statement of the first version on the version editing interface, wherein the editing operation is used for editing the statement content of the first candidate information protection statement of the first version;

and displaying the version information of the first candidate information protection statement of the first version in the statement version list based on the editing operation.

10. The method according to any one of claims 1 to 5, wherein after configuring the signing process of the at least one information protection claim in the account verification process corresponding to the first application in response to the process configuration operation, further comprising:

and displaying a statement record according to an account verification process initiated by the first account on the first application program, wherein the statement record is used for recording the signing result of the first account on the at least one information protection statement.

11. The method of claim 10, wherein displaying the declaration record includes:

Or alternatively, the process may be performed,

or alternatively, the process may be performed,

12. An information management apparatus, characterized in that the apparatus comprises:

13. A computer device, characterized in that it comprises a processor and a memory, in which at least one section of a computer program is stored, which is loaded and executed by the processor to implement the information management method according to any of claims 1 to 11.

14. A computer readable storage medium, characterized in that at least one section of a computer program is stored in the computer readable storage medium, which is loaded and executed by a processor to implement the information management method according to any one of claims 1 to 11.

15. A computer program product comprising a computer program which, when executed by a processor, implements the information management method according to any one of claims 1 to 11.