Intelligent operation and maintenance alarm lamp based on Bluetooth

Abstract

The invention relates to a Bluetooth-based intelligent operation and maintenance alarm lamp, and the alarm lamp comprises a permission adaptation decision module which is used for extracting a permission level and a task recording number according to operation and maintenance task information and Bluetooth link information, judging whether the permission meets the requirements or not, carrying out the adaptation evaluation through the combination of a task success rate and an execution frequency relation, verifying the matching state of the current permission and the task condition, and generating a permission allocation state result; the task path verification module is used for calling the permission allocation state result, extracting a path identification field, collecting a physical address of a relay node, constructing a path sequence list, comparing a node sequence and a role structure with a task declaration path, and verifying the consistency of the path structure; if the path structure consistency passes, the light alarm module emits light in a first state, and if the path structure consistency does not pass, the light alarm module emits light in a second state.

Description

Technical Field

[0001] The present invention relates to the field of operation and maintenance alarm lights, and in particular to a Bluetooth-based intelligent operation and maintenance alarm light. Background Art

[0002] The field of permission control encompasses the classification, verification, and control management of access and operational permissions within devices, systems, or operational processes. The core of this technology involves dynamically adjusting and restricting access to critical facilities, equipment, and information based on multiple dimensions, such as identity, operational permissions, and timing, during interactions between personnel and devices, to ensure the security and compliance of system operations.

[0003] Among them, the Bluetooth-based operation and maintenance permission alarm light refers to a system that combines Bluetooth communication technology to dynamically identify the proximity between operators and equipment at the operation and maintenance site. It then lights up different lights based on the operator's assigned permissions to inform the operator whether the operation can be performed. Due to the risks of misoperation and illegal power-on in operation and maintenance scenarios, this system covers close-range identification through Bluetooth signal detection, sending alarms and permission verification requests to the device terminal in real time via the communication link, triggering an alarm device based on the identified human proximity information to remind the operator that the current equipment is in operation and maintenance status, and also includes the transmission of power-off task information, operation time records, and executor identity data through Bluetooth interaction with the device terminal.

[0004] Existing Bluetooth-based access control technologies, in practical scenarios, often rely on a single, close-range identification and static alarm triggering mechanism. These technologies lack a multi-dimensional assessment of the stability and security of the communication link itself, making them susceptible to channel interference or unrecognized spoofed connections, leading to misidentification of illegal connection channels. Furthermore, pre-task access review often relies on a fixed permission level comparison approach, failing to comprehensively assess task complexity, historical execution performance, and the real-time status of the device. This leads to redundant or insufficient permissions, impacting task execution efficiency and security. Regarding path verification, traditional systems often rely on pre-set paths or logical identifiers for comparison, lacking a dual verification mechanism for physical addresses and role structures. This results in insufficient path consistency verification accuracy and the risk of discrepancies between the scheduled path and the actual execution path. Furthermore, the execution phase lacks dynamic alignment between task instructions and the real-time status of the device. This can result in critical instructions being executed despite abnormal device loads or unstable communications, leading to execution failures or equipment damage. For example, in the operation and maintenance of high-voltage power equipment, failure to fully verify the matching of device load status with instruction content can easily lead to serious consequences such as inadvertent power-on, exposing the shortcomings of existing access control systems in terms of refined control and dynamic response.

[0005] The purpose of this invention is to design a Bluetooth-based intelligent operation and maintenance alarm light to solve the problems existing in the above-mentioned prior art. Summary of the Invention

[0006] In response to the problems existing in the above-mentioned prior art, the present invention provides a Bluetooth-based intelligent operation and maintenance alarm light, which can effectively solve at least one problem existing in the above-mentioned prior art.

[0007] The technical solution of the present invention is:

[0008] A Bluetooth-based intelligent operation and maintenance alarm light, comprising:

[0009] The permission adaptation decision module is used to extract the permission level and the number of task records based on the operation and maintenance task information and Bluetooth link information, determine whether the permission meets the requirements, conduct adaptation evaluation based on the relationship between task success rate and execution frequency, verify the matching status of the current permission and task conditions, and generate the permission allocation status result;

[0010] A task path verification module is used to call the permission allocation status result, extract the path identification field, collect the physical address of the relay node, build a path sequence list, compare the node sequence and role structure with the task declaration path, and verify the consistency of the path structure;

[0011] The light alarm module emits light in a first state if the path structure consistency is passed, and emits light in a second state if the path structure consistency is not passed.

[0012] Furthermore, the authority adaptation decision module includes:

[0013] The level extraction submodule obtains the task risk carrying level label, authority level parameters and task record data, detects the number of task records based on the risk label and authority level, establishes a correspondence between the risk label and the authority level, calls the correspondence data for combined judgment, and obtains the task authority matching interval value;

[0014] The adaptation judgment submodule determines whether the success rate is within the interval limit according to the task authority matching interval value, the task success rate and the task execution frequency parameters, calls the joint distribution data of the success rate and the execution frequency, calculates the change gradient and determines the degree of deviation, and obtains the success rate deviation amplitude coefficient;

[0015] The status generation submodule calls the success rate deviation amplitude coefficient and the task authority matching interval value for joint comparison to determine whether the deviation degree is within the allocation judgment limit, marks the result as match or mismatch, and generates the authority allocation status result.

[0016] Furthermore, the specific calculation formula for determining whether the deviation degree is within the allocation judgment limit is:

[0017]

[0018] Calculate the dynamic deviation characteristic value, compare it with the allocation judgment limit threshold, and generate the permission allocation status result; among them, D c represents the comprehensive dynamic deviation eigenvalue, α c Represents the deviation coefficient of the success rate of the state generation submodule call, β m represents the median of the task authority matching interval, γ d represents the dynamic adjustment factor, τ represents the time attenuation coefficient, ε represents the call frequency influence coefficient, δ1 represents the permission request response time dispersion, δ2 represents the sub-module call success rate fluctuation, π represents the historical task matching benchmark constant, and η represents the current task priority weight coefficient.

