CN117034262B - Abnormality supervision system and abnormality supervision method - Google Patents

Abstract

This specification discloses an abnormality supervision system and an abnormality supervision method. The abnormality supervision system includes: user supervision chain, certification verification chain, and manager supervision chain. Among them, the user supervision chain includes each user node, the certification verification chain includes each verification node, and the manager supervision chain includes each manager node. The user supervision chain can receive abnormal events submitted by any user node and transmit the abnormal events to the certification The verification chain is used to verify abnormal events through verification nodes and obtain verification results. Based on the verification results, it manages the violation records and user points corresponding to each user node, and can receive points management requests sent by the manager's chain of custody. And manage the user points corresponding to each user node according to the received points management request.

Description

An abnormality supervision system and abnormality supervision method

Technical field

This manual relates to the field of blockchain technology, and in particular to an abnormality supervision system and abnormality supervision method.

Background technique

With the development of business platforms provided by various Internet service providers, more and more users have begun to use the services provided by each business platform for production and life. As the number of users of each business platform increases, users' various Types of violations are also increasing, which brings great difficulties to the user environment management of the business platform.

Therefore, how to effectively supervise users' abnormal behavior in the business platform is an urgent problem that needs to be solved.

Contents of the invention

This specification provides an abnormality supervision system and an abnormality supervision method to partially solve the above problems existing in the existing technology.

This manual adopts the following technical solutions:

This specification provides an abnormal supervision system. The abnormal supervision system includes: a user supervision chain, a certification verification chain, and a manager supervision chain. The user supervision chain includes each user node, and the certification verification chain includes each user node. Verification node, the manager chain of custody includes each manager node;

The user supervision chain is used to receive abnormal events submitted by any user node, and transmit the abnormal events to the certification verification chain, so as to verify the abnormal events through the verification nodes and obtain verification results. According to the Verify the results and manage the violation records and user points corresponding to each user node; and

Used to receive the first point recovery request sent by the abnormal user, and manage the user points corresponding to each user node according to the point recovery certification information contained in the first point recovery request;

The proof verification chain is used to receive abnormal events transmitted by the user supervision chain, verify the abnormal events through the verification node, obtain verification results and return them to the user supervision chain;

The manager chain of custody is used to respond to the second point recovery request sent by the abnormal user through the manager node, determine the target violation record, and determine whether to restore all points based on the certification information contained in the second point recovery request. The user points of the user node corresponding to the abnormal user, if so, generate points recovery certificate information and return it to the device used by the abnormal user.

Optionally, the user supervision chain is used to transmit the relevant material data of the abnormal event to the database through the user node for storage;

The proof verification chain is used to obtain the relevant material data from the database through the verification node to verify the abnormal event based on the relevant material data.

Optionally, the user supervision chain is used to perform designated management operations on the digital identity data of each user node included in the user supervision chain. The designated management operations include: authentication operations, creation operations, update operations, and destruction operations. , query operation.

Optionally, the proof verification chain is used to verify the abnormal event according to a preset smart contract to obtain the verification result. The smart contract is a pre-established user points change standard corresponding to different types of abnormal events. and pre-established verification standards corresponding to different types of abnormal events;

The user supervision chain is used to manage the violation records and user points corresponding to each user node based on the verification results and the preset smart contract.

Optionally, the manager chain is used to obtain the violation records saved in the user supervision chain, determine the violation category corresponding to the violation record, and determine whether the violation category is a specified category. If so, start from the default Determine a penalty plan that matches the violation category corresponding to the violation record, and punish the user node corresponding to the violation record according to the penalty plan.

This specification provides an abnormal supervision method, which is applied to an abnormal supervision system. The abnormal supervision system includes: a user supervision chain, a certification verification chain, and a manager supervision chain, wherein the user supervision chain includes Each user node, the certification verification chain includes each verification node, the manager custody chain includes each manager node, and the method includes:

Receive abnormal events submitted by any user node through the user supervision link;

Transmit the abnormal event to the proof verification chain to verify the abnormal event through the verification node to obtain the verification result, and manage the violation records and user points corresponding to each user node according to the verification result. ;as well as

Receive the first points recovery request sent by the abnormal user, and manage the user points corresponding to each user node according to the points recovery certification information contained in the first points recovery request, and the points recovery certification information is the manager's The chain of custody responds to the second point recovery request sent by the abnormal user through the manager node, determines the target violation record, and determines the user node corresponding to the abnormal user to be restored based on the certification information contained in the second point recovery request. User points are returned to the device used by the abnormal user.

