Rubber operation management method, system and storage medium

Abstract

The present invention discloses a rubber operation management method, system and storage medium. The method includes initiating a permission acquisition request from the client to the backend, where the permission acquisition request carries a permission identifier; obtaining the operation permission corresponding to the permission identifier in the client through the identity management service; initiating a corresponding rubber management request from the client to the backend, where the rubber management request carries the operation permission; and invoking the business service corresponding to the operation permission and the rubber management request in the backend through the operation permission and the interface authentication service. By setting three different levels of operation permissions in the present invention, different operation permissions can call different numbers of business services, which can effectively prevent users with low-level permissions from performing work beyond their authority scope during rubber operations, facilitating the monitoring and orderly management of rubber operations on the rubber operation pipeline. This application is applied to technical fields such as rubber operations and information networks.

Description

Technical Field

[0001] The present invention relates to the field of information network technologies, and particularly to a rubber operation management method, system, and storage medium. Background Art

[0002] Rubber refers to a highly elastic polymer material with reversible deformation. It is elastic at room temperature, can produce large deformations under very small external forces, and can return to its original state after the external force is removed. Rubber is usually divided into natural rubber and synthetic rubber, among which natural rubber is processed from the gums extracted from plants such as rubber trees and rubber grass. In recent years, with the progress and development of technology, people have developed automatic rubber operation equipment to replace manual rubber operations. The application of automatic rubber operation equipment can improve the efficiency of rubber operations and reduce labor costs.

[0003] In the field of rubber operations, a large rubber operation pipeline is usually managed through hierarchical management, that is, by setting different levels of permissions, such as setting a head office operation administrator - branch office operation administrator - front-line operation administrator to manage multiple rubber operation equipment in the rubber operation pipeline. Although the hierarchical management method can supervise the rubber operations to a certain extent, due to the lack of specific identity management methods and equipment management methods, it is difficult for high-level permission users to monitor and manage all low-permission users who are currently performing rubber operations on the rubber operation pipeline in real time. Moreover, the rubber output obtained on the rubber operation pipeline cannot be timely fed back to high-level permission users, which easily leads to low-level permission users using the rubber operation pipeline to perform work beyond the scope permitted by their permissions, such as stealing rubber, thereby causing certain economic losses to high-level permission users. Summary of the Invention

[0004] The embodiments of the present application provide a rubber operation management method, system, and storage medium to solve one or more technical problems existing in the prior art, and at least provide a beneficial choice or create conditions.

[0005] The solution of the present invention to solve its technical problems is: In a first aspect, the embodiments of the present application provide a rubber operation management method, including:

[0006] Sending a permission acquisition request from the client to the backend, where the permission acquisition request carries a permission identifier, and the permission acquisition request is used to invoke the identity management service of the backend;

[0007] When it is recognized that the permission acquisition request carries the permission identifier, configuring the corresponding operation permissions of each user on the client through the identity management service;

[0008] Among them, the permission identifier includes any one of a first permission identifier, a second permission identifier, or a third permission identifier, and the operation permissions corresponding to the client include any one of a first operation permission, a second operation permission, or a third operation permission;

[0009] Initiate a corresponding rubber management request to the backend through the client, where the rubber management request carries the operation permission, and the rubber management request is used to call the corresponding business service in the backend;

[0010] Call the interface authentication service through the backend, identify the operation permission carried by the rubber management request through the interface authentication service, and determine the business service corresponding to the operation permission;

[0011] When it is determined that the business service corresponding to the operation permission includes the business service corresponding to the rubber management request, call the business service corresponding to the rubber management request;

[0012] Among them, the number of business services corresponding to the first operation permission is greater than the number of business services corresponding to the second operation permission, and the number of business services corresponding to the second operation permission is greater than the number of business services corresponding to the third operation permission;

[0013] Among them, the business services corresponding to the operation permission at least include a first job authorization service, a second job authorization service, a device management service, a job data service, a status detection service, and a fault service;

[0014] The identifying the operation permission carried by the rubber management request through the interface authentication service and determining the business service corresponding to the operation permission includes:

[0015] When it is identified through the interface authentication service that the operation permission is the first operation permission, determine that the business services corresponding to the first operation permission include a first job authorization service, a device management service, a job data service, a status detection service, and a fault service;

[0016] Or, when it is identified through the interface authentication service that the operation permission is the second operation permission, determine that the business services corresponding to the second operation permission include a second job authorization service, a device management service, a job data service, a status detection service, and a fault service;

[0017] Or, when it is identified through the interface authentication service that the operation permission is the third operation permission, determine that the preset business service corresponding to the third operation permission is a device management service, a job data service, a status detection service, and a fault service.

[0018] As a further improvement of the above technical solution, when it is recognized that the permission acquisition request carries the permission identifier, the identity management service is used to respectively configure the operation permissions of each user corresponding to the client, including:

[0019] When it is recognized that the permission acquisition request carries the first permission identifier, the identity management service is used to configure the first operation permission of the user in the client;

[0020] Or, when it is recognized that the permission acquisition request carries the second permission identifier, the identity management service is used to configure the second operation permission of the user in the client;

[0021] Or, when it is recognized that the permission acquisition request carries the third permission identifier, the identity management service is used to configure the third operation permission of the user in the client.

[0022] As a further improvement of the above technical solution, the invocation of the business service corresponding to the rubber management request includes at least one of the following:

[0023] When the business service corresponding to the rubber management request is the first job authorization service, the first job authorization service is used to provide a service that grants the client corresponding to the second operation permission the permission to call the device management service;

[0024] When the business service corresponding to the rubber management request is the second job authorization service, the second job authorization service is used to provide a service that grants the client corresponding to the third operation permission the permission to call the device management service;

[0025] When the business service corresponding to the rubber management request is the device management service, it is determined whether there is permission to call the device management service. When it is determined that there is permission to call the device management service, the device management service is used to provide services for binding and debugging the device end, and generating and sending a rubber job instruction to the device end;

[0026] Wherein, the rubber job instruction is used to control the device end to execute the corresponding rubber job, and the corresponding rubber job includes a rubber tapping job or a rubber collection job;

[0027] When the business service corresponding to the rubber management request is the job data service, the job data service is used to provide a service for receiving data corresponding to the rubber tapping job or the rubber collection job from the device end and generating a data chart according to the data corresponding to the rubber collection job;

[0028] When the business service corresponding to the rubber management request is the fault service, a service is provided through the fault service to detect the fault condition of the device end at a preset first period, analyze the fault condition, and generate a fault analysis result and a fault notification;

[0029] When the business service corresponding to the rubber management request is the status detection service, a service is provided through the status detection service to detect the working condition of the device end performing the corresponding rubber operation at a preset second period, and generate a corresponding device notification according to the working condition of the device end performing the corresponding rubber operation.

[0030] As a further improvement of the above technical solution, the detecting the fault condition of the device end at a preset first period, analyzing the fault condition, and generating a fault analysis result and a fault notification includes:

[0031] Detect the fault condition of the device end through the fault service at the first period, generate current fault data and store it in the database at the back end;

[0032] Call a first prediction model through the fault service, input the current fault data into the first prediction model, and obtain a first fault prediction result;

[0033] Among them, the first prediction model is a pre-trained neural network model based on Xgboost, and the first prediction model is trained through first historical fault data and its manual labels, and the first historical fault data and its manual labels are obtained through the database;

[0034] Call a second prediction model through the fault service, input the current fault data into the second prediction model, and obtain a second fault prediction result;

[0035] Among them, the second prediction model is a pre-trained neural network model based on LSTM, and the second prediction model is trained through second historical fault data, its manual labels and timestamps, and the second historical fault data, its manual labels and timestamps are obtained through the database;

[0036] Assign a first weight to the first fault prediction result, assign a second weight to the second prediction result, and accumulate the first fault prediction result with the first weight and the second fault prediction result with the second weight to obtain an initial fault result;

[0037] Call a data analysis model through the fault service, analyze the initial fault result through the data analysis model, obtain the fault analysis result and output the fault notification.

[0038] As a further improvement of the above technical solution, the rubber operation management method further includes:

[0039] When invoking the business service corresponding to the rubber management request, the backend provides component services according to the corresponding business service; the component services include a log service, a network monitoring service, and a data service;

[0040] The providing of component services according to the corresponding business service includes:

[0041] Obtaining the operation logs of the client, the backend, and the device end through the log service, and storing the operation logs in a database;

[0042] Monitoring the network traffic situation of the backend and the invocation situation of the business service through the network monitoring service, and generating a monitoring notification according to the network traffic situation of the backend and the invocation situation of the business service;

[0043] Invoking the database of the backend through the data service, obtaining the data of the client and the device end through the database, and performing data storage, reading, and aggregation on the data of the client and the device end.

[0044] In a second aspect, an embodiment of the present application provides a rubber operation management system, including a client, a backend, and a device end. An identity management service, an interface permission service, a plurality of business services, and component services are provided in the backend;

[0045] The client is used to initiate a corresponding permission acquisition request to the backend. The permission acquisition request carries a permission identifier, and the permission acquisition request is used to invoke the identity management service;

[0046] The backend is used to, when recognizing that the permission acquisition request carries the permission identifier, configure the corresponding operation permissions of each user in the client through the identity management service;

[0047] Wherein, the permission identifier includes any one of a first permission identifier, a second permission identifier, or a third permission identifier; the corresponding operation permissions of the client include any one of a first operation permission, a second operation permission, or a third operation permission;

[0048] The client is further used to initiate a corresponding rubber management request to the backend. The rubber management request carries the operation permission, and the rubber management request is used to invoke the corresponding business service in the backend;

[0049] The backend is further used to identify the operation permission carried by the rubber management request through the interface authentication service, and determine the business service corresponding to the operation permission;