[0019] Furthermore, the task path verification module includes:

[0020] A path field extraction submodule calls the path identification field in the permission allocation status result, splits the node paragraphs based on the field content, extracts the node number and path sequence information, arranges the node numbers according to the sequence, and generates a path number sequence value;

[0021] The relay node collection submodule calls the path number sequence value, obtains the node name and relay information, extracts the associated address content, matches the node and address according to the number sequence, constructs a corresponding set, and generates a node sequence address list;

[0022] The structure comparison judgment submodule obtains the functional role corresponding to the node according to the node sequence address list, establishes the sequence pairing content of the address and the role, calls the node sequence and structure information in the task declaration path, performs sequence and role consistency judgment, and generates a path structure consistency judgment record.

[0023] Furthermore, it also includes:

[0024] an execution consistency verification module, configured to call the path structure consistency determination record, extract device role information and task instruction content, verify device status and instruction adaptation conditions, verify whether the instruction is executable in the current environment, record task execution conditions, generate a Bluetooth control task executable state identifier, and control the light alarm module to illuminate in a third state;

[0025] The Bluetooth control task executable state identifier includes a device state adaptation condition and an instruction execution environment condition.

[0026] Furthermore, the execution consistency verification module includes:

[0027] The path structure identification submodule obtains the device role and task instruction content in the call path based on the path structure consistency determination record, extracts the instruction type and target identifier, compares the node sequence to screen the combination relationship between the device role and the instruction type, calls the function type corresponding to the role, and generates a role-function matching coefficient value;

[0028] The state adaptation judgment submodule obtains the current state of the device according to the role function matching coefficient value, calls the function parameters in the task instruction, screens the parameter fields that have a dependency relationship with the device state, determines whether there is a relationship within the set condition constraints between the field and the current state, and generates a state instruction adaptation matching value;

[0029] The task status generation submodule calls the device role and task instruction content according to the state instruction adaptation matching value, compares whether the function type pointed to in the task is consistent with the function field in the configuration table, records the combination of matching field and adaptation degree, and generates the Bluetooth control task executable status identifier.

[0030] Furthermore, the status of the light alarm module includes one or more combinations of light color, flashing frequency, and light brightness.

[0031] Furthermore, the Bluetooth link information includes one or more of a Bluetooth communication address, a connection role, and a channel number.

[0032] Furthermore, the operation and maintenance task information includes one or more of device processor load, transmit power, and memory requirements.

[0033] Therefore, the present invention provides the following effects and / or advantages:

[0034] This application is based on Bluetooth and can judge the consistency of the current task path based on the current operation and maintenance task and Bluetooth link information, combined with the authority, historical situation, task level and other information of the operation and maintenance task. According to the situation, the corresponding light will emit light in different states, thereby giving the operation and maintenance operator corresponding status information to prevent misoperation.

[0035] Other features and advantages of the present invention will be described in the following description, and in part will become apparent from the description, or understood by practicing the present invention. The purpose and other advantages of the present invention are realized and obtained by the structures particularly pointed out in the description.

[0036] It is to be understood that both the foregoing general description and the following detailed description of the present invention are exemplary and explanatory and are intended to provide further explanation of the invention as claimed. DETAILED DESCRIPTION

[0037] In order to facilitate understanding by those skilled in the art, the structure of the present invention is further described in detail with reference to the following embodiments:

[0038] A Bluetooth-based intelligent operation and maintenance alarm light, comprising:

[0039] The permission adaptation decision module is used to extract the permission level and the number of task records based on the operation and maintenance task information and Bluetooth link information, determine whether the permission meets the requirements, conduct adaptation evaluation based on the relationship between task success rate and execution frequency, verify the matching status of the current permission and task conditions, and generate the permission allocation status result;

[0040] A task path verification module is used to call the permission allocation status result, extract the path identification field, collect the physical address of the relay node, build a path sequence list, compare the node sequence and role structure with the task declaration path, and verify the consistency of the path structure;

[0041] The light alarm module emits light in a first state if the path structure consistency is passed, and emits light in a second state if the path structure consistency is not passed.

[0042] During the execution of an operation and maintenance task, for example, when an operation and maintenance operation is performed on a device containing multiple switches, operator A may turn one of the switches on or off. When operator B approaches, if the switch is mistakenly turned off or on, the device may be powered on, causing an electric shock to operator A. In this embodiment, when the path structure consistency is passed, it is proved that the currently executed operation and maintenance task and the corresponding Bluetooth link information are matched and legal. At this time, a first state of light, such as blue light, is emitted to inform the operator that the operation and maintenance task at this location matches the operator's authority, operation history, etc., and the operator can operate at this location. When the path structure consistency is not passed, the operation and maintenance task at this location does not match the operator's authority, operation history, etc., and a second state of light, such as flashing red light, is emitted to inform the operator that the switch at this location is not allowed to be operated, thereby preventing the operator from accidentally touching it.

[0043] In this embodiment, extracting the authority level and the number of task records based on the operation and maintenance task information and the Bluetooth link information includes the following steps or modules:

[0044] The Bluetooth link identification module obtains the terminal Bluetooth communication address, connection role and channel number, matches the target device physical address list, determines the legitimacy of the connection channel, detects the communication stability duration and the number of channel hops, verifies the Bluetooth link status, and generates a link credibility status identifier;

[0045] The mission risk assessment module extracts the mission type field based on the link credibility status mark, collects the device processor load, transmit power and memory requirements, and combines the signal strength and communication duration to determine the mission's carryability risk level and generate a mission risk carrying level label;

