Operation and maintenance service boundary control methods, devices, electronic equipment and storage media

By generating service boundary records with version identifiers and verifying operation and maintenance projects and device mounting requests in real time, the problem of lacking real-time automatic contract boundary verification in existing technologies is solved, and the compliance of operation and maintenance services and the automated management of contract performance are realized.

CN123118075APending Publication Date: 2026-11-17SHENZHEN PUHUI ZHIWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611586476.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-10-14
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In existing technologies, the operation and maintenance service management system lacks real-time and automatic contract service boundary verification, which may result in equipment outside the contract being added to the operation and maintenance project, service types not covered by the contract still issuing work orders, and difficulty in timely detection of over-limit, leading to data inconsistency and control failure.

Method used

By acquiring contract data, service boundary records with version identifiers are generated. Operation and maintenance projects and equipment mounting requests are verified in real time. Based on whether the equipment belongs to the service boundary record and whether the service type and quota match, the boundary compliance result is determined. When the risk value reaches the threshold, the request is rejected, an expansion approval task is generated, and the fulfilled amount and remaining quota are updated.

Benefits of technology

It enables real-time automatic verification of contract service boundaries, avoids the post-event exposure of services exceeding the scope, reduces data inconsistencies and credit limit overdrafts, and ensures the compliance of operation and maintenance projects and equipment mounting.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123118075A_ABST
    Figure CN123118075A_ABST
Patent Text Reader

Abstract

This application relates to the field of data processing technology, and in particular to a method, device, electronic device, and storage medium for managing the boundaries of operation and maintenance services. It generates service boundary records with version identifiers by acquiring contract data. When an operation and maintenance project is created or activated, it verifies whether a valid contract and an activated service boundary are bound. If not, the generation of a dispatchable project is prohibited; if successful, a project identifier is bound. When a device is mounted or a work order is created, compliance is determined based on whether the device belongs to a device set, whether the service type and SLA match, and whether the remaining credit limit covers the intended credit limit. If non-compliant, a risk value is calculated; if it reaches a threshold, the application is rejected and no boundary expansion approval is generated; if it does not reach the threshold, a boundary expansion approval is generated. After approval, a new version is generated and re-verified. After the work order is closed, the fulfilled amount and remaining credit limit are updated according to the contract identifier and version identifier conditions; if it fails, a retry or rollback is performed. This application achieves real-time automatic verification of contract service boundaries, avoiding the post-event exposure of services exceeding the scope.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a method, apparatus, electronic device and storage medium for operation and maintenance service boundary management. Background Technology

[0002] In operations and maintenance (O&M) service management, contracts typically stipulate the scope of equipment covered by the service, permitted service types, SLA deadlines, and service limit caps. In existing technologies, contract information is mostly stored in business systems as text or scanned copies; O&M projects, equipment, and work orders are recorded in the O&M logbook. Project creation often relies solely on customer or project identifiers, without mandatory verification of contract validity or expiration. Furthermore, when equipment is mounted and work orders are created, there is no real-time comparison between equipment identifiers, service types, SLA requirements, and quota usage with contract terms. Therefore, equipment outside the contract may still be included in O&M projects, service types not covered by the contract may still generate work orders, and quota overruns are difficult to detect in a timely manner. This results in existing systems lacking the technical means to perform real-time, automatic verification of contract service boundaries during project creation, equipment mounting, and work order creation. Services exceeding the scope can only be exposed during post-event data aggregation, leading to data inconsistencies and control failures. Summary of the Invention

[0003] To overcome the shortcomings of existing technologies, this application provides a method, device, electronic device and storage medium for operation and maintenance service boundary management, which realizes real-time automatic verification of contract service boundaries and avoids the exposure of services exceeding the scope afterward.

[0004] A first aspect of this application provides a method for managing the boundary of operation and maintenance services, the method comprising: Obtain contract data; Generate a service boundary record with a version identifier based on the contract data; In response to a request to create or enable an operations and maintenance project, the system verifies whether the project is bound to a valid contract and whether an enabled service boundary record exists. If the verification fails, the system prohibits the generation of operations and maintenance projects that can be dispatched. If the verification passes, the system binds the project identifier of the operations and maintenance project to the service boundary record. In response to a device mounting request or a work order creation request, the boundary compliance result is determined based on whether the device belongs to the device set in the service boundary record, whether the requested service type and service level protocol match, and whether the remaining quota covers the quota to be occupied. If the boundary compliance result indicates compliance, the device mounting request or work order creation request is allowed; if the boundary compliance result indicates non-compliance, a risk value is calculated. When the risk value reaches a preset threshold, the device mounting request or work order creation request is rejected and no boundary expansion approval task is generated. When the risk value does not reach the preset threshold, a boundary expansion approval task is generated, and a new version of the service boundary record is generated after approval, and the operation of determining the boundary compliance result is returned. After the work order is closed, the fulfilled amount and remaining quota in the service boundary record are updated according to the contract identifier and version identifier conditions. If the condition update fails, a retry or rollback alarm is issued.

[0005] In an optional implementation, the determination of boundary compliance results includes: Determine the device boundary indicator: when the device belongs to the set of devices, the device boundary indicator is set to 1; otherwise, the device boundary indicator is set to 0. The Service Type Inbound Indicator is set to 1 when the requested service type is an allowed service type and the requested service level agreement time limit does not exceed the remaining service level agreement time limit budget; otherwise, the Service Type Inbound Indicator is set to 0. The credit limit coverage ratio is determined as follows: when the remaining credit limit is not less than the intended credit limit, the credit limit coverage ratio is 1; otherwise, the credit limit coverage ratio is the ratio of the remaining credit limit to the intended credit limit and does not exceed 1. The boundary compliance score is determined based on the device boundary indication, the service type boundary indication, and the quota coverage rate. When the boundary compliance score is equal to 1, the boundary compliance result is determined to be compliant. When the boundary compliance score is less than 1, the boundary compliance result is determined to be non-compliant.

[0006] In an optional implementation, determining the coverage rate of the credit limit includes: The coverage rate of the credit limit is determined using the following formula: ρ = min(1, Qr / max(ε, Δq)); Where ρ is the coverage rate of the quota, Qr is the remaining quota, Δq is the quota to be occupied, and ε is the amount to prevent zero division and has the same dimension as Δq; When Δq≤0, the coverage rate of the quota is 1, and the service type boundary indication of the device boundary indication still needs to be satisfied.

