Boundary conflict management method and system, electronic equipment and storage medium

Abstract

The invention provides a boundary conflict management method and system, an electronic device and a storage medium, and relates to the technical field of handover and delivery boundary management, and the method comprises the following steps: building ticket types of a plurality of priority levels; setting ticket types for all existing tickets according to the ticket types of the plurality of priority levels; acquiring a current ticket, and performing conflict check according to the ticket type and state information of the current ticket and the ticket types and state information of all existing tickets; and when a conflict exists, selecting a corresponding ticket selection result with a relatively high ticket issuing priority from the existing ticket and the current ticket according to a ticket issuing priority rule, and issuing the ticket. According to the boundary conflict management method and system, the electronic equipment and the storage medium provided by the invention, the risk controllability of the high-risk boundary state in the management process can be ensured, and the inspection efficiency of the boundary conflict is also improved.

Description

Technical Field

[0001] The present invention relates to the technical field of property transfer and handover boundary management, and in particular to a boundary conflict management method, system, electronic equipment and storage medium. Background Art

[0002] Boundary management is part of debugging management. The SAP information system needs to provide an information support platform for debugging management, and use information technology to implement process management of boundary management and debugging process, so that the interface relationship is clearer, the work is more standardized, and the management efficiency is more efficient.

[0003] In the existing boundary conflict management process, only conflict judgment and ticketing management under the same priority, such as standard isolation, are considered. However, when conducting conflict management, there will be more diverse management levels. In the face of rich and complex management levels, the existing conflict judgment method is obviously not enough to make a comprehensive judgment, and it cannot guarantee the controllability and stability of the boundary state. Summary of the invention

[0004] In view of the shortcomings of the prior art mentioned above, the purpose of the present invention is to provide a boundary conflict management method, system, electronic device and storage medium, which are used to solve the problem that when performing conflict management in the prior art, there are more diverse management levels, and in the face of relatively rich and complex management levels, the existing conflict determination method is obviously insufficient for comprehensive determination, and cannot guarantee the controllability and stability of the boundary state.

[0005] To achieve the above-mentioned purpose and other related purposes, the present invention provides a boundary conflict management method, comprising the following steps: establishing ticket types of several priority levels; setting ticket types for all existing tickets according to the ticket types of several priority levels; obtaining the current ticket, and performing a conflict check according to the ticket type and status information of the current ticket and the ticket type and status information of all existing tickets; when there is a conflict, selecting the corresponding voting result with a higher ticket issuance priority from the existing tickets and the current ticket according to the ticket issuance priority rule for ticket issuance.

[0006] In one embodiment of the present invention, establishing a plurality of priority levels of ticket types includes: creating a plurality of ticket type groups of different priorities, each ticket type group having at least one sub-ticket type.

[0007] In one embodiment of the present invention, ticket types are set for all existing tickets according to ticket types of several priority levels, including: setting a ticket type of corresponding priority level for each boundary instruction of each boundary device of all existing tickets; wherein the status information of the existing tickets includes the device status, the implementation status of the boundary instruction, and the boundary status, and the implementation status includes one of the isolation preparation status, isolation confirmation status, release preparation status and suspension preparation status.

[0008] In one embodiment of the present invention, a conflict check is performed based on the ticket type and status information of the current ticket and the ticket type and status information of all existing tickets, including: obtaining the ticket type, device status, implementation status of boundary instructions, and boundary status of the current ticket and existing tickets; performing a conflict check based on the ticket type, device status, implementation status of boundary instructions, and boundary status of the current ticket and existing tickets.

[0009] In one embodiment of the present invention, conflict detection is performed based on the ticket type, device status, implementation status of boundary instructions, and boundary status of the current ticket and existing tickets, including: performing validity detection on the existing ticket based on the implementation status corresponding to the boundary instruction in the existing ticket: judging whether the existing ticket is in an implemented state: if not, determining that the existing ticket is invalid; if so, judging whether the ticket type, device status, and boundary status of the current ticket and the ticket type, device status, and boundary status of the existing ticket satisfy conflict rules, including: whether the following three conditions are met at the same time: the ticket type of the current ticket is consistent with the ticket type of the existing ticket; and / or the device status of the current ticket and the device status of the existing ticket satisfy the device status rules; and / or the boundary status of the current ticket is consistent with the boundary status of the existing ticket; if so, determining that the conflict rules are satisfied, if not, determining that the conflict rules are not satisfied.