[0046] The authority adaptation decision module extracts the authority level and the number of task records according to the task risk bearing level label.

[0047] The link credibility status identification includes address legitimacy, role matching, channel stability, and jump number threshold. The task risk carrying level label includes load level, power range, memory threshold, signal strength range, and communication time standard. The authority allocation status result includes authority level matching, task record number threshold, success rate baseline value, and frequency compliance. The path structure consistency judgment record includes node sequence consistency and role structure matching. The Bluetooth control task executable status identification includes device status adaptation conditions and instruction execution environment conditions.

[0048] The Bluetooth link identification module includes:

[0049] The address identification submodule obtains the terminal Bluetooth communication address and the target device physical address list, calls the communication address and physical address fields, compares whether the terminal Bluetooth communication address is in the physical address list, filters the matching address items according to the matching status identification field, and records the corresponding communication identification number to generate the matching address recognition value;

[0050] The address recognition submodule extracts the Bluetooth communication address of the terminal and scans the environment to obtain a list of physical addresses of the target device. Each physical address is in Bluetooth MAC format, such as XX:XX:XX:XX:XX:XX:XX. The terminal's communication address is then compared with each item in the physical address list one by one. The comparison method is to directly perform a complete string consistency match. During the matching process, if the communication address is found to be consistent with a physical address, it is determined to be a valid match. The pre-marked match status field is used for screening, and all address items marked as valid are retained. The communication identification numbers associated with these matching addresses are recorded. The number of successfully matched address items is further counted, and the matching address recognition value is calculated based on the total number of scanned physical addresses. For example, if the total number of scanned addresses is 10 and 3 addresses are successfully matched, the matching recognition value is 30%. All valid matching items are registered in key-value pairs, with the key being the physical address and the value being its communication identification number. During the entire process, the data is cached and stored sequentially by the communication module to ensure that the records of each scan and comparison are completely retained, providing accurate data support for the subsequent association module.

[0051] The role-channel submodule obtains the terminal connection role and corresponding channel number based on the matching address recognition value, calls the connection role identifier and channel mapping number, determines whether the connection role and channel meet the set role-channel rule threshold, calculates the number of connection roles and channel number combinations for the connection relationship that meets the conditions, and generates the connection role-channel matching degree;

[0052] After obtaining the matching recognition value, the role-channel submodule compares it with a set recognition threshold, such as 25%. If the current recognition is greater than or equal to 25%, the subsequent processing flow continues. All connected role numbers and corresponding channel numbers are extracted from the terminal's connection information to form one-to-one matching role-channel combinations. Within the configured role-channel mapping rules, these combinations are determined one by one based on the set conditions. For example, the condition requires that the channel number of the master role should be between 10 and 40. These combinations are checked group by group, and all combinations that meet the conditions are recorded and counted. The number of different role types participating in the communication is also identified. Finally, the number of valid combinations is divided by the total number of possible role-channel combinations to obtain a matching ratio of the connected role-channel. For example, if there are two roles and the system sets the number of available channels to 50, if 10 matching combinations are detected, the matching ratio is 10 divided by 100, or 10%. The total matching ratio value serves as a prerequisite for link reliability analysis and is stored in the parameter management table for subsequent use.

[0053] The link verification submodule obtains the communication stability duration and the number of channel hops based on the connection role channel matching degree, calls the stability duration value and the hop count value, compares whether the stability duration is higher than the stability duration threshold and whether the hop count is lower than the hop count limit, calculates the hop stability coefficient for the link that meets the conditions, and establishes the link credibility status identification;

[0054] After obtaining the channel matching degree of the connection role, the link verification submodule sets a channel matching degree judgment threshold, such as 5%. If the current matching degree is higher than or equal to the threshold, the maximum stable duration of the current communication link in the continuous connection state and the number of channel hopping during this period are further obtained. The stable duration is counted by the continuous online time of the device, and the number of hopping is counted by the channel switching record of the device within a certain time window. For example, if the statistical period is set to 60 seconds and a link jumps 5 times during this period, the number of hopping is 5. The set stable duration threshold is 30 seconds, and the maximum number of hopping is 5. The allowed value is 10 times. Each link is judged to see whether both conditions are met at the same time. If the stability time of a link is 60 seconds and the number of jumps is 5 times, it is considered to be qualified in terms of both judgment criteria. For qualified links, a jump stability coefficient is obtained by dividing the stability time by the number of jumps plus one. If the value is 10, it is compared with the set credibility reference value. For example, if the reference value is 8, the jump stability coefficient of the current link is higher than the reference value, and the link is judged to be in a trustworthy state. A credibility flag is assigned to it and the result is stored in the link flag table for subsequent scheduling in the link selection and management module.

[0055] The mission risk assessment module includes:

[0056] The link marking submodule obtains the link communication status identifier, extracts the task type field, and matches the task type field with the link status information. Based on the link interruption frequency and duration, the link stability is matched with the task requirement level. Based on the matching results, the task link credibility level is determined and the link credibility coefficient is generated.