[0007] In an optional implementation, the calculation of the risk value includes: Obtain the device out-of-bounds weight, the service type out-of-bounds weight, and the insufficient quota weight, wherein the device out-of-bounds weight, the service type out-of-bounds weight, and the insufficient quota weight are all non-negative and their sum is 1; The degree of device boundary violation is determined based on the device boundary indicator, the degree of service type boundary violation is determined based on the service type boundary indicator, and the degree of credit insufficiency is determined based on the credit coverage rate. A first risk component is determined based on the degree of device boundary violation and the weight of device boundary violation; a second risk component is determined based on the degree of service type boundary violation and the weight of service type boundary violation; and a third risk component is determined based on the degree of insufficient credit and the weight of insufficient credit. The risk value is determined based on the first risk component, the second risk component, and the third risk component.

[0008] In one optional implementation, the contract data includes a contract identifier, validity period, service level agreement information, equipment scope information, service type, and maximum limit. The contract data also includes contract status, which includes at least draft, pending, effective, suspended, and expired; the method further includes: When a contract is in a pending state, if the contract's agreed-upon effective time is reached, the service level agreement information and device scope information have been bound, and the service boundary record has been enabled, the contract status will be automatically changed to an effective state. When a contract is in effect, if the agreed expiration date is reached, the contract status will automatically change to expired. When a contract is in effect, if a suspension instruction is received and the reason is recorded, the contract status will be changed to a suspended status. When a contract is suspended, reject new requests for creating or enabling maintenance projects, device mounting requests, and work order creation requests. Allow executed work orders to be closed and written back, but prohibit the creation of new work orders. When a contract is in an expired state, requests to create or activate maintenance projects, mount equipment, and create work orders will be rejected. Unclosed work orders will be carried over or closed according to the contract and will not be subject to new quota.

[0009] In an optional implementation, the equipment scope information includes inclusion rules and exclusion rules, each of which includes at least one of an asset identification list, a location code, and a category code; generating a service boundary record with a version identifier based on the contract data includes: The asset data source is invoked to expand the location code and category code into an in-service asset identifier; The set of devices is obtained by taking the union of multiple asset identifiers that are included in the rule and then subtracting the asset identifiers that are excluded from the rule. If the set of devices is empty, the location or category does not exist in the asset data source, or the asset data source query times out or the set is empty after exclusion, then the service boundary record is not enabled. If the set of devices is not empty and each rule can be applied to a known asset, then the service boundary record is enabled and the set of devices is persisted to the current version; Once the service boundary record is enabled, newly registered devices at the same location or of the same type will not be automatically added to the current version. Instead, they will be added through the generation of a new version of the service boundary record or by an expansion approval task.

[0010] In an optional implementation, generating a service boundary record with a version identifier based on the contract data further includes: The service boundary record is enabled only when both the service level agreement information and the device range information are bound. When the contract data includes multiple attachments, the attachments are merged according to the priority of the clauses, and conflicting items are marked as pending review and disabled.

[0011] A second aspect of this application provides an apparatus for managing the boundary of operation and maintenance services, the apparatus comprising: The data acquisition module is used to acquire contract data; The boundary generation module is used to generate service boundary records with version identifiers based on the contract data. The entry verification module is used to respond to the creation or activation request of the operation and maintenance project, and to verify whether the operation and maintenance project is bound to a valid contract and whether there is an enabled service boundary record. If the verification fails, the generation of an operation and maintenance project that can be dispatched is prohibited. If the verification passes, the project identifier of the operation and maintenance project is bound to the service boundary record. The order verification module is used to respond to device mounting requests or work order creation requests, and determine the boundary compliance result based on whether the device belongs to the device set in the service boundary record, whether the requested service type and service level protocol match, and whether the remaining quota covers the quota to be occupied. The risk triage module is used to allow the device mounting request or work order creation request if the boundary compliance result indicates compliance; if the boundary compliance result indicates non-compliance, calculate the risk value; when the risk value reaches a preset threshold, reject the device mounting request or work order creation request and do not generate an expansion approval task; when the risk value does not reach the preset threshold, generate an expansion approval task, and generate a new version of the service boundary record after approval, and return to execute the operation of determining the boundary compliance result. The fulfillment write-back module is used to update the fulfilled amount and remaining quota in the service boundary record according to the contract identifier and version identifier after the work order is closed. If the condition update fails, a retry or rollback alarm will be issued.

[0012] A third aspect of this application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the operation and maintenance service boundary control method.

[0013] A fourth aspect of this application provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the above-described operation and maintenance service boundary control method.

[0014] In summary, the operation and maintenance service boundary management method, device, electronic equipment, and storage medium provided in this application first acquire contract data and generate service boundary records with version identifiers based on the contract data. This transforms the contractual agreements originally stored in external contract data sources into boundary data that can be read and verified by the computer system, and uses the version identifier to lock the boundary status. Secondly, when an operation and maintenance project is created or activated, it verifies whether the project is bound to a valid contract and whether an activated service boundary record exists. If the verification fails, the generation of dispatchable operation and maintenance projects is prohibited. If the verification passes, the project identifier is bound to the service boundary record. Thus, automatic verification of contract validity and boundary activation status is completed at the project entry point, preventing the generation of dispatchable projects when the contract is not effective, expired, or the boundary is not activated. Secondly, during device mounting or work order creation, the boundary compliance result is determined based on whether the device belongs to the device set in the service boundary record, whether the requested service type and service level agreement match, and whether the remaining quota covers the intended quota. This moves contract service boundary verification to the device mounting and work order creation stages, enabling real-time and automatic judgment. For non-compliant requests, a risk value is further calculated. When the risk value reaches a preset threshold, the request is directly rejected without generating an expansion approval task. When the risk value does not reach the preset threshold, an expansion approval task is generated, and after approval, a new version of the service boundary record is generated and the boundary compliance result is re-determined. This prevents out-of-scope requests from being executed directly without being recorded. Finally, after the work order is closed, the fulfilled amount and remaining quota in the service boundary record are updated according to the contract identifier and version identifier conditions. If the condition update fails, a retry or rollback alarm is triggered, ensuring that the fulfilled amount is written back in a timely manner and preventing quota overdraft. Thus, by establishing a closed loop of "contract data acquisition - versioned service boundary record generation - entry verification - real-time entry boundary verification - risk diversion - performance write-back", the technical problems of existing systems lacking real-time and automatic boundary verification and out-of-scope services only being exposed after the fact are solved. Attached Figure Description

[0015] Figure 1 This is a flowchart illustrating one of the operation and maintenance service boundary control methods in an embodiment of this application; Figure 2This is a second flowchart illustrating a method for managing the boundary of operations and maintenance services, as shown in an embodiment of this application. Figure 3 This is a schematic diagram of the third process of an operation and maintenance service boundary control method shown in the embodiments of this application; Figure 4 This is a functional block diagram of an operation and maintenance service boundary control device shown in an embodiment of this application; Figure 5 This is a schematic diagram of the structure of an electronic device shown in an embodiment of this application. Detailed Implementation

[0016] The present application will be further described below with reference to the accompanying drawings and embodiments.

