ERP (Enterprise Resource Planning) system anomaly monitoring method, system, equipment, medium and program product

Abstract

The invention relates to an ERP system abnormity monitoring method, system and device, a medium and a program product, and belongs to the field of application interface security, and the method comprises the steps that an Internet of Things device obtains a first electronic code of a control device through an ERP system Internet of Things device management interface, and obtains a control device registry according to the first electronic code and the number of the control device; the control equipment obtains a second electronic code of the Internet of Things equipment through the ERP interface, and obtains an Internet of Things equipment registry according to the second electronic code and the serial number of the Internet of Things equipment; and the control equipment sends a control connection request to the Internet of Things equipment through the ERP interface according to the Internet of Things equipment registry, and the Internet of Things equipment carries out security authentication on the control connection request through the ERP interface according to the control equipment registry and returns an ERP system monitoring report. According to the method, the security risk of the ERP system can be found or avoided, and the security of the ERP system based on the Internet of Things equipment management interface can be improved.

Description

Technical Field

[0001] This application relates to the field of application interface security technology, and in particular to an ERP system anomaly monitoring method, system, device, medium and program product. Background Technology

[0002] With the iteration of storage computing technology, the upgrading of enterprise needs, and the evolution of industry ecosystems, ERP (Enterprise Resource Planning) systems have evolved beyond the traditional, integrated, and localized general-purpose ERP systems to include industry-specific, cloud-based vertical industry ERPs. Traditional general-purpose ERPs have a large number of basic interfaces, prioritizing cross-industry compatibility in their interface design. They provide cross-industry universal protocols, and to maintain cross-industry compatibility, they may include a large number of redundant interfaces. For example, SAP PI / PO supports 200+ standard connectors, but industry compatibility is low, and many interfaces require secondary development. Vertical industry ERPs, on the other hand, prioritize deep integration with industry scenarios in their interface design. To meet the data exchange needs of specific industries, they pre-configure industry-standard protocol interfaces, eliminating interfaces irrelevant to specific customer industries and focusing on high-frequency industry interaction protocols, thus "refining" the number of interfaces. For example, Meta ERP pre-configures port RFID interfaces to replace 10 general-purpose sensor adapters, resulting in high industry compatibility and fewer interfaces requiring secondary development.

[0003] Currently, mainstream ERP systems include general-purpose ERP and industry-specific ERP. Industry-specific ERP systems have fewer interfaces than general-purpose ERP systems; however, due to the functional positioning of ERP software, they still require a greater number of interfaces to handle various functions related to basic enterprise operations, such as IoT device management, inventory management, order management, and supply chain management. In IoT device management, with the continuous development of IoT technology, the scope and number of IoT smart devices are constantly expanding. On the one hand, IoT provides greater convenience for controlling smart devices; on the other hand, the risk of intrusion and manipulation of IoT-connected smart devices is higher, potentially triggering security incidents in the ERP system through the IoT device management interface. Therefore, a method for monitoring ERP system anomalies based on IoT device interfaces is needed to detect or prevent ERP system security risks early. Summary of the Invention

[0004] To address the aforementioned issues, this application provides an ERP system anomaly monitoring method, system, device, media, and program product.

[0005] Firstly, this application provides an ERP system anomaly monitoring method, applied to the IoT device management interface of the ERP system, including: The IoT device obtains the first electronic code of the control device through the IoT device management interface of the ERP system. The IoT device registers the control device according to the first electronic code and the control device number to obtain the control device registry. The control device obtains the second electronic code of the IoT device through the IoT device management interface of the ERP system. The control device registers the IoT device according to the second electronic code and the number of the IoT device to obtain the IoT device registry. The control device sends a control connection request to the IoT device through the IoT device management interface of the ERP system, based on the IoT device registry; the IoT device performs security authentication on the control connection request through the IoT device management interface of the ERP system, based on the control device registry, and returns an ERP system monitoring report.

