Registration equipment abnormity identification method and device and nonvolatile storage medium

Abstract

The invention discloses a registration equipment abnormity identification method and device and a nonvolatile storage medium. The method comprises the following steps: receiving a number taking request sent based on target equipment; determining a registration request corresponding to a number in the number taking request based on the number taking request; based on the registration request, determining registration equipment corresponding to the registration request; judging whether the target equipment is matched with the registration equipment or not; and under the condition that the target equipment is not matched with the registration equipment, processing the number taking request and updating the number of times that the registration equipment is abnormal stored in the block chain. According to the invention, the technical problem that the registration experience of a common user is affected because malicious registration equipment cannot be effectively identified in a traditional registration system is solved.

Description

Technical Field

[0001] The present invention relates to the field of information technology, and in particular to a registration equipment abnormality recognition method, device and non-volatile storage medium. Background Art

[0002] In the traditional hospital registration process, users need to register an account on the hospital platform, enter their own identity information (ID number, phone number) or biometric information (face recognition), etc., and then register. If the user cancels the registration, the remaining number will be returned to the registration pool and can be selected by others.

[0003] In the above traditional methods, in order to ensure that the user who registers and the user who takes the number are the same, although personal information and biometric information have been used for user identification verification, illegal profiteers can still bypass login verification by asking users for verification codes, ID information or videos, and complete the number grabbing operation. The current hospital registration system cannot effectively distinguish between patients and illegal profiteers. Illegal profiteers use plug-in software such as number-brushing scripts to maliciously grab numbers, causing ordinary patients to be unable to register, while illegal profiteers hoard a large number of hospital numbers, which leads to the deterioration of doctor-patient relations and even medical disputes. Under the existing technology, hospitals cannot effectively distinguish and trace these malicious number grabbers, and cannot accurately crack down on illegal activities.

[0004] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0005] The embodiments of the present invention provide a method, device and non-volatile storage medium for identifying abnormal registration equipment, so as to at least solve the technical problem that malicious registration equipment cannot be effectively identified in the traditional registration system, thus affecting the registration experience of ordinary users.

[0006] According to one aspect of an embodiment of the present invention, a method for identifying abnormalities in a registration device is provided, including: receiving a number-taking request issued by a target device; determining, based on the number-taking request, a registration request corresponding to the number in the number-taking request; determining, based on the registration request, a registration device corresponding to the registration request; judging whether the target device matches the registration device; if the target device does not match the registration device, processing the number-taking request and updating the number of abnormalities in the registration device stored in the blockchain.

[0007] Optionally, determining whether the target device matches the registered device includes: reading device information corresponding to the target device and the registered device, wherein the device information is stored in the blockchain, including an Ethernet address and a serial number of the corresponding device; when the device information of the target device is the same as the device information of the registered device, determining that the target device matches the registered device.

[0008] Optionally, when the device information of the target device is different from the device information of the registered device, the binding information corresponding to the target device is read from the blockchain, wherein the binding information includes the device bound to the target device; it is determined whether the registered device is located in the binding information of the target device; when the registered device is not located in the binding information of the target device, it is determined that the target device and the registered device do not match.

[0009] Optionally, when the registration device is located in the binding information of the target device, it is determined that the target device matches the registration device, and the number acquisition request is processed.

[0010] Optionally, before determining whether the target device matches the registered device, it also includes: reading historical geographic location information of the registered device within a preset historical time period from the blockchain, wherein the historical geographic location information represents the geographical location of the registered device within the preset historical time period; based on the historical geographic location information, recording the number of occurrences in which the position change distance of the registered device exceeds a preset distance threshold within the preset historical time period; based on the number of occurrences, updating the number of abnormalities of the registered device stored in the blockchain.

[0011] Optionally, a registration request for a registration device is received; based on the registration request, the number of times the registration device has an abnormality is read from the blockchain; when the number of times the registration device has an abnormality exceeds a preset threshold, the registration device is determined to be an abnormal device and the registration request is rejected.