[0010] In one embodiment of the present invention, whether the device status of the current ticket and the device status of the existing ticket satisfy the device status rules is determined, including: whether the following four conditions are met at the same time: the main device of the current ticket is the main device of the existing ticket; and / or the main device of the current ticket is the boundary device of the existing ticket; and / or the boundary device of the current ticket is the main device of the existing ticket; and / or the boundary device of the current ticket is the boundary device of the existing ticket; if so, the device status rules are satisfied, if not, the device status rules are not satisfied.

[0011] In one embodiment of the present invention, when there is a conflict, the corresponding voting result with a higher ticket issuance priority is selected from the existing ticket and the current ticket according to the ticket issuance priority rule to issue the ticket, including: determining the ticket issuance priority of the current ticket and the existing ticket according to the priority level of the ticket type; if the ticket issuance priority of the current ticket is higher than the ticket issuance priority of the existing ticket, issuing the ticket according to the boundary instruction of the current ticket; if the ticket issuance priority of the existing ticket is higher than the ticket issuance priority of the current ticket, issuing the ticket according to the boundary instruction with the highest priority among the existing tickets.

[0012] The present invention also provides a border conflict management system, comprising: a hierarchical creation unit, used to establish ticket types of several priority levels; a hierarchical setting unit, used to set ticket types for all existing tickets according to the ticket types of several priority levels; a conflict checking unit, used to obtain a current ticket, and perform a conflict check based on the ticket type and status information of the current ticket and the ticket types and status information of all existing tickets; a ticket issuing processing unit, used to select a corresponding voting result with a higher ticket issuing priority from the existing tickets and the current ticket according to the ticket issuing priority rule for ticket issuing when there is a conflict.

[0013] The present invention further provides an electronic device, which includes: one or more processors; and a storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the electronic device implements the aforementioned boundary conflict management method.

[0014] The present invention further provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor of a computer, the computer is enabled to execute the aforementioned boundary conflict management method.

[0015] As described above, a boundary conflict management method, system, electronic device and storage medium of the present invention have the following beneficial effects: by configuring / classifying existing tickets and current tickets according to ticket types of different priority levels in the process of managing existing tickets, it is possible to perform conflict checks on all existing tickets and current tickets, and while judging whether there is a boundary conflict based on the status information of existing tickets and current tickets, it is also possible to further determine whether there is a boundary conflict based on the priority level in combination with the ticket types of existing tickets and current tickets. And when there is a conflict, the ticket issuance priority is further determined based on the priority levels of the existing tickets and the current tickets, and the existing tickets or current tickets with higher priorities are selected for issuance to obtain the final boundary state of the current boundary device. In the above manner, it can be ensured that when adding a current ticket, the boundary state management based on different management levels can be completed more comprehensively and accurately to ensure that the risk of high-risk boundary states in the management process is controllable, and the efficiency of boundary conflict inspection is improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 A flow chart of a boundary conflict management method provided in an embodiment of the present invention.

[0017] Figure 2 Shown is a schematic diagram of a conflict determination process provided by an embodiment of the present invention.

[0018] Figure 3 Shown is a structural block diagram of a boundary conflict management system provided by an embodiment of the present invention.

[0019] Figure 4Shown is a structural schematic diagram of an electronic device according to an embodiment of the present invention.

[0020] Component number description

[0021] The electronic device 1 includes a conflict management system 11 , a memory 12 , a processor 13 , a hierarchy creation unit 111 , a hierarchy setting unit 112 , a conflict checking unit 113 and a ticket issuing processing unit 114 . DETAILED DESCRIPTION

[0022] The following describes the embodiments of the present invention by specific examples, and those skilled in the art can easily understand other advantages and effects of the present invention from the contents disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that the following embodiments and features in the embodiments can be combined with each other without conflict.

[0023] It should be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present invention, and thus the drawings only show components related to the present invention rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed arbitrarily, and the component layout may also be more complicated.