[0006] Specifically, the ERP system anomaly monitoring method further includes: A first electronic tag is set for the control device, and the first electronic code is specifically the first electronic code of the first electronic tag of the control device; a second electronic tag is set for the Internet of Things device, and the second electronic code is specifically the second electronic code of the second electronic tag of the Internet of Things device.

[0007] Specifically, the ERP system anomaly monitoring method further includes: The control device is equipped with a first positioning module and a first time synchronization module. The first electronic code is determined based on the location code of the first positioning module and the time code of the first time synchronization module. The IoT device is equipped with a second positioning module and a second time synchronization module. The second electronic code is determined based on the location code of the second positioning module and the time code of the second time synchronization module. The first time synchronization module and the second time synchronization module are used to acquire the IoT time and synchronize the time of the control device and the IoT device respectively.

[0008] Specifically, the IoT device registers the control device based on the first electronic code and the control device's serial number, obtaining a control device registry, including: The registration code of the control device is determined based on the first electronic code and the serial number of the control device; Obtain the controllable connection period of the IoT device; The control device is registered based on its registration code and the controllable connection period of the IoT device, resulting in a control device registry.

[0009] Specifically, the control device registers the IoT device based on the second electronic code and the IoT device's serial number, obtaining an IoT device registry, including: The registration code of the Internet of Things (IoT) device is determined based on the second electronic code and the IoT device's serial number; Obtain the controllable connection period of the IoT device; Based on the registration code of the control device and the controllable connection period of the IoT device, the IoT device is registered to obtain the IoT device registry.

[0010] Specifically, the control device sends a control connection request to the IoT device through the IoT device management interface of the ERP system, based on the IoT device registry, including: The control device obtains the control target through the IoT device management interface of the ERP system and searches for the IoT device corresponding to the control target in the IoT device registry. If the IoT device corresponding to the control target exists in the IoT device registry, the controllable connection period of the IoT device is obtained through the IoT device management interface of the ERP system according to the IoT device registry. During the controllable connection period of the IoT device, the control device sends a control connection request to the IoT device through the IoT device management interface of the ERP system.

[0011] Specifically, the IoT device, based on the control device registry, performs security authentication on the control connection request through the IoT device management interface of the ERP system and returns an ERP system monitoring report, including: In response to the control connection request, the IoT device obtains the control source through the IoT device management interface of the ERP system and searches for the corresponding control device in the control device registry. If the control device corresponding to the control source exists in the control device registry, the IoT device obtains the controllable connection period of the IoT device through the IoT device management interface of the ERP system based on the control device registry. During the controllable connection period of the IoT device, the control connection request is authenticated and a normal report of the IoT device management interface of the ERP system is sent to the ERP system. If the control device corresponding to the control source does not exist in the control device registry, or the control connection request is not within the controllable connection period of the IoT device, the IoT device rejects the control connection request and sends an abnormal alarm of the IoT device management interface of the ERP system to the ERP system.

[0012] Secondly, this application provides an ERP system anomaly monitoring system, applied to the IoT device management interface of the ERP system, including: The control device registration module is configured such that the Internet of Things (IoT) device obtains the first electronic code of the control device through the IoT device management interface of the ERP system, and the IoT device registers the control device according to the first electronic code and the control device number to obtain the control device registry. The IoT device registration module is configured such that the control device obtains the second electronic code of the IoT device through the IoT device management interface of the ERP system, and the control device registers the IoT device according to the second electronic code and the number of the IoT device to obtain the IoT device registry. The control connection security authentication module is configured such that the control device sends a control connection request to the IoT device through the IoT device management interface of the ERP system based on the IoT device registry; the IoT device performs security authentication on the control connection request through the IoT device management interface of the ERP system based on the control device registry and returns an ERP system monitoring report.

[0013] Thirdly, this application provides an ERP system anomaly monitoring method, applied to Internet of Things (IoT) devices, including: The IoT device obtains the first electronic code of the control device through the IoT device management interface of the ERP system. The IoT device registers the control device according to the first electronic code and the control device number to obtain the control device registry. In response to the control connection request from the control device, the IoT device performs security authentication on the control connection request through the IoT device management interface of the ERP system based on the control device registry and returns an ERP system monitoring report.