[0012] Optionally, when the number of abnormalities in the registration device does not exceed a preset threshold, the registration device is determined to be a normal device; based on the time when the registration request is received, the queue order of the registration device is determined; based on the queue order, the registration information of the registration device is generated.

[0013] According to another aspect of an embodiment of the present invention, a registration device abnormality identification device is also provided, including: a receiving module for receiving a number-taking request issued based on a target device; a first determination module for determining, based on the number-taking request, a registration request corresponding to the number in the number-taking request; a second determination module for determining, based on the registration request, a registration device corresponding to the registration request; a judgment module for judging whether the target device matches the registration device; and an update module for processing the number-taking request and updating the number of abnormalities of the registration device stored in the blockchain when the target device does not match the registration device.

[0014] According to another aspect of an embodiment of the present invention, a non-volatile storage medium is provided, the non-volatile storage medium including a stored program, wherein when the program is running, the device where the non-volatile storage medium is located is controlled to execute any one of the above-mentioned registration device abnormality identification methods.

[0015] According to another aspect of an embodiment of the present invention, a computer device is provided. The computer device includes a processor, and the processor is used to run a program. When the program is run, any one of the above-mentioned registration device abnormality identification methods is executed.

[0016] In an embodiment of the present invention, a registration device abnormality identification method is adopted, by receiving a number-taking request issued by a target device; based on the number-taking request, determining the registration request corresponding to the number in the number-taking request; based on the registration request, determining the registration device corresponding to the registration request; judging whether the target device and the registration device match; in the case that the target device and the registration device do not match, processing the number-taking request and updating the number of abnormalities of the registration device stored in the blockchain, thereby achieving the purpose of effectively identifying and tracing devices with malicious registration behaviors, thereby realizing the technical effect of timely tracing and banning illegal registration devices and improving the normal user experience, thereby solving the technical problem that malicious registration devices cannot be effectively identified in traditional registration systems, affecting the registration experience of ordinary users. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0018] Figure 1 A hardware structure block diagram of a computer terminal for implementing a registration device abnormality identification method is shown;

[0019] Figure 2 It is a flowchart of a registration device abnormality identification method provided according to an embodiment of the present invention;

[0020] Figure 3 is a schematic diagram of a registration system based on blockchain technology provided according to an optional embodiment of the present invention;

[0021] Figure 4 It is a structural block diagram of a registration equipment abnormality identification device provided according to an embodiment of the present invention. DETAILED DESCRIPTION

[0022] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0023] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0024] According to an embodiment of the present invention, an embodiment of a method for identifying abnormalities in a registration device is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0025] The method embodiment provided in the first embodiment of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 1 The hardware structure block diagram of a computer terminal for implementing the registration device abnormality identification method is shown. Figure 1 As shown, the computer terminal 10 may include one or more (102a, 102b, ..., 102n are used to illustrate) processors (the processor may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera. It can be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations are shown.

[0026] It should be noted that the one or more processors and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the computer terminal 10. As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0027] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the registration device abnormality identification method in the embodiment of the present invention. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, the registration device abnormality identification method of the above-mentioned application program is realized. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include a memory remotely arranged relative to the processor, and these remote memories may be connected to the computer terminal 10 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0028] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 10 .

[0029] Figure 2 FIG. 1 is a flow chart of a method for identifying abnormalities of a registration device according to an embodiment of the present invention. Figure 2 As shown, the method comprises the following steps:

[0030] Step S201, receiving a number acquisition request issued by a target device.

[0031] In this step, the target device can perform the number-taking operation at the hospital site and issue a number-taking request. For example, the operation can be performed on the hospital number-taking device terminal, and the QR code obtained on the user side when registering can be scanned on the APP or mini program. If the verification is passed, the number can be successfully taken and the subsequent medical treatment process can be carried out.

[0032] Step S202: based on the number taking request, determine the registration request corresponding to the number in the number taking request.

[0033] In this step, the number in the number-taking request can be a QR code obtained by the user end when the registration is successful, wherein the information in the QR code may include the local number, user information, device mac address, IMEI number, that is, device information and user information. The user information in the corresponding registration request and the number-taking request is the same, therefore, according to the user information in the QR code, the registration request corresponding to the number-taking request can be queried in the corresponding blockchain.