Optionally, transmit the abnormal event to the proof verification chain to verify the abnormal event through the verification node. Before obtaining the verification result, the method further includes:

Transmit the relevant material data of the abnormal event to the database for storage through the user node of the user supervision chain;

Transmit the abnormal event to the proof verification chain to verify the abnormal event through the verification node, specifically including:

The abnormal event is transmitted to the proof verification chain, so that the verification node obtains the relevant material data from the database and verifies the abnormal event according to the relevant material data.

Optionally, the method also includes:

Perform specified management operations on the digital identity data of each user node included in the user supervision chain through the user supervision chain. The specified management operations include: authentication operations, creation operations, update operations, destruction operations, and query operations.

Optionally, the abnormal event is verified through the verification node to obtain verification results, which specifically include:

Through the proof verification chain, the abnormal event is verified according to the preset smart contract to obtain the verification result. The smart contract is the pre-made user points change standards corresponding to different types of abnormal events and the pre-made rules for Verification standards corresponding to different types of abnormal events;

According to the verification results, the violation records and user points corresponding to each user node are managed, specifically including:

According to the verification results and the preset smart contract, the violation records and user points corresponding to each user node are managed.

Optionally, the method also includes:

Obtain the violation records saved in the user supervision chain through the manager chain, determine the violation category corresponding to the violation record, and determine whether the violation category is a designated category;

If so, a penalty plan matching the violation category corresponding to the violation record is determined from the preset penalty plan, and the user node corresponding to the violation record is punished according to the penalty plan.

This specification provides a computer-readable storage medium. The storage medium stores a computer program. When the computer program is executed by a processor, the above-mentioned abnormality monitoring method is implemented.

This specification provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, the above-mentioned abnormality monitoring method is implemented.

At least one of the above technical solutions adopted in this manual can achieve the following beneficial effects:

In the abnormality supervision method provided in this manual, the abnormal events submitted by any user node are first received through the user supervision chain, and the abnormal events are transmitted to the proof verification chain to verify the abnormal events through the verification nodes to obtain the verification results, and based on Verify the results, manage the violation records and user points corresponding to each user node, receive the first point recovery request sent by the abnormal user, and verify the points corresponding to each user node based on the points recovery certification information contained in the first point recovery request. User points are managed. The point recovery certification information here is the manager's chain of custody responding to the second point recovery request sent by the abnormal user through the manager node, determining the target violation record, and determining recovery based on the certification information contained in the second point recovery request. The user points of the user node corresponding to the abnormal user are returned to the device used by the abnormal user.

It can be seen from the above method that the user environment can be supervised through an abnormality supervision system composed of three parallel chains. Among them, users can submit abnormal events for other users’ abnormal behaviors through user nodes in the user supervision chain, and After passing the proof verification chain verification, the user points of the user nodes corresponding to the abnormal users can be deducted and corresponding penalties can be imposed, thereby effectively supervising the abnormal behavior of users in the business platform.

Description of the drawings

The drawings described here are used to provide a further understanding of this specification and constitute a part of this specification. The illustrative embodiments and descriptions of this specification are used to explain this specification and do not constitute an improper limitation of this specification. In the attached picture:

Figure 1 is a schematic diagram of the abnormality monitoring system provided in this manual;

Figure 2 is a schematic diagram of the use process of the abnormality monitoring system provided in this manual;

Figure 3 is a schematic flow chart of an abnormality monitoring method provided in this specification;

Figure 4 is a schematic diagram of an abnormality monitoring device provided in this specification;

FIG. 5 is a schematic diagram of an electronic device corresponding to FIG. 4 provided in this specification.

Detailed ways

In order to make the purpose, technical solutions and advantages of this specification more clear, the technical solutions of this specification will be clearly and completely described below in conjunction with specific embodiments of this specification and the corresponding drawings. Obviously, the described embodiments are only some of the embodiments of this specification, but not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the scope of protection of this specification.

The technical solutions provided by each embodiment of this specification will be described in detail below with reference to the accompanying drawings.

With the development of Internet technology, various types of network chaos have emerged one after another, causing great damage to the user environment of each business platform, thereby reducing the user experience. Therefore, how each business platform can supervise the user environment becomes apparent. Particularly important.