[0024] In the following description, numerous details are discussed to provide a more thorough explanation of the embodiments of the present invention. However, it is obvious to those skilled in the art that the embodiments of the present invention can be implemented without these specific details. In other embodiments, well-known structures and devices are shown in the form of block diagrams rather than in detail to avoid making the embodiments of the present invention difficult to understand.

[0025] See also Figure 1 In one embodiment of the present invention, the present invention provides a boundary conflict management method, comprising the following steps:

[0026] Step S10: Establishing several priority levels of ticket types;

[0027] Step S20: Setting ticket types for all existing tickets according to ticket types of several priority levels.

[0028] Step S30: Get the current ticket, and perform a conflict check based on the ticket type and status information of the current ticket and the ticket type and status information of all existing tickets.

[0029] Step S40: When there is a conflict, the voting result with a higher priority for issuing tickets is selected from the existing tickets and the current tickets according to the ticket issuing priority rule for issuing tickets.

[0030] In this embodiment, through step S10: establishing a plurality of priority levels of ticket types, it can be seen that in the process of boundary conflict management, management can be performed by setting the priority levels of ticket types. Specifically, by setting a plurality of priority levels of ticket types, it is convenient to manage the work tickets according to the priority levels of the ticket types, so that during conflict management, tickets can be issued according to the boundary status corresponding to the ticket types with higher priority levels.

[0031] Through step S20: setting ticket types for all existing tickets according to ticket types of several priority levels, it can be seen that after the ticket type is established, the ticket types of each priority level can be set for the existing tickets respectively. By setting the ticket type for the existing tickets, it is convenient to determine whether to issue the ticket in the boundary state of the existing ticket according to the priority of the existing ticket during the conflict check.

[0032] Through step 30: obtaining the current ticket, and performing a conflict check based on the ticket type and status information of the current ticket and the ticket type and status information of all existing tickets, it can be seen that after setting the ticket type for the existing ticket, the current ticket that needs to be checked for conflicts needs to be obtained. Furthermore, when entering the current ticket information, the ticket type and status information of the current ticket needs to be entered, so as to determine whether the ticket type and status information of the current ticket conflicts with the ticket type and status information of all existing tickets based on the ticket type and status information of the current ticket.

[0033] Through step S40: when there is a conflict, the corresponding voting result with a higher priority for issuing a ticket is selected from the existing tickets and the current ticket according to the ticket issuing priority rule for issuing a ticket. It can be seen that when judging whether the ticket type and status information of the current ticket conflict with the ticket type and status information of each existing ticket in all existing tickets, if it is determined that there is a conflict, it is necessary to select a work ticket with a higher priority for issuing a ticket from the existing tickets and the current ticket for issuing a ticket. Specifically, the work ticket with a higher priority for issuing a ticket can be an existing ticket, and of course, it can also be the current ticket. Through the above steps, it can be achieved that after a boundary conflict occurs, the existing ticket can be issued or blocked quickly. When blocking a ticket, the current ticket can be used for issuing a ticket, thereby ensuring the conflict checking efficiency and the ticket issuing efficiency.

[0034] In one embodiment of the present invention, when establishing a ticket type for a work ticket, multiple priority levels can be established for the work ticket. Among them, the work ticket can be an existing ticket or a current ticket. Specifically, establishing ticket types with several priority levels includes: creating multiple ticket type groups with different priorities, and at least one sub-ticket type is set under each ticket type group. In this embodiment, the established ticket types include ticket type groups with different priority levels. For example, the ticket types include administrative isolation tickets, maintenance isolation tickets, and transfer isolation tickets in sequence according to the priority level. Of course, multiple sub-ticket types can also be set under each ticket type group. For example, in the ticket type group of administrative isolation tickets, PA (administrative isolation) tickets and PO tickets (operation isolation) can be included. Transfer isolation tickets include TOB (isolation transfer) tickets and TOTO (temporary operation isolation) tickets.