[0034] Step S203: Based on the registration request, determine the registration device corresponding to the registration request.

[0035] In this step, one registration request corresponds to one registration device. When the registration device issues a registration request, the user end can save the device information of the registration device that issues the request and the user information uploaded by the user himself in the blockchain of the corresponding hospital system. Therefore, based on the user information corresponding to the registration request, the corresponding registration device and the device information of the registration device can be traced back in the blockchain.

[0036] Step S204, determining whether the target device matches the registration device.

[0037] In this step, after the target device sends a number-taking request, the number-taking terminal system can obtain the device information of the target device, and read the device information of the corresponding registration device in the blockchain, and determine whether the two match based on the device information of the two. Among them, the match can be that the device information is exactly the same, that is, the number-taking device and the registration device are the same device; or the device information of the number-taking device and the registration device are different, but the two are bound to each other, and the two are also matching devices.

[0038] Step S205: When the target device does not match the registration device, the number-taking request is processed and the number of abnormalities of the registration device stored in the blockchain is updated.

[0039] In this step, when the target device does not match the registration device, the screen of the number-taking terminal device can prompt that the number-taking device is inconsistent with the registration device. According to the data stored on the blockchain, the device information of the registration device is obtained, and the number of abnormalities of the registration device is updated and stored in the blockchain. Specifically, an early warning list can be set in the blockchain, and the number of abnormalities when the device is used as a registration device is recorded as a gray value. The increase in the number of abnormalities is an increase in the gray value. The early warning list records the device information of all devices that have had abnormalities, as well as the number of abnormal behaviors corresponding to each device. When the registration device does not match the number-taking device, the registration device will be included in the early warning list, and the gray value will increase by one for each mismatch. In addition, regardless of whether the target device matches the registration device, this number-taking request will be processed, and the user can proceed with the subsequent medical treatment process normally. The abnormality of the registration device only affects whether the registration is successful.

[0040] Through the above steps, the purpose of effectively identifying and tracing devices with malicious registration behaviors is achieved, thereby achieving the technical effect of timely tracing and banning illegal registration devices and improving the normal user experience, thereby solving the technical problem that malicious registration devices cannot be effectively identified in traditional registration systems, affecting the registration experience of ordinary users.

[0041] As an optional embodiment, determining whether the target device matches the registered device includes: reading device information corresponding to the target device and the registered device, wherein the device information is stored in the blockchain, including the Ethernet address and serial number of the corresponding device; when the device information of the target device is the same as the device information of the registered device, determining that the target device matches the registered device.

[0042] Optionally, the device information is stored in the corresponding blockchain. The device information may include the MAC (Media Access Control) address of the device and the IMEI (International Mobile Equipment Identity) code of the mobile device. By comparing the device information of the target device and the device information of the registered device, it can be determined whether the target device and the registered device are the same device. In the case where the device information of the two devices is exactly the same, it can be determined that the two devices are the same device, and then it is determined that the target device matches the registered device, and there is no abnormal registration behavior. Among them, the MAC address is also called the Ethernet address or physical address. It is an address used to confirm the location of the network device. The MAC address is used to uniquely identify a network card in the network. The IMEI code is the International Mobile Equipment Identity code, which is commonly referred to as the mobile phone serial number or the mobile phone "serial number". It is used to identify each independent mobile phone and other mobile communication devices in the mobile phone network, which is equivalent to the ID card of the mobile phone. Therefore, through the above two device information, it can be identified whether the target device and the registered device are the same device. There is no need to judge the user through personal information, verification code, biometric information, etc. Instead, through system logic judgment, it is effectively identified whether the registered device has malicious number grabbing behavior.

[0043] As an optional embodiment, when the device information of the target device is different from the device information of the registered device, the binding information corresponding to the target device is read from the blockchain, wherein the binding information includes the device bound to the target device; it is determined whether the registered device is located in the binding information of the target device; when the registered device is not located in the binding information of the target device, it is determined that the target device and the registered device do not match.