[0017] The following will clearly and completely describe the concept, specific structure, and resulting technical effects of this application in conjunction with embodiments and accompanying drawings, so as to fully understand the purpose, features, and effects of this application. Obviously, the described embodiments are only a part of the embodiments of this application, not all of them. Other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are all within the scope of protection of this application. Furthermore, all connections / linkages involved in the patent do not simply refer to direct contact between components, but rather to the ability to form a better connection structure by adding or reducing connecting accessories according to specific implementation conditions. The various technical features in this application can be combined interactively without contradicting each other.

[0018] The operation and maintenance service boundary control method provided in this application will be further described below with reference to the accompanying drawings and specific embodiments. The method of this embodiment can run on a regular server, which can communicate and connect with the contract system, asset ledger, and work order system, and is not limited to dedicated hardware. Figure 2 As shown, the system block diagram includes components such as contract number pre-setting, clause binding SLA and equipment scope, service boundaries, operation and maintenance project entry verification, equipment and work order entry, out-of-scope approval, and performance volume write-back; for example Figure 3 As shown, the system process includes: pre-entry of contract number, binding terms to SLA and generating service boundaries with equipment scope, determining whether the maintenance project entry is bound to a valid contract, determining whether the equipment or work order falls within the service boundary, determining whether the risk of exceeding the scope reaches the hard interception threshold, releasing the entry, writing the performance volume back to the contract and refreshing the remaining amount, approving the expansion of the scope, approving the expansion of the scope, and hard intercepting the entry of the project. Among them, pre-entry of contract number corresponds to S1, binding terms to SLA and generating service boundaries with equipment scope corresponds to S2, determining whether the maintenance project entry is bound to a valid contract corresponds to S3, determining whether the equipment or work order falls within the service boundary corresponds to S4, determining whether the risk of exceeding the scope reaches the hard interception threshold corresponds to S5, writing the performance volume back to the contract and refreshing the remaining amount corresponds to S6, and approving the expansion of the scope returns to S2 to regenerate a new version of the service boundary record.

[0019] To facilitate understanding of the technical solution of this application, the symbols and key technical parameters used in this embodiment are explained as follows. Table 1 is a symbol table for equipment, type and quota, Table 2 is a symbol table for equipment, type and quota, and Table 3 is a table of key technical parameters.

[0020] Table 1:

[0021] Table 2:

[0022] Table 3:

[0023] The values ​​in the table above do not constitute specific limitations. When implementing the quota, the quota can be calculated by the number of times, the number of units, or the amount, as long as the dimensions of ε and Δq are consistent.

[0024] Reference Figures 1 to 3 The diagram shown is a flowchart illustrating an operation and maintenance service boundary control method according to an embodiment of this application. The operation and maintenance service boundary control method includes the following steps.

[0025] S1, Obtain contract data.

[0026] The system acquires contract data, which includes contract identifier, validity period, service level agreement information, equipment scope information, service type, and maximum limit. The contract identifier is, for example, the contract number; the service level agreement information includes response time and repair time limits; the equipment scope information includes equipment identification lists, location codes, or category codes; the service type includes repair, inspection, and emergency services; and the maximum limit is denoted as Qc. Figure 2 As shown, the contract number is placed at the beginning of the process to obtain contract data before generating service boundaries and performing operation and maintenance project entry verification. Figure 3 As shown, the process begins with the pre-entry of the contract number. Only after the contract data is entered can the terms binding SLA and equipment scope generation service boundary be performed.

[0027] In an optional implementation, the contract data further includes contract status, which includes at least draft, pending, effective, suspended, and expired; the method further includes: When a contract is in a pending state, if the contract's agreed-upon effective time is reached, the service level agreement information and device scope information have been bound, and the service boundary record has been enabled, the contract status will be automatically changed to an effective state. When a contract is in effect, if the agreed expiration date is reached, the contract status will automatically change to expired. When a contract is in effect, if a suspension instruction is received and the reason is recorded, the contract status will be changed to a suspended status. When a contract is suspended, reject new requests for creating or enabling maintenance projects, device mounting requests, and work order creation requests. Allow executed work orders to be closed and written back, but prohibit the creation of new work orders. When a contract is in an expired state, requests to create or activate maintenance projects, mount equipment, and create work orders will be rejected. Unclosed work orders will be carried over or closed according to the contract and will not be subject to new quota.

[0028] In some embodiments, when a contract is in a pending state, if the agreed-upon effective time is reached, the service level agreement information and device scope information are bound, and service boundary records are enabled, the contract status is automatically changed to an effective state. When a contract is in an effective state, if the agreed-upon expiration time is reached, the contract status is automatically changed to an expired state. When a contract is in an effective state, if a suspension instruction is received and the reason is recorded, the contract status is changed to a suspended state. When a contract is in a suspended state, new requests for creating or enabling maintenance projects, device mounting requests, and work order creation requests are rejected. Executed work orders are allowed to be closed and written back, but new work orders are prohibited. When a contract is in an expired state, requests for creating or enabling maintenance projects, device mounting requests, and work order creation requests are rejected. Unclosed work orders are carried over or closed according to the contract and cannot occupy new quotas. Multiple contracts for the same customer are entered separately and numbered separately, and the device lists do not overwrite each other.

[0029] For ease of understanding, the contract status transition relationships are shown in Table 4. As can be seen, contract status transition relationships include draft to pending effectiveness, draft to effective, pending effectiveness to effective, pending effectiveness to draft, effective to suspended, effective to expiration, suspended to expiration, and draft or pending effectiveness to expiration.

[0030] Table 4:

[0031] S2, Generate a service boundary record with a version identifier based on the contract data.

[0032] like Figure 2 As shown, after the terms are bound to the SLA and the equipment scope, a service boundary is generated. This service boundary is used for subsequent maintenance project entry verification and for reading equipment and work order entries. The service boundary record includes the equipment set, allowed service types, service level agreement time limit budget, maximum credit limit, fulfilled amount, and remaining credit limit.

[0033] Specifically, the response time limit, repair time limit, allowed equipment identifiers or categories, allowed service types, and maximum credit limit (Qc) are extracted from the contract text or appendices. The Service Agreement (SLA) is then bound to the equipment scope to generate a service boundary. The service boundary uses the contract identifier plus a version identifier as keys, recording the currently valid equipment set, service type, SLA time limit budget, maximum credit limit (Qc), fulfilled amount (Qu), and remaining credit limit (Qr). Qu is initialized to 0, Qr to Qc, and a version identifier is added. For example... Figure 2 As shown in the system block diagram, after "Binding Terms and Conditions to SLA and Equipment Scope", a "Service Boundary" is generated. Figure 3 As shown, the terms are bound to the SLA and the equipment scope to generate the service boundary. After the scope is expanded due to an approval, the process returns to this step to regenerate a new version of the service boundary record. The symbols Qu, Qr, Qc, Δq, etc. can be found in Table 1, the compliance score, risk score, and write-back symbols can be found in Table 2, and the key technical parameters can be found in Table 3.