[0035] In one embodiment of the present invention, when setting the ticket type for an existing ticket, it can be set according to the boundary instructions of the existing ticket and its boundary status. Specifically, the ticket type is set for all existing tickets according to the ticket types of several priority levels, including: setting the ticket type corresponding to the priority level for each boundary instruction of each boundary device of all existing tickets; wherein the status information of the existing ticket includes the device status, the implementation status of the boundary instruction, and the boundary status, and the implementation status includes one of the isolation preparation state, isolation determination state, release preparation state and suspension preparation state. In this embodiment, after determining the boundary instructions of each boundary device of all existing tickets, the ticket type is set for each boundary instruction respectively, so as to set the priority level for each boundary instruction. The existing ticket includes an operation sheet, an isolation sheet, etc., and of course also includes status information such as the device status, the implementation status of the boundary instruction, and the boundary status. The implementation status of the boundary instruction can be one of the isolation preparation state, isolation determination state, release preparation state and suspension preparation state. Of course, the implementation status includes the status corresponding to the time period between the isolation preparation state and the isolation determination state, and the state after the isolation determination state. The implementation status also includes the status corresponding to the time period between the release preparation state and the termination preparation state, and the state after the termination preparation state.

[0036] In one embodiment of the present invention, when checking for conflicts, it is necessary to compare the ticket type and status information of the existing ticket and the current ticket to confirm whether there is a conflict. Specifically, a conflict check is performed based on the ticket type and status information of the current ticket and the ticket type and status information of all existing tickets, including: obtaining the ticket type, device status, implementation status of boundary instructions, and boundary status of the current ticket and the existing tickets; performing conflict detection based on the ticket type, device status, implementation status of boundary instructions, and boundary status of the current ticket and the existing tickets. In this embodiment, both the current ticket and the existing tickets include ticket type and status information. Among them, the status information includes the device status, implementation status of boundary instructions, and boundary status; the implementation status includes the status corresponding to the time period between the isolation preparation state and the isolation determination state, and the state after the isolation determination state, and the implementation status also includes the status corresponding to the time period between the release preparation state and the suspension preparation state, and the state after the suspension preparation state.

[0037] In one embodiment of the present invention, during the conflict check, it can be further determined whether the conflict rules are satisfied, that is, whether there is a conflict, based on the judgment of the status information such as the ticket type, device status, implementation status of the boundary instruction, and boundary status of the current ticket and the existing ticket. Specifically, the conflict detection is performed based on the ticket type, device status, implementation status of the boundary instruction, and boundary status of the current ticket and the existing ticket, including: performing validity detection of the existing ticket based on the implementation status corresponding to the boundary instruction in the existing ticket: judging whether the existing ticket is in the implemented state: if not, determining that the existing ticket is invalid; if so, judging whether the ticket type, device status, and boundary status of the current ticket and the ticket type, device status, and boundary status of the existing ticket meet the conflict rules, including: whether the following three conditions are met at the same time: the ticket type of the current ticket is consistent with the ticket type of the existing ticket; and / or the device status of the current ticket and the device status of the existing ticket meet the device status rule; and / or the boundary status of the current ticket is consistent with the boundary status of the existing ticket; if so, determining that the conflict rules are satisfied, if not, determining that the conflict rules are not satisfied.

[0038] In this embodiment, when performing conflict detection between the ticket type, device status, implementation status of the boundary instruction, and boundary status of the current ticket and the existing ticket, the implementation status of the boundary instruction of the existing ticket can be determined first, that is, the validity detection of the existing ticket can be performed according to the implementation status corresponding to the boundary instruction in the existing ticket. Specifically, by judging whether the existing ticket is in an implemented state, if the existing ticket is in a non-implemented state, for example, in the approval state before the isolation preparation state or in the approval state before the release preparation state, it is in a non-implemented state, then it can be determined that the existing ticket is in an invalid state. If it is in an implemented state, it is determined that the existing ticket is valid. That is to say, when the existing ticket is in one of the isolation preparation state, isolation determination state, release preparation state and suspension preparation state, or the state corresponding to the time period between the release preparation state and the suspension preparation state, and the state after the suspension preparation state, it can be determined that the existing ticket is in an implemented state and the existing ticket is valid.