[0044] Optionally, when the device information of the target device is different from the device information of the registration device, it is determined that the two devices are different devices, and it is further determined whether the two are bound mutually trusted authorized devices. Binding mutually trusted authorized devices means that the devices are bound to other devices as mutually trusted devices by scanning QR codes. The two bound devices can register and take numbers for each other without being judged as abnormal because of the different devices. Each device can be bound to two devices as mutually trusted authorized devices, and can also be flexibly set in the system. The number of changes can also be limited, such as limiting the opportunity to change twice within a year, to prevent illegal profit-making personnel from using multiple changes to commit violations. For example, when the registration device and the number-taking device are not the same device and the registration device and the number-taking device are not bound as mutually trusted devices, when the number-taking operation is performed, the registration device will be added to the warning list or the gray value will be increased.

[0045] As an optional embodiment, when the registration device is located in the binding information of the target device, it is determined that the target device matches the registration device, and the number acquisition request is processed.

[0046] Optionally, when the registration device is located in the binding information of the target device, the two devices are determined to be bound mutually trusted devices and can register and obtain numbers for each other. Therefore, the number obtaining request of the target device is processed normally and the number of abnormal behaviors of the registration device does not increase.

[0047] As an optional embodiment, before determining whether the target device matches the registered device, it also includes: reading the historical geographic location information of the registered device within a preset historical time period from the blockchain, wherein the historical geographic location information represents the geographical location of the registered device within the preset historical time period; based on the historical geographic location information, recording the number of occurrences in which the position change distance of the registered device exceeds a preset distance threshold within the preset historical time period; based on the number of occurrences, updating the number of abnormalities of the registered device stored in the blockchain.

[0048] Optionally, the historical geographic location information of the device is the IP address change information of the device within a preset historical time period. In order to seize a large number of hospital registrations, illegal profiteers usually use multiple IP addresses to disguise their user identities. Therefore, it is possible to determine whether the registration device is a malicious registration device used by illegal profiteers by detecting the IP address changes of the registration device. Specifically, when it is detected that the location of the registration device changes frequently and significantly in a short period of time, the registration device will be added to the warning list or the gray value will be increased. For example, if the IP address of the registration device changes across provinces within an hour, it can be considered that the device has abnormal behavior and is added to the warning list or the gray value in the warning list is increased.

[0049] As an optional embodiment, a registration request for a registration device is received; based on the registration request, the number of times the registration device has abnormalities is read from the blockchain; when the number of times the registration device has abnormalities exceeds a preset threshold, the registration device is determined to be an abnormal device and the registration request is rejected.

[0050] Optionally, before the user issues a registration request, the following steps are performed on the user side: obtain the device information and geographic location information of the registration device, and upload the device information and geographic location information of the registration device and the information submitted by the user to the blockchain along with the interface. After the platform system receives the user's registration request, it reads the above information and the preset threshold from the blockchain, traces back to the number of times the registration device has abnormalities in the historical time, and when the number of abnormalities exceeds the preset threshold, determines that the registration device is an abnormal device and rejects the registration request. For example, when there are abnormal times, that is, the gray value exceeds the preset threshold, the registration device can be moved from the warning list to the prohibited list, and the devices in the prohibited list are prohibited from performing registration operations. The time for entering the prohibited list and being banned can be flexibly configured. For example, the first time entering the banned list, the registration ban lasts for 1 month, and the ban is lifted after 1 month. The second time entering the banned list, the registration ban lasts for 6 months, and the ban is lifted after 6 months. The third time entering the banned list, the device is permanently banned and can no longer be registered in the system. In addition, you can also set an upper limit on the number of registrations for a single device on the same day. For example, limit each device to 3 registrations per day. Cancelling and changing numbers can restore the available registration times. When it is detected that the number of registrations for a device exceeds the threshold, the device will be temporarily locked and unable to perform registration operations. If there are special circumstances, you can apply for an additional registration opportunity by submitting objection feedback.

[0051] As an optional embodiment, when the number of abnormalities in the registration device does not exceed a preset threshold, the registration device is determined to be a normal device; based on the time when the registration request is received, the queue order of the registration device is determined; based on the queue order, the registration information of the registration device is generated.