[0014] Fourthly, this application provides an Internet of Things (IoT) device, which is used for: The first electronic code of the control device is obtained through the IoT device management interface of the ERP system. The control device is registered according to the first electronic code and the number of the control device to obtain the control device registry. In response to the control connection request from the control device, the system performs security authentication on the control connection request through the IoT device management interface of the ERP system based on the control device registry and returns an ERP system monitoring report.

[0015] Fifthly, this application provides an ERP system anomaly monitoring method, applied to control equipment, comprising: The control device obtains the second electronic code of the IoT device through the IoT device management interface of the ERP system. The control device registers the IoT device according to the second electronic code and the number of the IoT device to obtain the IoT device registry. The control device sends a control connection request to the IoT device through the IoT device management interface of the ERP system, based on the IoT device registry.

[0016] Sixthly, this application provides a control device, the control device being used for: The second electronic code of the IoT device is obtained through the IoT device management interface of the ERP system. The IoT device is registered according to the second electronic code and the number of the IoT device to obtain the IoT device registry. Based on the IoT device registry, a control connection request is sent to the IoT device through the IoT device management interface of the ERP system.

[0017] In a seventh aspect, this application provides an electronic device, including: a memory, a processor, and a computer program stored in the memory and running on the processor, wherein the processor executes the computer program to implement the steps of the aforementioned ERP system anomaly monitoring method.

[0018] Eighthly, this application provides a computer storage medium storing computer-executable instructions, which, when executed, implement the steps of the aforementioned ERP system anomaly monitoring method.

[0019] Ninthly, this application provides a computer program product, including a computer program / instructions, which, when executed by a processor, implement the steps of the aforementioned ERP system anomaly monitoring method.

[0020] The beneficial effects of the above-mentioned technical solutions provided in this application include at least the following: The ERP system anomaly monitoring method provided in this application performs two-way authentication on the control connection between the IoT devices and control devices connected to the IoT device management interface of the ERP system. This can prevent control devices from sending control connection requests to unregistered IoT devices, thus avoiding risks caused by unregistered IoT devices being accidentally manipulated. It can also prevent IoT devices from establishing control connections with unregistered control devices, thus avoiding risks caused by IoT devices being intruded upon or accidentally manipulated by unregistered control devices. This method can detect or avoid ERP system security risks early, helping to improve the security of ERP systems based on IoT device management interfaces, enhance the security of IoT device management interfaces, and prevent ERP system anomalies.

[0021] Other features and advantages of this application will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the application. The objectives and other advantages of this application may be realized and obtained by means of the structures particularly pointed out in the written description, claims, and drawings.

[0022] The technical solution of this application will be further described in detail below with reference to the accompanying drawings and embodiments. Attached Figure Description

[0023] The accompanying drawings are provided to further illustrate the present application and form part of the specification. They are used together with the embodiments of the present application to explain the application and do not constitute a limitation thereof. In the drawings: Figure 1 This is a flowchart of the ERP system anomaly monitoring method according to an embodiment of this application; Figure 2 This is a block diagram of an ERP system anomaly monitoring system according to an embodiment of this application; Figure 3 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Detailed Implementation

[0024] Exemplary embodiments of the present application will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present application are shown in the drawings, it should be understood that the present application may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this application will be thorough and complete, and will fully convey the scope of the present application to those skilled in the art.

[0025] To address the problems existing in the prior art, embodiments of this application provide an ERP system anomaly monitoring method, system, device, medium, and program product.

[0026] This application provides an ERP system anomaly monitoring method, the process of which is as follows: Figure 1 As shown, the IoT device management interface applied to the ERP system includes the following steps: Step 1: The IoT device obtains the first electronic code of the control device through the IoT device management interface of the ERP system. The IoT device registers the control device based on the first electronic code and the control device's serial number, obtaining a control device registry. Both the IoT device and the control device are connected to the IoT device management interface of the ERP system.