[0034] When generating service boundary records, service boundary records are only enabled if both service level agreement information and device scope information are bound. Records with only time limits and no inventory, or only inventory and no time limits, are considered unbound and inbound validation cannot be used. When contract data includes multiple attachments, they are merged according to clause priority, and conflicting items are marked as pending review and disabled.

[0035] In some embodiments, the equipment scope information includes inclusion rules and exclusion rules, each including at least one of an asset identifier list, a location code, and a category code. Generating a service boundary record with a version identifier based on contract data includes: calling an asset data source, expanding the location code and category code into in-service asset identifiers; taking the union of multiple asset identifiers matched by inclusion rules, and then subtracting the asset identifiers matched by exclusion rules to obtain the equipment set D. Specifically, the location rule extracts all in-service asset identifiers from the ledger for that location; the category rule extracts all in-service asset identifiers for that category; taking the union of multiple inclusion rules, and then subtracting the identifiers matched by exclusion rules to obtain the equipment set D. If an identifier in the asset identifier list cannot be found in the ledger or has been scrapped, it is recorded as an expansion failure and cannot be considered as in-boundary.

[0036] If the equipment set D is empty, the location or category does not exist in the asset data source, the asset data source query times out, or the set is empty after exclusion, then service boundary records are not enabled. If the equipment set D is not empty and each rule can be applied to a known asset, then service boundary records are enabled, and equipment set D is fixed to the current version. After service boundary records are enabled, newly recorded equipment at the same location or of the same category is not automatically added to the current version; it is only added through the generation of a new version of service boundary records or through an expansion approval task.

[0037] Once the boundary is enabled, changes to the list, rules, or weights can only be made through approval beyond the scope or by releasing a new version; they cannot be made directly without a record.

[0038] When generating a service boundary record, the device out-of-bounds weight α, service type out-of-bounds weight β, insufficient quota weight γ, and hard interception threshold τ are also written into that version. The weights are non-negative and α+β+γ=1. Default values ​​can be α=0.5, β=0.3, γ=0.2, and τ=0.6, and are allowed to be overridden by contract. Overriding these default values ​​is achieved by generating a new version of the service boundary record. Furthermore, if the weights or thresholds need to be changed, only a new version can be generated; the old, already enabled version cannot be modified. Work orders that have already been generated will still be interpreted according to the α, β, γ, and τ values ​​used at the time the order was created, and the risk value will not be recalculated or overturned due to subsequent weight changes. Only newly created work orders will read the new weights from the currently enabled version. The values ​​of α, β, γ, and τ can be found in Table 3.

[0039] S3, responding to the request to create or enable an operation and maintenance project, verifies whether the operation and maintenance project is bound to a valid contract and whether there is an enabled service boundary record.

[0040] If the verification fails, the generation of dispatchable maintenance projects is prohibited; if the verification passes, the project identifier of the maintenance project is bound to the service boundary record.

[0041] In some embodiments, combined with Figure 2 At the "Operation and Maintenance Project Entry Verification" stage, when an operation and maintenance project creation or activation request is received, entry verification is performed. Specifically, the following three items are verified: First, whether the operation and maintenance project is bound to a contract identifier; second, whether the bound contract is in effect and within its validity period; and third, whether an enabled service boundary record exists. If any of the above three verifications fails, the generation of an operation and maintenance project that can be dispatched is prohibited, meaning that the operation and maintenance project cannot enter the subsequent equipment mounting and work order creation process. If all three verifications pass, the project identifier of the operation and maintenance project is written into the project binding table of the service boundary record, thus binding the operation and maintenance project to the service boundary record. Figure 3 As shown, at the "Whether the operation and maintenance project entry is bound to a valid contract" judgment, if it is yes, then proceed to the judgment of whether the equipment or work order falls into the service boundary; otherwise, execute the no-contract interception project creation.

[0042] In an optional implementation, the contract data further includes contract status, which includes at least draft, pending, effective, suspended, and expired. Only contracts in the effective state and within their validity period are allowed to pass the entry verification; contracts in the draft, pending, suspended, and expired states cannot be used to generate dispatchable maintenance projects. When a contract is suspended, new maintenance project creation or activation requests, device mounting requests, and work order creation requests are rejected; executed work orders are allowed to be closed and written back, but new work orders are prohibited. When a contract is expired, maintenance project creation or activation requests, device mounting requests, and work order creation requests are rejected; unclosed work orders are carried over or closed according to the contract agreement and cannot occupy new quotas.

[0043] In one optional implementation, an operations and maintenance project is bound to only one master contract at a time. When multiple contracts exist for the same customer, the project is split into sub-projects by device, or priorities are set in the service boundary record. Device sets from different contracts are not mixed and attached to the same project, and their origins are not marked. When a project changes contracts, it is considered a re-entry; work orders that have not been closed on the old service boundary are carried over or closed first.

[0044] In some embodiments, after entry verification, subsequent device mounting requests and work order creation requests under the maintenance project all undergo entry verification. This involves determining the boundary compliance result based on whether the device belongs to the device set in the service boundary record, whether the requested service type and service level agreement match, and whether the remaining quota covers the intended quota. Thus, entry verification intercepts invalid contracts and inactive service boundaries at the maintenance project entry point, preventing the generation of dispatchable maintenance projects when contracts are ineffective, expired, suspended, or service boundaries are not enabled.

[0045] S4. In response to a device mounting request or a work order creation request, determine the boundary compliance result based on whether the device belongs to the device set in the service boundary record, whether the requested service type and service level protocol match, and whether the remaining quota covers the quota to be occupied.

[0046] In some embodiments, combined with Figure 2 At the "Device and Work Order Entry" section, when a device mounting request or work order creation request is received, the currently enabled service boundary records are read, and the following judgments are performed: whether the device belongs to the device set in the service boundary record, whether the requested service type and service level protocol match, and whether the remaining quota covers the intended quota; the boundary compliance result is determined based on the above judgment results. If the boundary compliance result indicates compliance, the device mounting request or work order creation request is allowed; if the boundary compliance result indicates non-compliance, subsequent risk value calculation and traffic diversion processing are initiated. Figure 3As shown, at the "Whether the operation and maintenance project entry is bound to a valid contract" judgment, if it is yes, then proceed to the judgment of whether the equipment or work order falls into the service boundary; otherwise, execute the no-contract interception project creation.