[0052] Optionally, if the number of abnormalities in the registration device does not exceed the preset threshold, the registration device is determined to be a normal device and registration can be performed normally. Due to the different orders in which users send requests, based on the principle of first come first served, the remaining number is preferentially allocated to the device that sends the registration request first, and the information uploaded by the user and the device information are uploaded to the corresponding blockchain. In addition, if the hospital does not have any remaining numbers, it can display "No remaining numbers" on the user end, and the user needs to wait.

[0053] As an optional embodiment, a normal registration process for a user is provided. Specifically, user A needs to register, opens the mobile phone APP, fills in the real personal information, and selects the corresponding hospital to register. The APP prompts to obtain location information, IMEI code, MAC address and other information; after the registration is successful, a QR code for number collection is generated in the APP, and the number collection is scanned at the hospital terminal with this QR code; user A presents the QR code at the hospital number collection terminal to obtain the number, and the number collection is successful.

[0054] As an optional embodiment, a process is provided in which an illegal profiteer maliciously registers and is banned. Specifically, illegal profiteer A uses the equipment and plug-in software in his hands to maliciously grab numbers, and sells the grabbed numbers at a higher price for illegal profiteers; illegal profiteer A uses device A to grab numbers, and at this time the threshold of the early warning list of the blockchain registration system is 2; illegal profiteer A successfully grabs the number for user B, and user B successfully obtains the number, and device A of illegal profiteer A enters the early warning list with a gray value of 1; illegal profiteer A successfully grabs the number for user C, and user C successfully obtains the number, and the gray value of device A of illegal profiteer A is 2 after +1, reaching the threshold of the early warning list and entering the banned list; illegal profiteer A grabs the number for user D, and because device A enters the banned list, it is prompted that "the device is included in the banned list, and the registration ban lasts for 1 month", and the registration operation cannot be performed.

[0055] As an optional embodiment, a process is provided in which a user and a relative are bound to each other as a mutually trusted device and successfully register for an appointment. Specifically, user A and user B are relatives, user A registers for an appointment, and user B needs to use it; user A uses an APP to scan user B's client, and the two parties are bound as mutually trusted authorized devices; each device can be bound to two mutually trusted authorized devices, and the binding relationship cannot be changed within 6 months; user A successfully registers for an appointment, and user B successfully obtains a number at the hospital terminal.

[0056] As an optional embodiment, the present invention also provides a registration system based on blockchain technology. Figure 3 Schematic diagram of a registration system based on blockchain technology provided according to an optional embodiment of the present invention. Figure 3 As shown, the system includes: a client, a system platform, and a hospital number-taking terminal.

[0057] The client (APP) includes the following functions: registration function, that is, registering at designated hospitals and departments. When registering, the MAC address, IMEI code, geographic location information and other information in the mobile phone will be read; QR code display function, that is, providing a QR code of the registered number. The QR code content includes the hospital registration number, the registrant's identity information, the mobile phone's MAC address, IMEI code, geographic location information, etc.; information chain and acquisition function, uploading registration information, equipment information, etc. to the blockchain to ensure that the information is traceable and cannot be tampered with; obtaining information from the chain to ensure the uniqueness of the information channel and the accuracy of the information; binding mutual trust authorized device function, which can bind with other clients (APPs) as mutual trust devices by scanning QR codes.

[0058] The system platform (system backend) includes the following functions: setting the warning list and prohibited list thresholds for registered devices; detecting whether the registered device is on the prohibited list; detecting whether the geographic location information changes frequently and significantly; uploading the updated threshold information to the chain to ensure that the threshold is not arbitrarily tampered with; obtaining the latest prohibited list and threshold information on the chain; and allocating remaining numbers to verified devices.

[0059] The hospital number-taking device terminal includes the following functions: determining whether the registration and number-taking devices are mutually trusted devices; obtaining the number information from the chain and comparing it with the information in the client (APP); obtaining the latest warning list and prohibited list on the chain; updating the warning list and prohibited list information and uploading them to the chain; increasing the grayscale value of the device in the warning list; and printing hospital registration certificates.