Based on this, this specification provides an abnormality monitoring system, as shown in Figure 1.

Figure 1 is a schematic diagram of the abnormality monitoring system provided in this specification.

It can be seen from Figure 1 that the above-mentioned abnormal supervision system includes: user supervision chain, certification verification chain, and manager supervision chain. Among them, the user supervision chain, the certification verification chain, and the manager supervision chain are three parallel chains. The user supervision here The chain can be used as a relay chain among the three blockchains (that is, the chain used for cross-chain information transmission and cross-chain task execution).

It should be noted that the above-mentioned user supervision chain can be managed using the public chain consensus mechanism NPoS (Nominated Proof of Stake), including each user node. The user nodes here can be created and used by different users of the business platform after digital identity authentication. The above-mentioned proof verification chain can be managed using the consensus-generated block Aura (Authority-based round-robin scheduling) mechanism, including each verification node. The verification nodes here can be created and used by relevant verification agencies after digital identity authentication. The above-mentioned manager chain of custody can be managed using Aura or alliance chain mechanisms, including each manager node. The manager nodes here can be created and used by relevant government departments, business platform-related departments, etc. after digital identity authentication. .

Specifically, if a user discovers violations of other users while using the business platform to perform business, they can collect relevant material data and submit corresponding abnormal events through the user node in the user supervision chain, and report The relevant material data is transferred to the database and saved, where the above-mentioned relevant material data can be data such as photos, videos, recordings, etc., as shown in Figure 2.

Figure 2 is a schematic diagram of the use process of the abnormality monitoring system provided in this manual.

As can be seen from Figure 2, the user supervision chain can be used to receive abnormal events submitted by any user node, and transmit the abnormal events to the proof verification chain, so that the abnormal events can be verified through the verification nodes, and the verification results can be obtained based on The verification results and the preset smart contract manage the violation records and user points corresponding to each user node. The smart contract here can provide pre-made user point change standards for different types of abnormal events and pre-made rules for Verification standards corresponding to different types of abnormal events.

It is proved that after receiving the abnormal event transmitted by the user supervision chain, the verification chain can obtain the relevant material data of the received abnormal event from the database through the verification node to verify the abnormal event based on the relevant material data. The abnormal event can be verified and verified. The results are returned to the user chain of supervision.

Among them, the evidence verification chain can verify the abnormal event by transmitting the relevant material data of the received abnormal event to the device used by the abnormal user corresponding to the abnormal event, so as to verify the authenticity of the abnormal user who is the subject of the violation. Verification: Verify the format of the material data related to the received abnormal event according to the preset smart contract, verify the authenticity of the material data related to the received abnormal event through the preset neural network model, and store the received abnormal event The relevant material data is transmitted to the designated equipment used by the staff to manually verify the authenticity of the received abnormal event-related material data.

The abnormal user corresponding to the above abnormal event refers to the user who is the subject of the reported violation, that is, the user who committed the violation and was submitted to the corresponding abnormal event by other users.

Of course, users can also upload relevant material data to the database through the device they are using, obtain the hash value of the storage location of the relevant material data returned by the database, and send a verification request to the certification verification chain, so that the certification verification chain can pass the verification. The node responds to the verification request and obtains the relevant material data from the database based on the hash value of the storage location of the relevant material data carried in the verification request. After verifying the relevant material data, the node returns the signature data.

Further, users can submit abnormal events to the user supervision chain through user nodes, so that after the user supervision chain determines that there is signature data proving the verification chain in the abnormal event, it can calculate the user points of the abnormal user corresponding to the abnormal event based on the signature data. manage.

In actual application scenarios, there are some abnormal users whose abnormal behavior is more serious, such as causing serious damage to the property of other users. Based on this, the manager chain can obtain the violation records saved in the user supervision chain and determine the corresponding records of the violation. Violation category, and determine whether the violation category is the specified category. If so, determine the penalty plan that matches the violation category corresponding to the violation record from the preset penalty plan, and remove and deduct the user node corresponding to the violation record according to the penalty plan. As for additional penalties in addition to points, the penalty options here can include fines, rectification, and restrictions on at least some of the permissions of abnormal users in the business platform, etc.

When an abnormal user needs to restore points after completing the corresponding punishment, or when a violation appeal is needed to restore points, the user can send a second point restoration request to the manager's chain of custody through the device used, so that the manager's chain of custody passes the management The user node responds to the second point recovery request sent by the abnormal user, determines the target violation record, and determines whether to restore the user points of the user node corresponding to the abnormal user based on the certification information contained in the second point recovery request. If so, generates a points recovery certificate. Information is returned to the device used by the abnormal user.