[0039] Furthermore, after determining that the existing ticket is valid, it is further determined whether the ticket type, device status, and boundary status of the current ticket and the ticket type, device status, and boundary status of the existing ticket meet the conflict rules. In other words, when the ticket type, device status, and boundary status of the current ticket are all different from the ticket type, device status, and boundary status of the existing ticket, it is determined that the conflict rules are not met. On the contrary, the conflict rules are met, which means that the boundary instructions of the existing ticket and the current ticket are consistent. When issuing a ticket, it can be directly determined that the ticket can be issued with the boundary instructions of the existing ticket or with the boundary instructions of the current ticket.

[0040] In one embodiment of the present invention, when determining whether the device status of the current ticket satisfies the device status rule with the device status of the existing ticket, it is also necessary to further determine whether the device status of the current ticket is the main device or the boundary device, and whether the device status of the corresponding existing ticket is the main device or the boundary device. Specifically, judging whether the device status of the current ticket satisfies the device status rule with the device status of the existing ticket includes: whether the following four conditions are met at the same time: the main device of the current ticket is the main device of the existing ticket; and / or the main device of the current ticket is the boundary device of the existing ticket; and / or the boundary device of the current ticket is the main device of the existing ticket; and / or the boundary device of the current ticket is the boundary device of the existing ticket; if so, the device status rule is satisfied, and if not, the device status rule is not satisfied.

[0041] In this embodiment, when judging whether the device status of the current ticket and the device status of the existing ticket meet the device status rules, it is necessary to determine whether the device status type of the current ticket is a main device or a boundary device. That is, when the current ticket is the main device and the existing ticket can be the main device, a main-main conflict check is performed; and when the current ticket is the main device and the existing ticket can be the boundary device, a main-side conflict check is performed. When the current ticket is the boundary device and the existing ticket can be the main device, a side-main conflict check is performed; when the current ticket is the boundary device and the existing ticket can be the main device, a side-side conflict check is performed.

[0042] In a preferred embodiment of the present invention, during the master-master conflict check, when the current ticket master device is the master device of other existing tickets, a conflict judgment is made according to the ticket type. If the existing ticket WCA (isolation operation sheet) status is isolation approved by the isolation manager, the ticket is blocked. If the existing ticket WCA status is approved by the plan / approved by the operator, it is only in the approval status and is not in the implemented status and is invalid, so the ticket is not blocked. During the master-side conflict check, when the current ticket master device is in the isolation preparation, label printing, isolation confirmation, release preparation, and abort preparation status, the conflict check is performed for other ticket boundary instructions. Except for the boundary devices of A (PA administrative isolation ticket) / O (PO operation isolation ticket), TO (TOTO temporary operation transfer ticket) / TB (TOB isolation transfer ticket) (in the instruction status of A_RTCLOSED... / O_RTCLOSED...TO_RTCLOSED... / TB_RTCLOSED...), which can be the master device of W (a type of maintenance isolation ticket), I (a type of maintenance isolation ticket), T (a type of maintenance isolation ticket), R (a type of maintenance isolation ticket), and X (a type of maintenance isolation ticket), the boundary devices of other device status are not allowed to be the master devices of W, I, T, R, and X. The master devices of TB and TO are both systems, and the system will not be used as the boundary of the ticket. During the conflict check of the edge master, that is, the conflict check when the boundary device of the current ticket is the master device of other tickets. The master device of the W, I, T, R, and X tickets approved by the isolation manager cannot be used as the boundary device of the current non-A / O / TB / TO ticket; if the WCA status of the existing ticket is approved by the plan / approved by the operator, a warning reminder will be given, but it will not be blocked. The master devices of TB and TO are both systems, and the system will not be used as the boundary of the ticket. During the edge conflict check, that is, when the boundary device of the current ticket is in the isolation preparation, isolation confirmation, release preparation, and abort preparation states, a conflict check is performed when other ticket boundary instructions are in progress.

[0043] See also Figure 2In a preferred embodiment provided, it can be seen that only when the ticket type of the current ticket is the same as the ticket type of the existing ticket, and the grouping, condition, and the isolation board corresponding to the boundary instruction are all the same, will no conflict occur at this time. The remaining states will have conflict situations such as conflict red light, warning yellow light, and no verification. Specifically, when the ticket type of the existing ticket is a PA / PO ticket and the boundary state is CLOSED, and the isolation board is NT (a type of isolation board), the current ticket is also a PA / PO ticket type, the boundary state is CLOSED, and the isolation board is NT, the current ticket does not conflict with the existing ticket. When the existing ticket is a PA / PO ticket type, the boundary state is DISCONNECT, and the isolation board is NT, the current ticket is also a PA / PO ticket type, the boundary state is DISCONNECT, and the isolation board is NT, the current ticket does not conflict with the existing ticket. By analogy, other ticket types, boundary states, and isolation board types are also realized in the same way without conflict, which will not be repeated here one by one.