[0060] Through the above-mentioned registration system based on blockchain technology, the registration equipment can be effectively traced. When abnormal behaviors such as malicious registration grabbing are detected in the registration equipment, the illegal equipment can be traced and banned in time, which greatly increases the illegal cost of ticket scalpers, accurately prevents the registration speculation, and effectively curbs the phenomenon of doctors adding or reserving numbers without permission, safeguarding the legitimate rights and interests of patients and promoting fairness in medical treatment.

[0061] It should be noted that, for the above-mentioned method embodiments, for the sake of simplicity, they are all described as a series of action combinations, but those skilled in the art should know that the present invention is not limited by the described action sequence, because according to the present invention, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present invention.

[0062] Through the description of the above implementation methods, those skilled in the art can clearly understand that the registration device abnormality identification method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present invention.

[0063] According to an embodiment of the present invention, there is also provided a device for identifying abnormalities of a registration device for implementing the above-mentioned method for identifying abnormalities of a registration device. Figure 4 is a structural block diagram of a registration device abnormality identification device provided according to an embodiment of the present invention, such as Figure 4As shown, the registration equipment abnormality identification device includes: a receiving module 41, a first determination module 42, a second determination module 43, a judgment module 44 and an update module 45. The registration equipment abnormality identification device is described below.

[0064] The receiving module 41 is used to receive a number acquisition request sent by a target device.

[0065] The first determining module 42 is connected to the receiving module 41, and is used to determine a registration request corresponding to the number in the number taking request based on the number taking request.

[0066] The second determining module 43 is connected to the first determining module 42, and is used to determine the registration device corresponding to the registration request based on the registration request.

[0067] The judging module 44 is connected to the second determining module 43 and is used to judge whether the target device matches the registration device.

[0068] The updating module 45 is connected to the judging module 44, and is used to process the number taking request and update the number of abnormalities of the registration device stored in the blockchain when the target device does not match the registration device.

[0069] It should be noted that the receiving module 41, the first determining module 42, the second determining module 43, the judging module 44 and the updating module 45 correspond to steps S201 to S205 in the embodiment, and the examples and application scenarios implemented by the multiple modules and the corresponding steps are the same, but are not limited to the contents disclosed in the above embodiment. It should be noted that the above modules, as part of the device, can be run in the computer terminal 10 provided in the embodiment.

[0070] An embodiment of the present invention may provide a computer device. Optionally, in this embodiment, the computer device may be located in at least one network device among multiple network devices of a computer network. The computer device includes a memory and a processor.

[0071] Among them, the memory can be used to store software programs and modules, such as the program instructions / modules corresponding to the registration device abnormality identification method and device in the embodiment of the present invention. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory, that is, the above-mentioned registration device abnormality identification method is realized. The memory may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include a memory remotely arranged relative to the processor, and these remote memories can be connected to the computer terminal via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0072] The processor can call the information and application stored in the memory through the transmission device to perform the following steps: receive a number-taking request based on the target device; determine the registration request corresponding to the number in the number-taking request based on the number-taking request; determine the registration device corresponding to the registration request based on the registration request; determine whether the target device matches the registration device; if the target device does not match the registration device, process the number-taking request and update the number of abnormalities of the registration device stored in the blockchain.

[0073] By adopting the embodiment of the present invention, a registration device abnormality identification method is provided. By receiving a number-taking request issued by a target device; determining a registration request corresponding to the number in the number-taking request based on the number-taking request; determining a registration device corresponding to the registration request based on the registration request; judging whether the target device matches the registration device; in the case where the target device does not match the registration device, processing the number-taking request and updating the number of abnormalities of the registration device stored in the blockchain, the purpose of effectively identifying and tracing devices with malicious registration behaviors is achieved, thereby achieving the technical effect of timely tracing and banning illegal registration devices and improving the normal user experience, thereby solving the technical problem that malicious registration devices cannot be effectively identified in the traditional registration system, affecting the registration experience of ordinary users.