[0027] If the first electronic code is the electronic code of the electronic tag of the control device, then the IoT device obtains the first electronic code of the control device through the electronic tag reader (or reader). If the control device is equipped with a first positioning module and a first time synchronization module, and the first electronic code is determined according to the position code of the first positioning module and the time code of the first time synchronization module, then the IoT device obtains the first electronic code by encoding the position code of the first positioning module and the time code of the first time synchronization module.

[0028] Each control device number should uniquely correspond to its corresponding control device. Control devices can specifically include microcontrollers (MCUs), vehicle networking control devices, remote terminal units (RTUs), programmable logic controllers (PLCs), infrared remote controls, smart screens, and other intelligent devices with installed control applications.

[0029] The control device registry can be stored in the storage unit of the IoT device or in the IoT cloud system. After the IoT device uploads the control device registry to the cloud system, the IoT device downloads the control device registry from the cloud system and searches for the control device corresponding to the control source in the control device registry; or the cloud system searches for the control device corresponding to the control source in the control device registry and returns the search result to the IoT device.

[0030] In some specific embodiments, the IoT device registers the control device based on the first electronic code and the control device's serial number, obtaining a control device registry, including: The registration code of the control device is determined based on the first electronic code and the serial number of the control device; Obtain the controllable connection period of the IoT device; The control device is registered based on its registration code and the controllable connection period of the IoT device, resulting in a control device registry.

[0031] By using the registration code of the control device, the control device can be authenticated. By controlling the connection period, security control can be performed based on the connection period. The control device is registered from both the device and the time period perspective. Through the control device registry, the control connection request is securely authenticated. This can prevent IoT devices from establishing control connections with unregistered control devices, and avoid the risk of IoT devices being manipulated by intrusion or unregistered control devices. This can further improve the security management capabilities of control connections.

[0032] Step 2: The control device obtains the second electronic code of the IoT device through the IoT device management interface of the ERP system. The control device registers the IoT device according to the second electronic code and the IoT device number to obtain the IoT device registry.

[0033] If the second electronic code is the electronic code of the electronic tag of the IoT device, the control device obtains the second electronic code of the IoT device through the electronic tag reader. If a second positioning module and a second time synchronization module are set up for the IoT device, and the second electronic code is determined according to the location code of the second positioning module and the time code of the second time synchronization module, the control device obtains the second electronic code by encoding the location code of the second positioning module and the time code of the second time synchronization module.

[0034] Each IoT device ID should uniquely correspond to an IoT device. The IoT device registry can be stored in the storage unit of the control device or in the IoT cloud system. After the control device uploads the IoT device registry to the cloud system, the control device downloads the IoT device registry from the cloud system and searches for the IoT device corresponding to the control target in the IoT device registry; alternatively, the cloud system searches for the control device corresponding to the control target in the IoT device registry and returns the search result to that control device.

[0035] In some specific embodiments, the control device registers the IoT device based on the second electronic code and the IoT device's serial number, obtaining an IoT device registry, including: The registration code of the Internet of Things (IoT) device is determined based on the second electronic code and the IoT device's serial number; Obtain the controllable connection period of the IoT device; The IoT device is registered based on its registration code and the controllable connection period, resulting in an IoT device registry.

[0036] By using the registration code of IoT devices, the control device can authenticate IoT devices. By controlling the connection period, it can perform security control based on the connection period. The control device is registered from both the device and time period perspectives. Through this IoT device registry, the control device sends control connection requests to registered IoT devices, which can prevent the control device from sending control connection requests to unregistered IoT devices. This avoids the risk of unregistered IoT devices being accidentally manipulated and can further improve the security management capabilities of the control connection.

[0037] To enhance the security of the control connection, the first electronic code and the second electronic code in this application should be independent of the control device and the Internet of Things device, and the above electronic codes should be generated by independent devices or modules.