[0057] First, the link parameters in the data packet are read through the communication protocol stack, including packet loss rate, delay and jitter, etc. The task type field is extracted from the identification segment of the data packet. For example, voice communication can be set to T1, high-definition video transmission is set to T2, and data synchronization task is T3. The relationship between the task type field and the link status is defined by establishing a parameter tolerance model. Different types of tasks have their own acceptable link status thresholds. For example, the T1 task tolerates a packet loss rate less than or equal to 2%, a delay not exceeding 150ms, and a jitter not exceeding 30ms. If the current packet loss rate of a link is 1.5%, the delay is 120ms, and the jitter is 28ms, it is considered to meet the T1 requirement. Then the number of link interruptions and the average interruption duration are monitored. The interruption count statistical period can be set to 30 minutes to record the interruption frequency of the link within the period. If the number of interruptions exceeds 5 times or the average interruption duration exceeds 3s, it is determined to be an unstable link, otherwise it is a stable link. The task requirement level refers to the real-time and continuous nature of the task type itself. For example, the T2 task requires strong link continuity and high real-time performance, with only two interruptions allowed and an average interruption duration of no more than 1 second. Task matching is performed by comparing the current link status with the task requirement level. If the link status meets the task level requirements, the corresponding trust level is high. If it does not fully match, it is downgraded to medium or low. The link trust factor is then calculated using a weighted approach based on the five indicators of packet loss rate, latency, jitter, interruption frequency, and average interruption duration. Each indicator is first converted into a standardized proportion. For example, if the packet loss rate is 1.5% and the maximum tolerance is 10%, the standardization value is 0.15. A delay of 120ms accounts for 0.24 of the maximum reference value of 500ms. The same applies to the remaining indicators. After obtaining their respective proportions, the weights of packet loss rate, latency, jitter, interruption frequency, and interruption duration are set to 0.3, 0.2, 0.1, and 0.2 each for interruption frequency and interruption duration. The link trust factor is calculated using a weighted superposition method, with a total value of approximately 0.815.

[0058] The resource calculation submodule uses the link credibility coefficient to collect information about the device processor load, task transmit power, and memory requirements. It then selects the corresponding resource interval based on the task type, calculates the degree of match between device resource usage and task requirements, and generates a resource matching value.

[0059] The specific calculation formula for the degree of matching between computing device resource usage and task requirements is:

[0060]

[0061] Calculate multi-dimensional adaptation coefficients and generate resource matching values;

[0062] Among them, F represents the resource matching value, η k Indicates the performance conversion rate of the k-th resource (processor / memory / communication), Indicates the real-time available amount of the k-th type of resource of the device. represents the standard requirement benchmark value of the task for the k-th type of resource, θ represents the resource conversion curvature factor, P tx Indicates the current task transmission power, P base Indicates the rated power base of the equipment, ν indicates the power impact attenuation coefficient, Indicates the used capacity of the mth type of memory module. Indicates the total capacity of the mth type of memory module;

[0063] Efficiency conversion rate η k The resource efficiency benchmark table provided by the device manufacturer shows 0.85, 0.72, and 0.91 for the processor, memory, and communication resources, respectively. These values ​​are based on the resource efficiency grading defined in the International Telecommunication Union ITU-TG.1070 standard and are dynamically adjusted based on device model and firmware version updates.

[0064] Real-time availability Real-time data collection is performed through the device monitoring interface. The available processor cores are 6 cores, the available memory capacity is 8GB, and the available communication bandwidth is 50Mbps.

[0065] Standard demand benchmark value The task scheduling system automatically allocates resources based on the task type. The current task requires a 4-core processor, 6GB of memory, and 30Mbps of bandwidth.

[0066] The resource conversion curvature factor θ = 1.2 is set based on the experimental data of the heterogeneous resource scheduling model published in IEEE Transactions on Cloud Computing in 2023. This value varies linearly with task complexity in the range of 1.1-1.3;

[0067] Mission transmission power P tx =24dBm directly measured by wireless module power sensor, rated power reference P base =30dBm Refer to the nominal value in the equipment technical specification;

[0068] The power impact attenuation coefficient ν = 0.8 is determined based on the power efficiency curve in the 3GPP TS 38.101-1 protocol and fluctuates with the ambient temperature within the range of 0.7-0.9;

[0069] Memory usage data is collected through the operating system memory management unit, and the first memory channel has been used Total capacity

[0070] Second memory channel usage Total capacity

[0071] The third memory channel is not enabled.

[0072] Numerator calculation:

[0073] Processor item: (0.85×6 / 4) 1.2 =1.275 1.2 =1.322;

[0074] Memory item: (0.72×8 / 6) 1.2 =0.96 1.2 =0.937;

[0075] Communication item: (0.91×50 / 30) 1.2 =1.517 1.2 =1.643;

[0076] Numerator sum: 1.322 + 0.937 + 1.643 = 3.902;

[0077] Denominator calculation:

[0078] Power ratio item: (24 / 30) 0.8 =0.8 0.8 =0.836;

[0079] Memory usage item:

[0080] First channel: 4 / 8=0.5;

[0081] Second channel: 3 / 8 = 0.375;

[0082] The third channel: 0 / 0=0 (invalid items are eliminated);

[0083] Total of the denominators: 0.836 + 0.5 + 0.375 = 1.711;

[0084] Final calculation: F = 3.902 / 1.711 = 2.281;

[0085] The results show that the resource matching value reached 2.281, exceeding the baseline threshold of 1.0, indicating that the equipment resources meet the current task requirements and have redundancy. The value is positively correlated with the step results and is directly output to the scheduling system as the resource matching value. When the F value is in the range of 0.8-1.2, resource supply and demand are balanced. A value below 0.8 triggers a resource alarm, and a value above 1.2 initiates resource optimization and recovery mechanisms.

[0086] The risk assessment submodule uses the resource matching value and link credibility coefficient to detect the mission signal strength and communication duration. It then determines the mission sustainment capability based on signal changes and communication maintenance. It then combines the sustainment capability with the aforementioned indicators to generate a mission risk-bearing level label.