[0047] In an optional implementation, the determination of boundary compliance results includes: Determine the device boundary indicator: when the device belongs to the set of devices, the device boundary indicator is set to 1; otherwise, the device boundary indicator is set to 0. The Service Type Inbound Indicator is set to 1 when the requested service type is an allowed service type and the requested service level agreement time limit does not exceed the remaining service level agreement time limit budget; otherwise, the Service Type Inbound Indicator is set to 0. The credit limit coverage ratio is determined as follows: when the remaining credit limit is not less than the intended credit limit, the credit limit coverage ratio is 1; otherwise, the credit limit coverage ratio is the ratio of the remaining credit limit to the intended credit limit and does not exceed 1. The boundary compliance score is determined based on the device boundary indication, the service type boundary indication, and the quota coverage rate. When the boundary compliance score is equal to 1, the boundary compliance result is determined to be compliant. When the boundary compliance score is less than 1, the boundary compliance result is determined to be non-compliant.

[0048] In some embodiments, in response to a device mounting request or a work order creation request, the current service boundary is read, the device boundary indication u, the service type boundary indication v, and the quota coverage rate ρ are determined, and the boundary compliance result is determined.

[0049] Determine the device boundary indicator u: when the device belongs to the set of devices, the device boundary indicator is 1, otherwise it is 0.

[0050] Determine the service type boundary indicator v: when the requested service type is an allowed service type and the requested service level agreement duration does not exceed the remaining service level agreement duration budget, the service type boundary indicator is set to 1, otherwise it is set to 0.

[0051] Determine the credit limit coverage rate ρ: When the remaining credit limit is not less than the intended credit limit, the credit limit coverage rate is 1; otherwise, the credit limit coverage rate is the ratio of the remaining credit limit to the intended credit limit and does not exceed 1.

[0052] Specifically, the coverage ratio ρ can be determined using the following formula: ρ=min(1,Qr / max(ε,Δq)); Where ρ is the coverage rate of the credit limit, Qr is the remaining credit limit, Δq is the proposed credit limit, and ε is the amount to prevent zero division and has the same dimension as Δq, for example, ε = 0.01 times.

[0053] When Δq≤0, the quota coverage rate is 1, but the device in-boundary indicator and the service type in-boundary indicator still need to be satisfied. Pure queries with Δq≤0 do not occupy quota, ρ is counted as 1, but the device and service type still need to be in-boundary.

[0054] The boundary compliance score s is determined based on the device boundary indication, the service type boundary indication, and the credit limit coverage rate. The boundary compliance score s is the minimum value among u, v, and ρ, that is: s=min(u,v,ρ).

[0055] When the boundary compliance score is equal to 1, the boundary compliance result is determined to be compliant; when the boundary compliance score is less than 1, the boundary compliance result is determined to be non-compliant. If any of the equipment, type, or limit is insufficient, the order cannot be directly processed.

[0056] S5. If the boundary compliance result indicates compliance, allow the device mounting request or work order creation request; if the boundary compliance result indicates non-compliance, calculate the risk value.

[0057] When the risk value reaches the preset threshold, the device mounting request or work order creation request is rejected and no boundary expansion approval task is generated. When the risk value does not reach the preset threshold, a boundary expansion approval task is generated, and a new version of the service boundary record is generated after approval, and the operation of determining the boundary compliance result is returned.

[0058] In some embodiments, if the boundary compliance result indicates compliance (s=1), the device mounting request or work order creation request is allowed, the device is successfully mounted or the work order is executed, and step S6 is executed after the work order is closed. If the boundary compliance result indicates non-compliance (s<1), a risk value is calculated. Figure 3 As shown, at the "Does the risk of exceeding the scope reach the hard interception threshold?" judgment point, if yes, hard interception will be executed and the order will not be entered; otherwise, it will enter the over-scope approval process. After the over-scope approval expands the scope, it will return to "Terms binding SLA and equipment scope generate service boundary". If rejected, hard interception will be executed and the order will not be entered.

[0059] In an optional implementation, the calculation of the risk value includes: Obtain the device out-of-bounds weight, the service type out-of-bounds weight, and the insufficient quota weight, wherein the device out-of-bounds weight, the service type out-of-bounds weight, and the insufficient quota weight are all non-negative and their sum is 1; The degree of device boundary violation is determined based on the device boundary indicator, the degree of service type boundary violation is determined based on the service type boundary indicator, and the degree of credit insufficiency is determined based on the credit coverage rate. A first risk component is determined based on the degree of device boundary violation and the weight of device boundary violation; a second risk component is determined based on the degree of service type boundary violation and the weight of service type boundary violation; and a third risk component is determined based on the degree of insufficient credit and the weight of insufficient credit. The risk value is determined based on the first risk component, the second risk component, and the third risk component.

[0060] Among them, the degree of equipment exceeding the boundary is 1. u, Service type out-of-bounds level is 1 v, Insufficient credit limit level 1 The risk value R is calculated using the following formula: ρ R=α(1 u)+β(1 v)+γ(1 ρ); Where α is the device out-of-bounds weight, β is the service type out-of-bounds weight, γ is the quota insufficient weight, u is the device in-bounds indicator, v is the service type in-bounds indicator, and ρ is the quota coverage rate.

[0061] When the risk value reaches a preset threshold τ (i.e., R≥τ), the device mounting request or work order creation request is rejected, and no extended approval task is generated; only a log entry is made. For example, if both the device and type exceed the limit, the risk value reaches the hard interception line, the order cannot be entered, and no approval order is issued.

[0062] When the risk value does not reach the preset threshold (R < τ), an expansion approval task is generated. The expansion approval task includes a summary of the contract terms, the current boundary version, and the risk value R, and records the applicant, approver, time, and reason. If the approval is rejected, the block remains in effect; if the approval is granted, a new version of the service boundary record is generated, which can expand the device, type, or temporarily increase the credit limit, and the operation to determine the boundary compliance result is returned. Requests that have already been hard-blocked do not enter the expansion approval task.

[0063] In some embodiments, only a new version of the service boundary record is generated after approval, while the old version of the billing period corresponding to the closed work order remains unchanged; modifications to the device set, allowed service types, limit cap, risk calculation weight, or preset threshold are all implemented by generating a new version of the service boundary record; generated work orders are executed according to the version of the service boundary record bound when the order is opened.

[0064] S6. After the work order is closed, update the fulfilled amount and remaining quota in the service boundary record according to the contract identifier and version identifier conditions. If the condition update fails, retry or rollback alarm.

[0065] After a work order is closed within the designated area and passes acceptance, the order's quota Δq is added to the fulfilled amount Qu according to the write-back coefficient η, and the remaining quota Qr=Qc is updated. Qu, keeping Qu≤Qc and Qr≥0. The write-back coefficient η is 1 when the work order is closed, and η is 0 when the work order is cancelled or voided, not affecting the quota. The write-back submission includes the contract identifier and version identifier. For example... Figure 3 As shown, after the order is released, the system will write back the performance volume to the contract and refresh the remaining amount.