[0038] For example, in some specific embodiments, the ERP system anomaly monitoring method further includes: setting a first electronic tag on the control device, wherein the first electronic code is specifically the first electronic code of the first electronic tag of the control device; and setting a second electronic tag on the IoT device, wherein the second electronic code is specifically the second electronic code of the second electronic tag of the IoT device. Depending on the application scenario, the first and second electronic tags can be different types of RFID electronic tags, such as low-frequency (LF), high-frequency (HF), ultra-high-frequency (UHF), and microwave. For example, low-frequency electronic tags are used in access control systems, high-frequency electronic tags in library management systems, ultra-high-frequency electronic tags in warehousing systems, and microwave electronic tags in road toll collection systems. The electronic code generated by the electronic tag is independent of the control device and the IoT device, enabling independent authentication. Furthermore, the electronic tag has low cost, and the electronic code can be obtained through an electronic tag reader, making it convenient to use and with low configuration costs, suitable for deployment on a large number of IoT devices and control devices. When IoT devices and control devices acquire each other's electronic tag codes, they need to be kept within a relatively close physical distance. Using an electronic tag reader to obtain the electronic tag codes facilitates secure management of both devices and helps ensure the authenticity and security of the IoT device registry and the control device registry. After obtaining the IoT device registry and the control device registry, the IoT devices and control devices no longer need to maintain a fixed reading distance for the electronic tags and can move or remain stationary within the IoT's connection range or the range of control signal transmission and reception.

[0039] For example, in some specific embodiments, the ERP system anomaly monitoring method further includes: setting a first positioning module and a first time synchronization module for the control device, and determining a first electronic code based on the location code of the first positioning module and the time code of the first time synchronization module; setting a second positioning module and a second time synchronization module for the IoT device, and determining a second electronic code based on the location code of the second positioning module and the time code of the second time synchronization module. The first time synchronization module and the second time synchronization module are used to acquire the IoT time and synchronize the time of the control device and the IoT device respectively. The aforementioned first positioning module and second positioning module can determine the physical location of the control device and the IoT device respectively, which facilitates the security management of the control device and the IoT device and the investigation of suspicious control connections. Determining the first electronic code based on the location code of the first positioning module and the time code of the first time synchronization module specifically involves mapping the location code and the time code according to a preset coding model to obtain either the first electronic code or the second electronic code. By decoding the first or second electronic code, the location code of the first positioning module and the time code of the first time synchronization module, or the location code of the second positioning module and the time code of the second time synchronization module, are obtained. This further determines the physical location and registration time of the control device or IoT device at the time of registration, facilitating the investigation of abnormal control connections. The first and second time synchronization modules are used to synchronize the time of the control device and the IoT device respectively, ensuring time alignment between them. This facilitates comparison based on their time codes and allows for subsequent steps.

[0040] Step 3: The control device sends a control connection request to the IoT device through the IoT device management interface of the ERP system, based on the IoT device registry. The IoT device performs security authentication on the control connection request through the IoT device management interface of the ERP system, based on the control device registry, and returns a monitoring report to the ERP system. The IoT device and the control device establish a mutually authenticated control connection based on the control device registry and the IoT device registry, further improving IoT security management capabilities.

[0041] In some specific embodiments, the control device sends a control connection request to the IoT device through the IoT device management interface of the ERP system, based on the IoT device registry, including: The control device obtains the control target through the IoT device management interface of the ERP system and searches for the corresponding IoT device in the IoT device registry. If the IoT device corresponding to the control target exists in the IoT device registry, the controllable connection period of the IoT device is obtained through the IoT device management interface of the ERP system based on the IoT device registry. During the controllable connection period of the IoT device, the control device sends a control connection request to the IoT device through the IoT device management interface of the ERP system. If the IoT device corresponding to the control target does not exist in the IoT device registry, the control device reports that the control target is not registered and authentication failed through the IoT device management interface of the ERP system.