After the abnormal user obtains the points recovery certificate information returned by the manager node in the manager's chain of custody, the abnormal user can send a first points recovery request to the user's chain of custody through the user node used by the abnormal user. The user supervision chain can receive the first point management request sent by the abnormal user, and after verifying the certification information contained in the first point management request, can manage the user points corresponding to each user node.

Among them, if the abnormal user has completed the corresponding punishment, the submitted certification information can be the certification materials for completing the punishment, such as: fine payment records, proof of rectification completion, etc. It should be noted that the above-mentioned abnormal users can complete the corresponding punishment by going to the designated location to complete the corresponding punishment offline, or they can complete the corresponding punishment online.

If an abnormal user needs to appeal against a violation, the certification information submitted by the user can be used as proof to prove that there is no violation.

In addition, the user supervision chain can also be used to perform designated management operations on the digital identity data of each user node included in the user supervision chain. The designated management operations include: authentication operations, creation operations, update operations, destruction operations, and query operations. .

As can be seen from the above content, the abnormality supervision system can supervise the user environment through three parallel chains. Among them, users can submit abnormal events targeting other users’ abnormal behaviors through user nodes in the user supervision chain, and can After verification through the proof verification chain, the user points of the user node corresponding to the abnormal user can be deducted and punished accordingly, thereby effectively supervising the abnormal behavior of users in the business platform.

Figure 3 is a schematic flow chart of an abnormality monitoring method provided in this manual, including the following steps:

S301: Receive abnormal events submitted by any user node through the user supervision link.

S302: Transmit the abnormal event to the proof verification chain to verify the abnormal event through the verification node to obtain the verification result, and according to the verification result, the violation record and user points corresponding to each user node are To manage.

S303: Receive the first points recovery request sent by the abnormal user, and manage the user points corresponding to each user node according to the points recovery certification information contained in the first points recovery request, where the points recovery certification information is the The manager's chain of custody responds to the second point recovery request sent by the abnormal user through the manager node, determines the target violation record, and determines to restore the corresponding points of the abnormal user based on the certification information contained in the second point recovery request. The user points of the user node are returned to the device used by the abnormal user.

In this specification, the business platform can receive abnormal events submitted by any user node through the user supervision chain, and transmit the abnormal events to the certification verification chain to verify the abnormal events through the verification nodes, obtain the verification results, and verify according to the verification As a result, the violation records and user points corresponding to each user node are managed, and the first point recovery request sent by the abnormal user is received, and each user node is processed according to the point recovery certification information contained in the first point recovery request. The corresponding user points are managed. The point recovery certification information here is the manager's chain of custody responding to the second point recovery request sent by the abnormal user through the manager node to determine the target violation record. According to the certification information contained in the second point recovery request, When it is determined to restore the user points of the user node corresponding to the abnormal user, they will be returned to the device used by the abnormal user.

Specifically, the business platform can transmit the relevant material data of abnormal events to the database for storage through the user node of the user supervision chain, and transmit the abnormal events to the proof verification chain, so that the verification node obtains relevant material data from the database and based on Relevant material data is used to verify abnormal events.

In addition, the business platform can also perform designated management operations on the digital identity data of each user node included in the user supervision chain through the user supervision chain. The designated management operations here include: authentication operations, creation operations, update operations, and destruction operations. , query operation.

Furthermore, the business platform can verify abnormal events through the proof verification chain according to the preset smart contract, and obtain the verification results. Based on the verification results and the preset smart contract, the violation records and user points corresponding to each user node can be verified. manage. The smart contracts here are pre-established user points change standards for different types of abnormal events and pre-established verification standards for different types of abnormal events.

In addition, the business platform can also obtain the violation records saved in the user supervision chain through the manager chain, determine the violation category corresponding to the violation record, and determine whether the violation category is the specified category. If so, it will be determined from the preset penalty plan. Determine a penalty plan that matches the violation category corresponding to the violation record, and punish the user node corresponding to the violation record according to the penalty plan.

It can be seen from the above method that the user environment can be supervised through an abnormality supervision system composed of three parallel chains. Among them, users can submit abnormal events for other users’ abnormal behaviors through user nodes in the user supervision chain, and After passing the proof verification chain verification, the user points of the user nodes corresponding to the abnormal users can be deducted and corresponding penalties can be imposed, thereby effectively supervising the abnormal behavior of users in the business platform.