[0044] In one embodiment of the present invention, when it is determined that a conflict occurs, it is necessary to further set a ticket issuance rule to determine the boundary state of each boundary after adding a new current ticket. Specifically, when there is a conflict, the corresponding voting result with a higher ticket issuance priority is selected from the existing tickets and the current ticket according to the ticket issuance priority rule to issue the ticket, including: determining the ticket issuance priority of the current ticket and the existing ticket according to the priority level of the ticket type; if the ticket issuance priority of the current ticket is higher than the ticket issuance priority of the existing ticket, issuing the ticket according to the boundary instruction of the current ticket; if the ticket issuance priority of the existing ticket is higher than the ticket issuance priority of the current ticket, issuing the ticket according to the boundary instruction with the highest priority among the existing tickets. In this embodiment, when it is determined that there is a boundary conflict between the current ticket and the existing ticket, it is necessary to selectively issue the ticket according to the order of the ticket issuance priority. That is, by determining the working ticket with a higher priority among the current ticket and the existing ticket, when the ticket issuance priority of the current ticket is higher than the ticket issuance priority of the existing ticket, the boundary instruction of the current ticket can be selected to issue the ticket to obtain the final boundary state. If the ticket issuance priority of the existing ticket is higher than the ticket issuance priority of the current ticket, the boundary instruction of the existing ticket with the highest priority can be selected from all the existing tickets for ticket issuance, and the final boundary state can be further obtained.

[0045] like Figure 3As shown, in one embodiment of the present invention, the present invention further provides a border conflict management system 11, including: a hierarchy creation unit 111, used to establish ticket types of several priority levels; a hierarchy setting unit 112, used to set ticket types for all existing tickets according to the ticket types of several priority levels; a conflict checking unit 113, used to obtain the current ticket, and perform a conflict check according to the ticket type and status information of the current ticket and the ticket type and status information of all existing tickets; a ticket issuing processing unit 114, used to select the corresponding voting result with a higher ticket issuing priority from the existing tickets and the current ticket according to the ticket issuing priority rule for issuing tickets when there is a conflict.

[0046] In the present embodiment, in the border conflict management system 11 of the present invention, the level creation unit 111 can be used to establish a ticket type of a corresponding priority level for each work ticket during the border conflict management process, so as to realize the classification management of the existing tickets in the work ticket. The level setting unit 112 can be used to implement the application of the ticket types of each priority level to the existing tickets after the priority level of the ticket type is established, so as to realize the classification of the existing tickets according to the ticket type. The conflict check unit 113 can be used to implement the conflict check according to the ticket type and status information of the existing ticket and the current ticket, so as to determine whether the existing ticket and the current ticket conflict. The ticket issuing processing unit 114 can be used to implement the determination of the conflict between the existing ticket and the current ticket, and further determine which of the existing ticket and the current ticket has a higher priority level, and the priority level is corresponding to the ticket issuing priority level, and the existing ticket or the current ticket with a higher priority level, that is, the ticket issuing priority level is selected for issuing. From the above content, it can be seen that by establishing a priority level for management of the existing tickets and the current tickets in the work ticket, and based on the ticket type and status information of the priority level, it is further determined whether there is a conflict, and when there is a conflict, a work ticket corresponding to a reasonable ticket type is selected for ticket management to ensure the stability and security of the boundary state after the current ticket is combined with the existing ticket.

[0047] It should be noted that the boundary conflict management system 11 provided in the above embodiment and the boundary conflict management method provided in the above embodiment belong to the same concept, wherein the specific manner in which each module and unit performs operations has been described in detail in the method embodiment and will not be repeated here. In practical applications, the boundary conflict management system 1 provided in the above embodiment can distribute the above functions to different functional modules as needed, that is, divide the internal structure of the device into different functional modules to complete all or part of the functions described above, and this is not limited here.