[0042] In some specific embodiments, the IoT device, based on the control device registry, performs security authentication on the control connection request through the IoT device management interface of the ERP system and returns an ERP system monitoring report, including: In response to the control connection request, the IoT device obtains the control source through the IoT device management interface of the ERP system and searches for the corresponding control device in the control device registry. If the control device corresponding to the control source exists in the control device registry, the IoT device obtains the controllable connection period of the IoT device through the IoT device management interface of the ERP system based on the control device registry. During the controllable connection period of the IoT device, the control connection request is authenticated and a normal report of the IoT device management interface of the ERP system is sent to the ERP system. If the control device corresponding to the control source does not exist in the control device registry, or the control connection request is not within the controllable connection period of the IoT device, the IoT device rejects the control connection request and sends an abnormal alarm of the IoT device management interface of the ERP system to the ERP system.

[0043] The "control connection" mentioned above refers to the logical relationship of device control, not necessarily a direct electrical connection. This control connection can be implemented through wireless signals, wired signals, optical signals, or control connections based on other physical quantities such as temperature or air pressure. Furthermore, terms like "first" and "second" do not indicate a sequential order, but rather distinguish between different characteristics.

[0044] In the above-described method of this embodiment, the ERP system anomaly monitoring method provided in this application performs bidirectional authentication on the control connection between the IoT devices and control devices connected to the IoT device management interface of the ERP system through the IoT device management interface of the ERP system. This can prevent the control device from sending control connection requests to unregistered IoT devices, avoid risks caused by unregistered IoT devices being accidentally manipulated, prevent IoT devices from establishing control connections with unregistered control devices, and avoid risks caused by IoT devices being intruded upon or accidentally manipulated by unregistered control devices. This helps to improve the security of the ERP system based on the IoT device management interface, enhance the security of the IoT device management interface, and prevent ERP system anomalies.

[0045] Those skilled in the art can change the above order without departing from the scope of protection of this application.

[0046] Another embodiment of this application provides an ERP system anomaly monitoring system, the structure of which is as follows: Figure 2 As shown, it includes: The control device registration module is configured such that the Internet of Things (IoT) device obtains the first electronic code of the control device through the IoT device management interface of the ERP system, and the IoT device registers the control device according to the first electronic code and the control device number to obtain the control device registry. The IoT device registration module is configured such that the control device obtains the second electronic code of the IoT device through the IoT device management interface of the ERP system, and the control device registers the IoT device according to the second electronic code and the number of the IoT device to obtain the IoT device registry. The control connection security authentication module is configured such that the control device sends a control connection request to the IoT device through the IoT device management interface of the ERP system based on the IoT device registry; the IoT device performs security authentication on the control connection request through the IoT device management interface of the ERP system based on the control device registry and returns an ERP system monitoring report.

[0047] Regarding the system in the above embodiments, the specific ways in which each module performs operations have been described in detail in the embodiments related to the method, and will not be elaborated here.

[0048] In this embodiment, the ERP system anomaly monitoring system provided by this application performs bidirectional authentication on the control connection between the IoT devices and control devices connected to the IoT device management interface of the ERP system through the IoT device management interface of the ERP system. This can prevent control devices from sending control connection requests to unregistered IoT devices, avoid risks caused by unregistered IoT devices being accidentally manipulated, and prevent IoT devices from establishing control connections with unregistered control devices. This can also prevent risks caused by IoT devices being intruded upon or accidentally manipulated by unregistered control devices, thus helping to improve the security of the ERP system based on the IoT device management interface, enhance the security of the IoT device management interface, and prevent ERP system anomalies.

[0049] Thirdly, this application provides an ERP system anomaly monitoring method, applied to Internet of Things (IoT) devices, including: The IoT device obtains the first electronic code of the control device through the IoT device management interface of the ERP system. The IoT device registers the control device according to the first electronic code and the control device number to obtain the control device registry. In response to the control connection request from the control device, the IoT device performs security authentication on the control connection request through the IoT device management interface of the ERP system based on the control device registry and returns an ERP system monitoring report.

[0050] The above-mentioned ERP system anomaly monitoring method applied to IoT devices can prevent IoT devices from establishing control connections with unregistered control devices, avoid risks caused by IoT devices being manipulated by intrusion or unregistered control devices, improve the security of ERP systems based on IoT device management interfaces, enhance the security of IoT device management interfaces, and prevent ERP system anomalies.