The above is one or more implementation model deployment methods in this specification. Based on the same idea, this specification also provides a corresponding abnormality monitoring device, as shown in Figure 4.

Figure 4 is a schematic diagram of an abnormality monitoring device provided in this manual, including:

The acquisition module 401 is used to receive abnormal events submitted by any user node through the user supervision link;

The verification module 402 is used to transmit the abnormal event to the certification verification chain, so as to verify the abnormal event through the verification node, obtain the verification result, and according to the verification result, determine the violation corresponding to each user node. Records and user points management; and

The recovery module 403 is configured to receive the first points recovery request sent by the abnormal user, and manage the user points corresponding to each user node according to the points recovery certificate information contained in the first points recovery request, and the points recovery certificate The information is that the manager chain of custody responds to the second point recovery request sent by the abnormal user through the manager node, determines the target violation record, and determines to restore the said point violation record based on the certification information contained in the second point recovery request. When the user points of the user node corresponding to the abnormal user are returned to the device used by the abnormal user.

Optionally, the verification module 402 is specifically configured to transmit the relevant material data of the abnormal event to the database for storage through the user node of the user supervision chain; transmit the abnormal event to the certification verification chain, So that the verification node obtains the relevant material data from the database, and verifies the abnormal event according to the relevant material data.

Optionally, the verification module 402 is specifically configured to perform specified management operations on the digital identity data of each user node included in the user supervision chain through the user supervision chain. The specified management operations include: authentication operations, Create operations, update operations, destroy operations, and query operations.

Optionally, the verification module 402 is specifically configured to verify the abnormal event through the proof verification chain according to a preset smart contract to obtain verification results. The smart contract is pre-made for different types of User points change standards corresponding to abnormal events and pre-established verification standards corresponding to different types of abnormal events; based on the verification results and preset smart contracts, the violation records and user points corresponding to each user node are managed.

Optionally, the recovery module 403 is specifically configured to obtain the violation records saved in the user supervision chain through the manager chain, determine the violation category corresponding to the violation record, and determine whether the violation category is specified. Category; if yes, determine a penalty plan that matches the violation category corresponding to the violation record from the preset penalty plan, and punish the user node corresponding to the violation record according to the penalty plan.

This specification also provides a computer-readable storage medium that stores a computer program. The computer program can be used to execute an abnormality monitoring method provided in Figure 4 above.

This specification also provides a schematic structural diagram of the electronic device shown in FIG. 5 corresponding to FIG. 4 . As shown in Figure 5, at the hardware level, the electronic device includes a processor, internal bus, network interface, memory and non-volatile memory, and of course may also include other hardware required for business. The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it to implement the exception monitoring method described in Figure 1 above. Of course, in addition to software implementation, this specification does not exclude other implementation methods, such as logic devices or a combination of software and hardware, etc. That is to say, the execution subject of the following processing flow is not limited to each logical unit, and may also be hardware or logic device.

Improvements in a technology can be clearly distinguished as hardware improvements (for example, improvements in circuit structures such as diodes, transistors, switches, etc.) or software improvements (improvements in method processes). However, with the development of technology, many improvements in today's method processes can be regarded as direct improvements in hardware circuit structures. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement of a method flow cannot be implemented using hardware entity modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic functions are determined by the user programming the device. Designers can program themselves to "integrate" a digital system on a PLD, instead of asking chip manufacturers to design and produce dedicated integrated circuit chips. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented using "logic compiler" software, which is similar to the software compiler used in program development and writing. Before compiling, The original code must also be written in a specific programming language, which is called Hardware Description Language (HDL). There is not only one type of HDL, but many types, such as ABEL (AdvancedBoolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (JavaHardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby HardwareDescription Language), etc. The most commonly used one at present is VHDL ( Very-High-Speed IntegratedCircuit Hardware Description Language) and Verilog. Those skilled in the art should also know that by simply logically programming the method flow using the above-mentioned hardware description languages and programming it into the integrated circuit, the hardware circuit that implements the logical method flow can be easily obtained.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (eg, software or firmware) executable by the (micro)processor. , logic gates, switches, Application Specific Integrated Circuit (ASIC), programmable logic controllers and embedded microcontrollers. Examples of controllers include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20 and Silicone Labs C8051F320, the memory controller can also be implemented as part of the memory control logic. Those skilled in the art also know that in addition to implementing the controller in the form of pure computer-readable program code, the controller can be completely programmed with logic gates, switches, application-specific integrated circuits, programmable logic controllers and embedded logic by logically programming the method steps. Microcontroller, etc. to achieve the same function. Therefore, this controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be considered as structures within the hardware component. Or even, the means for implementing various functions can be considered as structures within hardware components as well as software modules implementing the methods.