[0050] The backend is further configured to, when determining that the business services corresponding to the operation permission include the business service corresponding to the rubber management request, call the business service corresponding to the rubber management request;

[0051] Wherein, the number of business services corresponding to the first operation permission is greater than the number of business services corresponding to the second operation permission, and the number of business services corresponding to the second operation permission is greater than the number of business services corresponding to the third operation permission; the business services corresponding to the operation permission at least include a first job authorization service, a second job authorization service, a device management service, a job data service, a status detection service, and a fault service;

[0052] Wherein, the first job authorization service is configured to grant the client corresponding to the second operation permission the permission to call the device management service;

[0053] The second job authorization service is configured to grant the client corresponding to the third operation permission the permission to call the device management service;

[0054] The device management service is configured to bind and debug the device terminal, generate a rubber operation instruction and send it to the device terminal; wherein, the rubber operation instruction is used to control the device terminal to execute the corresponding rubber operation, and the corresponding rubber operation includes a rubber tapping operation or a rubber collecting operation;

[0055] The job data service is configured to receive data corresponding to the rubber tapping operation or the rubber collecting operation from the device terminal, and generate a data chart according to the data corresponding to the rubber collecting operation;

[0056] The fault service is configured to detect the fault condition of the device terminal at a preset first period, analyze the fault condition, and generate a fault analysis result and a fault notification;

[0057] The status detection service is configured to detect the working condition of the device terminal executing the corresponding rubber operation at a preset second period, and generate a corresponding device notification according to the working condition of the device terminal executing the corresponding rubber operation;

[0058] The identifying, by the interface authentication service, the operation permission carried in the rubber management request and determining the business service corresponding to the operation permission includes:

[0059] When the interface authentication service identifies that the operation permission is the first operation permission, determining that the business services corresponding to the first operation permission include a first job authorization service, a device management service, a job data service, a status detection service, and a fault service;

[0060] Alternatively, when the interface authentication service identifies that the operation permission is the second operation permission, determine that the business services corresponding to the second operation permission include a second job authorization service, a device management service, a job data service, a status detection service, and a fault service;

[0061] Alternatively, when the interface authentication service identifies that the operation permission is the third operation permission, determine that the preset business services corresponding to the third operation permission are a device management service, a job data service, a status detection service, and a fault service.

[0062] As a further improvement of the above technical solution, the backend is further configured to, when the business service corresponding to the rubber management request is the first job authorization service, provide, through the first job authorization service, a service for granting the client corresponding to the second operation permission the permission to call the device management service;

[0063] The backend is further configured to, when the business service corresponding to the rubber management request is the second job authorization service, provide, through the second job authorization service, a service for granting the client corresponding to the third operation permission the permission to call the device management service;

[0064] The backend is further configured to, when the business service corresponding to the rubber management request is the device management service, determine whether it has the permission to call the device management service. When it is determined that it has the permission to call the device management service, provide, through the device management service, a service for binding and debugging the device end, and generating and sending a rubber job instruction to the device end;

[0065] The backend is further configured to, when the business service corresponding to the rubber management request is the job data service, provide, through the job data service, a service for receiving data corresponding to the rubber tapping operation or the rubber collection operation from the device end, and generating a data chart based on the data corresponding to the rubber collection operation;

[0066] The backend is further configured to, when the business service corresponding to the rubber management request is the fault service, provide, through the fault service, a service for detecting the fault condition of the device end at a preset first period, analyzing the fault condition, and generating a fault analysis result and a fault notification;

[0067] The backend is further configured to, when the business service corresponding to the rubber management request is the status detection service, provide, through the status detection service, a service for detecting the working condition of the device end performing the corresponding rubber operation at a preset second period, and generating a corresponding device notification based on the working condition of the device end performing the corresponding rubber operation.

[0068] As a further improvement of the above technical solution, the component service includes a log service, a network monitoring service, and a data service. The backend is further configured to provide component services according to the corresponding business service when invoking the business service corresponding to the rubber management request.

[0069] Among them, the log service is used to obtain the operation logs of the client, the backend, and the device end, and store the operation logs in a database.

[0070] The network monitoring service is used to monitor the network traffic situation and business service invocation situation of the backend, and generate a monitoring notification according to the network traffic situation and business service invocation situation of the backend.

[0071] The data service is used to call the database of the backend, obtain the data of the client and the device end through the database, and perform data storage, reading, and aggregation on the data of the client and the device end.

[0072] As a further improvement of the above technical solution, the client displays a main area, a device area, a message area, and a management area.

[0073] In the main area, there is a device end list, permission settings, and job control. The device end list is used to display the data corresponding to the rubber tapping operation or the rubber collecting operation of the device end, the fault analysis result, and the working condition of the device end performing the corresponding rubber operation; the permission settings are used to grant the permission to call the device management service to the user corresponding to the second operation permission, or grant the permission to call the device management service to the user corresponding to the third operation permission; the job control is used to send rubber operation instructions to multiple device ends.

[0074] In the device area, there is a barcode scanning sub-area, viewing device, and debugging device. The barcode scanning sub-area is used to scan the QR code information of the device end to obtain the device information of the device end; the viewing device is used to view the device information of the device end; the debugging device is used to debug the device end.

[0075] In the message area, there is a device end notification list, an exception alarm list, and contact customer service; the device end notification list is used to display the device notifications sent by the backend; the exception alarm list is used to display the monitoring notifications and fault notifications sent by the backend.

[0076] In the management area, there is device management and identity management; the identity management is used to log in to the client and generate a corresponding permission identifier, obtain the operation permission corresponding to the permission identifier, and call the business service of the backend corresponding to the operation permission; the device management is used to bind the device end and the client.

[0077] In a third aspect, an embodiment of the present application provides a storage medium storing instructions executable by a processor, and the instructions executable by the processor are used to execute the rubber operation management method described above when executed by the processor.

[0078] The embodiments of the present application at least include the following beneficial effects: By providing a job management method, system, and storage medium, different levels of operation permissions are configured in the client through a permission acquisition request, and business services corresponding to the operation permissions and rubber management requests are called through a rubber management request, achieving the purpose of accurately classifying and managing rubber operations. The technical solution provided by the present application enables users with high-level permissions to monitor in real time the rubber operations performed by users with low-level permissions, facilitating the monitoring and orderly management of rubber operations throughout the rubber operation pipeline; Since the present application is provided with operation permissions, the operation permissions can effectively prevent users with low-level permissions from performing work beyond their permission scope during rubber operations, reducing the possibility of the occurrence of rubber theft.

[0079] Other features and advantages of the present application will be described in the subsequent description, and some of them will become obvious from the description or be understood by implementing the present application. The objectives and other advantages of the present application can be achieved and obtained through the structures specifically pointed out in the description, claims, and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0080] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below. Obviously, the described drawings are only a part of the embodiments of the present invention, rather than all the embodiments. Those skilled in the art can obtain other design solutions and drawings based on these drawings without creative efforts.

[0081] Figure 1 It is a work flow chart of the rubber operation management method provided by the embodiment of the present application;

[0082] Figure 2 It is a method flow chart for determining operation permissions provided by the embodiment of the present application;

[0083] Figure 3 It is a structural schematic diagram of the rubber operation management system provided by the embodiment of the present application;

[0084] Figure 4 It is a structural schematic diagram of the client provided by the embodiment of the present application;

[0085] Figure 5 It is a work flow chart for generating a fault analysis result provided by the embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0086] In order to make the objectives, technical solutions, and advantages of this application clearer, the following further elaborates on this application in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not used to limit this application.

[0087] The following further describes this application in conjunction with the drawings in the specification and specific embodiments. The described embodiments should not be regarded as a limitation to this application. All other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the scope of protection of this application.

[0088] In the following description, reference is made to "some embodiments", which describe a subset of all possible embodiments. However, it can be understood that "some embodiments" can be the same subset or different subsets of all possible embodiments and can be combined with each other without conflict.

[0089] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the technical field to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of this application and are not intended to limit this application.

[0090] Before further elaborating on the embodiments of this application, the nouns and terms involved in the embodiments of this application are described, and the nouns and terms involved in the embodiments of this application are explained as follows.

[0091] (1) The HTTPS protocol (Hypertext Transfer Protocol Secure) is a network protocol that can perform encrypted transmission and identity authentication by adding SSL (Secure Socket Layer) to HTTP (Hypertext Transfer Protocol). It mainly completes the encryption of Internet data transmission through technologies such as digital certificates, encryption algorithms, and asymmetric keys, realizes Internet transmission security protection, improves the confidentiality of data transmission, and can effectively prevent replay attacks while doing so.

[0092] (2) The MQTT protocol (Message Queuing Telemetry Transport) is a message protocol based on the publish / subscribe paradigm under the ISO standard (ISO / IEC PRF 20922), and is also a client-server based message publish / subscribe transport protocol. It works on the TCP / IP protocol family and is a publish / subscribe type message protocol designed for remote devices with low hardware performance and poor network conditions.

[0093] (3) LSTM (Long Short-Term Memory) is a type of recurrent neural network. All recurrent neural networks have the form of a chain of repeating neural network modules. In a standard RNN, this repeating module will have a very simple structure, such as a single tanh layer. LSTM also has this chain-like structure, but the repeating module has a different structure. Compared with a simple single layer of a neural network, LSTM has four layers, and these four layers interact in a special way to solve the long-term dependence problem existing in general RNNs (recurrent neural networks).

[0094] (4) XGBoost is an optimized distributed gradient boosting library designed to be efficient, flexible, and portable. It implements machine learning algorithms under the Gradient Boosting framework. XGBoost provides parallel tree boosting and can quickly and accurately solve many data science problems. It is one of the commonly used machine learning models.