[0087] After receiving the resource matching and link credibility, the risk assessment submodule continues to collect the task's communication signal strength and communication duration. Signal strength is read as the RSSI indicator in dBm, and communication duration is calculated by logging the complete period of time the device remains connected to the link and calculating the average value. For example, if a task requires a signal strength greater than -65dBm and a communication duration of at least 10 minutes, if the current signal is -60dBm and the communication duration is 12 minutes, the task is considered to have good maintainability and is assigned a value of 1. The resource matching and link credibility are then combined and input into the task risk assessment model. The model weights the three indicators according to a pre-set weight ratio, with resource matching and link credibility each accounting for 40% and maintainability accounting for 20%. This structure derives a comprehensive risk value and sets a risk level range. Risk values ​​between 0 and 0.3 are low risk, 0.3 to 0.6 are medium risk, and above 0.6 are high risk. If the final value is 0.274, the task is marked as low risk.

[0088] The permission adaptation decision module includes:

[0089] The level extraction submodule obtains the task risk carrying level label, permission level parameters and task record data, detects the number of task records based on the risk label and permission level, establishes the corresponding relationship between the risk label and permission level, calls the corresponding relationship data for combined judgment, and obtains the task permission matching interval value;

[0090] The level extraction submodule receives task record data, which contains the task's risk-bearing level label and permission level parameters. It first categorizes tasks based on their IDs and extracts information on both the risk level and permission level dimensions. For example, 100 records are retrieved from the task database, each containing an R level and an L level. The system reads each record individually and counts the number of occurrences of each R and L combination. For example, if L1 corresponds to R1 12 times, R2 9 times, R3 5 times, R4 1 time, and R5 0 times, a frequency table is constructed and the proportion of each combination is calculated. For example, if the combination L2–R3 occurs 10 times, accounting for 10% of the total 100 tasks, a frequency threshold of 5% is set, meaning combinations with a frequency of at least 5 are considered significant. All combinations meeting this threshold are recorded as valid risk-permission correspondences. This relationship is then established as a search rule table. When new task data enters the system, its risk and permission levels are extracted and compared with the combinations in the rule table. If a corresponding combination, such as L2–R2, is found, it is considered a "valid match"; if no record is found, it is considered a "no match." The final matching situation is output as a result with a status label, such as the L2–R2 combination status is "matched" and L4–R5 is "unmatched". The matching interval value will be used for subsequent module processing.

[0091] The adaptation judgment submodule matches the interval value, task success rate, and task execution frequency parameters according to the task authority, determines whether the success rate is within the interval limit, calls the joint distribution data of the success rate and execution frequency, calculates the change gradient, determines the degree of deviation, and obtains the success rate deviation amplitude coefficient;

[0092] The adaptation judgment submodule uses the task authority matching interval value as input. For example, if a task combination is L3–R2, the system recognizes it as a "matching" state. At the same time, it introduces two parameters: task success rate and task execution frequency. For example, if the success rate of a task is 78% and the execution frequency is 45 times, the system presets the success rate range from 70% to 90%. It judges whether the current success rate is within the interval. If 78% is between the upper and lower limits, it is judged as "within the interval". If it is 65%, it is judged as "below the lower limit". Then the joint distribution data is called, in which the success rate is divided into multiple levels of 10%, and the frequency is one level every 10 times. The current task falls into the combination level of 70% to 80% success rate and 40 to 50 frequency. The system retrieves the historical average success rate in this level. For example, the historical average of this level is 75%. The difference between the current success rate and the average is calculated to be 3 percentage points. Combined with the preset change tolerance range, for example, the difference between the upper and lower limits is 20 percentage points, the deviation amplitude is 3÷20, and 0.15 is obtained as the deviation coefficient. If the deviation coefficient is greater than 0.1, it is defined as "significant deviation", otherwise it is defined as "acceptable deviation" or "normal fluctuation". In this example, the deviation coefficient is 0.15, which is judged to be outside the deviation range. The final success rate deviation amplitude coefficient is 0.15.

[0093] The status generation submodule performs a joint comparison between the call success rate deviation coefficient and the task authority matching interval value to determine whether the deviation degree is within the allocation judgment limit. The result is marked as a match or a mismatch, and the authority allocation status result is generated;

[0094] The specific calculation formula for determining whether the degree of deviation is within the allocation judgment limit is:

[0095]

[0096] Calculate the dynamic deviation characteristic value, compare it with the allocation judgment limit threshold, and generate the permission allocation status result; among them, D c represents the comprehensive dynamic deviation eigenvalue, α c Represents the deviation coefficient of the success rate of the state generation submodule call, β m represents the median of the task authority matching interval, γ d represents the dynamic adjustment factor, τ represents the time attenuation coefficient, ε represents the call frequency influence coefficient, δ1 represents the permission request response time dispersion, δ2 represents the submodule call success rate fluctuation, π represents the historical task matching benchmark constant, and η represents the current task priority weight coefficient;

[0097] State generation submodule call success rate deviation coefficient α c The real-time monitoring system shows that the call success rate in the current monitoring period is 92%, and the benchmark success rate is 90%. c =(92%-90%) / 90%=0.0222;

[0098] Task authority matching interval median β m According to the permission management system, the current task permission matching interval is [75,85], and β is calculated. m =(75+85) / 2=80;

[0099] Dynamic adjustment factor γ d According to the dynamic calculation of system load, the current load rate is 65%, according to the linear mapping rule γ d =0.8+0.2×(65% / 100%)=0.93;

[0100] The time decay coefficient τ is calculated based on the task duration. The task has been running for 120 minutes.

[0101] τ=1 / (1+ln(120 / 60+1))≈0.72;

[0102] The call frequency impact coefficient ε is calculated by counting the number of calls in the past 10 minutes as 150 times and the base frequency as 100 times, and the result is ε = 150 / 100 = 1.5;

[0103] The permission request response time dispersion δ1 takes the standard deviation of the response time of the last 100 requests. The measured data is δ1 = 12.5ms;

[0104] The call success rate fluctuation δ2 is calculated as the standard deviation of the call success rate in the past hour, and the statistics are