The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or A combination of any of these devices.

For the convenience of description, when describing the above device, the functions are divided into various units and described separately. Of course, when implementing this specification, the functions of each unit can be implemented in the same or multiple software and/or hardware.

Those skilled in the art will understand that embodiments of the present specification may be provided as methods, systems, or computer program products. Thus, the present description may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment that combines software and hardware aspects. Furthermore, the present description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

This specification is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the specification. It will be understood that each process and/or block in the flowchart illustrations and/or block diagrams, and combinations of processes and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine, such that the instructions executed by the processor of the computer or other programmable data processing device produce a use A device for realizing the functions specified in a process or processes in a flowchart and/or a block or blocks in a block diagram.

These computer program instructions may also be stored in a computer-readable memory that causes a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction means, the instructions The device implements the functions specified in a process or processes in the flowchart and/or in a block or blocks in the block diagram.

These computer program instructions may also be loaded onto a computer or other programmable data processing device, causing a series of operating steps to be performed on the computer or other programmable device to produce computer-implemented processing, thereby executing on the computer or other programmable device. Instructions provide steps for implementing the functions specified in a process or processes of a flowchart diagram and/or a block or blocks of a block diagram.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

Memory may include non-permanent storage in computer-readable media, random access memory (RAM), and/or non-volatile memory in the form of read-only memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.