[0051] Fourthly, this application provides an Internet of Things (IoT) device, which is used for: The first electronic code of the control device is obtained through the IoT device management interface of the ERP system. The control device is registered according to the first electronic code and the number of the control device to obtain the control device registry. In response to the control connection request from the control device, the system performs security authentication on the control connection request through the IoT device management interface of the ERP system based on the control device registry and returns an ERP system monitoring report.

[0052] The aforementioned IoT devices can specifically include smart home appliances, smart door locks and other smart home devices, smart glasses, smartwatches and other smart wearable devices, smart valves and other industrial IoT (IIoT) devices, vehicle-to-everything (V2X) devices such as in-vehicle terminals, agricultural IoT devices, medical IoT devices, etc.

[0053] The aforementioned IoT devices can prevent IoT devices from establishing control connections with unregistered control devices, avoid risks arising from IoT devices being compromised or accidentally manipulated by unregistered control devices, improve the security of ERP systems based on IoT device management interfaces, enhance the security of IoT device management interfaces, and prevent ERP system anomalies.

[0054] Fifthly, this application provides an ERP system anomaly monitoring method, applied to control equipment, comprising: The control device obtains the second electronic code of the IoT device through the IoT device management interface of the ERP system. The control device registers the IoT device according to the second electronic code and the number of the IoT device to obtain the IoT device registry. The control device sends a control connection request to the IoT device through the IoT device management interface of the ERP system, based on the IoT device registry.

[0055] The aforementioned ERP system anomaly monitoring method applied to control devices can prevent control devices from sending control connection requests to unregistered IoT devices, avoid risks caused by unregistered IoT devices being accidentally manipulated, improve the security of ERP systems based on IoT device management interfaces, enhance the security of IoT device management interfaces, and prevent ERP system anomalies.

[0056] Sixthly, this application provides a control device, the control device being used for: The second electronic code of the IoT device is obtained through the IoT device management interface of the ERP system. The IoT device is registered according to the second electronic code and the number of the IoT device to obtain the IoT device registry. Based on the IoT device registry, a control connection request is sent to the IoT device through the IoT device management interface of the ERP system.

[0057] The aforementioned control device can prevent control connection requests from the control device to unregistered IoT devices, avoid risks caused by unregistered IoT devices being accidentally manipulated, improve the security of ERP systems based on IoT device management interfaces, enhance the security of IoT device management interfaces, and prevent ERP system anomalies.

[0058] Seventhly, this application provides an electronic device with the following structure: Figure 3 As shown, it includes: a memory, a processor, and a computer program stored in the memory and running on the processor, wherein the processor executes the computer program to implement the steps of the aforementioned ERP system anomaly monitoring method.

[0059] Eighthly, this application provides a computer storage medium storing computer-executable instructions, which, when executed, implement the steps of the aforementioned ERP system anomaly monitoring method.

[0060] Ninthly, this application provides a computer program product, including a computer program / instructions, which, when executed by a processor, implement the steps of the aforementioned ERP system anomaly monitoring method.

[0061] Any modifications, additions, and equivalent substitutions made within the scope of the principles of this application shall still fall within the scope of the patent coverage of this application.

Claims

1. A method for anomaly monitoring in an ERP system, characterized in that, Interfaces for managing IoT devices in ERP systems include: The IoT device obtains the first electronic code of the control device through the IoT device management interface of the ERP system. The IoT device registers the control device according to the first electronic code and the control device number to obtain the control device registry. The control device obtains the second electronic code of the IoT device through the IoT device management interface of the ERP system. The control device registers the IoT device according to the second electronic code and the number of the IoT device to obtain the IoT device registry. The control device sends a control connection request to the IoT device through the IoT device management interface of the ERP system, based on the IoT device registry; the IoT device performs security authentication on the control connection request through the IoT device management interface of the ERP system, based on the control device registry, and returns an ERP system monitoring report.