[0105] δ2=1.8%;

[0106] The historical task matching benchmark constant π is calculated based on the historical database statistics, and the median of the most recent 1000 task matching degrees is π = 78.3;

[0107] The current task priority weight coefficient η is assigned by the task scheduling system. The current task priority level is level 3, corresponding to η = 1.2;

[0108] Substitute into the formula to calculate:

[0109]

[0110] Step-by-step calculation:

[0111] Numerator: 0.93 × 0.0222 = 0.0206;

[0112] Denominator: 0.72 × 1.5 = 1.08;

[0113] First fraction: 0.0206 / 1.08≈0.0191;

[0114] Cube root terms:

[0115] Second fraction: 80 / 2.82≈28.37;

[0116] The third score: 78.3 / 1.2≈65.25;

[0117] Sum in brackets: 28.37 + 65.25 = 93.62;

[0118] Final result: 0.0191×93.62≈1.79;

[0119] The results show that the dynamic deviation characteristic value D c The value is 1.79. When this value exceeds the preset threshold of 1.5, the deviation is determined to exceed the allocation judgment limit, triggering a mismatch in the permission allocation status. The numerical result directly determines the judgment conclusion in step D. During the calculation process, all parameters are obtained from real-time monitoring data, historical statistics, or system configuration parameters; no assumed values ​​are used.

[0120] The task path verification module includes:

[0121] The path field extraction submodule calls the path identification field in the permission allocation status result, splits the node paragraphs based on the field content, extracts the node number and path sequence information, arranges the node numbers according to the sequence, and generates the path number sequence value;

[0122] After the path field extraction submodule obtains the path identification field in the permission allocation status result, it needs to separate and parse the content of the field. For example, if the field format is "number-name-serial number", the string is split into three parts according to "-", corresponding to the node number, node name and path sequence number. For the node number and path sequence number, a corresponding tuple set is constructed and sorted in ascending order according to the path sequence number to ensure that the processing order is consistent with the logical path in the structure. For example, if the field set is "P1-A-2", "P3-B-1", and "P2-C-3", the tuple set {P1,2}, {P3,1}, and {P2,3} are formed after splitting, and the sequence {P3,1}, {P1,2}, and {P2,3} are formed after sorting. The path number sequence composed of the node numbers extracted is

[0123] [P3, P1, P2]. In implementation, the parsing function extracts the corresponding parts based on the field position, and the sorting function arranges the fields according to the path order, ultimately returning a node number sequence. This process is suitable for path management systems with a clear permission structure. In actual device link identity resolution, the fields can be obtained through the interface and the above steps can be performed to complete the standardized processing of the path number sequence for subsequent node information association operations.

[0124] The relay node collection submodule calls the path number sequence value, obtains the node name and relay information, extracts the associated address content, matches the node and address according to the number sequence, builds the corresponding set, and generates a node sequence address list;

[0125] After the relay node acquisition submodule obtains the path number sequence value, it matches the node information and relay attributes one by one according to the sequence number. The system maintains a mapping table of node numbers, node names and relay information, and the matching method is based on a hash search structure. For example, if the input sequence is [P3, P1, P2], the corresponding node name and relay identifier are obtained by looking up the table in sequence. For example, P3 corresponds to "node X" and "R3", P1 corresponds to "node Y" and "R1", and P2 corresponds to "node Z" and "R2". After constructing the relay identifier set, the address information bound to each relay identifier is extracted. The address can be in IPv4 format, such as 192.168.1.1, 192.168.1.2, etc. An address comparison table is established through the search structure to generate a sequential matching set of nodes and addresses. If the sequence is [P3, P1, P2], the corresponding address list is

[0126] ["192.168.1.3","192.168.1.1","192.168.1.2"]. This list is used as the path sequence address list for downstream structure comparison modules. In medium-sized network topology management systems, relay node collection can be achieved through regular updates of mapping tables, interface call address databases, and other methods. Nodes and network addresses are bound together by combining path numbering sequence to ensure the basic integrity of subsequent node functional role positioning.

[0127] The structure comparison judgment submodule obtains the corresponding functional roles of the nodes according to the node sequence address list, establishes the sequence pairing content of the address and role, calls the node sequence and structure information in the task declaration path, judges the consistency of the sequence and role, and generates a path structure consistency judgment record;

[0128] The structure comparison judgment submodule receives the path sequence address list as input, such as