[0095] Currently, when performing rubber tapping operations, automatic rubber operation equipment is usually adopted to replace manual rubber operations, so as to improve the efficiency of rubber tapping and reduce the labor costs spent on rubber operations. In the face of the demand for large-scale rubber production, in order to further improve the working efficiency of rubber operations, multiple automatic rubber operation equipment are usually integrated to form a rubber operation production line, and multiple automatic rubber operation equipment are controlled to perform rubber operations simultaneously to achieve the purpose of quickly producing rubber.

[0096] In terms of managing the rubber operation production line, hierarchical management is usually adopted, that is, different levels of permissions are set to manage the huge rubber operation production line. The most common hierarchical method is to set the general company operation administrator - branch company operation administrator - front-line operation administrator. The general company operation administrator manages the rubber operations of multiple branch company operation administrators, and the branch company administrator manages the rubber operations of multiple front-line operation administrators. However, since there is still a lack of specific identity management methods and equipment management methods in the field of this application, when hierarchically managing the rubber operation production line, it is difficult for high-level permission users to supervise all low-level permission users who are currently performing rubber operations on the rubber operation production line. Moreover, since it is difficult to timely feedback the rubber output obtained on the rubber operation production line to high-level permission users, high-level permission users cannot know the total rubber output currently produced on the rubber operation production line. This situation is likely to cause low-level permission users to use the rubber operation production line to perform work beyond the scope permitted by their permissions. For example, low-level permission users control the equipment on the rubber operation production line to privately perform rubber tapping operations to achieve the purpose of stealing rubber, thereby causing a certain degree of economic loss to high-level permission users.

[0097] Based on the above problems, the embodiments of the present application provide a rubber operation management method, system and storage medium. Different levels of operation permissions are configured in the client through a permission acquisition request. The operation permissions are divided into a first operation permission, a second operation permission and a third operation permission. The business services corresponding to the operation permissions and the rubber management request are called through the rubber management request. The number of business services that can be called by the first operation permission, the second operation permission and the third operation permission decreases in turn, so as to achieve the purpose of accurately classifying and managing rubber operations. The technical solution provided by the present application enables users with high-level permissions to monitor the rubber operations performed by users with low-level permissions in real time, so as to monitor and manage the rubber operations of the entire rubber operation pipeline in an orderly manner; since the present application is provided with operation permissions, the operation permissions can effectively prevent users with low-level permissions from performing work beyond their authority when performing rubber operations, and reduce the possibility of the occurrence of rubber theft.

[0098] Referring to Figure 1 as shown, Figure 1 as shown is the workflow diagram of the rubber operation management method provided by the embodiments of the present application. The implementation process of the rubber operation management method will be described and elaborated below. The rubber operation management method may include but is not limited to the following steps 101 to step 105.

[0099] 101. Send a permission acquisition request from the client to the backend. The permission acquisition request carries a permission identifier, and the permission acquisition request is used to call the identity management service of the backend.

[0100] In this step, the identity management service is used to determine which of the first permission identifier, the second permission identifier or the third permission identifier the permission identifier is, and assign the corresponding operation permission to the client (100) according to the determined permission identifier. Among them, different operation permissions can call different business services.

[0101] 102. When it is recognized that the permission acquisition request carries a permission identifier, assign the corresponding operation permission to each user in the client through the identity management service.

[0102] It should be noted that the permission identifier includes any one of the first permission identifier, the second permission identifier or the third permission identifier.

[0103] It should be noted that the operation permission corresponding to the client (100) includes any one of the first operation permission, the second operation permission or the third operation permission.

[0104] Furthermore, when it is recognized that the permission acquisition request carries a permission identifier, assign different operation permissions to each user in the client through the identity management service, specifically including:

[0105] When it is recognized that the permission acquisition request carries the first permission identifier, configure the first operation permission of the user in the client through the identity management service;

[0106] Or, when it is recognized that the permission acquisition request carries the second permission identifier, configure the second operation permission of the user in the client through the identity management service;

[0107] Or, when it is recognized that the permission acquisition request carries the third permission identifier, configure the third operation permission of the user in the client through the identity management service.

[0108] In the above steps, the operation permission corresponding to the first permission identifier is the first operation permission, the operation permission corresponding to the second permission identifier is the second operation permission, and the operation permission corresponding to the third permission identifier is the third operation permission. When it is determined that the permission identifier is the first permission identifier, the backend (200) configures the first operation permission of the client (100); when it is determined that the permission identifier is the second permission identifier, the backend (200) configures the second operation permission of the client (100); when it is determined that the permission identifier is the third permission identifier, the backend (200) configures the third operation permission of the client (100).

[0109] 103. Initiate a corresponding rubber management request from the client to the backend. The rubber management request carries the operation permission and is used to call the corresponding business service in the backend;

[0110] 104: The backend calls the interface authentication service to identify the operation permission carried by the rubber management request through the interface authentication service and determine the business service corresponding to the operation permission.

[0111] It should be noted that the interface authentication service is used to determine which of the first operation permission, the second operation permission, or the third operation permission is the operation permission embedded in the rubber management request, and determine the business service that can be called according to the determined operation permission.

[0112] It should be noted that different operation permissions have different numbers of business services that can be called. Among them, the client (100) with the first operation permission can call the most business services, followed by the client (100) with the second operation permission, and the client (100) with the third operation permission can call the fewest business services.

[0113] 105: When it is determined that the business service corresponding to the operation permission includes the business service corresponding to the rubber management request, call the business service corresponding to the rubber management request.

[0114] It should be noted that the business services corresponding to the operation permissions at least include a first job authorization service, a second job authorization service, a device management service, a job data service, a status detection service, and a fault service.

[0115] Specifically, the first job authorization service is used to grant the client (100) corresponding to the second operation permission the right to call the device management service.

[0116] Specifically, the second job authorization service is used to grant the client (100) corresponding to the third operation permission the right to call the device management service.

[0117] Specifically, the device management service is used to bind the device side (300), output rubber operation instructions to the device side (300), control the device side (300) to perform corresponding rubber operations through the rubber operation instructions, perform debugging operations on the device side (300), and burn programs related to rubber operations into the device side (300). Among them, the rubber operation includes any one of rubber tapping operations or rubber collecting operations. When the device management service outputs a rubber tapping operation instruction, the device side (300) performs a rubber tapping operation. When the device management service outputs a rubber collecting operation instruction, the device side (300) performs a rubber collecting operation.

[0118] Specifically, the job data service is used to obtain data corresponding to rubber tapping operations or rubber collecting operations, and the data corresponding to rubber tapping operations or rubber collecting operations is generated by the device side (300). Optionally, the data corresponding to rubber tapping operations may include, but is not limited to, the number of sub-devices that have successfully completed rubber tapping operations and the number of sub-devices that have abnormally completed rubber tapping operations. The data corresponding to rubber collecting operations may include, but is not limited to, the number of sub-devices that have successfully completed rubber collecting operations, the number of sub-devices that have abnormally completed rubber collecting operations, and the rubber yield data of rubber collecting operations.

[0119] Optionally, through the job data service, a rubber yield data chart is generated in combination with the data corresponding to rubber collecting operations.

[0120] Specifically, the fault service is used to detect whether there is a fault condition in the device side (300) at a preset first period. If there is a fault condition in the device side (300), the fault service analyzes the fault condition, outputs a fault analysis result and a fault notification, and displays them through the client (100).

[0121] It should be noted that the first period can be set according to the actual situation, and the present application does not make specific restrictions on the first period.

[0122] Specifically, the status detection service is used to detect the working condition of the device end (300) performing the rubber operation at a preset second period, output a device notification according to the working condition of the rubber operation, and display it through the client (100). Optionally, outputting the device notification according to the working condition of the rubber operation may be to output the device notification according to the working condition of the device end (300) that abnormally performs the rubber tapping operation or the rubber collecting operation.

[0123] It should be noted that the second period can be set according to the actual situation, and the present application does not specifically limit the second period.

[0124] It should be noted that the business services that can be invoked by the first operation permission at least include the first operation authorization service, the device management service, the operation data service, the status detection service, and the fault service. The business services that can be invoked by the second operation permission at least include the second operation authorization service, the device management service, the operation data service, the status detection service, and the fault service. The business services that can be invoked by the third operation permission at least include the device management service, the operation data service, the status detection service, and the fault service.

[0125] In this step, when the business service corresponding to the rubber management request is included in the business service corresponding to its operation permission, it indicates that the business service requested by the client (100) to be invoked conforms to its corresponding operation permission, and the business service it requests to invoke is in a callable state. If the business service corresponding to the rubber management request is not included in the business service corresponding to its operation permission, it indicates that the client (100) is requesting to invoke a business service that exceeds its operation permission range, and the business service it requests to invoke is in a non-callable state.

[0126] Refer to Figure 2 as shown Figure 2 as shown is the method flowchart for determining the operation permission provided by the embodiment of the present application. In an embodiment of the present application, the business service corresponding to the operation permission will be further described and elaborated below. Step 105 may include but is not limited to the following steps.

[0127] When it is recognized by the interface authentication service that the operation permission is the first operation permission, determine that the business services corresponding to the first operation permission include the first operation authorization service, the device management service, the operation data service, the status detection service, and the fault service;

[0128] Or, when it is recognized by the interface authentication service that the operation permission is the second operation permission, determine that the business services corresponding to the second operation permission include the second operation authorization service, the device management service, the operation data service, the status detection service, and the fault service;

[0129] Alternatively, when the operation permission is identified as the third operation permission through the interface authentication service, determine that the business services corresponding to the preset third operation permission are the device management service, the operation data service, the status detection service, and the fault service.