[0048] See also Figure 4The electronic device 1 may include a memory 12, a processor 13 and a bus, and may also include a computer program stored in the memory 12 and executable on the processor 13, such as a border conflict management program.

[0049] Among them, the memory 12 includes at least one type of readable storage medium, and the readable storage medium includes flash memory, mobile hard disk, multimedia card, card-type memory (for example: SD or DX memory, etc.), magnetic memory, disk, optical disk, etc. In some embodiments, the memory 12 can be an internal storage unit of the electronic device 1, such as a mobile hard disk of the electronic device 1. In other embodiments, the memory 12 can also be an external storage device of the electronic device 1, such as a plug-in mobile hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. equipped on the electronic device 1. Further, the memory 12 can also include both an internal storage unit of the electronic device 1 and an external storage device. The memory 12 can not only be used to store application software and various types of data installed in the electronic device 1, such as codes for border conflict management, etc., but can also be used to temporarily store data that has been output or is to be output.

[0050] In some embodiments, the processor 13 may be composed of an integrated circuit, for example, a single packaged integrated circuit, or a plurality of packaged integrated circuits with the same or different functions, including one or more central processing units (CPUs), microprocessors, digital processing chips, graphics processors, and combinations of various control chips. The processor 13 is the control core (Control Unit) of the electronic device 1, and uses various interfaces and lines to connect various components of the entire electronic device 1, and executes or executes programs or modules (such as boundary conflict management programs, etc.) stored in the memory 12, and calls data stored in the memory 12 to execute various functions of the electronic device 1 and process data.

[0051] The processor 13 executes the operating system and various installed applications of the electronic device 1. The processor 13 executes the applications to implement the steps in the above-mentioned boundary conflict management method.

[0052] Exemplarily, the computer program may be divided into one or more modules, which are stored in the memory 12 and executed by the processor 13 to complete the present application. The one or more modules may be a series of computer program instruction segments capable of completing specific functions, which are used to describe the execution process of the computer program in the electronic device 1. For example, the computer program may be divided into a hierarchy creation unit 111, a hierarchy setting unit 112, a conflict checking unit 113, and a ticket processing unit 114.

[0053] The above-mentioned integrated unit implemented in the form of a software function module can be stored in a computer-readable storage medium, and the computer-readable storage medium can be non-volatile or volatile. The above-mentioned software function module is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a computer device, or a network device, etc.) or a processor to perform part of the functions of the boundary conflict management method described in each embodiment of the present application.

[0054] In summary, the present invention discloses a boundary conflict management method, system, electronic device and storage medium. In the process of managing existing tickets, the ticket types of different priority levels are configured / classified for existing tickets and current tickets. In the process of checking conflicts between all existing tickets and current tickets, it is possible to determine whether there is a boundary conflict based on the status information of the existing tickets and the current tickets, and further determine whether there is a boundary conflict based on the priority level in combination with the ticket types of the existing tickets and the current tickets. And when there is a conflict, the ticket issuance priority is further determined according to the priority level of the existing tickets and the current tickets, and the existing tickets or current tickets with higher priority are selected for issuance to obtain the final boundary state of the current boundary device. In this way, it can be ensured that when adding the current ticket, the boundary state management based on different management levels can be completed more comprehensively and accurately, so as to ensure that the risk of high-risk boundary states in the management process is controllable, and the efficiency of checking boundary conflicts is also improved. The cross-group conflict rules between PA / PO / TOB / TOTO and standard isolation established above are the prerequisites for the integrated management of isolation functions. Only after the rules are clarified can the three module systems be integrated and automatically operated. Therefore, the present invention effectively overcomes various shortcomings in the prior art and has high industrial utilization value.

[0055] The above embodiments are merely illustrative of the principles and effects of the present invention, and are not intended to limit the present invention. Anyone familiar with the art may modify or alter the above embodiments without departing from the spirit and scope of the present invention. Therefore, all equivalent modifications or alterations made by a person of ordinary skill in the art without departing from the spirit and technical concept disclosed by the present invention shall still be covered by the claims of the present invention.

Claims