[0129] ["192.168.1.3","192.168.1.1","192.168.1.2"], according to the function information corresponding to each address in the role library, find the role bound to the address, for example, 192.168.1.3 corresponds to "master", 192.168.1.1 corresponds to "gateway", 192.168.1.2 corresponds to "terminal". The address and the function role form an ordered pair to form a pairing structure, such as [(192.168.1.3, master), (192.168.1.1, gateway)

[0130] The system reads the pre-defined structural role order in the task's declared path, such as "Master → Gateway → Terminal," and compares each role in the actual matching order with the declared roles. During the judgment process, a status flag is set for each comparison item, with a consistency value of 1 and a mismatch value of 0. A cumulative consistency count is set and divided by the total number of nodes to form a consistency score. If the roles are consistent, the score is 1. If there is one mismatch, the score is 66.7%, and if there are two mismatches, the score is 33.3%. The consistency judgment threshold is determined based on the network scenario. In environments with frequent node changes, the threshold can be set as low as 60%, while in highly stable environments, it can be set to above 90%. The judgment result is finally recorded with content such as "Path Number: PX-01, Consistency Result: Consistent, Consistency Value: 100%." ​​This judgment process does not rely on external software and is completed through logical comparison and statistical judgment. When deployed in multi-tiered distributed network systems, this method is suitable for verifying whether the path role distribution is consistent with the pre-defined logical structure, helping to identify path changes or abnormal node configurations.

[0131] The modules for performing consistency verification include:

[0132] The path structure identification submodule obtains the device role and task instruction content in the call path based on the path structure consistency judgment record, extracts the instruction type and target identifier, compares the node sequence to screen the combination relationship between the device role and instruction type, calls the function type corresponding to the role, and generates the role-function matching coefficient value;

[0133] First, load a set of standard models of task paths as a reference for path verification. For example, if the path model is set to nodes A, B, C, and D connected in sequence, the current task path must also fully conform to this structure to enter the next stage of processing. Then read the device role bound to each node in the path, such as A for the control unit, B for the data relay, C for the actuator, and D for the monitoring terminal. Then extract key content from the task instruction, including the action type and the target device. For example, if the instruction is "node C performs action X", "action X" is identified as the instruction type, and "node C" is the target device. Next, compare the node roles in the path to filter out nodes with the ability to process this type of instruction, and confirm whether node C supports the functional category to which "action X" belongs. If it does, establish a combination of role and instruction type, and then further call the functional configuration data to check Query the function categories supported by the device. For example, if the actuator has "action" and "feedback" functions, compare the category of the current instruction with the function list of the device, and set the importance ratio of each sub-function. For example, the critical function ratio is set to 50%, the auxiliary function is set to 30%, and the secondary function is set to 20%. Then, based on the device's support for each sub-function, assign values ​​of 1, 0.5, and 0 according to support, partial support, and non-support, respectively. The matching coefficient value is obtained by weighted summation. For example, if the three sub-functions are 1, 0.5, and 0 respectively, and the weights are 50%, 30%, and 20%, the final value is 0.65. According to the interval division standard, if the matching coefficient value is less than 0.4, it is a low match, 0.4 to 0.7 is a medium match, and more than 0.7 is a high match. The value here is in the medium match interval, and the value will be recorded for subsequent processing.

[0134] The state adaptation judgment submodule obtains the current state of the device based on the role function matching coefficient value, calls the function parameters in the task instruction, filters the parameter fields that have a dependency relationship with the device state, determines whether there is a relationship within the set condition constraints between the field and the current state, and generates the state instruction adaptation matching value;

[0135] After obtaining the role-function matching coefficient, the state adaptation judgment submodule must synchronously retrieve the current device operating state. For example, if the current actuator state is "idle," the module then extracts the function parameters from the task instruction. For example, if "Action X" requires an execution time of 3 seconds and a target position of 150 mm, the module must verify whether there are any conditional restrictions between the parameters and the current device state. For example, the device's internal operating rules require a minimum action interval of 2 seconds and a maximum action frequency of 0.5 times per second. The current task requires an execution time of 3 seconds, which meets the action interval restriction and the frequency is within the allowable range. Therefore, the parameter is deemed to meet the dependency condition. Based on the importance of each parameter field, a different weight is assigned, for example, 40% for the execution time field and 60% for the position field. The satisfaction of each condition is converted to a "satisfaction" value, with a "satisfaction" value of 1 and a "failure" value of 0. In this case, both fields are satisfied, resulting in a calculated weighted match value of 1.0. This value falls above the set standard of 0.8, indicating a fully adapted state match level, which serves as the input basis for the next stage.

[0136] The task status generation submodule matches the status instruction adaptation matching value, calls the device role and the task instruction content, compares whether the function type pointed to in the task is consistent with the function field in the configuration table, records the combination of the matching field and the adaptation degree, and generates the Bluetooth control task executable status identifier;

[0137] After receiving the state adaptation matching value, the task state generation submodule combines the function type field involved in the current task. For example, if the instruction requires the execution of the "action type: push and pull" function, it is necessary to first retrieve the function type list registered by the current device from the device configuration table. For example, if device C is registered to support "action type: push and pull, rotation, and fixation", it is compared with the task requirement field item by item. If the task field "push and pull" exists in the configuration table, it is considered that the function field matches successfully. Next, this matching result is combined with the matching value obtained in the previous stage and recorded to form the basis for task state evaluation. Then, it is judged whether the task has entered the executable state. If the role function obtained in the previous stage matches If the value is greater than or equal to 0.7, and the state adaptation value is greater than or equal to 0.8, and the function field matches successfully, the task status flag is 1, indicating that it is executable. If any of the above three conditions is not met, the status flag is 0, indicating that it is not executable. In the actual example, if the role matching value is 0.65 and the state adaptation is 1.0, although the current state of the device fully meets the task requirements, the function matching degree does not meet the high matching standard, so the status flag is set to 0; conversely, if the device role matching value in another task is 0.8, the state adaptation is 0.9, and the function field is completely consistent, the task status flag is set to 1, marking it as the currently executable task.

[0138] Furthermore, the status of the light alarm module includes one or more combinations of light color, flashing frequency, and light brightness.

[0139] Furthermore, the Bluetooth link information includes one or more of a Bluetooth communication address, a connection role, and a channel number.

[0140] Furthermore, the operation and maintenance task information includes one or more of device processor load, transmit power, and memory requirements.

[0141] In this embodiment, as used herein, the term "network element" may be considered synonymous with and / or referred to as:

[0142] It should be noted that in the claims, any reference signs placed between parentheses shall not be construed as limiting the claims. The word "comprising" does not exclude the presence of components or steps not listed in the claim. The word "a" or "an" preceding a component does not exclude the presence of a plurality of such components. The invention can be implemented by means of hardware comprising several different components and by means of a suitably programmed computer. In a unit claim enumerating several means, several of these means may be embodied by one and the same item of hardware. The use of the words first, second, third etc. does not indicate any order. These words may be interpreted as names.

[0143] Although the preferred embodiments of the present invention have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present invention.

[0144] In the present invention, unless otherwise expressly specified or limited, the terms "mounted," "connected," "connect," "fixed," etc. should be understood broadly. For example, they may refer to fixed connection, detachable connection, or integration; mechanical connection or electrical connection; direct connection or indirect connection through an intermediate medium; internal communication between two components or interaction between two components. Those skilled in the art will understand the specific meanings of the above terms in the present invention based on specific circumstances.

[0145] In the description of this specification, the reference terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" mean that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic expressions of the above terms should not be understood as necessarily referring to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art can combine and combine different embodiments or examples described in this specification and features of different embodiments or examples without contradiction.

Claims

1. A Bluetooth-based intelligent operation and maintenance alarm light, characterized by: include: The permission adaptation decision module is used to extract the permission level and the number of task records based on the operation and maintenance task information and Bluetooth link information, determine whether the permission meets the requirements, conduct adaptation evaluation based on the relationship between task success rate and execution frequency, verify the matching status of the current permission and task conditions, and generate the permission allocation status result; A task path verification module is used to call the permission allocation status result, extract the path identification field, collect the physical address of the relay node, build a path sequence list, compare the node sequence and role structure with the task declaration path, and verify the consistency of the path structure; The light alarm module emits light in a first state if the path structure consistency is passed, and emits light in a second state if the path structure consistency is not passed.

2. The Bluetooth-based intelligent operation and maintenance alarm light according to claim 1, characterized in that: The authority adaptation decision module includes: The level extraction submodule obtains the task risk carrying level label, authority level parameters and task record data, detects the number of task records based on the risk label and authority level, establishes a correspondence between the risk label and the authority level, calls the correspondence data for combined judgment, and obtains the task authority matching interval value; The adaptation judgment submodule determines whether the success rate is within the interval limit according to the task authority matching interval value, the task success rate and the task execution frequency parameters, calls the joint distribution data of the success rate and the execution frequency, calculates the change gradient and determines the degree of deviation, and obtains the success rate deviation amplitude coefficient; The status generation submodule calls the success rate deviation amplitude coefficient and the task authority matching interval value for joint comparison to determine whether the deviation degree is within the allocation judgment limit, marks the result as match or mismatch, and generates the authority allocation status result.

3. The Bluetooth-based intelligent operation and maintenance alarm light according to claim 2, characterized in that: The specific calculation formula for determining whether the deviation degree is within the allocation judgment limit is: Calculate the dynamic deviation characteristic value, compare it with the allocation judgment limit threshold, and generate the permission allocation status result; among them, D c represents the comprehensive dynamic deviation eigenvalue, α c Represents the deviation coefficient of the success rate of the state generation submodule call, β m represents the median of the task authority matching interval, γ d represents the dynamic adjustment factor, τ represents the time attenuation coefficient, ε represents the call frequency influence coefficient, δ1 represents the permission request response time dispersion, δ2 represents the sub-module call success rate fluctuation, π represents the historical task matching benchmark constant, and η represents the current task priority weight coefficient.

4. The Bluetooth-based intelligent operation and maintenance alarm light according to claim 3, characterized in that: The task path verification module includes: A path field extraction submodule calls the path identification field in the permission allocation status result, splits the node paragraphs based on the field content, extracts the node number and path sequence information, arranges the node numbers according to the sequence, and generates a path number sequence value; The relay node collection submodule calls the path number sequence value, obtains the node name and relay information, extracts the associated address content, matches the node and address according to the number sequence, constructs a corresponding set, and generates a node sequence address list; The structure comparison judgment submodule obtains the functional role corresponding to the node according to the node sequence address list, establishes the sequence pairing content of the address and the role, calls the node sequence and structure information in the task declaration path, performs sequence and role consistency judgment, and generates a path structure consistency judgment record.

5. The Bluetooth-based intelligent operation and maintenance alarm light according to claim 1, characterized in that: Also includes: an execution consistency verification module, configured to call the path structure consistency determination record, extract device role information and task instruction content, verify device status and instruction adaptation conditions, verify whether the instruction is executable in the current environment, record task execution conditions, generate a Bluetooth control task executable state identifier, and control the light alarm module to illuminate in a third state; The Bluetooth control task executable state identifier includes a device state adaptation condition and an instruction execution environment condition.

6. The Bluetooth-based intelligent operation and maintenance alarm light according to claim 5, characterized in that: The execution consistency verification module includes: The path structure identification submodule obtains the device role and task instruction content in the call path based on the path structure consistency determination record, extracts the instruction type and target identifier, compares the node sequence to screen the combination relationship between the device role and the instruction type, calls the function type corresponding to the role, and generates a role-function matching coefficient value; The state adaptation judgment submodule obtains the current state of the device according to the role function matching coefficient value, calls the function parameters in the task instruction, screens the parameter fields that have a dependency relationship with the device state, determines whether there is a relationship within the set condition constraints between the field and the current state, and generates a state instruction adaptation matching value; The task status generation submodule calls the device role and task instruction content according to the state instruction adaptation matching value, compares whether the function type pointed to in the task is consistent with the function field in the configuration table, records the combination of matching field and adaptation degree, and generates the Bluetooth control task executable status identifier.

7. The Bluetooth-based intelligent operation and maintenance alarm light according to claim 1 or 5, characterized in that: The status of the light alarm module includes one or more combinations of light color, flashing frequency, and light brightness.

8. The Bluetooth-based intelligent operation and maintenance alarm light according to claim 1, characterized in that: The Bluetooth link information includes one or more of a Bluetooth communication address, a connection role, and a channel number.

9. The Bluetooth-based intelligent operation and maintenance alarm light according to claim 1, characterized in that: The operation and maintenance task information includes one or more of device processor load, transmit power, and memory requirement.

Images