[0130] In this embodiment, the operation permission of the client (100) is the first operation permission, the second operation permission, or the third operation permission, and the range of callable business services corresponding to the operation permission increases in sequence. Among them, the client (100) with the first operation permission can call the most business services, followed by the client (100) with the second operation permission, and the client (100) with the third operation permission can call the fewest business services.

[0131] Among them, when the permission identifier of the user using the client (100) is the third permission identifier, the corresponding operation permission is the third operation permission, and only has the permission to use some functions of the client (100), such as the device management service, the operation data service, the status detection service, and the fault service can be called.

[0132] When the permission identifier of the user using the client (100) is the second permission identifier, the corresponding operation permission is the second operation permission. Compared with the third operation permission, the range of callable services corresponding to the second operation permission is expanded, and it has the permission to call most functions of the client (100), such as the second operation authorization service, the device management service, the operation data service, the status detection service, and the fault service can be called.

[0133] When the permission identifier of the user using the client (100) is the first permission identifier, the corresponding operation permission is the first operation permission, and has the permission to use all functions of the client (100). For example, the client (100) with the first operation permission configures the permission for the client (100) with the second operation permission to call the device management service by calling the first operation authorization service. Optionally, the client (100) with the first operation permission obtains and displays the data corresponding to the rubber tapping operation or the rubber collecting operation of the client (100) with the second operation permission and the client (100) with the third operation permission through the operation data service, and statistically analyzes and integrates the data corresponding to the rubber collecting operation to generate a rubber production data chart.

[0134] The rubber work management method provided by the embodiments of the present application will be further described below with an example. Suppose on a rubber operation assembly line, the head office has multiple rubber operation areas and evenly distributes these rubber operation areas to multiple branch companies. Each branch company assigns a front-line administrator to each rubber operation area. Then there are three roles on the rubber operation assembly line: the head office administrator, the branch company administrator, and the front-line administrator. The head office administrator manages multiple branch company administrators belonging to the head office, and the branch company administrator manages multiple front-line administrators belonging to the branch company. That is, the head office administrator has the first operation authority, the branch company administrator has the second-level operation authority, and the front-line administrator has the third-level operation authority. The administrator authenticates the operation authority through the client (100) and the authority identifier, and the backend (200) calls the identity management service to configure the corresponding operation authority for the client (100). After obtaining the corresponding operation authority, the manager can call the business services within the scope of the operation authority limit.

[0135] Specifically, the head office administrator realizes the authority to configure the branch company administrator and the front-line administrator to call the device management service through the business service corresponding to the first operation authority, and manages the rubber operations of the device end (300) of all rubber operation areas through the device management service, the operation data service, the status detection service, and the fault service. The branch company administrator realizes the authority to configure the front-line administrator to call the device management service through the business service corresponding to the second operation authority, and manages the rubber operations of the device end (300) of the rubber operation area corresponding to the branch company through the device management service, the operation data service, the status detection service, and the fault service. The front-line administrator does not have the ability to configure the authority to call the device management service, and manages the rubber operations of the device end (300) of its corresponding rubber operation area through the device management service, the operation data service, the status detection service, and the fault service. Optionally, before the device end (300) leaves the factory, the supplier of the device end (300) can batch-authorize the devices purchased by the head office administrator by scanning the QR code of the device end (300) through the client (100). Then the head office administrator and the branch company administrator perform operation authorization to the lower-level administrators. When authorizing the device end (300), the backend (200) records the binding relationship between the administrator and the device end (300) in its database.

[0136] Through the above steps, the rubber work management method provided by the embodiments of the present application realizes real-time monitoring of the rubber operation situation of the entire rubber operation assembly line, facilitating the manager to orderly manage the work of multiple device ends (300) on the rubber operation assembly line; and effectively avoids the phenomenon that users with lower-level permissions perform work beyond their authority scope during rubber operations by setting operation permissions, reducing the possibility of rubber theft.

[0137] Refer to Figure 3As shown Figure 3 It is a schematic structural diagram of a rubber operation management system provided by an embodiment of the present application. The system includes a client (100), a backend (200), and a device end (300). The client (100) is connected to the backend (200) by wireless communication, and the backend (200) is connected to the device end (300) by wireless communication. The device end (300) is a device for performing rubber operations and is set in the rubber operation area.

[0138] The client (100) can be a smart phone, a tablet computer, a notebook computer, a desktop computer, a vehicle-mounted terminal, etc., but is not limited thereto. The client (100) includes at least one of a WeChat mini-program, a web page end, or a computer-side upper computer.

[0139] Optionally, the WeChat mini-program can run on WeChat software under various operating systems of the mobile end and the computer end.

[0140] Optionally, the web page end is used to display data and working conditions corresponding to rubber operations, fault analysis results and device notifications of the device end (300), and monitoring notifications. The web page end logs in by scanning the code of the WeChat mini-program.

[0141] Optionally, the computer end is used for burning the program when the device end (300) leaves the factory, authenticating, repairing, and debugging the device end (300), etc.

[0142] The backend (200) can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. The backend (200) at least has the function of providing business services to the client (100). For example, after receiving a permission acquisition request sent by the client (100), it can configure the operation permissions corresponding to the client (100), so that the client (100) can call the corresponding business services according to its operation permissions.

[0143] Further, the backend (200) includes a first server (210) and a second server (220). The first server (210) is implemented through load balancing technology; the second server (220) is an application server, which deploys the same or different services respectively, and these application servers are scheduled through the first server (210). The client (100) and the device side (300) are both connected to the first server (210) through a preset domain name. The first server (210) reverse-proxies the requests of the client (100) or the device side (300) to a corresponding second server (220), and returns the response result of the second server (220) to the client (100) or the device side (300). At the same time, the first server (210) monitors the traffic and security of the requests of the client (100) or the device side (300), and monitors the health status of the business services of multiple second servers (220), such as whether the business services are normally called, so as to ensure that the number of available business services is maintained within a certain range. When the traffic of the requests changes greatly, the first server (210) can adapt to the change of the traffic by elastically scaling the number of business services. When an abnormal situation occurs in the business service, a monitoring notification is sent to the client (100) and displayed on the client (100). The abnormal situation at least includes that the business service cannot be normally called and the second server (220) fails.

[0144] Furthermore, the first server (210) includes a main distributor and a standby distributor. When the main distributor of the first server (210) is in a down state, the distributor connected to the client (100) and the device side (300) is switched from the main distributor to the standby distributor.

[0145] It should be noted that the down state is defined as that the main distributor cannot reverse-proxy the requests of the client (100) or the device side (300) to the second server (220).

[0146] Furthermore, the second server (220) provides a service interface for the client (100) to process various service requests of the client (100) and the device side (300). The second server (220) deploys multiple application services, including interface authentication service, identity management service, first job authorization service, second job authorization service, device management service, job data service, fault service, and status detection service. The second server (220) also deploys multiple component services, including log service, message service, network monitoring service, and data service. In addition, the second server (220) also deploys a database.

[0147] Furthermore, the backend (200) also includes an MQTT server, and the backend (200) constructs a connection with the device side (300) through the MQTT server.

[0148] Specifically, the client (100) is used to embed a permission identifier into a permission acquisition request and send the permission acquisition request to the backend (200). The permission acquisition request is used to invoke the identity management service set by the backend (200).

[0149] The backend (200) is used to identify the permission identifier, invoke the identity management service, and configure the operation permissions corresponding to the user in the client (100) for the client (100).

[0150] The client (100) is also used to obtain the operation permissions. The operation permissions are generated by the backend (200), embed the operation permissions into a rubber management request, and send the rubber management request to the backend (200) to implement the invocation of the business service set by the backend (200).

[0151] The backend (200) is also used to invoke the interface authentication service, verify and identify the operation permissions embedded in the rubber management request, and determine the business service corresponding to the operation permissions based on the identified operation permissions, that is, the business service that the client (100) can invoke.

[0152] The backend (200) is also used to determine whether the business service corresponding to the operation permissions includes the business service corresponding to the rubber management request sent by the client (100). If so, it invokes the business service corresponding to the rubber management request; otherwise, it refuses to invoke the business service corresponding to the rubber management request.

[0153] Optionally, the client (100) establishes a connection with the backend (200) through the HTTPS protocol.

[0154] Optionally, the device side (300) periodically uploads the data it collects to the database by invoking the data service.

[0155] Refer to Figure 4 as shown Figure 4 This is a schematic structural diagram of the client provided by an embodiment of the present application. In an embodiment of the present application, the structural composition of the client (100) will be described and elaborated below. The client (100) at least includes the following four regions:

[0156] The main region (110) is used to display data charts such as the rubber production and solid content summary and abnormal conditions of each rubber area, authorize subordinate rubber tapping, and initiate rubber operation instructions. It includes a device list (111), permission settings (112), and operation control (113).

[0157] It should be noted that the device list (111) displays relevant information of the device (300). The relevant information of the device (300) includes data corresponding to the rubber tapping operation, data corresponding to the rubber collection operation, the fault analysis result, the working conditions of the rubber tapping operation, and the working conditions of the rubber collection operation. Optionally, the data corresponding to the rubber tapping operation may include, but is not limited to, the number of sub-devices that have successfully completed the rubber tapping operation and the number of sub-devices that have abnormally completed the rubber tapping operation. The data corresponding to the rubber collection operation may include, but is not limited to, the number of sub-devices that have successfully completed the rubber collection operation, the number of sub-devices that have abnormally completed the rubber collection operation, and the rubber output data of the rubber collection operation.

[0158] In one embodiment, in response to the user's selection instruction for the device list (111), the client (100) sends a rubber management request corresponding to the job data service, the fault service, and the status detection service to the backend (200), obtains the relevant information of the device (300), and displays it in the device list (111). Through the device list (111), the user can learn about the conditions of the device (300) performing the rubber collection operation and the rubber tapping operation, and can also learn the fault reasons of the faulty device (300), achieving the purpose of promptly troubleshooting and repairing the device (300).