[0066] In an optional implementation, the service boundary record further includes a monotonically increasing write sequence number k; the update based on contract identifier and version identifier conditions includes: reading the fulfilled amount, remaining quota, and write sequence number k corresponding to the contract identifier and version identifier; calculating the new fulfilled amount; updating the fulfilled amount to the new fulfilled amount and the remaining quota to the quota limit minus the new fulfilled amount only if the contract identifier, version identifier, and write sequence number k are still equal to the read values; and incrementing the write sequence number k by one; if the number of updates is 0, then rereading and recalculating, with a maximum of 3 retries; if 3 attempts still fail or the quota limit is exceeded after recalculation, then rolling back the current shutdown and issuing an alarm.

[0067] In some embodiments, in addition to Qu and Qr, a monotonically increasing write sequence number k is set on the service boundary record. During a write-back of a closed order, (Qu, Qr, k) on the contract identifier and version identifier are read first. The new fulfilled quantity is calculated using the formula Qu = Qu + η·Δq. If Qu > Qc, the closure fails, the work order is not recorded as closed, an alarm is triggered, and no write is made to the database. Otherwise, a conditional update is issued: only if the contract identifier, version identifier, and k are still equal to the values ​​just read, is Qu written to the new Qu and Qr written to Qc. Qu, and add one to k.

[0068] If the update count is 0, it means another project has already written to it, causing a conflict: reread the latest (Qu,k) and recalculate, with a maximum of 3 retries. If the conflict persists after 3 attempts, or if the recalculation exceeds Qc, roll back the current update and issue an alert. A later write cannot overwrite an earlier write, and it is absolutely forbidden to write a negative remaining number while displaying a successful transaction closure.

[0069] After a successful write-back, settlement records can be exported based on this version, including used amount, remaining balance, and out-of-scope approval records. For cancelled work orders, η=0; if a work order has already been written back and is cancelled again, a negative offset is generated, following the same update conditions as above, without directly modifying closed billing periods in historical versions. Settlement comparison data is generated by summarizing fulfilled amounts, remaining credit limits, number of out-of-scope approvals, and number of hard interceptions based on contract and version identifiers. External settlements are primarily based on contracts; maintenance projects only undergo internal aggregation.

[0070] Compared to existing technologies, this application proposes a service boundary control method for operation and maintenance. By placing the contract number at the beginning and binding the SLA, equipment scope, service type, and credit limit to a service boundary record with a version identifier, this service boundary record is used for verification and risk diversion in all stages of operation and maintenance project entry, equipment mounting and work order creation, and work order closure and write-back. This enables immediate interception or approval of equipment and service types outside the contract, approval expansion only generates a new version and does not modify the closed billing period, and the performance volume is written back according to the contract identifier and version identifier conditions, thereby avoiding the exposure of services exceeding the scope afterward, reducing reconciliation disputes and credit limit overdrafts.

[0071] To more clearly illustrate the practical application of the technical solution of this application, the above steps S1 to S6 are described in general with reference to three specific embodiments. These three embodiments correspond to the scenarios of normal release of equipment within the contract, approval of equipment outside the contract exceeding the scope, and hard blocking or approval caused by exceeding the type and amount limits. These embodiments are only used to illustrate the technical solution of this application and do not constitute a limitation on the scope of protection of this application.

[0072] Example 1: Equipment within the contract, project establishment, invoicing, and write-back.

[0073] The contract administrator entered Client A's campus security contract as contract identifier C1, with a validity period covering the current year. The SLA in the terms was linked to the equipment scope: 120 PTZ cameras (including equipment identifier E12), allowing only maintenance and inspection, with a maximum quota of Qc=100 times, a response time limit of 4 hours, and a repair time limit of 24 hours. Based on this, a service boundary record was generated, with version identifier version 1, initial fulfilled quantity Qu=20 times, and remaining quota Qr=80 times.

[0074] The project manager creates a daily operation and maintenance project P1 for the park and binds it to the contract identifier C1. The project manager performs an entry verification: the contract C1 is in effect and within the validity period, and the service boundary record version 1 is enabled. The verification passes, and the project identifier P1 is written into the project binding table of the service boundary record.

[0075] The service desk creates a repair work order W1 for device E12, with a planned quota of Δq = 10 repairs. Upon entry, the system checks: device E12 belongs to the set of devices recorded in the service boundary records, therefore the device is within the boundary indication u = 1; the repair is a permitted service type, and the promised response time of 4 hours and repair time of 24 hours do not exceed the remaining SLA budget, therefore the service type is within the boundary indication v = 1; the remaining quota Qr = 80 repairs is not less than the planned quota of Δq = 10 repairs, therefore the quota coverage rate ρ = min(1,80 / max(0.01,10)) = 1. The boundary compliance score s = min(1,1,1) = 1, the boundary compliance result is compliant, the risk value R = 0, and the work order W1 is released.

[0076] Work order W1 is completed and closed on-site. After acceptance, S6 write-back is executed: η=1, Qu=20+10=30 times, Qr=100-30=70 times. During settlement, work order W1 and its quota usage records can be found by using contract identifier C1 and version identifier version 1.

[0077] Example 2: Equipment outside the contract, applying for approval beyond the scope.

[0078] The dispatcher plans to add access controller E99 to maintenance project P1 and create one maintenance work order for E99. Upon entry verification: device E99 does not belong to the device set of service boundary record version 1, therefore the device is within the boundary indication u=0; maintenance is a permitted service type, therefore the service type is within the boundary indication v=1; the proposed quota Δq=1 time, and the remaining quota Qr=80 times is sufficient for coverage, therefore the quota coverage rate ρ=1. The boundary compliance score s=min(0,1,1)=0, the boundary compliance result is non-compliant. The risk value is calculated as: R=0.5×1+0.3×0+0.2×0=0.5, which does not reach the hard interception threshold τ=0.6, i.e., R<τ, generating an expansion approval task. The approval task carries a summary of the contract terms, the current boundary version, and the risk value R=0.5.

[0079] The approver reviews the application based on Contract C1: E99 is not part of this contract; if rejected, the block will remain in effect, and E99 cannot be added to Project P1 or have a work order created. If the supplementary business agreement includes E99 within the contract scope, after approval, a new version (Version 2) of the service boundary record will be generated. E99 will be included in the device set of Version 2, and the application will be returned for verification. During re-verification, device E99 belongs to the device set of Version 2, with u=1, v=1, ρ=1, s=1, and is allowed to proceed.

[0080] Work orders W1 that have been closed in version 1 will have their fulfillment records unchanged and will still be settled according to the payment period of version 1, without being affected by the expansion of version 2.

[0081] Example 3: Incorrect type and insufficient quota, hard interception.

[0082] The service desk applied for a "engineering modification" type work order for the equipment within the scope of contract C1. Contract C1 does not allow this type of service, and it is intended to occupy the quota Δq=10 times, while the remaining quota at that time was Qr=3 times.