Computer-readable media includes both persistent and non-volatile, removable and non-removable media that can be implemented by any method or technology for storage of information. Information may be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), and read-only memory. (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, Magnetic tape cassettes, tape magnetic disk storage or other magnetic storage devices or any other non-transmission medium can be used to store information that can be accessed by a computing device. As defined in this article, computer-readable media does not include transitory media, such as modulated data signals and carrier waves.

It should also be noted that the terms "comprises," "comprises," or any other variation thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements not only includes those elements, but also includes Other elements are not expressly listed or are inherent to the process, method, article or equipment. Without further limitation, an element defined by the statement "comprises a..." does not exclude the presence of additional identical elements in a process, method, article, or device that includes the stated element.

Those skilled in the art will appreciate that embodiments of the present specification may be provided as methods, systems, or computer program products. Thus, the present description may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment that combines software and hardware aspects. Furthermore, the present description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

This specification may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present description may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through communications networks. In a distributed computing environment, program modules may be located in both local and remote computer storage media including storage devices.

Each embodiment in this specification is described in a progressive manner. The same and similar parts between the various embodiments can be referred to each other. Each embodiment focuses on its differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple. For relevant details, please refer to the partial description of the method embodiment.

The above descriptions are only examples of this specification and are not intended to limit this specification. Various modifications and changes may occur to this description to those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of this specification shall be included in the scope of the claims of this specification.

Claims (7)

1. An exception supervision system, the exception supervision system comprising: the system comprises a user supervision chain, a proof verification chain and a manager supervision chain, wherein the user supervision chain comprises all user nodes, the proof verification chain comprises all verification nodes, the manager supervision chain comprises all manager nodes, the user supervision chain, the proof verification chain and the manager supervision chain are three parallel chains, the user supervision chain, the proof verification chain and the manager supervision chain are managed by adopting different management mechanisms, and the user supervision chain is used as a relay chain in three block chains;

the user supervision chain is used for receiving an abnormal event submitted by any user node, transmitting the abnormal event to the verification chain, verifying the abnormal event through the verification node to obtain a verification result, and managing the violation record and the user score corresponding to each user node according to the verification result, wherein the user supervision chain transmits the related material data of the abnormal event to the database through the user node for storage; and

the system comprises a first point recovery request, a second point recovery request and a user node, wherein the first point recovery request is used for receiving abnormal users and managing user points corresponding to each user node according to point recovery proving information contained in the first point recovery request;

The verification chain is used for receiving abnormal events transmitted by the user supervision chain, verifying the abnormal events through the verification node, obtaining verification results and returning the verification results to the user supervision chain, wherein the verification chain obtains the related material data from the database through the verification node so as to verify the abnormal events according to the related material data;

the manager chain of custody is used for responding to a second point recovery request sent by the abnormal user through the manager node, determining a target violation record, determining whether to recover the user point of the user node corresponding to the abnormal user according to the proving information contained in the second point recovery request, if yes, generating point recovery proving information, and returning the point recovery proving information to equipment used by the abnormal user, wherein the proving information is the proving material which is uploaded after the user finishes corresponding punishment and is finished or the proving material which is not in violation; and

and the method is used for acquiring the violation records stored in the user supervision chain, determining the violation categories corresponding to the violation records, judging whether the violation categories are specified categories, if so, determining a punishment scheme matched with the violation categories corresponding to the violation records from preset punishment schemes, and punishment is carried out on the user nodes corresponding to the violation records according to the punishment scheme.

2. The system of claim 1, wherein the user supervision chain is configured to perform a specified management operation on digital identity data of each user node included in the user supervision chain, the specified management operation comprising: authentication operation, creation operation, update operation, destruction operation, and inquiry operation.

3. The system of claim 1, wherein the certification verification chain is configured to verify the abnormal event according to a preset intelligent contract to obtain a verification result, where the intelligent contract is about a preset user point change standard corresponding to the abnormal event of different types and a preset verification standard corresponding to the abnormal event of different types;

and the user supervision chain is used for managing the violation records and the user scores corresponding to each user node according to the verification result and the preset intelligent contract.

4. An anomaly supervision method, wherein the anomaly supervision method is applied to an anomaly supervision system, the anomaly supervision system comprising: the user supervision chain, the proof verification chain and the manager supervision chain are three parallel chains, the user supervision chain, the proof verification chain and the manager supervision chain are managed by different management mechanisms, and the user supervision chain is used as a relay chain in three block chains, and the method comprises the following steps:

Receiving an abnormal event submitted by any user node through the user supervision chain;

transmitting related material data of the abnormal event to a database through the user node of the user supervision chain for storage, transmitting the abnormal event to a verification chain for verification through the verification node to obtain a verification result, and managing violation records and user points corresponding to each user node according to the verification result, wherein the abnormal event is transmitted to the verification chain for verification, so that the verification node acquires the related material data from the database, and verifies the abnormal event according to the related material data; and

and receiving a first point recovery request sent by an abnormal user, and managing the user points corresponding to each user node according to point recovery proving information contained in the first point recovery request, wherein the point recovery proving information is obtained by the manager chain of custody through the second point recovery request sent by the abnormal user, a target violation record is determined, when the user points of the user node corresponding to the abnormal user are recovered according to proving information contained in the second point recovery request, the report is returned to equipment used by the abnormal user, the proving information is proving materials which are uploaded after the user completes corresponding punishment and are subjected to punishment or proving materials which are not subjected to punishment, the punishment is obtained by the manager node, the punishment record stored in the user chain of custody is determined, a punishment scheme corresponding to the punishment record is determined from a preset punishment scheme, and the punishment scheme corresponding to the punishment scheme is determined according to the punishment scheme.

5. The method of claim 4, wherein the method further comprises:

performing specified management operation on digital identity data of each user node contained in the user supervision chain through the user supervision chain, wherein the specified management operation comprises the following steps: authentication operation, creation operation, update operation, destruction operation, and inquiry operation.

6. The method of claim 4, wherein the verifying the abnormal event by the verification node obtains a verification result, specifically comprising:

verifying the abnormal event through the proving verification chain according to a preset intelligent contract to obtain a verification result, wherein the intelligent contract is about a preset user integral change standard corresponding to different types of abnormal events and a preset verification standard corresponding to different types of abnormal events;

and managing the violation records and the user scores corresponding to each user node according to the verification result, wherein the method specifically comprises the following steps:

and managing the violation records and the user points corresponding to each user node according to the verification result and the preset intelligent contract.

7. The method of claim 4, wherein the method further comprises:

Obtaining a violation record stored in the user supervision chain through the manager chain, determining a violation category corresponding to the violation record, and judging whether the violation category is a specified category or not;

if yes, determining a punishment scheme matched with the punishment category corresponding to the punishment record from preset punishment schemes, and punishment is carried out on the user node corresponding to the punishment record according to the punishment scheme.