[0159] It should be noted that the permission setting (112) is used to authorize subordinate rubber tapping. Specifically, the permission setting (112) configures the permission for the client (100) with the second operation permission to call the device management service, or the permission setting (112) configures the permission for the client (100) with the third operation permission to call the device management service.

[0160] In one embodiment, in response to the user's selection instruction for the permission setting (112), the client (100) sends a rubber management request corresponding to the first job authorization service or the second job authorization service to the backend (200), and configures the permission for the client (100) with the second operation permission or the third operation permission to call the device management service.

[0161] It should be noted that the job control (113) is used to initiate a rubber job instruction. Specifically, the rubber job instruction is sent to multiple devices (300) through the job control (113) to control the device (300) to perform the rubber tapping operation or the rubber collection operation.

[0162] In one embodiment, in response to the user's selection instruction for the job control (113), the client (100) sends a rubber management request corresponding to the device management service to the backend (200), and the backend (200) sends the rubber job instruction to the devices (300) bound to multiple clients (100) to control the device (300) to perform the rubber tapping operation and the rubber collection operation.

[0163] Device area (120), which is used to scan the QR code information of the device end (300) through the client (100), view and modify the device information of the device end (300), and debug the device end (300). It includes a QR code scanning sub-area (121), a device debugging unit (122), and a device viewing unit (123).

[0164] It should be noted that by scanning the QR code information of the device end (300) through the QR code scanning sub-area (121), the QR code information is the information set on the device end (300) at the time of factory, and the device information of the device end (300) is obtained. The device information includes the device number of the device end (300), the longitude and latitude position of the device end (300), the client (100) bound to the device end (300), the rubber area information where the device end (300) is located, the information of the installer, and the installation time.

[0165] It should be noted that the device debugging unit (122) is used to perform debugging operations on the device end (300), and burn the programs related to rubber operations into the device end (300). Optionally, the device debugging unit (122) can also be used for the supplier of the device end (300) to remotely upgrade the functions of the device end (300).

[0166] In an embodiment, in response to the user's selection instruction for the device debugging unit (122), the client (100) sends a rubber management request corresponding to the device management service to the backend (200), and invokes the device management service to debug the device end (300), or burn the program into the control board of the device end (300).

[0167] It should be noted that the device viewing unit (123) is used to query, display, and modify the device information. In an embodiment, in response to the user's selection instruction for the device viewing unit (123), the client (100) displays the device information.

[0168] In an embodiment, in response to the user's selection instruction for the QR code scanning sub-area (121), a QR code scanning frame is displayed, and the QR code information is obtained through the QR code scanning frame. After the client (100) analyzes the QR code information, the device number corresponding to the device end (300) is obtained. In response to the user's selection instruction for the device viewing unit (123), the client (100) sends a query request to the backend (200). The query request carries the device number, and the backend (200) calls the device information corresponding to the device number from its database, outputs the device information to the client (100) and displays it. In this embodiment, the entity that processes the QR code information is the client (100), which can effectively reduce the data operation volume and load pressure of the backend (200).

[0169] A message area (130) for displaying relevant notifications such as the completion of rubber tapping, the completion of rubber collection, equipment failures, etc., and contacting the customer service of the supplier of the equipment end (300), which includes an equipment end notification list (131), an exception alarm list (132), and a contact customer service (133).

[0170] It should be noted that the equipment end notification list (131) is used to display equipment notifications. Equipment notifications can include, but are not limited to, notifications of the completion of rubber tapping operations, notifications of the completion of rubber collection operations, notifications of the start of rubber tapping operations, and notifications of the start of rubber collection operations.

[0171] It should be noted that the exception alarm list (132) is used to display fault notifications and monitoring notifications. Fault notifications can include, but are not limited to, the equipment information of the equipment end (300) where a fault occurs and the fault analysis results. Monitoring notifications can include, but are not limited to, the business service information of abnormal calls and the abnormal network traffic conditions.

[0172] In one embodiment, the client (100) obtains equipment notifications, fault notifications, and monitoring notifications by calling a message service and displays them in the message area (130). The client (100) monitors the situation of the equipment end (300) and the backend (200) in real time by receiving notifications. Optionally, Kafla and RocketMQ are used as message middleware for the message service. Kafla refers to a distributed publish-subscribe message system with high throughput, partitionable, and redundant backup, mainly used to process all action flow data in a website. Kafla can collect data generated by web browsing or when searching for a certain keyword, and can also collect log messages and monitoring data. It is one of the more commonly used message middleware in a distributed architecture. RocketMQ is a message middleware with a queue model, featuring high performance, high reliability, high real-time, and distribution. Based on high-availability distributed cluster technology, RocketMQ provides a series of message services such as message subscription and publishing, message trace query, and timed messages, providing the capabilities of asynchronous decoupling and peak shaving and valley filling for distributed application systems.

[0173] A management area (140) for binding and allocating the equipment end (300) and allocating the operation permissions of other clients (100), which includes equipment management (141) and identity management (142).

[0174] It should be noted that the identity management (142) is used to log in to the client (100), generate corresponding permission identifiers, obtain operation permissions corresponding to the permission representations, and call business services corresponding to the operation permissions.

[0175] It should be noted that before logging in to the client (100) through identity management (142), the main area (110), the device area (120), the message area (130), and the device management (141) in the management area (140) are all unavailable.

[0176] In one embodiment, in response to a response instruction from the user for identity management (142), the client (100) obtains the user's information and enables the user to log in to the client (100). When successfully logging in to the client (100), the client (100) will generate a corresponding permission identifier and embed the permission identifier into a permission acquisition request and send it to the backend (200). Subsequently, through the identity management service of the backend (200), the client (100) can obtain the corresponding operation permissions. The user can use the main area (110), the device area (120), and the message area (130) of the client (100) as well as the device management (141) in the management area (140) to call the required business services.

[0177] It should be noted that the device management (141) is used to bind the device side (300) and obtain the device information of the bound device side (300).

[0178] It should be noted that before binding the device side (300) through the device management (141), the main area (110), the device area (120), and the message area (130) are all unavailable.

[0179] In one embodiment, after the client (100) obtains the corresponding operation permissions, in response to a response instruction from the user for device management (141), the client (100) generates a rubber management request corresponding to the device management service and sends it to the backend (200), and completes the binding of the client (100) and the device side (300) by calling the device management service.

[0180] The following uses an example to further illustrate and elaborate on the management of rubber operations using the client (100). First, the user selects the identity management (142) of the management area (140), logs in to the client (100) and obtains the corresponding operation permissions; then selects the device management (141) of the management area (140) and binds multiple device terminals (300) under its management. After binding multiple device terminals (300) under its management, a user with the first operation permission or the second operation permission can select the permission setting (112) to configure the permission to call the device management service for the subordinate client (100); a user with the first operation permission or the second operation permission or the third operation permission controls the device terminals (300) under its management to perform rubber operations by selecting the job control (113), and views the situation of the device terminals (300) performing rubber operations as well as the situation of the backend (200) and the client (100) through the device terminal list (111) and the message area (130). In addition, when the user needs to view the specific device information of the device terminals (300) under its management, the user can obtain the device information by scanning the QR code information of the device terminals (300) through the scanning area, and view the device information by clicking on view device (123). The user can also debug and burn programs for the device terminals (300) by clicking on debug device (122).

[0181] In an embodiment of the present application, the invocation of the business service corresponding to the rubber management request will be described and elaborated below. Step 105 includes at least one of the following:

[0182] When the business service corresponding to the rubber management request is the first job authorization service, a service is provided through the first job authorization service to grant the permission for the client corresponding to the second operation permission to call the device management service.

[0183] In one embodiment, the first job authorization service is only open to the client (100) with the first operation permission. The client (100) with the first operation permission can authorize the client (100) with the second operation permission for the device management service through this service, and the client (100) with the authorized second operation permission can control the rubber operations of multiple device terminals (300) through the device management service.

[0184] When the business service corresponding to the rubber management request is the second job authorization service, a service is provided through the second job authorization service to grant the permission for the client corresponding to the third operation permission to call the device management service.

[0185] In one embodiment, the second job authorization service is only open to clients (100) with the second operation permission. The clients (100) with the second operation permission can authorize the clients (100) with the third operation permission to perform device management services through this service. The clients (100) with the authorized third operation permission can control rubber operations on multiple device terminals (300) through the device management service.

[0186] When the business service corresponding to the rubber management request is the device management service, determine whether there is the permission to call the device management service. When it is determined that there is the permission to call the device management service, provide services such as binding and debugging the device terminal through the device management service, generating a rubber operation instruction and sending it to the device terminal.

[0187] In one embodiment, since the call of the device management service is only open to clients (100) with the permission to call the device management service. Therefore, when the backend (200) receives a rubber management request corresponding to the device management service, first determine whether the client (100) sending the request has the permission to call the device management service. If so, allow the request to call the device management service. If it does not have the permission to call the device management service, reject the request to call the device management service to prevent users without the permission to call the device management service from performing rubber production through the device management service and reduce the possibility of rubber theft.

[0188] When the business service corresponding to the rubber management request is the job data service, provide services such as receiving data corresponding to rubber tapping operations or rubber collection operations from the device terminal through the job data service and generating a data chart based on the data corresponding to the rubber collection operation.

[0189] It should be noted that the job data service is open to clients (100) with the first operation permission or the second operation permission or the third operation permission. In one embodiment, when a client (100) with the first operation permission calls the job data service, it can learn about the rubber operation conditions in all rubber operation areas, which is convenient for controlling the rubber operations of all device terminals (300). In another embodiment, when a client (100) with the second operation permission or the third operation permission calls the job data service, it can learn about the rubber operation conditions in the rubber operation area it manages, so as to facilitate the control of the device terminals (300) it manages. It can be understood that the number of rubber operation areas managed by the clients (100) with the first operation permission, the clients (100) with the second operation permission, and the clients (100) with the third operation permission decreases in turn.