[0083] Scenario 1: Equipment within the permitted scope, type exceeding the permitted scope, insufficient quota. The equipment belongs to the equipment set, so u=1; the service type "engineering renovation" is not within the permitted service types, so v=0; the quota coverage rate ρ=min(1,3 / 10)=0.3. The boundary compliance score s=min(1,0,0.3)=0, and the boundary compliance result is non-compliant. Calculate the risk value: R=0.5×0+0.3×1+0.2×0.7=0.44, which does not reach the hard interception threshold of 0.6. The expansion approval task can be used to apply for a temporary increase in quota or an increase in service type. The channel is the same as in Scenario 2.

[0084] Scenario 2: Based on Scenario 1, the device is also not in the device set. In this case, u=0, v=0, ρ=0.3. Calculate the risk value: R=0.5×1+0.3×1+0.2×0.7=0.94, which reaches the hard interception threshold τ=0.6, i.e., R≥τ. The work order creation request is directly rejected, and no extended approval task is generated; only the log is recorded.

[0085] Scenario 3: Only the credit limit is insufficient; both the device and type are within limits. In this case, u=1, v=1, and ρ=0.3. Calculate the risk value: R=0.2×0.7=0.14, which does not reach the hard interception threshold of 0.6. The task of expanding the credit limit can be initiated to apply for a temporary increase in the credit limit. The channel is the same as in Scenario 2.

[0086] Reference Figure 4 The diagram shown is a functional block diagram of the operation and maintenance service boundary control device according to an embodiment of this application.

[0087] In some embodiments, the operation and maintenance service boundary control device 40 may include multiple functional modules composed of computer program segments. The computer programs of each program segment of the operation and maintenance service boundary control device 40 may be stored in the memory of an electronic device and executed by at least one processor to perform the function of operation and maintenance service boundary control. Based on the function performed, it can be divided into multiple functional modules. The functional modules may include: a data acquisition module 401, a boundary generation module 402, an entry verification module 403, an entry order verification module 404, a risk diversion module 405, and a fulfillment write-back module 406. The term "module" in this application refers to a series of computer program segments that can be executed by at least one processor and perform a fixed function, and which are stored in memory. In this embodiment, the functions of each module will be described in detail in subsequent embodiments.

[0088] The data acquisition module 401 is used to acquire contract data.

[0089] The boundary generation module 402 is used to generate service boundary records with version identifiers based on the contract data.

[0090] The input verification module 403 is used to respond to the creation or activation request of the operation and maintenance project, verify whether the operation and maintenance project is bound to a valid contract and whether there is an enabled service boundary record; if the verification fails, the generation of an operation and maintenance project that can be dispatched is prohibited; if the verification passes, the project identifier of the operation and maintenance project is bound to the service boundary record.

[0091] The order verification module 404 is used to respond to device mounting requests or work order creation requests, and determine the boundary compliance result based on whether the device belongs to the device set in the service boundary record, whether the requested service type and service level protocol match, and whether the remaining quota covers the quota to be occupied.

[0092] The risk triage module 405 is used to allow the device mounting request or work order creation request if the boundary compliance result indicates compliance; if the boundary compliance result indicates non-compliance, calculate the risk value; when the risk value reaches a preset threshold, reject the device mounting request or work order creation request and do not generate an expansion approval task; when the risk value does not reach the preset threshold, generate an expansion approval task, and after approval, generate a new version of the service boundary record and return to execute the operation of determining the boundary compliance result.

[0093] The fulfillment write-back module 406 is used to update the fulfilled amount and remaining quota in the service boundary record according to the contract identifier and version identifier conditions after the work order is closed. If the condition update fails, a retry or rollback alarm will be issued.

[0094] It should be understood that the various variations and specific embodiments of the operation and maintenance service boundary control method provided in the above embodiments are also applicable to the operation and maintenance service boundary control device of this embodiment. Through the foregoing detailed description of the operation and maintenance service boundary control method, those skilled in the art can clearly understand the implementation method of the operation and maintenance service boundary control device in this embodiment. For the sake of brevity, it will not be described in detail here.

[0095] See Figure 5 The diagram shown is a schematic representation of the structure of an electronic device according to an embodiment of this application. In a preferred embodiment of this application, the electronic device 5 includes a memory 51, at least one processor 52, and at least one communication bus 53.

[0096] Those skilled in the art should understand that Figure 5 The structure of the electronic device shown does not constitute a limitation of the embodiments of this application. It can be a bus structure or a star structure. The electronic device 5 may also include more or fewer other hardware or software than shown, or different component arrangements.

[0097] In some embodiments, the electronic device 5 is a device capable of automatically performing numerical calculations and / or information processing according to pre-set or stored instructions. Its hardware includes, but is not limited to, microprocessors, application-specific integrated circuits (ASICs), programmable gate arrays (FPGAs), digital processors, and embedded devices. The electronic device 5 may also include user equipment, which includes, but is not limited to, any electronic product capable of human-computer interaction with a user via a keyboard, mouse, remote control, touchpad, or voice control device, such as a personal computer, tablet computer, smartphone, or digital camera.

[0098] In the embodiments provided in this application, it should be understood that the disclosed methods, apparatuses, computer-readable storage media, and electronic devices can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple components or modules may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices, components, or modules may be electrical, mechanical, or other forms.

[0099] The components described as separate parts may or may not be physically separate. The components shown as components may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the components can be selected to achieve the purpose of this embodiment according to actual needs.

[0100] Furthermore, the functional modules in the various embodiments of this application can be integrated into one processing module, or each component can exist physically separately, or two or more modules can be integrated into one module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0101] If the integrated module is implemented as a software functional module 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 the 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 to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes: USB flash drive, portable hard drive, read-only memory (ROM). Various media that can store program code, such as only memory, random access memory (RAM), magnetic disks or optical disks.

[0102] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0103] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0104] The above is a detailed description of the preferred embodiments of this application. However, the invention of this application is not limited to the embodiments described. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of this application. All such equivalent modifications or substitutions are included within the scope defined by the claims of this application.

Claims

1. A method for managing the boundary of operation and maintenance services, characterized in that, The method includes: Obtain contract data; Generate a service boundary record with a version identifier based on the contract data; In response to a request to create or enable an operations and maintenance project, the system verifies whether the project is bound to a valid contract and whether an enabled service boundary record exists. If the verification fails, the system prohibits the generation of operations and maintenance projects that can be dispatched. If the verification passes, the system binds the project identifier of the operations and maintenance project to the service boundary record. In response to a device mounting request or a work order creation request, the boundary compliance result is determined based on whether the device belongs to the device set in the service boundary record, whether the requested service type and service level protocol match, and whether the remaining quota covers the quota to be occupied. If the boundary compliance result indicates compliance, the device mounting request or work order creation request is allowed; if the boundary compliance result indicates non-compliance, a risk value is calculated. When the risk value reaches a preset threshold, the device mounting request or work order creation request is rejected and no boundary expansion approval task is generated. When the risk value does not reach the preset threshold, a boundary expansion approval task is generated, and a new version of the service boundary record is generated after approval, and the operation of determining the boundary compliance result is returned. After the work order is closed, the fulfilled amount and remaining quota in the service boundary record are updated according to the contract identifier and version identifier conditions. If the condition update fails, a retry or rollback alarm is issued.