1. A border conflict management method, characterized in that: The steps include: Establishing several priority tiers of ticket types; Set ticket types for all existing tickets according to several priority levels of ticket types; Obtain the current ticket, and perform a conflict check based on the ticket type and status information of the current ticket and the ticket type and status information of all existing tickets; When there is a conflict, the voting result with a higher ticket issuance priority is selected from the existing tickets and the current ticket according to the ticket issuance priority rule to issue the ticket.

2. The border conflict management method according to claim 1, characterized in that: Establish several priority tiers of ticket types, including: A plurality of ticket type groups of different priorities are created, each of which has at least one sub-ticket type.

3. The border conflict management method according to claim 1, characterized in that: Set ticket types for all existing tickets based on several priority levels of ticket types, including: A ticket type corresponding to a priority level is set for each boundary instruction of each boundary device of all existing tickets; wherein the status information of the existing tickets includes the device status, the implementation status of the boundary instruction, and the boundary status, and the implementation status includes one of the isolation preparation status, isolation confirmation status, release preparation status and suspension preparation status.

4. The border conflict management method according to claim 1, characterized in that: A conflict check is performed based on the ticket type and status information of the current ticket and the ticket type and status information of all existing tickets, including: Get the ticket type, device status, implementation status of boundary instructions, and boundary status of the current ticket and existing tickets; Conflict detection is performed based on the ticket type, device status, implementation status of boundary instructions, and boundary status of the current ticket and existing tickets.

5. The border conflict management method according to claim 4, characterized in that: Conflict detection is performed based on the ticket type, device status, implementation status of boundary instructions, and boundary status of the current ticket and existing tickets, including: Check the validity of existing tickets according to the implementation status of the boundary instructions in the existing tickets: Determine whether an existing ticket is in the implemented state: If not, the existing ticket is determined to be invalid; If yes, determine whether the ticket type, device status, and boundary status of the current ticket and the ticket type, device status, and boundary status of the existing ticket meet the conflict rules, including whether the following three conditions are met at the same time: The ticket type of the current ticket is consistent with the ticket type of the existing ticket; and / or The device status of the current ticket and the device status of the existing ticket satisfy the device status rule; and / or The boundary state of the current ticket is consistent with the boundary state of the existing ticket; If so, it is determined that the conflict rule is satisfied; if not, it is determined that the conflict rule is not satisfied.

6. The border conflict management method according to claim 5, characterized in that: Determining whether the device status of the current ticket and the device status of the existing ticket meet the device status rules includes: whether the following four conditions are met at the same time: The current ticket's host device is the host device of an existing ticket; and / or The current ticket's master device is an edge device that already has a ticket; and / or The boundary device for the current ticket is the master device for the existing ticket; and / or The boundary device of the current ticket is the boundary device of the existing ticket; If so, the device status rule is satisfied; if not, the device status rule is not satisfied.

7. The border conflict management method according to claim 1, characterized in that: When there is a conflict, the voting result with a higher priority for issuing a ticket is selected from the existing ticket and the current ticket according to the ticket issuing priority rule for issuing a ticket, including: Determine the ticket issuance priority of the current ticket and existing tickets according to the priority level of the ticket type; If the priority of the current ticket is higher than that of the existing ticket, the ticket will be issued according to the boundary instruction of the current ticket; If the priority of the existing ticket is higher than the priority of the current ticket, the ticket will be issued according to the boundary instruction with the highest priority among the existing tickets.

8. A border conflict management system, characterized in that: include: A tier creation unit, used to establish several priority tiers of ticket types; A level setting unit sets ticket types for all existing tickets according to ticket types of several priority levels; A conflict checking unit, used to obtain a current ticket and perform a conflict check based on the ticket type and status information of the current ticket and the ticket type and status information of all existing tickets; The ticket processing unit is used to select a corresponding voting result with a higher ticket issuance priority from the existing ticket and the current ticket according to the ticket issuance priority rule to issue the ticket when there is a conflict.

9. An electronic device, characterized in that: The electronic device comprises: one or more processors; A storage device for storing one or more programs, which, when executed by the one or more processors, enables the electronic device to implement the border conflict management method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and when the computer program is executed by a processor of a computer, the computer is caused to execute the border conflict management method according to any one of claims 1 to 7.

Images