[0190] When the business service corresponding to the rubber management request is a fault service, it is a service that detects the fault situation of the device end at a preset first period through the fault service, analyzes the fault situation, and generates a fault analysis result and a fault notification.

[0191] It should be noted that the fault service is open to clients (100) with the first operation permission, the second operation permission, or the third operation permission. The fault service provides periodic detection of whether there are fault problems in the device end (300). If there are fault problems, it analyzes the causes of the faults, outputs the fault analysis results and fault notifications, and displays them on the client (100). In an embodiment, the user can learn about the device end (300) with faults through the fault notifications displayed on the client (100), so as to timely notify the manager to which the device end (300) belongs to conduct fault troubleshooting and repair on the device end (300) with faults, and avoid delaying rubber operations due to fault problems.

[0192] When the business service corresponding to the rubber management request is a status detection service, it is a service that provides detection of the working conditions of the device end performing the corresponding rubber operations at a preset second period through the status detection service, and generates corresponding device notifications according to the working conditions of the device end (300) performing the corresponding rubber operations.

[0193] It should be noted that the status detection service is open to clients (100) with the first operation permission, the second operation permission, or the third operation permission. The status detection service provides periodic detection of the working conditions of the device end (300) performing the corresponding rubber operations, outputs the corresponding device notifications, and displays them on the client (100). In an embodiment, the user can learn about the working conditions of the device end (300) in the rubber operation area under his management through the device notifications displayed on the client (100), so as to achieve the effect of real-time monitoring and management of rubber operations.

[0194] In an embodiment of the present application, the implementation process of calling component services will be described and elaborated below. The rubber operation management method further includes:

[0195] When calling the business service corresponding to the rubber management request, the backend provides component services according to the corresponding business service.

[0196] It should be noted that the component services include a log service, a message service, a network monitoring service, and a data service.

[0197] Furthermore, providing component services according to the corresponding business service includes:

[0198] Obtaining the operation logs of the client, the backend, and the device end through the log service, and storing the operation logs in the database.

[0199] It should be noted that the operation log is used for troubleshooting the client (100), the backend (200), or the device side (300).

[0200] Monitor the relevant conditions of the backend through the network monitoring service, and generate monitoring notifications based on the relevant conditions of the backend.

[0201] It should be noted that the relevant conditions of the backend at least include the network traffic conditions and the invocation conditions of the business services.

[0202] Forward the monitoring notifications, fault notifications, and device notifications to the client (100) through the message service.

[0203] It should be noted that the message service is used to provide services for receiving monitoring notifications, fault notifications, and device notifications for the client (100) to display relevant notifications. Optionally, the corresponding notifications can be notified to the client (100) in the form of WeChat service notifications, emails, or text messages through the message service.

[0204] Invoke the database of the backend through the data service, obtain the data of the client and the device side through the database, and perform data storage, reading, and aggregation on the data of the client and the device side.

[0205] In this step, the device side (300) periodically uploads the data it collects to the database by invoking the data service. Optionally, the device side (300) collects and uploads data at a cycle of five minutes.

[0206] In this embodiment, the data is transmitted and stored in JSON format. The JSON format can record data formats such as string type, boolean type, numerical type, and array type. Among them, when the data collection fails, the data is marked as NULL type. Due to the limited storage capacity of the device side (300), the device side (300) only temporarily stores the collected data within a certain time range and periodically stores the collected data in the database by invoking the data service. After obtaining the collected data of the device side (300), the backend (200) attaches the corresponding timestamp to the collected data to facilitate reading and aggregating the data according to the timestamp.

[0207] In one embodiment, before the device side (300) leaves the factory, the production information of the device side (300) is entered and uploaded to the database for storage through the client (100) during automated production. When the user uses the device side (300), the production information can be obtained by scanning the QR code information set on the device side (300). Optionally, the client (100) is a computer upper-level software, and the production information is the supplier information and production batch of the device side (300), etc.

[0208] In another embodiment, when installing the device terminal (300), the installer of the device terminal (300) binds the device through the client (100), enters the device information of the device terminal (300), and uploads it to the database for storage. Optionally, the device information includes the device number of the device terminal (300), the longitude and latitude position of the device terminal (300), the client (100) bound to the device terminal (300), the rubber area information where the device terminal (300) is located, the information of the installer, and the installation time, etc. In another embodiment, when using the device terminal (300), the user of the device terminal (300) debugs, controls, and maintains the device terminal (300) through the client (100), and uploads the installation and management information of the device terminal (300) to the database for storage. Optionally, the client (100) is a WeChat mini-program.

[0209] Referring to Figure 5 as shown Figure 5 As shown in the figure is the work flow chart for generating a fault analysis result provided by an embodiment of the present application. In one embodiment of the present application, the implementation process of generating a fault analysis result through a fault service will be described and elaborated below. Detect the fault condition of the device terminal (300) at a preset first period, analyze the fault condition, and generate a fault analysis result, including:

[0210] A. Detect the fault condition of the device terminal at the first period through the fault service, generate current fault data, and store it in the database at the backend;

[0211] B. Call the first prediction model through the fault service, input the current fault data into the first prediction model, and obtain a first fault prediction result.

[0212] It should be noted that the first prediction model is a neural network model based on Xgboost. The first prediction model is pre-trained through the first historical fault data and its manual labels, and the first historical fault data and its manual labels are obtained from the database of the backend (200). XGBoost is an optimized distributed gradient boosting library, which is an improvement to the gradient boosting algorithm. The Newton method is used to solve the extreme value of the loss function, and the loss function is Taylor-expanded to the second order. In addition, a regularization term is added to the loss function. The objective function during training consists of two parts, the first part is the loss of the gradient boosting algorithm, and the second part is the regularization term.

[0213] C. Call the second prediction model through the fault service, input the current fault data into the second prediction model, and obtain a second fault prediction result.

[0214] It should be noted that the second prediction model is a neural network model based on LSTM (Long Short-Term Memory). The second prediction model is pre-trained through the second historical fault data, its manual labels, and timestamps. The second historical fault data, its manual labels, and timestamps are obtained from the database of the backend (200). The long short-term memory neural network is a type of time-recurrent neural network suitable for processing and predicting important events with relatively long intervals and delays in time series.

[0215] D, assign the first weight to the first fault prediction result, assign the second weight to the second prediction result, and accumulate the first fault prediction result with the assigned first weight and the second fault prediction result with the assigned second weight to obtain the initial fault result;

[0216] E, through the fault service call data analysis model, analyze the initial fault result through the data analysis model to obtain the fault analysis result and output a fault notification.

[0217] In this embodiment, in the rubber operation, if there is a fault in the device end (300), the rubber operation cannot be normally executed, which will affect the operation efficiency and progress of the rubber operation. Therefore, timely checking the fault situation and fault causes of the device end (300) is an important part of the rubber operation. In order to timely check the fault situation of the device end (300) and improve the analysis accuracy of the fault causes, this application reads the historical fault data of the device end (300) collected in the past and the manually marked fault results from the database of the backend (200), preprocesses the data, and trains two neural network models through the data related to the fault type in the database to obtain the trained neural network models; analyzes and processes the causes of the fault situation according to these two trained neural network models to obtain the fault type and fault causes corresponding to the fault situation, thereby improving the analysis accuracy of the fault causes and achieving the purpose of timely checking the fault situation of the device end (300).

[0218] In one embodiment, the steps of training the first prediction model based on the Xgboost algorithm to obtain the trained first prediction model specifically include:

[0219] B1, retrieve the first historical fault data and its corresponding manual labels from the database, perform data preprocessing and feature selection on the first historical fault data and its corresponding manual labels, and generate the first sample dataset.

[0220] It should be noted that the manual label refers to the fault type corresponding to the first historical fault data, and the number of fault types is multiple.

[0221] B2. Based on the Xgboost algorithm, construct the first neural network model. Divide the first sample dataset into a first training set and a first test set at a first ratio. Use the first training set as the input of the first neural network model to train the first neural network model and generate a first prediction model.

[0222] Optionally, the first ratio satisfies that the first training set: the first test set = 8:2.

[0223] It should be noted that before training the first neural network model, it is necessary to set the general parameters, booster parameters, learning objective parameters, etc. of the first neural network model. Among them, the general parameters are used to determine the booster selected during the improvement process of the first neural network model, the booster parameters are used to set the type of the booster, and the learning objective parameters are used to control the learning scenario of the first neural network model. The type of booster selected in this application is a tree model.

[0224] Optionally, the process of training the first neural network model is specifically as follows: Initialize the first sample dataset; Define the loss function and calculate the first derivative value of the loss function for each data in the first sample dataset; Build a new decision tree based on the first derivative value; Use the new decision tree to predict the sample value and accumulate it to the original predicted value; Loop the above steps until the set end condition is met to generate the first neural network model.

[0225] B3. Evaluate the performance of the first prediction model according to the first test set and the first evaluation index.

[0226] Optionally, the first evaluation index includes at least accuracy, feature importance, and recall rate.

[0227] B4. Judge whether the accuracy of the first prediction model is greater than or equal to the preset first accuracy threshold; if so, output the first prediction model; if the accuracy of the first prediction model is less than the preset first accuracy threshold, execute step B5;

[0228] B5. Optimize the hyperparameters of the first prediction model and re - execute steps B2 to B5.