2. The ERP system anomaly monitoring method as described in claim 1, characterized in that, The ERP system anomaly monitoring method also includes: A first electronic tag is set for the control device, and the first electronic code is specifically the first electronic code of the first electronic tag of the control device; a second electronic tag is set for the Internet of Things device, and the second electronic code is specifically the second electronic code of the second electronic tag of the Internet of Things device.

3. The ERP system anomaly monitoring method as described in claim 1, characterized in that, The IoT device registers the control device based on the first electronic code and the control device's serial number, resulting in a control device registry, which includes: The registration code of the control device is determined based on the first electronic code and the serial number of the control device; Obtain the controllable connection period of the IoT device; The control device is registered based on its registration code and the controllable connection period of the IoT device, resulting in a control device registry.

4. The ERP system anomaly monitoring method as described in claim 1, characterized in that, The control device registers the IoT device based on the second electronic code and the IoT device's serial number, obtaining an IoT device registry, including: The registration code of the Internet of Things (IoT) device is determined based on the second electronic code and the IoT device's serial number; Obtain the controllable connection period of the IoT device; Based on the registration code of the control device and the controllable connection period of the IoT device, the IoT device is registered to obtain the IoT device registry.

5. The ERP system anomaly monitoring method as described in claim 1, characterized in that, The control device, based on the IoT device registry, sends a control connection request to the IoT device through the IoT device management interface of the ERP system, including: The control device obtains the control target through the IoT device management interface of the ERP system and searches for the IoT device corresponding to the control target in the IoT device registry. If the IoT device corresponding to the control target exists in the IoT device registry, the controllable connection period of the IoT device is obtained through the IoT device management interface of the ERP system according to the IoT device registry. During the controllable connection period of the IoT device, the control device sends a control connection request to the IoT device through the IoT device management interface of the ERP system.

6. The ERP system anomaly monitoring method as described in claim 1, characterized in that, The IoT device, based on the control device registry, performs security authentication on the control connection request through the IoT device management interface of the ERP system and returns an ERP system monitoring report, including: In response to the control connection request, the IoT device obtains the control source through the IoT device management interface of the ERP system and searches for the corresponding control device in the control device registry. If the control device corresponding to the control source exists in the control device registry, the IoT device obtains the controllable connection period of the IoT device through the IoT device management interface of the ERP system based on the control device registry. During the controllable connection period of the IoT device, the control connection request is authenticated and a normal report of the IoT device management interface of the ERP system is sent to the ERP system. If the control device corresponding to the control source does not exist in the control device registry, or the control connection request is not within the controllable connection period of the IoT device, the IoT device rejects the control connection request and sends an abnormal alarm of the IoT device management interface of the ERP system to the ERP system.

7. An ERP system anomaly monitoring system, characterized in that, Interfaces for managing IoT devices in ERP systems include: The control device registration module is configured such that the Internet of Things (IoT) device obtains the first electronic code of the control device through the IoT device management interface of the ERP system, and the IoT device registers the control device according to the first electronic code and the control device number to obtain the control device registry. The IoT device registration module is configured such that the control device obtains the second electronic code of the IoT device through the IoT device management interface of the ERP system, and the control device registers the IoT device according to the second electronic code and the number of the IoT device to obtain the IoT device registry. The control connection security authentication module is configured such that the control device sends a control connection request to the IoT device through the IoT device management interface of the ERP system based on the IoT device registry; the IoT device performs security authentication on the control connection request through the IoT device management interface of the ERP system based on the control device registry and returns an ERP system monitoring report.

8. An electronic device, characterized in that, include: A memory, a processor, and a computer program stored in the memory and running on the processor, wherein the processor executes the computer program to implement the steps of the ERP system anomaly monitoring method according to any one of claims 1 to 6.

9. A computer storage medium, characterized in that, The computer storage medium stores computer-executable instructions, which, when executed, implement the steps of the ERP system anomaly monitoring method according to any one of claims 1 to 6.

10. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instruction is executed by the processor, it implements the steps of the ERP system anomaly monitoring method according to any one of claims 1 to 6.

Images