[0074] A person of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing the hardware related to the terminal device through a program, and the program can be stored in a non-volatile storage medium, and the storage medium may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0075] The embodiment of the present invention further provides a non-volatile storage medium. Optionally, in this embodiment, the non-volatile storage medium can be used to store the program code executed by the registration device abnormality identification method provided in the above embodiment.

[0076] Optionally, in this embodiment, the non-volatile storage medium may be located in any computer terminal in a computer terminal group in a computer network, or in any mobile terminal in a mobile terminal group.

[0077] An optional embodiment of the present invention further provides a computer program product, including a computer program. Optionally, in this embodiment, when the computer program is executed by a processor, the program code executed by the registration device abnormality identification method provided in the above embodiment can be implemented.

[0078] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0079] In the above embodiments of the present invention, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0080] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0081] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0082] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0083] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a non-volatile storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes.

[0084] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A registration equipment abnormality identification method, characterized in that: include: Receiving a number acquisition request based on a target device; Based on the number taking request, determining a registration request corresponding to the number in the number taking request; Based on the registration request, determining a registration device corresponding to the registration request; Determining whether the target device matches the registration device; In the case where the target device does not match the registration device, the number-taking request is processed and the number of abnormalities of the registration device stored in the blockchain is updated.

2. The method according to claim 1, characterized in that: The determining whether the target device matches the registration device includes: Reading device information corresponding to the target device and the registered device, wherein the device information is stored in the blockchain and includes an Ethernet address and a serial number of the corresponding device; In the case where the device information of the target device is the same as the device information of the registered device, it is determined that the target device matches the registered device.

3. The method according to claim 2, characterized in that Also includes: When the device information of the target device is different from the device information of the registered device, reading the binding information corresponding to the target device from the blockchain, wherein the binding information includes the device bound to the target device; Determine whether the registered device is located in the binding information of the target device; In the case that the registered device is not located in the binding information of the target device, it is determined that the target device does not match the registered device.

4. The method according to claim 3, characterized in that Also includes: In the case that the registration device is located in the binding information of the target device, it is determined that the target device matches the registration device, and the number acquisition request is processed.

5. The method according to claim 1, characterized in that Before determining whether the target device matches the registration device, the method further includes: Reading historical geographic location information of the registration device within a preset historical period from the blockchain, wherein the historical geographic location information represents the geographical location of the registration device within the preset historical period; Based on the historical geographic location information, record the number of occurrences of the situation where the location change distance of the registration device exceeds the preset distance threshold within the preset historical time period; Based on the number of occurrences, the number of abnormalities of the registration device stored in the blockchain is updated.

6. The method according to any one of claims 1 to 5, characterized in that: Also includes: receiving a registration request from the registration device; Based on the registration request, read the number of times the registration device is abnormal from the blockchain; When the number of abnormalities of the registration device exceeds a preset threshold, the registration device is determined to be an abnormal device and the registration request is rejected.

7. The method according to claim 6, characterized in that Also includes: When the number of abnormalities of the registration device does not exceed a preset threshold, determining that the registration device is a normal device; Determining a queue order of the registration devices based on the time when the registration request is received; Based on the queuing order, the registration information of the registration device is generated.

8. A registration equipment abnormality identification device, characterized in that: include: A receiving module, used for receiving a number acquisition request issued by a target device; A first determining module, configured to determine, based on the number taking request, a registration request corresponding to the number in the number taking request; A second determination module is used to determine the registration device corresponding to the registration request based on the registration request; A judgment module, used to judge whether the target device matches the registration device; An update module is used to process the number-taking request and update the number of abnormalities of the registration device stored in the blockchain when the target device does not match the registration device.

9. A non-volatile storage medium, characterized in that: The non-volatile storage medium includes a stored program, wherein when the program is running, the device where the non-volatile storage medium is located is controlled to execute the registration device abnormality identification method described in any one of claims 1 to 7.

10. A computer device, characterized in that: include: Memory and processor, The memory stores a computer program; The processor is used to execute the computer program stored in the memory, and when the computer program is running, the processor executes the registration device abnormality identification method described in any one of claims 1 to 7.

Images