[0229] It should be noted that optimizing the hyperparameters of the model can effectively improve the model prediction performance. Since the random combinations of hyperparameters are infinite, the combined optimization of hyperparameters can only obtain a better solution, rather than an optimal solution. The main hyperparameter tuning methods include grid search, random grid search, and Bayesian optimization. Grid search conducts a comprehensive search for all possible enumerations, and can obtain the optimal hyperparameter combination among all enumerated combinations, but it takes too long. Random grid search conducts a certain random search for the possible combinations of hyperparameters, so it runs faster, but the probability of obtaining the "optimal" combination is relatively low. The performance of Bayesian optimization is between the above two methods, running faster and also being able to obtain a better hyperparameter combination. During the hyperparameter tuning process, to avoid the contingency brought by the random division of data, the k-fold cross-validation method is usually combined to train the model, so as to obtain a more reasonable hyperparameter combination.

[0230] Furthermore, preprocessing the data and selecting features for the first historical fault data and its corresponding manual markings to generate the first sample dataset may include but are not limited to the following steps.

[0231] B11, query the null values in the first historical fault data and its corresponding manual markings, and fill them with the median of the column where the null values are located;

[0232] B12, call the scoring function to perform univariate feature selection on the first historical fault data and its corresponding manual markings after filling the null values.

[0233] Optionally, the scoring function is the f_regression() function. The scoring function can also be other scoring functions in the sklearn library, and this application does not make specific limitations on this.

[0234] B13, perform feature selection on the first historical fault data and its corresponding manual markings after univariate feature selection, calculate the Pearson correlation coefficient, and filter out the historical fault data and the manual markings of the historical fault data with a correlation coefficient greater than 10% to generate the first sample dataset.

[0235] It should be noted that during the training of the prediction model, the more the number of features in the data, the longer the time required for analyzing features and training the model, and too many feature numbers are likely to cause the curse of dimensionality, resulting in overfitting of the model. Feature selection is an important part of model training, and its goal is to find the optimal feature subset. Feature selection can eliminate irrelevant or redundant features, so as to reduce the number of features, improve the accuracy of the prediction model, and reduce the running time. In this embodiment, feature selection is performed on the first historical fault data and its corresponding manual markings through a scoring function and the Pearson correlation coefficient in sequence. The scoring function can perform univariate feature selection on the first historical fault data, and the Pearson correlation coefficient can screen out the first historical fault data with low correlation, making the generated first sample data set closer to the data required for fault detection, thereby improving the performance of the first prediction model.

[0236] In one embodiment, the steps of training the second prediction model based on the long short-term memory neural network to obtain the trained second prediction model specifically include:

[0237] C1. Retrieve the second historical fault data, its corresponding manual marking, and time stamp from the database, and divide the second historical fault data and its corresponding manual marking according to the time stamp with a preset first value.

[0238] Optionally, the first value is twenty-four hours.

[0239] In this step, since the second prediction model is a neural network model based on the long short-term memory neural network, it is necessary to obtain the time stamp of the second historical fault data and divide the second historical fault data according to the first value to make it have timeliness.

[0240] C2. Perform data preprocessing and normalization processing on the second historical fault data and its corresponding manual marking to generate a second sample data set;

[0241] C3. Divide the second sample data set into a second training set and a second test set at a second ratio, construct a second neural network model based on the long short-term memory neural network, use the second training set as the input of the second neural network model, train the second neural network model, and generate a second prediction model.

[0242] Optionally, the second ratio satisfies the second training set: the second test set = 8:2.

[0243] In this embodiment, the second neural network model is established based on the long short-term memory neural network. The long short-term memory neural network usually includes a forget gate, an update gate, an output gate, and a current cell state. The three gates work together to complete the selection and forgetting of the feature information of the data in the second sample data set and the update of the current cell state. The feature information is stored in the cell state.

[0244] C4. Evaluate the second prediction model according to the second test set and the second evaluation metric.

[0245] Optionally, set the second evaluation metric based on the mean absolute error and the root mean square error, respectively assign the first sub-weight to the mean absolute error and the second sub-weight to the root mean square error, and calculate the final performance parameter of the second prediction model.

[0246] C5. Determine whether the final performance parameter is greater than or equal to the preset performance parameter threshold; if so, output the second prediction model; if the final performance parameter is less than the performance parameter threshold, then execute step C6.

[0247] C6. Optimize the hyperparameters of the second prediction model, and loop to execute steps C3 to C5.

[0248] In one embodiment, perform data preprocessing and normalization on the second historical fault data and its corresponding manual labels to generate a second sample data set, which specifically includes:

[0249] C21. Search for missing values in the second historical fault data and its corresponding manual labels, and complete the missing values through a regression algorithm.

[0250] In this step, complete the missing values through a regression algorithm, use the missing fields of the fault data and its corresponding manual labels as the target variables for prediction, and obtain the most likely completion values. Optionally, the regression algorithm is a random forest.

[0251] C22. Search for duplicate values and outliers in the second historical fault data and its corresponding manual labels, and discard the duplicate values and outliers.

[0252] In this step, the outliers in the second historical fault data and its corresponding manual labels are defined as feature data outside the set range, and the outliers are also called noise data. Duplicate values are multiple feature data with exactly the same data values.

[0253] C23. Normalize the second historical fault data and its corresponding manual labels to generate a second sample data set.

[0254] In this step, the normalization process is to convert both the second historical fault data and its corresponding manual labels into the same specification, and both the normalized second historical fault data and its corresponding manual labels are within the range of [0, 1].

[0255] Optionally, before training the first neural network model and the second neural network model, the first neural network model and the second neural network model can be co-trained through a learning rate decay function, aiming to make the learning rate in their hyperparameters decrease as the number of iterations increases, so as to ensure that the loss function of the neural network oscillates in a region closer to the optimal value, thereby improving the training efficiency of the neural network.

[0256] The present application also provides a storage medium, which stores instructions executable by a processor. The instructions executable by the processor are used to execute the rubber job management method when executed by the processor.

[0257] In the description of the present application and the above-mentioned drawings, the terms "first", "second", "third", "fourth", etc. (if any) are used to distinguish similar objects, and do not necessarily have to be used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0258] It should be understood that in the present application, "at least one (item)" means one or more, and "a plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships can exist. For example, "A and / or B" can mean: only A exists, only B exists, and both A and B exist at the same time. Among them, A and B can be singular or plural. The character " / " generally means that the associated objects before and after are in an "or" relationship. "At least one (one) of the following" or a similar expression means any combination of these items, including any combination of single items (ones) or plural items (ones). For example, at least one (one) of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0259] In several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. 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 displayed or discussed couplings or direct couplings or communication connections to each other can be indirect couplings or communication connections through some interfaces, devices, or units, and can be in electrical, mechanical, or other forms.

[0260] The units described as separate components may or may not be physically separated. The components displayed as units may or may not be physical units, that is, they can be located in one place or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0261] In addition, in each embodiment of this application, the functional units can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

[0262] If the above-mentioned 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 computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in each embodiment of this application. The foregoing storage medium includes: various media that can store program codes such as read-only memory (ROM for short), random access memory (RAM for short), magnetic disks, or optical discs.

[0263] Regarding the step numbers in the above method embodiments, they are only set for the convenience of elaboration and explanation, and no limitation is imposed on the order between the steps. The execution order of each step in the embodiments can be adaptively adjusted according to the understanding of those skilled in the art.

Claims

1. A rubber operation management method, characterized in that, Including: Initiate a permission acquisition request from the client to the backend. The permission acquisition request carries a permission identifier and is used to invoke the identity management service of the backend; When it is recognized that the permission acquisition request carries the permission identifier, configure the corresponding operation permissions of each user on the client through the identity management service; Among them, the permission identifier includes any one of a first permission identifier, a second permission identifier, or a third permission identifier, and the corresponding operation permissions of the client include any one of a first operation permission, a second operation permission, or a third operation permission; Initiate a corresponding rubber management request from the client to the backend. The rubber management request carries the operation permission and is used to invoke the corresponding business service in the backend; Invoke the interface authentication service through the backend. Identify the operation permission carried by the rubber management request through the interface authentication service and determine the business service corresponding to the operation permission; When it is determined that the business service corresponding to the operation permission includes the business service corresponding to the rubber management request, invoke the business service corresponding to the rubber management request; Among them, the number of business services corresponding to the first operation permission is greater than the number of business services corresponding to the second operation permission, and the number of business services corresponding to the second operation permission is greater than the number of business services corresponding to the third operation permission; Among them, the business services corresponding to the operation permission at least include a first job authorization service, a second job authorization service, a device management service, a job data service, a status detection service, and a fault service; The identifying the operation permission carried by the rubber management request through the interface authentication service and determining the business service corresponding to the operation permission includes: When it is recognized through the interface authentication service that the operation permission is the first operation permission, determine that the business services corresponding to the first operation permission include a first job authorization service, a device management service, a job data service, a status detection service, and a fault service; Or, when it is recognized through the interface authentication service that the operation permission is the second operation permission, determine that the business services corresponding to the second operation permission include a second job authorization service, a device management service, a job data service, a status detection service, and a fault service; Or, when it is recognized through the interface authentication service that the operation permission is the third operation permission, determine that the preset business service corresponding to the third operation permission is a device management service, a job data service, a status detection service, and a fault service; Among them, the invoking the business service corresponding to the rubber management request includes at least one of the following: When the business service corresponding to the rubber management request is the first job authorization service, provide, through the first job authorization service, a service for granting the permission for the client corresponding to the second operation permission to invoke the device management service; When the business service corresponding to the rubber management request is the second job authorization service, a service is provided through the second job authorization service to grant the client corresponding to the third operation permission the permission to call the device management service; When the business service corresponding to the rubber management request is the device management service, it is determined whether there is permission to call the device management service. When it is determined that there is permission to call the device management service, a service is provided through the device management service to bind and debug the device side, and generate and send a rubber job instruction to the device side; Among them, the rubber job instruction is used to control the device side to execute the corresponding rubber job, and the corresponding rubber job includes a rubber tapping job or a rubber collecting job; When the business service corresponding to the rubber management request is the job data service, a service is provided through the job data service to receive data corresponding to the rubber tapping job or the rubber collecting job from the device side, and generate a data chart based on the data corresponding to the rubber collecting job; When the business service corresponding to the rubber management request is the fault service, a service is provided through the fault service to detect the fault condition of the device side at a preset first period, analyze the fault condition, and generate a fault analysis result and a fault notification; When the business service corresponding to the rubber management request is the status detection service, a service is provided through the status detection service to detect the working condition of the device side executing the corresponding rubber job at a preset second period, and generate a corresponding device notification based on the working condition of the device side executing the corresponding rubber job.