2. The operation and maintenance service boundary control method according to claim 1, characterized in that, The results of determining the boundary compliance include: Determine the device boundary indicator: when the device belongs to the set of devices, the device boundary indicator is set to 1; otherwise, the device boundary indicator is set to 0. The Service Type Inbound Indicator is set to 1 when the requested service type is an allowed service type and the requested service level agreement time limit does not exceed the remaining service level agreement time limit budget; otherwise, the Service Type Inbound Indicator is set to 0. The credit limit coverage ratio is determined as follows: when the remaining credit limit is not less than the intended credit limit, the credit limit coverage ratio is 1; otherwise, the credit limit coverage ratio is the ratio of the remaining credit limit to the intended credit limit and does not exceed 1. The boundary compliance score is determined based on the device boundary indication, the service type boundary indication, and the quota coverage rate. When the boundary compliance score is equal to 1, the boundary compliance result is determined to be compliant. When the boundary compliance score is less than 1, the boundary compliance result is determined to be non-compliant.

3. The operation and maintenance service boundary control method according to claim 2, characterized in that, The determination of the coverage rate of the credit limit includes: The coverage rate of the credit limit is determined using the following formula: ρ = min(1, Qr / max(ε, Δq)); Where ρ is the coverage rate of the quota, Qr is the remaining quota, Δq is the quota to be occupied, and ε is the amount to prevent zero division and has the same dimension as Δq; When Δq≤0, the coverage rate of the quota is 1, and the service type boundary indication of the device boundary indication still needs to be satisfied.

4. The operation and maintenance service boundary control method according to claim 1, characterized in that, The calculated risk value includes: Obtain the device out-of-bounds weight, the service type out-of-bounds weight, and the insufficient quota weight, wherein the device out-of-bounds weight, the service type out-of-bounds weight, and the insufficient quota weight are all non-negative and their sum is 1; The degree of device boundary violation is determined based on the device boundary indicator, the degree of service type boundary violation is determined based on the service type boundary indicator, and the degree of credit insufficiency is determined based on the credit coverage rate. A first risk component is determined based on the degree of device boundary violation and the weight of device boundary violation; a second risk component is determined based on the degree of service type boundary violation and the weight of service type boundary violation; and a third risk component is determined based on the degree of insufficient credit and the weight of insufficient credit. The risk value is determined based on the first risk component, the second risk component, and the third risk component.

5. The operation and maintenance service boundary control method according to claim 1, characterized in that, The contract data includes contract identifier, validity period, service level agreement information, equipment scope information, service type, and maximum limit; The contract data also includes contract status, which includes at least draft, pending, effective, suspended, and expired; the method further includes: When a contract is in a pending state, if the contract's agreed-upon effective time is reached, the service level agreement information and device scope information have been bound, and the service boundary record has been enabled, the contract status will be automatically changed to an effective state. When a contract is in effect, if the agreed expiration date is reached, the contract status will automatically change to expired. When a contract is in effect, if a suspension instruction is received and the reason is recorded, the contract status will be changed to a suspended status. When a contract is suspended, new requests for creating or enabling maintenance projects, device mounting requests, and work order creation requests will be rejected. Executed work orders will be allowed to be closed and written back, but new work orders will be prohibited. When a contract is in an expired state, requests to create or activate maintenance projects, mount equipment, and create work orders will be rejected. Unclosed work orders will be carried over or closed according to the contract and will not be subject to new quota.

6. The operation and maintenance service boundary control method according to claim 5, characterized in that, The equipment scope information includes inclusion rules and exclusion rules, each of which includes at least one of an asset identification list, a location code, and a category code; generating a service boundary record with a version identifier based on the contract data includes: The asset data source is invoked to expand the location code and category code into an in-service asset identifier; The set of devices is obtained by taking the union of multiple asset identifiers that are included in the rule and then subtracting the asset identifiers that are excluded from the rule. If the set of devices is empty, the location or category does not exist in the asset data source, or the asset data source query times out or the set is empty after exclusion, then the service boundary record is not enabled. If the set of devices is not empty and each rule can be applied to a known asset, then the service boundary record is enabled and the set of devices is persisted to the current version; Once the service boundary record is enabled, newly registered devices at the same location or of the same type will not be automatically added to the current version. Instead, they will be added through the generation of a new version of the service boundary record or by an expansion approval task.

7. The operation and maintenance service boundary control method according to claim 5, characterized in that, The step of generating a service boundary record with a version identifier based on the contract data further includes: The service boundary record is enabled only when both the service level agreement information and the device range information are bound. When the contract data includes multiple attachments, the attachments are merged according to the priority of the clauses, and conflicting items are marked as pending review and disabled.

8. A maintenance service boundary control device, characterized in that, The device includes: The data acquisition module is used to acquire contract data; The boundary generation module is used to generate service boundary records with version identifiers based on the contract data. The entry verification module is used to respond to the creation or activation request of the operation and maintenance project, and to verify whether the operation and maintenance project is bound to a valid contract and whether there is an enabled service boundary record. If the verification fails, the generation of an operation and maintenance project that can be dispatched is prohibited. If the verification passes, the project identifier of the operation and maintenance project is bound to the service boundary record. The order verification module is used to respond to device mounting requests or work order creation requests, and determine the boundary compliance result based on whether the device belongs to the device set in the service boundary record, whether the requested service type and service level protocol match, and whether the remaining quota covers the quota to be occupied. The risk triage module is used to allow the device mounting request or work order creation request if the boundary compliance result indicates compliance; if the boundary compliance result indicates non-compliance, calculate the risk value; when the risk value reaches a preset threshold, reject the device mounting request or work order creation request and do not generate an expansion approval task; when the risk value does not reach the preset threshold, generate an expansion approval task, and generate a new version of the service boundary record after approval, and return to execute the operation of determining the boundary compliance result. The fulfillment write-back module is used to update the fulfilled amount and remaining quota in the service boundary record according to the contract identifier and version identifier after the work order is closed. If the condition update fails, a retry or rollback alarm will be issued.

9. An electronic device, characterized in that, It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the operation and maintenance service boundary control method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the operation and maintenance service boundary control method as described in any one of claims 1 to 7.