2. The rubber operation management method according to claim 1, wherein When it is recognized that the permission acquisition request carries the permission identifier, the identity management service configures the corresponding operation permissions of each user on the client, including: When it is recognized that the permission acquisition request carries the first permission identifier, the identity management service configures the first operation permission of the user on the client; Or, when it is recognized that the permission acquisition request carries the second permission identifier, the identity management service configures the second operation permission of the user on the client; Or, when it is recognized that the permission acquisition request carries the third permission identifier, the identity management service configures the third operation permission of the user on the client.

3. The rubber operation management method according to claim 1, characterized in that The detecting the fault condition of the device side at a preset first period, analyzing the fault condition, and generating a fault analysis result and a fault notification includes: Detecting the fault condition of the device side at a first period through the fault service, generating current fault data and storing it in the backend database; Calling a first prediction model through the fault service, inputting the current fault data into the first prediction model, and obtaining a first fault prediction result; Among them, the first prediction model is a pre-trained neural network model based on Xgboost, and the first prediction model is trained through first historical fault data and its manual labels, and the first historical fault data and its manual labels are obtained through the database; Invoke the second prediction model through the fault service, input the current fault data into the second prediction model, and obtain a second fault prediction result; Among them, the second prediction model is a pre-trained neural network model based on LSTM. The second prediction model is trained through second historical fault data, its manual labels, and timestamps. The second historical fault data, its manual labels, and timestamps are obtained through the database; Assign a first weight to the first fault prediction result, assign a second weight to the second fault prediction result, and accumulate the first fault prediction result with the first weight and the second fault prediction result with the second weight to obtain an initial fault result; Invoke the data analysis model through the fault service, analyze the initial fault result through the data analysis model, obtain the fault analysis result, and output the fault notification.

4. The rubber operation management method according to claim 1, characterized in that, The rubber operation management method further includes: When invoking the business service corresponding to the rubber management request, the backend provides component services according to the corresponding business service; the component services include a log service, a network monitoring service, and a data service; The providing component services according to the corresponding business service includes: Obtain the operation logs of the client, the backend, and the device end through the log service, and store the operation logs in the database; Monitor the network traffic situation and the business service invocation situation of the backend through the network monitoring service, and generate a monitoring notification according to the network traffic situation and the business service invocation situation of the backend; Invoke the database of the backend through the data service, obtain the data of the client and the device end through the database, and perform data storage, reading, and aggregation on the data of the client and the device end.

5. Rubber operation management system, characterized in that, It includes a client, a backend, and a device end. An identity management service, an interface permission service, multiple business services, and component services are set in the backend; The client is used to initiate a corresponding permission acquisition request to the backend. The permission acquisition request carries a permission identifier, and the permission acquisition request is used to invoke the identity management service; The backend is used to, when identifying that the permission acquisition request carries the permission identifier, configure the corresponding operation permissions of each user in the client through the identity management service; Among them, the permission identifier includes any one of a first permission identifier, a second permission identifier, or a third permission identifier; the corresponding operation permissions of the client include any one of a first operation permission, a second operation permission, or a third operation permission; The client is further used to initiate a corresponding rubber management request to the backend. The rubber management request carries the operation permission, and the rubber management request is used to invoke the corresponding business service in the backend; The backend is further used to identify the operation permission carried by the rubber management request through the interface authentication service, and determine the business service corresponding to the operation permission; The backend is further configured to, when it is determined that the business service corresponding to the operation permission includes the business service corresponding to the rubber management request, call the business service corresponding to the rubber management request; Among them, the number of business services corresponding to the first operation permission is greater than the number of business services corresponding to the second operation permission, and the number of business services corresponding to the second operation permission is greater than the number of business services corresponding to the third operation permission; the business services corresponding to the operation permission at least include a first job authorization service, a second job authorization service, a device management service, a job data service, a status detection service, and a fault service; Among them, the first job authorization service is used to grant the client corresponding to the second operation permission the permission to call the device management service; The second job authorization service is used to grant the client corresponding to the third operation permission the permission to call the device management service; The device management service is used to bind and debug the device end, generate a rubber operation instruction and send it to the device end; among them, the rubber operation instruction is used to control the device end to execute the corresponding rubber operation, and the corresponding rubber operation includes a rubber tapping operation or a rubber collection operation; The job data service is used to receive data corresponding to the rubber tapping operation or the rubber collection operation from the device end, and generate a data chart according to the data corresponding to the rubber collection operation; The fault service is used to detect the fault condition of the device end at a preset first period, analyze the fault condition, and generate a fault analysis result and a fault notification; The status detection service is used to detect the working condition of the device end executing the corresponding rubber operation at a preset second period, and generate a corresponding device notification according to the working condition of the device end executing the corresponding rubber operation; The identifying the operation permission carried by the rubber management request through the interface authentication service and determining the business service corresponding to the operation permission includes: When it is identified through the interface authentication service that the operation permission is the first operation permission, it is determined that the business services corresponding to the first operation permission include a first job authorization service, a device management service, a job data service, a status detection service, and a fault service; Or, when it is identified through the interface authentication service that the operation permission is the second operation permission, it is determined that the business services corresponding to the second operation permission include a second job authorization service, a device management service, a job data service, a status detection service, and a fault service; Or, when it is identified through the interface authentication service that the operation permission is the third operation permission, it is determined that the preset business service corresponding to the third operation permission is a device management service, a job data service, a status detection service, and a fault service.

6. The rubber operation management system according to claim 5, characterized in that The backend is further configured to, when the business service corresponding to the rubber management request is the first job authorization service, provide, through the first job authorization service, a service for granting the client corresponding to the second operation permission the permission to call the device management service; The backend is further configured to, when the business service corresponding to the rubber management request is the second job authorization service, provide, through the second job authorization service, a service that grants the client corresponding to the third operation permission the permission to call the device management service; The backend is further configured to, when the business service corresponding to the rubber management request is the device management service, determine whether it has the permission to call the device management service. When it is determined that it has the permission to call the device management service, provide, through the device management service, a service for binding and debugging the device terminal, generating a rubber job instruction, and sending it to the device terminal; The backend is further configured to, when the business service corresponding to the rubber management request is the job data service, provide, through the job data service, a service for receiving data corresponding to the rubber tapping operation or the rubber collection operation from the device terminal and generating a data chart based on the data corresponding to the rubber collection operation; The backend is further configured to, when the business service corresponding to the rubber management request is the fault service, provide, through the fault service, a service for detecting the fault condition of the device terminal at a preset first period, analyzing the fault condition, and generating a fault analysis result and a fault notification; The backend is further configured to, when the business service corresponding to the rubber management request is the status detection service, provide, through the status detection service, a service for detecting the working condition of the device terminal performing the corresponding rubber operation at a preset second period and generating a corresponding device notification based on the working condition of the device terminal performing the corresponding rubber operation; 7. The rubber operation management system according to claim 5, characterized in that, The component service includes a log service, a network monitoring service, and a data service. The backend is further configured to provide the component service according to the corresponding business service when calling the business service corresponding to the rubber management request; Among them, the log service is used to obtain the operation logs of the client, the backend, and the device terminal and store the operation logs in a database; The network monitoring service is used to monitor the network traffic condition of the backend and the invocation condition of the business service, and generate a monitoring notification according to the network traffic condition of the backend and the invocation condition of the business service; The data service is used to call the database of the backend, obtain the data of the client and the device terminal through the database, and perform data storage, reading, and aggregation on the data of the client and the device terminal; 8. The rubber operation management system according to claim 5, characterized in that The client displays a main area, a device area, a message area, and a management area; The main area is provided with a device terminal list, permission settings, and job control. The device terminal list is used to display the data corresponding to the rubber tapping operation or the rubber collection operation of the device terminal, the fault analysis result, and the working condition of the device terminal performing the corresponding rubber operation; The permission settings are used to grant the user corresponding to the second operation permission the permission to call the device management service, or grant the user corresponding to the third operation permission the permission to call the device management service; The job control is used to send rubber job instructions to multiple device terminals; A code scanning sub-region, a device viewing device, and a device debugging device are provided within the device area. The code scanning sub-region is used to scan the QR code information of the device end to obtain the device information of the device end; the device viewing device is used to view the device information of the device end; the device debugging device is used to debug the device end; A device end notification list, an exception alarm list, and a contact customer service are provided within the message area. The device end notification list is used to display device notifications sent by the backend; the exception alarm list is used to display monitoring notifications and fault notifications sent by the backend; Device management and identity management are provided within the management area. The identity management is used to log in to the client and generate a corresponding permission identifier, obtain the operation permissions corresponding to the permission identifier, and call the business services of the backend corresponding to the operation permissions; the device management is used to bind the device end and the client.

9. A storage medium storing instructions executable by a processor, characterized in that, The instructions executable by the processor, when executed by the processor, are used to execute the rubber operation management method according to any one of claims 1-4.

Images