RU2780964C2 - System and method for automated drilling network - Google Patents

Abstract

FIELD: computer technology.

SUBSTANCE: system of interaction of a drilling control network and a user network contains the first control system connected to a set of network elements, which forms the drilling control network; a virtualization service dispatcher connected to the first control system and the set of network elements; a virtual connection controller connected to the set of network elements, wherein the virtual connection controller establishes a virtual connection between the first control system and the user network; and an operation ending dispatcher connected to the virtualization service dispatcher, the set of network elements, and the first control system, wherein the operation ending dispatcher finishes operations of the first control system and the virtualization service dispatcher in accordance with a sequence of operation ending for the drilling control network.

EFFECT: increase in the degree of safety in the interaction of a drilling control network and a user network.

14 cl, 34 dwg

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority of U.S. Provisional Application No. 62/556,815 entitled "Rig Security", which was filed September 11, 2017, and is incorporated herein by reference in its entirety.

BACKGROUND OF THE INVENTION

[0002] To control various operations on the drilling rig, various network devices may be located throughout the drilling rig. These network devices may control the drilling equipment, monitor the performance of the drilling rig, and/or perform various maintenance activities on the drilling rig. Accordingly, there are various problems regarding the effective enforcement of security protocols in relation to such network devices.

SUMMARY OF THE INVENTION

[0003] In general, in one aspect, the disclosed technology relates to a system. The system comprises a control system connected to various network elements that form a drilling control network. The control system contains a programmable logic controller (PLC) that performs drilling operations. The system further comprises a virtualization service manager connected to the management system and network elements. The virtualization service manager implements a virtualization service on the drilling control network that controls the drilling operation. The system further comprises a controller connected to the network elements. The virtual connection controller establishes a virtual connection between the control system and the user network.

[0004] In general, in one aspect, the disclosed technology relates to a system comprising a control system coupled to a first set of network elements that form a first security zone in a drilling control network. The control system contains a programmable logic controller (PLC) that performs drilling operations. The system further comprises a virtualization services manager connected to the management system and the first set of network elements. The virtualization service manager implements a virtualization service on the drilling control network that controls the drilling operation. The system further comprises a firewall connected to the first security zone and the second security zone containing the second set of network elements. The drilling control network reconfigures, in response to checking the network device, the first security zone to allow the network device to communicate with the destination device in the second security zone.

[0005] In general, in one aspect, the disclosed technology relates to a system. The system comprises a control system connected to various network elements that form a drilling control network. The control system contains a programmable logic controller (PLC) that performs drilling operations. The system further comprises a virtualization service manager connected to the management system and network elements. The virtualization service manager implements a virtualization service on the drilling control network that controls the drilling operation. The system further comprises a configuration manager connected to the network elements and the control system. The Configuration Manager installs the update on the management system using the security agent on the system.

[0006] Other aspects of the invention will become apparent from the following description and the appended claims.

BRIEF DESCRIPTION OF GRAPHICS

[0007] FIG. 1, 2, 4, 9.1, 9.2, 9.3, 13, 16, 17, 20.1, 20.2, 24, and 28 illustrate systems in accordance with one or more embodiments of the invention.

[0008] FIG. 3, 5, 7, 10, 11, 15, 18, 19, 21, 22, 25, 27, 29 and 30 illustrate block diagrams in accordance with one or more embodiments of the invention.

[0009] FIG. 6, 8.1, 8.2, 12, 14, 23, 26.1, 26.2, 31, 32, and 33 illustrate examples in accordance with one or more embodiments of the invention.

[0010] FIG. 34.1 and 34.2 illustrate a computing system in accordance with one or more embodiments of the invention.

DETAILED DESCRIPTION OF THE INVENTION

[0011] Specific embodiments of the invention will be described in detail with reference to the accompanying figures. To ensure consistency, the same elements in different figures are indicated by the same reference numbers.

[0012] In the following detailed description of embodiments of the invention, numerous specific details are provided in order to provide a better understanding of the invention. However, it will be apparent to those skilled in the art that the invention may be practiced without these specific details. In other cases, well-known features have not been described in detail in order to avoid over-complicating the description.

[0013] Throughout the application, ordinal numbers (eg, first, second, third, etc.) can be used as having adjective properties for the element (ie, any noun in the application). The use of ordinal numbers does not imply or create any particular ordering of the elements, nor does it restrict any element to only one element unless it is explicitly described, for example, through the use of the terms "before", "after", "one", and other similar terms. Rather, the use of ordinal numbers is intended to distinguish between elements. As an example, the first element is different from the second element, wherein the first element may contain more than one element and follow (or precede) the second element in the arrangement of the elements.

[0014] In general, embodiments of the invention include various systems and various methods for operating a drilling control network. In particular, one or more embodiments of the invention relate to a drilling control network that includes various programmable logic controller (PLC) control systems. In particular, a virtualization services manager running on a network may create virtual machines and/or software containers at the virtualization services layer. These virtual machines and/or software containers may perform one or more drilling and/or maintenance operations.

[0015] In addition, the drilling control network may include a configuration manager, a coordinated controller, and/or other network devices for automating and/or prioritizing various processes running on the drilling control network. Thus, the disclosed technology describes various implementations that can provide solutions to the operational challenges associated with a drilling control network. Accordingly, one or more methods of the disclosed technology can bridge the gaps between process automation found in various industries and those conditions that are characteristic of a drilling control network.

[0016] FIG. 1 illustrates a block diagram of a system in accordance with one or more embodiments of the invention. In FIG. 1 illustrates a drilling system (10) in accordance with one or more embodiments of the invention. The drill string (58) is illustrated as being located within the wellbore (46). The borehole (46) may be located in the earth (40) having a surface (42). The wellbore (46) is illustrated as being cut by the action of a drill bit (54). The drill bit (54) may be located at the distal end of the bottom hole assembly (56) that is attached to and forms the bottom of the drill string (58). The bottom hole assembly (56) may comprise a number of devices containing various subassemblies. The sub-units (62) may include measurement-while-drilling (MDD) sub-units. Examples of BSI measurements may include the following: direction, borehole inclination, inspection data, downhole pressure (pressure inside and/or outside the drill pipe, and/or annulus pressure), resistivity, density, and porosity. Subassemblies (62) may also include subassemblies for measuring torque and axial load on the drill bit (54). The signals from the subblocks (62) may be processed in the processor (66). After processing, information from the processor (66) can be transmitted to the block (64) of the pulse generator. Block (64) of the pulse generator can convert information from the processor (66) into pressure pulses in the flushing fluid. The pressure pulses can be generated into a special structure, which is the data from the sub-units (62). The pressure pulses can travel upward through the flushing fluid in the central hole in the drill string and to the system at the surface. The subassemblies in the bottom hole assembly (56) may further comprise a turbine or motor to provide power to rotate and control the drilling direction of the drill bit (54).

[0017] The drilling rig (12) may include a drilling derrick (68) and a lifting system, a rotating system and/or a drilling fluid circulation system, for example. The lifting system may suspend the drill string (58) and may include a drawworks (70), a running end (71) of a wireline, a crown block (75), a wireline (79), a traveling block and a hook (72), a swivel (74) and /or fixed end (77) of the drilling line. The rotating system may include a kelly (76), a rotary table (88), and/or motors (not shown). The rotating system can impart rotational force to the drill string (58). Similarly, the embodiments of the invention illustrated in FIG. 1 may also be applicable to top drive drilling configurations. Although the drilling system (10) is illustrated as being located on land, those skilled in the art will find that the described embodiments of the invention are equally applicable to offshore and coastal environments as well.

[0018] The mud circulation system may force the drilling fluid down along the hole in the drill string. The drilling fluid may be referred to as a drilling fluid, which may be a mixture of water and/or diesel fuel, specialty clays and/or other chemicals. The drilling fluid may be stored in the drilling fluid storage pit (78). The mud may be diverted to mud pumps (not shown) which may force the mud through the drill string (86) and into the kelly (76) through a swivel (74) which may include a rotary seal. Likewise, the techniques described may also be applicable to reduced hydrostatic pressure drilling. In the case where low hydrostatic pressure drilling is used, gas may be introduced at some points before the drill string is introduced into the drilling fluid by means of an injection system (not shown).

[0019] The drilling fluid may pass through the drill string (58) and through the drill bit (54). As the teeth of the drill bit (54) grind and gouge the geologic formation, forming drill cuttings, drilling fluid can be supplied through the holes or flushing nozzles of the drill bit (54). These mud jets can lift cuttings from the bottom of the hole and away from the drill bit (54), and up to the surface in the annulus between the drill string (58) and the borehole wall (46).

[0020] At the surface, drilling fluid and cuttings may exit the wellbore through a side arm of the blowout preventer (99) and through a mud return line (not shown). The blowout preventer (99) includes a pressure control device and a rotary seal. The mud return conduit may supply the drilling fluid to one or more separators (not shown) that may separate the drilling fluid from the drilling cuttings. From the separator, the drilling fluid can be returned for storage and reuse to the drilling fluid storage pit (78).

[0021] Various sensors may be located on the drill string (12) to take measurements of the drilling equipment. In particular, the hook load can be measured by means of a hook load sensor (94) mounted on the fixed end (77) of the drilling line, the position of the block and the associated speed of the block can be measured by means of a block sensor (95), which may be included in composition of the drawworks (70). The surface torque can be measured by means of a sensor on the rotary table (88). The pressure of the drill stem can be measured by a pressure sensor (92) located on the drill stem (86). Signals from these measurements may be transmitted to the surface processor (96) or other network elements (not shown) located near the drilling rig (12). In addition, mud pulsations moving up the drill string can be detected by the pressure sensor (92). For example, the pressure sensor (92) may include a transducer that converts mud pressure into electronic signals. The pressure sensor (92) may be connected to a surface processor (96) which digitizes the signal from the pressure signal, stores and demodulates the digital signal into usable SPI data. In accordance with the various embodiments of the invention described above, the surface processor (96) may be programmed to automatically detect one or more rig states based on the various input channels described. The processor (96) may be programmed, for example, to perform automated event detection as described above. The processor (96) may communicate information about a specific rig state and/or detected condition to a user interface (97) system that may be designed to alert various rig personnel of events occurring on the rig and/or advise drilling rig personnel to take action. to prevent certain events. As described below, one or more of these equipments may be controlled by a drilling control network connected to the drilling rig (12). For example, the drilling control network (210) described below with reference to FIG. 2 can automate one or more of the drilling processes associated with this equipment without manual user intervention.

[0022] Returning to FIG. 2, in FIG. 2 illustrates a block diagram of a system in accordance with one or more embodiments of the invention. As illustrated in FIG. 2, the drilling control network (210) may contain a human machine interface (HMI, human machine interface) (for example, HMI (218)), an archive data server (for example, an archive data server (225)), various network elements (for example, elements (224) of the network). The human-machine interface may be hardware and/or software associated with the drilling control network (210) and which is configured to present data and/or receive input from a user related to various drilling and/or maintenance operations. service performed in the drilling control network (210). For example, the human-machine interface may include software for providing a graphical user interface (GUI) for presenting data and/or receiving control commands for operating the drilling rig. The archive server may be hardware and/or software that is configured to record events occurring on the drilling control network. For example, the history server may store the time and description of events related to equipment and/or control systems, sensor measurements, and/or operational parameters in the history server's records, such as when troubleshooting. A network element may refer to various hardware components in a network, such as switches, routers, hubs, user equipment, or any other logical entity for connecting one or more physical devices in a network.

[0023] In one or more embodiments, the drilling control network (210) comprises drilling equipment (e.g., drilling equipment (219), blowout preventer (99), drilling rig (12), and other components described above in FIG. 1, and in the accompanying description) and various physical components associated with the drilling equipment, for example, for measuring and/or controlling the drilling equipment. The drilling control network (210) may further comprise control systems (eg, control systems (221)), such as various drilling operations control systems and/or various maintenance control systems, which are deterministic parts of the network. Drilling operations control systems and/or maintenance management systems may include, for example, programmable logic controllers (PLCs) (eg, PLC (217)), which contains hardware and/or software with functionality to control one or more processes performed by by means of a drilling rig, including but not limited to the components illustrated in FIG. 1. In particular, the programmable logic controller may control valve states, fluid levels, pipe pressures, alarms, and/or depressurizations throughout the rig. For more information on control systems in the drilling control network, see U.S. Patent Application No. 14/788,124 entitled "Rig Control System", which was filed June 30, 2015, published as US 2016/0290119, and U.S. Patent Application No. 14 /788,038, entitled “Unified Control System for Drilling Rigs”, which was filed June 30, 2015, published as US 2016/0222775, US Patent Application No. 14/754,901, entitled “Drilling Control System”, which was filed June 30 2015 published as US 2016/0290120. Each of the published patent applications is incorporated herein by reference in its entirety.

[0024] In addition, the programmable logic controller may be a computer system with increased resistance to adverse environmental conditions, designed to withstand vibrations, extreme temperatures, humid environmental conditions and/or dusty environmental conditions, such as near a drilling rig. Drilling control systems and/or maintenance control systems may also refer to control systems that include a plurality of PLCs in a drilling control network. In addition, the control system may be part of a drilling control feedback network that is configured to control operations within the system, block, and/or sub-block illustrated above in FIG. 1 and in the accompanying description. The PLC may transmit PLC data to one or more devices connected to the drilling control network and/or user network. The PLC data may include: sensor measurements, status updates and/or information related to drilling operations and/or maintenance operations. Likewise, one or more control systems (e.g., control system (221)) may be configured to control and/or perform various drilling operations with respect to a mud circulation system, a rotary system, a pipe supply system, and/or various other drilling operations. illustrated with respect to FIG. 1 and described in the accompanying description.

[0025] In addition, the drilling control network may be connected to a user network (eg, user network (230)). In particular, the user network may comprise various network elements, user devices (eg, user device X (251)), and/or user equipment at the well site (eg, user equipment (242) at the well site). For example, user equipment at a well site may include a telephone network, personal computers, printers, application servers, and/or file servers located near the drilling rig. User devices may also be connected to the drilling control network, where user devices may include personal computers, smartphones, human-machine interfaces, and any other network-connected devices that receive input from one or more users. The network elements, HMIs, historical data servers, well site user equipment, user devices, and/or other network devices may comprise computing systems similar to computing systems (3400) shown in FIG. 34.1 and 34.2, and described in the accompanying description.

[0026] In some embodiments, the virtual connection controller (eg, virtual connection controller (243)) controls access to the drilling control network. The virtual connection controller may be hardware and/or software that is configured to establish a virtual connection (e.g., virtual connection (235)) between a user network (e.g., user network (230)) and a drilling control network (e.g., network (210) drilling control). A virtual connection may be, for example, a link layer connection between two adjacent network elements, such as two network switches. In other embodiments of the invention, the virtual connection may be a point-to-point connection through a plurality of network nodes. Similarly, the virtual connection controller may be a virtual machine (VM, virtual machine), a software container, or a physical network element located on the user's network. For example, the virtual connection controller (243) may be an installation server or a network element that communicates with an installation server in the user network (230). In some embodiments of the invention, the drilling control network contains a plurality of installation servers for different security zones, such as control zones, for example, in cases where the virtual connection controller communicates with each installation server based on where one or more virtual connections are established. In one or more embodiments of the invention, for example, the virtual connection controller is configured to power on and/or power off the installation server that communicates with devices on the drilling control network.

[0027] In one or more embodiments of the invention, the virtual connection controller is located in the user network (eg, user network (230)). Similarly, in some embodiments of the invention, the virtual connection controller comprises hardware and/or software distributed among a plurality of network elements in the user network and the drilling control network. In one or more embodiments of the invention, for example, the virtual connection controller is an installation server that is configured to manage security on a drilling control network. In particular, the drilling control network may be a separate security zone from the user network. For more information about the Virtual Connection Controller, see the section below entitled "Virtual Connection Controller" and the accompanying description.

[0028] In some embodiments, the drilling control network includes a virtualization services manager (eg, virtualization services manager (213)). The Virtualization Services Manager may include hardware and/or software that is configured to generate, terminate, monitor, and/or manage one and/or more virtual machines (e.g., virtual machines (227)) and/or software containers (e.g., software containers (229)) operating at the level of drilling control network virtualization services. In some embodiments of the invention, the virtualization services manager includes a hypervisor for managing one or more virtualized environments in the drilling control network. For example, the virtualization services may include a network process that manages drilling operations and/or maintenance operations implemented on the drilling control network, such as where virtual machines and/or software containers operate at the network layer. Instead of implementing a virtual machine or software container on a single host device, for example, a virtualization service may be implemented using a virtual machine or software container that runs on multiple host devices. For more information about the Virtualization Services Manager, see the sections below entitled "Managing Shutdown and Startup" and "Replication of Secure Data" and the accompanying descriptions.

[0029] In some embodiments, the drilling control network includes a coordinated controller (eg, coordinated controller (229)). For example, the coordinated controller may communicate with the virtualization services manager to prioritize various automated operations, such as drilling operations and/or maintenance operations, in the drilling control network. For more information about the Coordinated Controller, see the section below entitled "Configuration Manager and Coordinated Controller" and the accompanying descriptions.

[0030] In some embodiments, the drilling control network includes a shutdown manager (eg, shutdown manager (211)). A shutdown manager may be hardware and/or software that is configured to initiate shutdown operations on one or more host devices, one or more virtual machines, one or more virtual containers, one or more virtualization controllers, and/or a shutdown manager. virtualization services. In one or more embodiments of the invention, the virtualization services manager and the shutdown manager are the same software application on the network device. For example, the shutdown manager may be configured to monitor environment variables and other network variables for various systems in the drilling control network. Thus, in response to various triggers associated with environment variables and network variables, the shutdown manager can initiate a coordinated process based on established rules to perform a complete shutdown of the control system or subsystems in the drilling control network. For more information about Shutdown Manager, see the section below titled "Managing Shutdown and Startup" and the accompanying description.

[0031] In some embodiments of the invention, the various components of the drilling control network are divided into different security zones, such as a control zone and a control zone. In particular, different security zones may be connected using a firewall (eg, firewall (226)). For example, the firewall may include hardware and/or software configured to filter data packets transmitted between the control zone and the control zone. In particular, the firewall may perform packet analysis at one or more network layers, such as the transport layer and/or the application layer of the drilling control network. In particular, the firewall may analyze the packet and/or the application that sent the packet to determine whether the data transfer between the source device and the destination device was authorized in different security zones. In some embodiments of the invention, the authorization of packages is determined using certificate-based authentication. For example, network devices in control zones and management zones can be assigned security certificates that can be stored on network devices. The firewall may be configured to act as an authentication server to determine if a security certificate has expired and/or if a source device (e.g., configuration manager (216) ) is authorized to communicate with a destination device, such as an archive server. data, management system, user device, virtual machine, etc. For more information about network communication management in the zone of control, see the section below entitled "Control system cybersecurity" and the accompanying description. Similarly, additional information on the interworking of firewalls and the drilling control network can be found in U.S. Patent Application No. 15/361,781 entitled “Well Construction Site Communications Network”, which was filed November 28, 2016 and published as US 2018/0152319 , which is incorporated herein by reference in its entirety.

[0032] In some embodiments of the invention, one or more network devices in the zone of control may contain one or more security agents (eg, agents (261) security). The security agent may comprise hardware and/or software configured to operate as a local entity on a host network device within a zone of control. For example, the security agent may be located on a human-machine interface, an archive server, one or more control systems, etc. Accordingly, the security agent may be configured to enforce a security rule and an access control policy on an appropriate network device. . Thus, the security agent may communicate with a configuration manager (eg, configuration manager (216)) and/or an application manager via a firewall to administer software installations and/or software processes on its host network device. In addition, the configuration manager may be hardware and/or software that is configured to manage software settings for one or more devices in the drilling control system. For example, the configuration manager may detect a software update to manage the system and coordinate software installation using a security agent on the control system. For more information about the security agent and the configuration manager, see the sections below entitled "Control System Cyber Security" and "Configuration Manager and Coordinated Controller" and the accompanying description.

[0033] In some embodiments, the drilling control network comprises a data control controller (eg, data control controller (212)) connected to various persistent storage devices (eg, persistent storage devices (215)). The persistent storage device may comprise hardware and/or software that is configured to implement a non-volatile storage device. For example, the persistent storage device may include a persistent storage drive such as a hard drive and/or solid state drive in a central data repository. In one or more embodiments of the invention, the data management controller comprises hardware and/or software that is configured to manage the storage and/or retrieval of data with respect to various persistent storage devices. For example, a data management controller may be part of a central data repository that contains various persistent data storage devices in a drilling control network. Similarly, the data controller may establish one or more network connections with one or more remote devices (eg, device Y (252) user). Thus, the data management controller can manage data communication between the network device and the drilling control network via the Internet (eg, Internet (250)). For more information about the data controller and persistent storage devices, see the section below titled "Secure Data Replication" and the accompanying description.

[0034] In some embodiments, the drilling control network includes a drilling rig commissioning system (eg, drilling rig commissioning system (222)). For example, a drilling rig commissioning system may generate a knowledge graph that describes the control system and subsystems within the control system. Accordingly, using the knowledge graph, the drilling rig commissioning system can automatically commission the control system for drilling operations and/or maintenance operations in the drilling control network. Further information about the knowledge graph and the rig commissioning system can be found in the section below entitled "Smart Control System Commissioning" and the accompanying description.

[0035] While in FIG. 1 and 2 illustrate various component configurations, other configurations may be used without departing from the scope of the present invention. For example, the various components in FIG. 1 and 2 can be combined to create one component. In another example, the components illustrated in the user network (230) may also be located in the drilling control network (210), while the components illustrated in the drilling control network (210) may also be located in the user network (230). As another example, functions performed by one component may be performed by two or more components.

[0036] In addition, the various components in FIG. 1 and 2 are described as "configured" with a specific type of functionality. Thus, "configured" in this application may mean certain computer-readable instructions residing in software, such as firmware in a physical device, that performs one or more of the methods as described in this application. Likewise, "configured" may also mean certain configurations, settings, parameters, and other stored variables that define a particular function performed by the hardware and/or software. For example, a hardware register may be configured with specific values that define the type and/or mode of operation of the hardware device. Thus, various network devices may be configured to implement a particular confirmation operation with the drilling control network and/or user network. In addition, "configured" can also refer to the hardware and/or software protocols that define the physical interactions between components within and/or outside the network.

[0037] Returning to FIG. 3, in FIG. 3 illustrates a block diagram in accordance with one or more embodiments of the invention. In particular, in FIG. 3 illustrates the operation of a drilling control network. One or more steps in FIG. 3 may be performed by one or more components (eg, a virtual connection controller (243)), as illustrated in FIG. 1 and/or 2. While the various steps in FIG. 3 are illustrated and described sequentially, it will be apparent to those skilled in the art that some or all of the steps may be performed in different order, may be combined or omitted, and some or all of the steps may be performed in parallel. In addition, steps can be performed actively or passively.

[0038] At step 300, start is initiated for various virtualization services in the zone of control in accordance with one or more embodiments of the invention. For example, the components in the drilling control network may contain functionality for implementing various methods to initiate an automated start-up process. In particular, different virtual connection controllers running on different host devices can choose a virtualization service manager from their group. Accordingly, the virtualization service manager may control the automated process of starting various virtualization services, virtual machines, and/or software containers via the drilling control network using time-delayed initialization commands. More information about the automated startup process can be found in FIG. 11 and in the section below entitled "Managing Shutdown and Startup" and the accompanying description.

[0039] At step 310, the control area is reconfigured to account for one or more new network devices, in accordance with one or more embodiments of the invention. In some embodiments of the invention, networking for various devices within a control zone is limited to predetermined links. In other words, a network device may only be allowed to communicate with certain authorized devices in the control area. For example, when a new network device is added to the control zone, the new network device can be checked to determine which devices inside and/or outside the control zone are authorized to communicate with the new network device. Accordingly, the control zone may be reconfigured, for example, using network elements and/or firewalls, to implement authorized data transmission. Additional information on reconfiguration and control of data transmission in the monitoring area can be found in FIG. 18 and in the section below entitled "Control System Cybersecurity" and the accompanying description.

[0040] At step 320, one or more software applications are installed on one or more network devices in the zone of control using one or more security agents in accordance with one or more embodiments of the invention. For example, the drilling control network may include a configuration manager that communicates with a security agent. The security agent may be located on a network device within the control zone, while the configuration manager may be located in the control zone outside the control zone. Thus, the configuration manager can detect software updates for software applications running in the zone of control, such as software applications for providing virtualization services through virtual machines, software containers, management systems, etc. Accordingly, the configuration manager can coordinate with the security agent installing software installation files, such as which days and times the network device is not used for drilling and/or maintenance operations. Additional information about installing software on network devices in the control zone can be found in Fig. 19 and in the section below entitled "Control System Cybersecurity" and the accompanying description.

[0041] At step 330, one or more control systems for the control area are automatically put into operation in accordance with one or more embodiments of the invention. For example, a drilling rig commissioning system in a drilling control network may generate a knowledge graph. Using the knowledge graph, the rig commissioning system may automatically commission the control system for drilling operations and/or maintenance operations within the control zone. Further information on automatic commissioning control systems can be found in the section below entitled "Smart Commissioning of the Control System" and the accompanying description.

[0042] At 340, sensor data is obtained from one or more sensor devices, in accordance with one or more embodiments of the invention. In some embodiments, for example, the drilling control network may comprise sensor devices (eg, sensor device (214)) that establishes a network connection directly to the drilling control network. For example, the sensor device may include a smart sensor device with a communication interface for receiving and transmitting data, such as sensor data, over a drilling control network. Thus, control systems in the drilling control network can subscribe to receive sensor data from the sensor smart device. Similarly, the control system may receive sensor data, parse the sensor data as to whether the sensor data type is being used by any application, and then use or ignore the sensor data accordingly. Thus, sensor data can be transmitted over the drilling control network by implementing a communication protocol that routes sensor data from the sensor smart device to the control system. For more information about sensor smart devices and the transmission of sensor data over the drilling control network, see the section below entitled "Sensor Smart Device Integration" and the accompanying description.

[0043] At step 350, a virtual connection is established with the control zone in accordance with one or more embodiments of the invention. In some embodiments of the invention, for example, after a network device is authenticated by a virtual connection controller, a virtual connection is established for a certain period of time between the control zone and another security zone, such as one that may be present in the user network. For example, the virtual connection controller may control the time channel that establishes the virtual connection. Although the virtual connection is made over the Internet, network traffic can flow outside and in the zone of control. After the virtual connection is completed, the zone of control can again become a closed network, protected from various possible security breaches. Likewise, such temporary virtual connections can enforce security criteria simultaneously for local users and/or for remote users who enter the user's network over the Internet. In addition, the drilling control network can provide automatic control of when and to what parts of the control zone different users access. Additional information about virtual connections and virtual connection controllers can be found in the sections below entitled "Virtual Connection Controller" and "Cyber Security Framework" and the accompanying descriptions.

[0044] At step 360, one or more drilling operations are performed using one or more control systems in the control zone in accordance with one or more embodiments of the invention. In addition, the control zone in the drilling control network may contain one or more components, such as a coordinated controller or a virtualization service manager, for administering drilling operations and/or maintenance operations. For example, the control zone may include control systems that automate drilling operations and/or maintenance operations without user intervention. Further information on managing drilling operations, for example, can be found in U.S. Patent Application No. 14/982,917 entitled "Well Construction Display", which was filed December 29, 2015 and published as US 2017/0167200, which is incorporated herein in its entirety. through a link.

[0045] At 370, the virtual connection is terminated in accordance with one or more embodiments of the invention. For example, a virtual connection may be terminated when the virtual connection controller removes the link layer connection between the control zone and another security zone, such as a user network. Termination may return the zone of control to a closed state. Similarly, firewall settings can be set by the virtual connection controller to block network traffic from and to the zone of control. In the case of a switched virtual connection, the virtual connection controller may set the switched virtual connection to a state such that it represents an open circuit. In one or more embodiments of the invention, for example, the virtual connection controller turns off the power and disconnects after determining that the virtual connection is completed.

[0046] At step 380, shutdown of the control zone is initiated in accordance with one or more embodiments of the invention. In some embodiments of the invention, for example, the drilling control network includes a shutdown manager that manages the shutdown sequence for shutdown operations for devices in the control zone. In some embodiments of the invention, shutdown is initiated for the entire drilling control network. Shutdown sequencing can be performed using time-delay shutdown commands that allow devices in the control zone to shut down in an orderly manner. For more information on shutdown sequences and shutdown managers, see the section below entitled "Managing Shutdown and Startup" and the accompanying description.

Virtual connection controller

[0047] In general, embodiments of the invention include a system and various methods for accessing control systems in a drilling control network.

[0048] Returning to FIG. 4 in FIG. 4 illustrates a block diagram of a system in accordance with one or more embodiments of the invention. As illustrated in FIG. 4, the drilling control network (410) may include a human machine interface (HMI) (e.g., HMI (421)), a history server (e.g., a history server (425)) and various network elements (e.g., elements (424) networks). The human-machine interface may be hardware and/or software associated with the drilling control network (410) and which contains functionality for presenting data and/or receiving input from a user related to various drilling and/or drilling operations. maintenance performed on the drilling control network (410). For example, the human-machine interface may include software for providing a graphical user interface (GUI) for presenting data and/or receiving control commands for operating a drilling rig. A network element may refer to various hardware components in a network, such as switches, routers, hubs, or any other logical entity for connecting one or more physical devices in a network. In particular, the network element, the human-machine interface, and/or the archive server may be a computing system similar to the computing system (3400) illustrated in FIG. 34.1 and 34.2, and described in the accompanying description.

[0049] In one or more embodiments, the drilling control network (410) may include drilling equipment (e.g., drilling equipment (426)), such as a blowout preventer (99), a drilling rig (12), and other components illustrated above in fig. 1 and in the accompanying description. The drilling control network (410) may further comprise various drilling operations management systems (eg, drilling operations management systems (422)) and various maintenance management systems (eg, maintenance management systems (423)). Drilling operations control systems and/or maintenance management systems may include, for example, a programmable logic controller (PLC) that contains hardware and/or software with functionality to control one or more processes performed by a drilling rig, including, but, without being limited to the components illustrated in FIG. 1. In particular, the programmable logic controller may control valve states, fluid levels, pipe pressures, alarms, and/or depressurizations throughout the rig. In particular, the programmable logic controller may be a ruggedized computer system with functionality to withstand vibration, extreme temperatures, wet environments, and/or dusty environments, such as near a drilling rig.

[0050] In addition, drilling operations control systems and/or maintenance management systems may refer to control systems that contain a plurality of PLCs in the drilling control network (410). For example, the control system may include functionality for control operations within the system, block, and/or sub-block illustrated above in FIG. 1 and in the accompanying description. Thus, one or more drilling control systems (422) may comprise functionality to control and/or perform various drilling operations with respect to a mud circulation system, a rotary system, a pipe supply system, and/or various other drilling operations illustrated with respect to fig. 1 and in the accompanying description. Similarly, one or more maintenance management systems (423) may include functionality to monitor and/or perform various maintenance activities related to drilling equipment located near the drilling rig. While drilling operations control systems and maintenance management systems are illustrated as separate devices in FIG. 4, in one or more embodiments of the invention, the PLC and other drilling equipment (426) on the rig may be used simultaneously in the drilling operations control system and in the maintenance management system.

[0051] In one or more embodiments of the invention, the drilling control network (410) is connected to a user network (eg, user network (430)). In particular, the user network (430) may comprise various network elements (eg, network elements (441)) and/or wellsite user equipment (eg, wellsite user equipment (442)). For example, user equipment at the well site may include a telephone network, personal computers for different users, printers, application servers, and/or file servers located near the drilling rig. Similarly, the drilling control network (410) and the user network (430) may be connected via one or more physical data links. In one or more embodiments of the invention, for example, the user network (410) shares one or more network elements with the drilling control network (410).

[0052] In one or more embodiments of the invention, the drilling control network (410) transmits data over a virtual connection without restrictions on the type of data and the source of the data. Thus, the virtual connection can control the communication between the drilling control network (410) and the user network (430).

[0053] In the idle state, the virtual connection controller (443) may be physically connected to the drilling control network (410) and isolated from any network communication with the network elements (424) in the drilling control network (410). In one or more embodiments of the invention, when the virtual connection controller (443) detects a request to access the drilling control network (410) from an unauthorized user or user device, the virtual connection controller (443) may implement various rules on a local firewall (not shown). ) to establish a virtual connection to the drilling control network (410). The implemented rules may allow the user to access one or more approved software applications, set which network ports can receive data over the virtual connection, and/or assign network protocols to use approved Internet Protocol (IP) addresses within the virtual connection.

[0054] In one or more embodiments of the invention, the virtual connection controller (443) is disconnected from the drilling control network (410) while the drilling rig is performing drilling operations. Moreover, the virtual connection controller (443) may include functionality for powering up the installation server and establishing a virtual connection after receiving confirmation that the drilling rig is not performing a drilling operation.

[0055] In one or more embodiments of the invention, for example, the virtual connection controller (443) contains functionality for managing a switched virtual connection (for example, switched virtual connection (415)) located between the drilling control network (410) and the user network ( 430). For example, the switched virtual connection (415) may include hardware and/or software in the drilling control network (410) and user network (430) to implement the virtual connection. Thus, when the switched virtual connection (415) is in the "open" state, no virtual connection can occur between the user network (430) and the drilling control network (410). When the switched virtual connection (415) is in the "open" state, the switched virtual connection (415) can form a temporary virtual circuit that allows network traffic, such as PLC data (for example, PLC data (417) ), between the network (410 ) drilling and user network management (430). The PLC data may include: sensor measurements, status updates, and/or information related to drilling operations and/or maintenance operations performed on the drilling control network (410) that come from the drilling control network (410). In particular, the default state of the switched virtual connection (415) may occur when the drilling control network (410) disconnects from the user network (430) until the virtual connection controller (443) detects an authorized user and/or user device. The requesting access.

[0056] Similarly, although FIG. 4 illustrates one switched virtual connection, the drilling control network (410) and the user network (430) can connect a plurality of switched virtual connections. For example, in the event of a failure in a physical data link in a switched virtual connection, a plurality of switched virtual connections can be implemented for redundancy purposes. Similarly, the drilling control network (410) may comprise two or more physically separated networks, and different virtual connections may be established to provide access to different drilling control systems (422) and/or maintenance control systems (423). In addition, other network links may exist between the drilling control network (410) and the user network (430) that are not shown in FIG. 4 and enable the transmission of PLC data outside the drilling control network (410).

[0057] In one or more embodiments of the invention, the drilling control network (410) is a closed network. For example, the drilling control network (410) may be a physical network or a virtual network in cases where network communication is controlled between network nodes in the drilling control network (410) (e.g., network elements (424), operations control systems (422) drilling, maintenance management systems (423)), and network nodes outside the drilling management network (410) (e.g., network nodes in the user network (430), such as network elements (441) and/or user equipment (442) at the drilling site). In one or more embodiments of the invention, for example, while the drilling control network (410) and the user network (430) share one or more network elements, the network nodes in the drilling control network (410) cannot communicate with different devices. user (eg, user device X (451)) until a virtual connection is established in the switched virtual connection (415).

[0058] Moreover, the user network (430) may be an open network. In particular, network nodes in the user network (430) can receive and/or transmit data outside the user network (430), for example, via the Internet (450). Where the drilling control network (410) may be limited to network communication between network nodes in the drilling control network (410), users in the user network (430) may establish many different authorized network connections outside the user network (430) for example, users can make VoIP phone calls over the Internet (450), send emails, and/or access the Internet from a user's device on the user's network (eg, the user's device X (451)). Likewise, different user devices (eg, user device A (452) and user device N (458) may be connected to the user network (430). User devices may include various computer systems that contain functionality for connecting to the user network (430), such as smartphones, laptops, personal computers, etc.

[0059] In one or more embodiments of the invention, the drilling control network (410) comprises a distributed architecture. For example, the drilling control network (410) may include functionality to control drilling operations and/or maintenance operations located near the drilling rig without the use of a central controller. In another example, the drilling control network (410) may be a ring network in which PLC data, control commands, and other network traffic flows in one direction or multiple directions throughout the ring network. In one or more embodiments of the invention, when a virtual connection to the user network (430) is established, PLC data is transmitted in one direction through the drilling control network (410) to the virtual connection controller (443) and/or one or more user devices .

[0060] While in FIG. 1 and 2 illustrate various component configurations, other configurations may be used without departing from the scope of this invention. For example, the various components in FIG. 1 and 2 can be combined to create one component. As another example, functions performed by one component may be performed by two or more components.

[0061] Returning to FIG. 5 in FIG. 5 illustrates a block diagram in accordance with one or more embodiments of the invention. In particular, in FIG. 5 illustrates a method for accessing one or more control systems in a drilling control network. One or more steps in FIG. 5 may be performed by one or more components (eg, a virtual connection controller (443)), as illustrated in FIG. 1, 2 and/or 4. While the various steps in FIG. 5 are illustrated and described sequentially, it will be apparent to those skilled in the art that some or all of the steps may be performed in different order, may be combined or omitted, and some or all of the steps may be performed in parallel. In addition, steps can be performed actively or passively.

[0062] At step 500, a request is received to access one or more programmable logic controllers located in the drilling control network, in accordance with one or more embodiments of the invention. For example, the user device may send a request to access a virtual connection controller assigned to manage a switched virtual connection to a drilling control network. The user device may connect locally on the user network connected to the drilling control network, or connect to the virtual connection controller remotely, such as via the Internet.

[0063] In addition, the request may be a message that identifies the device of the user and/or the user attempting to access one or more PLCs in the drilling control network. For example, the request may contain password information and/or other identification information that may be used by the virtual connection controller to determine if the user's device is authorized. The request may also contain information related to which PLC the user's device or the user is trying to access. While step 500 describes a request for access to one or more PLCs, in one or more embodiments of the invention, the request is for access to one or more drilling operations control systems and/or one or more maintenance control systems, as illustrated above in fig. 4 and described in the accompanying description.

[0064] In one or more embodiments of the invention, the virtual connection controller performs multi-factor authentication to access the drilling control network. For example, the user's device may log into the user's network using a username and password. Accordingly, after establishing a network connection with the user network to establish a virtual connection, the virtual connection controller may request an additional password and/or identification. For example, the additional password and/or identification information may be a personal identification number, a biometric identifier such as a fingerprint, personal information relating to the user requesting access, and/or a user device code transmitted independently to the user's device. For more information on user device codes, see block 740 in FIG. 7 and the accompanying description.

[0065] At step 510, a determination is made whether the user device is authorized to access one or more programmable logic controllers in accordance with one or more embodiments of the invention. In response to the received request at step 500, for example, the network element and/or software application may determine if the user device has permission to access a particular PLC. For example, the virtual connection controller may access the account of the user associated with the user's device and/or the user operating the user's device. The user account may contain user credentials that define which PLC the user and/or the user's device can access. In addition, the user credentials may also indicate one or more time windows when the user and/or user device can control a particular PLC and/or any PLC. For more information regarding time windows, see steps 720, 725, and 730 illustrated below in FIG. 7 and the accompanying description. The user's credentials may be manually entered into the user's account by an administrator and/or generated automatically based on various information associated with the user and/or the user's device, stored in the user's account or elsewhere.

[0066] In step 520, a virtual connection is established between the drilling control network and the user network in response to determining that the user device is authorized in accordance with one or more embodiments of the invention. If it is determined that the user device is authorized to access a particular PLC, for example, the virtual connection controller may establish a virtual connection to the drilling control network. If a switched virtual connection exists between the drilling control network and the user network, the virtual connection controller may allow network communication over the switched virtual connection to establish a virtual connection. The switched virtual connection may be similar to the virtual connection (415) illustrated above in FIG. 4 and in the accompanying description. On the other hand, if it is determined that the user device is not authorized to access one or more of the PLCs and/or the user device is not currently authorized, the virtual connection cannot be established at step 520.

[0067] In one or more embodiments of the invention, the virtual connection controller is turned off and/or disconnected from the drilling control network. After it is determined in step 510 that the user is authorized to access the drilling control network, the virtual connection controller may power up and establish a virtual connection to the drilling control network.

[0068] At step 530, the virtual connection is terminated in accordance with one or more embodiments of the invention. In particular, the virtual connection controller or other software application may terminate the virtual connection established at 520. For example, the virtual connection controller may remove the link layer connection between the drilling control network and the user network, thereby returning the drilling control network to a closed state. Similarly, firewall settings can be set by the virtual connection controller to block network traffic to and from the drilling control network. In the case of a switched virtual connection, the virtual connection controller may set the switched virtual connection to a state such that it represents an open circuit. In one or more embodiments of the invention, for example, the virtual connection controller turns off the power and disconnects after determining that the virtual connection is completed.

[0069] In one or more embodiments of the invention, for example, the user and/or user device is assigned a specific period of time when the virtual connection at step 520 remains active. Once, at step 520, the virtual connection is established, the virtual connection may automatically end after an hour or other specified period of time. In one or more embodiments of the invention, for example, the virtual connection is automatically terminated after the approved maintenance time period, except for an increase in this time period, which is asserted through one or more appropriate channels. Similarly, in another implementation, a software application running on the user's network and/or the user's device monitors whether a specific period of time has elapsed since any user action on the virtual connection has taken place. For example, if the user device has not transmitted a control command and/or received any PLC data via the virtual connection from step 520 within a specific period of time, the virtual connection controller may determine that the user device is idle and terminate the virtual connection accordingly.

[0070] In another embodiment, the user device may send a request to terminate the virtual connection, for example, to a virtual connection controller. The user may decide that he or she terminates access to one or more PLCs or control systems and send a command to the virtual connection controller to terminate the virtual connection. Accordingly, the user device may automatically send a request to terminate the virtual connection in response to the user exiting a graphical user interface provided for accessing one or more PLCs.

[0071] In addition, as illustrated above in FIG. 5 and below in FIG. 7, access may describe read and/or control access to one or more network devices, such as PLCs, located on the drilling control network. However, in one or more embodiments of the invention, access refers to control commands transmitted to the drilling control network. For example, between the drilling control network and the user network, there may be one or more network links that provide data transmission to the PLC. In this case, the established virtual connection may be restricted to transmit control commands and/or other control data that is transmitted to change the settings, parameters and processes performed in the drilling control network. For example, in some embodiments of the invention, the user device may be configured to monitor the drilling control network without establishing a virtual connection at 520. Here, the virtual connection may only be established when the user device attempts to adjust various settings on one or more PLCs and/or other network devices in the drilling control network.

[0072] Returning to FIG. 6, in FIG. 6 illustrates an example end-to-end connection from a network node in a drilling control network to an installation server. The following example is given solely for the purpose of explaining and not limiting the scope of the invention. Returning to FIG. 6, in FIG. 6 illustrates a logical path (680) that is established from a programmable logic controller (eg, PLC A (661)) to an installation server Q (674). As illustrated in FIG. 6, various network links (for example, network link A (681) communication, network line B (682) communication, network line C (683) communication, network line D (684) communication, network line E (685) communication) are formed between different network nodes in the drilling control network X (610) (for example, PLC A (661), PLC B (662), switch A (671), switch B (672)) and user network B (630) (for example, switch C (673), installation server Q (674)). In addition, a virtual connection X (615) is established between switch A (671) in drilling control network A (610) and switch C (673) in drilling control network B (630). The X virtual connection (615) forms a logical path (680) between PLC A (661) and installation server Q (674) that allows installation server Q (674) to receive data from PLC A (661) and/or transmit data to PLC A (661). The logical path (680) may allow installation server Q (674) to communicate with PLC A (661), for example by adjusting settings in PLC A (661) using control commands. Similarly, installation server Q (674) may receive PLC data from PLC A (661), which provides information about various drilling operations and/or maintenance tasks performed on the drilling control network A (610). When virtual connection X (615) is terminated, the logical path (680) between PLC A (661) and installation server Q (674) is also terminated.

[0073] In one or more embodiments of the invention, for example, the virtual connection between the drilling control network and the user network does not provide direct access for the user device (for example, user device X (451)) to drilling control systems and / or technical control systems. service. In contrast to that illustrated in FIG. 6, for example, in some embodiments of the invention, user device Z (651) may not communicate directly with PLC A (661), but through a virtual connection controller and/or other network facility. There may be a logical path through virtual connection X (615) to the virtual connection controller. Based on the control commands received in the virtual connection controller from the user device, the virtual connection controller may retransmit new control commands directly to the programmable logic controller or control system in the drilling control network. Similarly, the virtual connection controller may receive PLC data from a programmable logic controller or control system before retransmitting the PLC data to the user device.

[0074] Returning to FIG. 7 in FIG. 7 illustrates a flowchart for generating a vulnerability map in accordance with one or more embodiments of the invention. In particular, in FIG. 7 illustrates a method for accessing one or more control systems in a drilling control network. One or more steps in FIG. 7 may be performed by one or more components (eg, a virtual connection controller (443)), as illustrated in FIG. 1, 2 and/or 4. While the various steps in FIG. 7 are illustrated and described sequentially, it will be apparent to those skilled in the art that some or all of the steps may be performed in different order, may be combined or omitted, and some or all of the steps may be performed in parallel. In addition, steps can be performed actively or passively.

[0075] At 700, a network connection is established between the user device and the user network, in accordance with one or more embodiments of the invention. In particular, the user's device may connect to the user's network remotely via the Internet. Similarly, the network connection may be established locally on the user's network, for example by connecting the user's device to a switch located on the drilling rig. With respect to a remote network connection, a network connection can be established using a remote display protocol such as Remote Desktop Protocol to access the virtual connection controller on the user's network. In one or more embodiments of the invention, the user's device connects to a network element in the user's network that can communicate with a virtual connection controller and/or installation server. For example, the user's device may provide login information, such as identification and/or password information for logging into the user's network. In one or more embodiments of the invention, the user network may be similar to the user network (430) illustrated in FIG. 4 and described in the accompanying description.

[0076] At step 705, a request is received to access one or more programmable logic controllers located in the drilling control network, in accordance with one or more embodiments of the invention. Step 705 may be similar to step 500 illustrated in FIG. 5 and described in the accompanying description.

[0077] At block 710, user credentials are obtained from a user account associated with the user's device, in accordance with one or more embodiments of the invention. For example, the various user accounts may be stored on the user's network in a storage device or remote storage location that is accessible by one or more software applications running on the user's network. In one or more embodiments of the invention, the virtual connection controller identifies the user's device from block 700 and associates the user's device with a specific user account. For example, the identification and/or password information from block 700 may also be associated with a particular user account. On the other hand, user devices may be assigned an additional unique identification that associates the user device with a particular user account.

[0078] In one or more embodiments of the invention, the user's credentials contain permission granting attributes. For example, the permission attributes may designate one or more control systems and/or one or more programmable logic controllers in the drilling control network that the user and/or user device can access. In particular, various employees in the drilling control network may be assigned access based on their functional duties and responsibilities. For example, a user whose job is to operate and maintain a mud pump may have permission grant attributes that assign access to the mud pump PLC and the mud processing PLC. However, the user cannot have permission attributes that provide access to the top drive PLC that controls the rotation of the drill string. Accordingly, permission granting attributes for a user may be described in the corresponding user account for the user.

[0079] At 715, a determination is made as to which programmable logic controllers are associated with a user account, in accordance with one or more embodiments of the invention. For example, the request from step 705 may be a request to access a particular PLC or control system on the drilling control network. The virtual connection controller may parse the user credentials from block 710 to determine if the grant attributes are appropriate for a particular PLC. On the other hand, if the request is a general request for access to the drilling control network, the virtual connection controller may check the granting attributes of the PLCs and/or control systems associated with the user and/or user device. If the user device is not currently authorized to access any PLCs on the drilling control network, the request from step 705 may be rejected. Likewise, step 715 may be similar to step 510 illustrated in FIG. 5 and described in the accompanying description.

[0080] At step 720, a determination is made whether one or more time windows are associated with one or more programmable logic controllers and/or a user account in accordance with one or more embodiments of the invention. In one or more embodiments of the invention, for example, access to the drilling control network is time limited. In particular, access to the PLC and/or control system may be granted to the user's device at approved times. Thus, in one or more embodiments of the invention, access to one or more PLCs and/or control systems is associated with one or more time windows. For example, the time window may define a start time and an end time when a user device can access a particular PLC. Between the start time and end time, the user device may receive PLC data from a particular PLC and/or transmit one or more control commands to a particular PLC. Likewise, a time window may be assigned to a particular user and/or user device, for example, to prevent access to the control system during a routine maintenance operation.

[0081] In another embodiment of the invention, a time window may refer to a limited period of time during which a user device is allowed to access a particular PLC. For example, the virtual connection controller may record the period of time that the user device accesses a particular PLC before terminating the virtual connection. Accordingly, when the user device exceeds the time period assigned to the time window, the virtual connection can be terminated. Thus, after a particular time window has elapsed, the virtual connection controller may prevent a subsequent virtual connection from being established until the time window is reset. For example, for the user and/or the user's device, the time window may reset on a weekly, monthly, or other periodic interval.

[0082] For example, in a further embodiment of the invention, a user may be assigned one or more common time windows to access a PLC or control system on a drilling control network. In a common time window, a virtual connection may be established in cases where the user device can access any PLC or control system for which the user device is otherwise authorized to access. On the other hand, in one or more embodiments of the invention, a user is assigned a particular time window for a particular PLC or control system. In a specific time window, a virtual connection is established when a user device can access a specific PLC or control system associated with a specific time window. In addition, a particular time window for a user's device may overlap at some point in time with another particular time window, or may not overlap in time.

[0083] In one or more embodiments of the invention, the user credentials from block 710 contain time window attributes. In particular, time window attributes may be data fields that contain information related to start times, end times, specific days of the week, month, or year, and allocated time periods for various time windows assigned to the user and/or user device. In addition, time window attributes may describe general time windows and private time windows.

[0084] In step 725, the time window start time for the virtual connection is obtained, in accordance with one or more embodiments of the invention. The virtual connection controller may retrieve various time window attributes from the user account to determine, for example, the start time of the time window for the virtual connection to the drilling control network. In particular, the start time of the time window may be a time before or after the time at which the request was received in step 705. If the start time of the time window is the time after the request, the virtual connection controller may notify the user device that the virtual connection cannot be established. before the start time. If the start time is the time before the request, the virtual connection controller may immediately establish a virtual connection.

[0085] At step 730, the end time of the time window for the virtual connection is obtained in accordance with one or more embodiments of the invention. Similarly to block 725, various attributes of the time window may be checked to determine the end time of the time window. In one or more embodiments of the invention, the virtual connection controller notifies the user device of the period of time during which the virtual connection will be established, for example, until the end time of the current time window.

[0086] At 735, a user device code for a virtual connection is generated, in accordance with one or more embodiments of the invention. In one or more embodiments of the invention, for example, after determining that the user device is authorized to access the drilling control network, the virtual connection controller starts a process to generate a time-limited set of virtual connection credentials. For example, the virtual connection credentials may contain network and/or firewall configurations for communicating over the virtual connection. In addition, in response to the virtual connection controller determining that the user's device is authorized, the virtual connection credential may contain a user device ID specially generated for the user's device. The user device code may be a pseudo-random or otherwise defined alphanumeric sequence that allows the user device to communicate with a PLC and/or control system on a drilling control network.

[0087] In one or more embodiments of the invention, for example, the user device code is configured to allow the user device to enter the control system application represented by the virtual connection controller. In particular, since the user device ID may be different from the identification and/or password information used to establish the network connection at 700, the user device ID can provide multi-factor authentication for security purposes. For example, the user device ID may be a temporary soft token that stores the user device ID on the user network or user device. Once the virtual connection is terminated, such as when the time window expires, the user device code may no longer allow communication with the drilling control network via any current or future virtual connections. Thus, a user device code may be generated in response to an authorized request and limited to one or more virtual connections.

[0088] At 740, the user device code is transmitted to the user device in accordance with one or more embodiments of the invention. In response to the generated user device code in step 735, the virtual connection controller may transmit the user device code to the user device from step 700. However, in one or more embodiments of the invention, the virtual connection controller acts as a network facility between the user device and control systems in the control network. drilling. Thus, the virtual connection controller can store the user device code locally on the user network without transmitting the user device code to the user device.

[0089] At 743, the installation server is powered on, in accordance with one or more embodiments of the invention. For example, the installation server may be a virtual connection controller or a device separate from the virtual connection controller. When the power of the installation server is turned off, network communication between the drilling control network and the user network that contains the installation server may be terminated. The power of the installation server can be turned on, for example, by a software application running on the user's network.

[0090] At 745, a virtual connection is established at start time, in accordance with one or more embodiments of the invention. In one or more embodiments of the invention, for example, a virtual connection is established in a manner similar to that illustrated at block 520 in FIG. 5 and described in the accompanying description. The start time may be the same as the start time as illustrated at 725 and described in the accompanying description. Similarly, a virtual connection may be established by a virtual connection controller. Moreover, in one or more embodiments of the invention, the virtual connection controller or other network application controls network traffic through the virtual connection. For example, the virtual connection controller may record requests for specific types of PLC data from the drilling control network, as well as any control commands sent to any PLCs or control systems in the drilling control network.

[0091] In one or more embodiments of the invention, for example, the virtual connection controller determines one or more access rights for the user's device with respect to the virtual connection. For example, a user device may be granted read access and/or control access to one or more settings in a PLC or control system in a drilling control network. For example, access rights for a user's device may be stored in the user's account, described at 710, along with time window attributes and permission grant attributes.

[0092] At 750, one or more control commands are received for one or more programmable logic controllers, in accordance with one or more embodiments of the invention. Control commands may be a message or instruction that causes the PLC or control system to perform a given type of operation. For example, control commands may change one or more processes to be performed by the drilling operations control system and/or the maintenance management system. Moreover, control commands may adjust equipment settings and parameters in relation to one or more processes. In one or more embodiments of the invention, for example, the drilling control network only receives control commands from the user network and/or user device via the virtual connection at 745. When the virtual connection is terminated, the user network and/or user device may still receive PLC data. from the drilling control network, but cannot modify the settings and/or processes running on the drilling control network.

[0093] In some embodiments of the invention, for example, the user device may send a control command to the virtual connection controller. Accordingly, the virtual connection controller may translate the control command to the respective PLC or control system into specific software and/or hardware commands. In another embodiment of the invention, the user device transmits the control command directly to the respective PLC or control system without passing through an intermediate application. For example, an end-to-end connection may be established between a user device and a PLC or control system in a drilling control network.

[0094] In step 755, programmable logic controller data related to one or more programmable logic controllers is transmitted, in accordance with one or more embodiments of the invention. In one or more embodiments of the invention, for example, a graphical user interface is provided on a user device that presents PLC data related to a virtual connection controller or control system. In particular, the historical data server may be located in the drilling control network, which stores the previous drilling control data, for example, sensor measurements, quality control data, system failures, for example, collected from various PLCs and control systems in the drilling control network. On a graphical user interface, PLC data can be presented as raw data and/or transformed data using various raw data statistics analysis techniques. For example, if a user requests access to the drilling progress of a particular drill bit over the past week, the corresponding PLC data for the drill bit may be displayed on the GUI.

[0095] In one or more embodiments of the invention, the virtual connection controller in the user network receives PLC data directly from the PLC and control systems in the drilling control network. Accordingly, the virtual connection controller may transmit a portion of the PLC data to the user device. Similarly, the virtual connection controller may convert the PLC data to a different format before transmitting the PLC data to the user device.

[0096] Although step 755 is shown as occurring during the establishment of a virtual connection at step 745, and before the virtual connection is terminated at step 770, in one or more embodiments of the invention, PLC data is transmitted without using a virtual connection. For example, between the drilling control network and the user network, there may be one or more network links that allow the transmission of PLC data from the PLC in the drilling control network to the user network. However, these network links may contain functionality that prevents transmission of control commands over the network links.

[0097] At block 760, a determination is made whether an end time has been reached for the virtual connection, in accordance with one or more embodiments of the invention. In one or more embodiments of the invention, for example, the virtual connection controller monitors the clock generator as to whether the virtual connection was established at 745 outside of a particular time window. Once the time window ends, the virtual connection controller may terminate the virtual connection in a manner similar to that illustrated above with respect to block 530 in FIG. 5 and described in the accompanying description. Similarly, if the user's device sends a request to terminate the virtual connection, it may be determined that the end time has been reached. When a determination is made that the end time has been reached, the process may proceed to block 770. When a determination is made that the end time has not been reached, the process may return to block 750.

[0098] At 770, the virtual connection is terminated in accordance with one or more embodiments of the invention. In one or more embodiments of the invention, after determining the end time of the virtual connection, the user device code from block 735 becomes unusable. Accordingly, the virtual connection controller may terminate the virtual connection in a similar manner as illustrated at block 530 of FIG. 5 and described in the accompanying description.

[0099] At step 775, the power of the installation server is turned off in accordance with one or more embodiments of the invention. For example, the installation server or virtual connection controller in the user network may detect that there are no remaining virtual connections to the drilling control network and the installation server may automatically shut down accordingly. When shut down, the installation server cannot be compromised by security breaches on the user's network.

[00100] Accordingly, as shown in the processes illustrated above in FIG. 5 and 7, the automation of establishing and terminating virtual connections may be invisible to the user and with minimal operator intervention. In particular, highly specialized maintenance can be performed with minimal involvement of rig personnel (for example, to approve different time windows in different user accounts). In addition, the workflow of drilling and maintenance operations can be consistent whether any user device is connected at the wellsite or remotely. Similarly, the algorithms illustrated in FIG. 5 and 7 can eliminate various manual drilling control network connections that depend on the readiness of operations and rig personnel. Similarly, manual connections to the drilling control network can be forgotten and mismanaged, leading to various security risks for the drilling control network.

[00101] In one or more embodiments of the invention, the algorithms illustrated in FIG. 5 and 6 and described in the accompanying description eliminate manual intervention by users to connect user devices to a PLC in a drilling control network. For example, in well construction systems, various control systems may be controlled locally. Because a security breach in a control system can pose various risks to operational, equipment, personnel and/or environmental safety, securing drilling control systems and maintenance management systems can be challenging. Accordingly, ancillary tasks such as inspecting network traffic to the drilling control network may not be optional features. In addition, various security measures can be based on passive monitoring. Thus, maintenance work is often performed locally due to the risks associated with providing remote access. For this reason, the algorithms described above can automate local and remote connections of user devices with physical connection and disconnection of connections between the drilling control network and various networks.

[00102] Referring to FIG. 8.1 and 8.2, and in Fig. 8.1 and 8.2 illustrate an example of establishing a virtual connection to access a control system in a drilling control network. The following example is given solely for the purpose of explaining and not limiting the scope of the invention.

[00103] Returning to FIG. 8.1, in which the rig controller (810) is shown acting as the virtual connection controller in this example. Specifically, the rig controller (810) identifies the current date and time based on the data stored in the current time attribute (801). In addition, the rig controller (810) receives various pending requests (for example, user Joe's request to access the fuel management PLC (821), user Bill's request to access the power PLC (822), and user Katie's request to access the PLC (823). ) drilling fluid processing) to access various programmable logic controllers located in the network near the drilling rig.

[00104] Referring to FIG. 8.1, the rig controller (810) analyzes user Joe's access request (821) using the PLC's authorization function (841) to determine whether to deny or grant user Joe's request (821) access to the fuel management PLC (815). The PLC authorization function (841) may correspond to one or more of the steps illustrated in FIG. 3 and 5 and described in the accompanying description. First, the controller (810) of the drilling rig obtains information from the user account (824) Joe located in the user network (not shown) near the drilling rig. Specifically, based on data stored in user Joe's account (824), user Joe has permission grant attributes (803) assigned to him by authorization to access the mud pump PLC (811), drilling control PLC (812), and PLC (813). ) mud treatment. Similarly, based on data stored in user Joe's account (824), user Joe has time window attributes (804) that define a common time window (831) to access the PLC every Tuesday from 9:00 am to 12:00 pm nights and another general time window (832) for PLC access every Thursday from 2:00 pm to 5:00 pm. After parsing the information from user Joe's account (824), the rig controller (810) determines that user Joe has failed in authorization to access the rig's fuel management PLC (815). Accordingly, user Joe's request (821) is denied and the virtual connection is not established.

[00105] In addition, as illustrated in FIG. 8.1, the rig controller (810) analyzes Bill's user's request (822) for access using the PLC's authorization function (841) to determine whether to deny or grant Bill's user's request (822) access to the power PLC (814). First, the controller (810) of the drilling rig receives information from the account (825) of the user Bill, located in the user network near the drilling rig. Specifically, based on the data stored in Bill's user account (825), Bill has permission grant attributes (803) assigned to him by authorization to access the Power PLC (814) and Fuel Management PLC (815). Similarly, based on user Bill's account (825), user Bill has time window attributes (804) that define a private time window (833) to access the Power PLC (814) every Tuesday from 11:00 am to 1:00 pm and another private time window (834) to access the fuel management PLC (815) every Thursday from 8:00 am to 5:00 pm. After parsing the information from user Bill's account (825), the rig controller (810) determines that user Bill is authorized on the current date and time to access the power PLC (814) on the rig. Accordingly, user Bill's request (822) is granted and a virtual connection is established by the rig controller (810) which allows the user device (851) owned by user Bill to access the power supply PLC (815).

[00106] Referring to FIG. 8.1, the rig controller (810) analyzes user Cathy's access request (823) using the PLC's authorization function (841) to determine whether to deny or grant user Cathy's request (823) access to the fuel management PLC (813). First, the rig controller (810) obtains information from user Katie's account (826) located on the user's network. Specifically, based on the data stored in user Kathy's account (826), user Kathy has permission grant attributes (803) assigned to her by the authorization to access the mud pump PLC (811) and the mud processing PLC (813). Similarly, based on the data stored in user Kathy's account (826), user Kathy has time window attributes (804) that define a common time window (835) for accessing the PLC every Monday from 10:00 am to 1:00 am days and another general time window (836) for PLC access every Wednesday from 2:00 pm to 5:00 pm. After parsing the information from user Katie's account (826) the rig controller (810) determines that user Cathy is authorized to access the drilling fluid PLC (813) on the drilling rig, but user Cathy's request (823) is outside of both common time windows (835, 636) for her user account (826). Accordingly, user Cathy's request (823) is denied and the virtual connection is not established.

[00107] Returning to FIG. 8.2, in fig. 8.2 illustrates a graphical user interface (860) running on a user device (851) owned by user Bill. While a virtual connection is being established with the drilling control network on the drilling rig, the installation server in the user network can send PLC data from the power supply PLC (814) to the user device (851) owned by the user Bill, which are presented on the PLC status display (880) power supply. In particular, various state attributes are shown, such as the current state (881) of the PLC (814) power supply, the current power consumption (882) of the drilling rig, the power consumption of the last seven days (883) and the power consumption of the last thirty days (884) . In addition, the graphical user interface (860) contains a power PLC command panel (890). Using the power PLC command panel (890), user Bill can send one or more control commands to the installation server to control the power PLC (814). For example, the control commands may include turning off power to the mud pump (891), turning off power to the downhole motor (892), and adjusting maximum power settings for various equipment (893) of the drilling rig. In addition, the graphical user interface (860) also includes a PLC clock display (870) that displays the current date (871) and current time (872) to the user Bill. Similarly, the rig controller (810) calculated the remaining time (873) in the total time window (831) and presented the remaining time (873) on the PLC clock display (870).

Shutdown and startup management

[00108] In general, embodiments of the invention include a system and various methods for initiating shutdown and startup operations in a drilling control network. In particular, one or more embodiments of the invention relate to a system that includes a shutdown manager that controls the shutdown sequence of the drilling control network. In some embodiments of the invention, for example, the use of the virtual machines and the software container is terminated before the virtualization services manager operations are terminated. The virtualization services manager may manage and provide virtualization services over the drilling control network, such as generating and/or terminating various virtual machines and software containers running at the virtualization services layer. After the Virtualization Services Manager is terminated, host devices running throughout the drilling control network can be sequentially terminated. Finally, the host devices may be terminated.

[00109] Accordingly, in some embodiments of the invention, the shutdown sequence is an automated process controlled by a shutdown manager. In particular, the shutdown manager may coordinate the shutdown sequence using various time-delay shutdown commands that tell the time when network devices shut down. Thus, by using shutdown commands with a time delay, the shutdown manager can manage a graceful shutdown of the network while the shutdown manager is online, as well as while the shutdown manager is offline, i.e. after how the shutdown manager has already completed its own operations.

[00110] Returning to FIG. 9.1, in Fig. 9.1 illustrates a block diagram of a system in accordance with one or more embodiments of the invention. As illustrated in FIG. 9.1, the drilling control network (900) may contain various user devices (for example, user device (990), various network elements (for example, network elements (905)), and various host devices (for example, host device A (911) , host device N (912), host devices (913)). The user devices may comprise hardware and/or software associated with the drilling control network (900) and which includes functionality for presenting data and/or receiving input from the user related to various drilling and/or maintenance operations. performed in the drilling control network (900). For example, a user device may include personal computers, smartphones, human-machine interfaces, and any other network-connected devices that receive input from one or more users, such as by providing a graphical user interface (GUI). Likewise, the user device may present data and/or receive control commands from the user to control the drilling rig. A network element may refer to various software and/or hardware components in a network, such as switches, routers, hubs, user equipment, or any other logical entities for connecting one or more physical devices in a network.

[00111] In one or more embodiments of the invention, the network (900) may further comprise various host devices. In particular, the host device may include hardware and/or software that communicates with drilling equipment (e.g., drilling equipment A (986), drilling equipment N (987)) and one or more programmable logic controllers (PLCs) (e.g. , PLC A (981), PLC N (982)). The drilling equipment may include a blowout preventer (99), a drilling rig (12), and other components illustrated above in FIG. 1 and discussed in the accompanying description. PLCs connected with host devices can form various control systems such as various drilling control systems and various maintenance control systems. In particular, PLCs may comprise hardware and/or software functionality for controlling one or more of the processes performed by the drilling rig, including but not limited to the components illustrated in FIG. 1. Specifically, the PLC can control valve states, fluid levels, pipe pressures, alarms and/or depressurizations throughout the rig. Further, the programmable logic controller may be a ruggedized computer system with functionality to withstand vibration, extreme temperatures, wet environments, and/or dusty environments, such as near a drilling rig.

[00112] In one or more embodiments of the invention, the host device comprises a virtualization controller (e.g., virtualization controller A (931), virtualization controller N (932)), running on a host operating system (e.g., host operating system A (921), operating system of N (922) host). The virtualization controller may include hardware and/or software that includes functionality for communicating with other virtualization controllers on the drilling control network and/or implementing various virtualization services on the drilling control network. For example, virtualization controllers may be virtual machines and/or software containers running on host devices (911, 912). The virtualization services may include network processes that run on a plurality of network devices (eg, host devices (911, 912), network elements (905), host devices (913)). Examples of virtualization services may include managing field data among PLCs and/or drilling equipment, managing a virtual machine, managing a software container, allocating memory resources among host devices in a drilling control network, various network processes for administering a drilling control network, etc. .

[00113] A software container may be a special case of user space implemented by a single host operating system kernel (eg, host operating system A (921), host operating system N (922). In particular, a software container may be an application layer abstraction that allows isolated processes to run within a software container. Similarly, multiple software containers can run on a single operating system core. Software containers may include Docker containers, Java™ containers, Windows Server containers, etc. In contrast, a virtual machine may include hardware and/or software that can provide an abstraction of the physical hardware. For example, the virtual machine may have an independent operating system that is separate from the host operating system, and the virtual machine may run on one or more host devices with dedicated memory and other computing resources.

[00114] Returning to FIG. 9.2, in one or more embodiments of the invention, the virtualization services manager (960) is selected by the virtualization controller, which is assigned by other virtualization controllers to initialize virtualization services, virtual machines and/or software containers running at the virtualization services layer. Additional information about the selected Virtualization Services Manager can be found below in FIG. 9.3 and in the above description.

[00115] In addition, a virtualization services manager (eg, a virtualization services manager (960)) may administer and/or monitor various host device resources for virtual machines and/or software containers running at the virtualization services layer. Likewise, the overall virtualization architecture of the drilling control network (900) may be the same as when the host operating system runs on a non-operating computer system (eg, a hardware computer system) or as a virtual machine. For example, virtual machines and software containers can communicate with each other at the virtualization service layer and start the virtualization services in a consistent manner.

[00116] Referring to FIG. 9.2, in some embodiments of the invention, the shutdown manager may receive a request from a user device (eg, user device (990)) to complete the operation of all or part of the drilling control network. Accordingly, the shutdown manager may initiate shutdown operations for host devices, virtual machines, software containers, virtualization service managers, and/or virtualization controllers. In some embodiments, the shutdown manager initiates shutdown automatically in response to the detection of one or more shutdown conditions corresponding to predetermined conditions on the drilling control network, such as rig equipment failures caused by the termination of operations on the drilling control network. Similarly, the shutdown manager may automatically initiate the completion of operations at a predetermined time, for example, the user may designate a predetermined day and/or time to shut down the drilling control network.

[00117] In some embodiments of the invention, for example, the shutdown manager comprises functionality for sending a shutdown command with a time delay (e.g., command A (971) shutdown with a time delay, command N (972) shutdown with a time delay, B (973) timeout shutdown command) for one or more host devices, one or more virtualization controllers, etc. The timeout shutdown command may include instructions assigning a predetermined time when the corresponding hardware and/or or software (e.g. host device A (911), virtual machine A (941), software container A (946), virtualization controller A (931), virtualization services manager (960), etc.) completes operations . The completion time may be a specific time of day, such as 8:00 pm CST, or a relative time, such as 10 minutes after the appropriate time-delayed shutdown command is received from the shutdown manager.

[00118] At a given shutdown time, for example, a software application or a network device may shut down various software and/or hardware processes running on the network device. Similarly, the completion time may correspond to various processes associated with shutdown operations, such as, for example, freeing computer resources, system memory and processing power, and/or stored data from software and/or hardware processes in storage for further extraction. The shutdown operations may further correspond to the end of power supply to the corresponding network device, such as a virtual machine, a software container, and/or a host device.

[00119] Returning to FIG. 9.3, in fig. 9.3 illustrates a block diagram of a system in accordance with one or more embodiments of the invention. As illustrated in FIG. 9.3, the drilling control network (900) may contain functionality to initialize one or more processes for restart services in the drilling control network (900). In one or more embodiments of the invention, for example, various virtualization controllers (e.g., virtualization controller A (931), virtualization controller N (932), virtualization controller X (933)) contain functionality for determining which virtualization controller can act as the selected virtualization service manager for the drilling control network (933). In particular, the virtualization services manager selected may be a temporary virtualization services manager until the virtualization services layer is established throughout the drilling control network. As illustrated in FIG. 9.3, for example, the virtualization controllers (931, 932, 933) select the virtualization controller X (933) as the virtualization services manager (965). Like other virtualization controllers, the virtualization controller X (933) operates as a virtualized environment on the host operating system X (923) located in the host device X (913). Since the virtualization services manager (965) for the network is selected, the virtualization controller X (933) can act as master in coordinating various processes among other virtualization controllers (931, 932) in the drilling control network (900). In particular, the selected virtualization services manager (965) may contain functionality similar to the virtualization services manager (960) in FIG. 9.1.

[00120] In some embodiments of the invention, the virtualization service manager includes functionality for sending one or more time-delay initialization commands (e.g., time-delay initialization commands A (976), time-delay initialization commands N (977) ) . For example, the selected network virtualization services manager (965) may include functionality to determine one or more predetermined times in the startup sequence for virtual machines, software containers, and/or other virtualization services running on the drilling control network (900). Thus, the time-delay initialization commands may enable the implementation of the various virtualization services provided by the virtualization services manager prior to the implementation of the various virtual machines and/or software containers in the drilling control network (900).

[00121] While in FIG. 9.1, 9.2 and 9.3 illustrate various component configurations, other configurations may be used without departing from the scope of this invention. For example, the various components in FIG. 9.1, 9.2 and 9.3 can be combined to create one component. As another example, functions performed by one component may be performed by two or more components.

[00122] Returning to FIG. 10 in FIG. 10 illustrates a block diagram in accordance with one or more embodiments of the invention. In particular, in FIG. 10 illustrates a method for shutting down a network. One or more steps in FIG. 10 may be performed by one or more components (eg, shutdown manager (950)), as illustrated in FIG. 1, 2, 9.1, 9.2 and/or 9.3. While the various steps in FIG. 10 are illustrated and described sequentially, it will be apparent to those skilled in the art that some or all of the steps may be performed in different order, may be combined or omitted, and some or all of the steps may be performed in parallel. In addition, steps can be performed actively or passively.

[00123] At step 1000, a request is received in the drilling control network to initiate shutdown in accordance with one or more embodiments of the invention. For example, a user may provide user input on a user's device in the drilling control network to perform graceful shutdown. In response to user input, the user device may send a request to the completion manager to initiate a process to complete operations throughout the drilling control network. The request may be a message that identifies the date and/or time, as well as which control systems and other network devices are assigned to complete operations. In some embodiments, the shutdown manager is similar to the shutdown manager (950) illustrated above in FIG. 9.1 and in the attached description.

[00124] In some embodiments, the shutdown manager automatically initiates a shutdown if various shutdown conditions such as environmental conditions (e.g., temperature, humidity, condensation, etc.), network conditions, and/or drilling operation conditions exceed the specified operational limits of one or more virtualized systems (eg, virtualization service manager, various virtualization controllers, etc.). For example, the shutdown manager and/or the virtualization services manager may monitor the drilling control network regarding shutdown conditions. If a particular shutdown condition is detected, the shutdown manager may automatically initiate a drilling control network shutdown sequence. Thus, the shutdown manager can trigger a graceful network shutdown without user intervention. In some embodiments of the invention, the shutdown manager may activate shutdown in the event of a power outage. Thus, the shutdown manager can perform a network shutdown before either system runs out of backup power. In some embodiments of the invention, for example, after the shutdown manager detects that drilling operations have been completed, the shutdown manager initiates shutdown.

[00125] At 1010, one or more termination times are determined for the virtualization service manager, one or more virtualization controllers, and/or one or more host devices, in accordance with one or more embodiments of the invention. The shutdown manager may determine when various programs of the software system and network devices in the drilling control network complete operations. In addition, the completion times may correspond to a shutdown sequence described by the order in which the shutdown manager, virtualization services manager, one or more virtualization controllers, and one or more host devices complete operations on the drilling control network. In some embodiments, for example, the shutdown sequence designates the shutdown manager as the first program of the software system or network device to complete operations. After the completion of the shutdown manager, the shutdown sequence can designate the shutdown manager as next. After the Virtualization Services Manager completes, the shutdown sequence can designate an individual virtualization controller as the next one to complete operations. After the virtualization controllers are shut down, the host device can be scheduled to complete operations. In another embodiment of the invention, a different shutdown sequence may be used, such as where in the shutdown sequence one host device completes operations before the virtualization services manager or the shutdown manager.

[00126] In some embodiments, shutdown times are based on how much power resources remain for various hardware devices on the network. For example, in response to a power outage on the network, one or more power supplies of the host devices can tell the shutdown manager how many minutes of uptime the host devices have left. The shutdown manager can then calculate an allocated period of time to complete the shutdown process for each virtual machine, software container, virtualization service manager, virtualization controllers, and so on, before any of the devices are powered down.

[00127] At 1015, various virtualization services associated with one or more virtual machines and/or one or more virtual containers are terminated, in accordance with one or more embodiments of the invention. For example, a virtualization service manager and/or a shutdown manager may communicate with virtual machines and software containers to stop virtualization services that are running on the virtual machines and software containers. Virtualization services can include critical processes that can lose data as a result of hard or forced shutdown of critical processes.

[00128] At 1020, one or more virtual machines and/or one or more virtual containers are shut down, in accordance with one or more embodiments of the invention. After the virtualization services on the virtual machines and/or software containers are terminated, for example, the virtualization services manager and/or shutdown manager may begin communicating with the virtual machines and/or software containers to ensure that the virtual machines and/or software containers are shut down as part of the shutdown sequence.

[00129] If the virtual machine and/or software container cannot gracefully complete operations, for example, an underlying process fails to gracefully shut down, the shutdown manager or virtualization services manager may force shutdown the virtual machine or software container. In particular, the difference between a hard shutdown and a graceful shutdown may include whether data was successfully saved or lost/corrupted during the shutdown process.

[00130] At 1030, various timed shutdown commands corresponding to one or more completion times are transmitted to the virtualization service manager, one or more virtualization controllers, and one or more host devices, in accordance with one or more embodiments of the invention. In some embodiments, for example, a timed shutdown command for a host device has a delay time of: T+X+Y, where T is the time the shutdown manager completes operations, X is the time the virtualization services manager completes operations , and Y is the scheduled time when the virtualization controllers completed operations. The virtualization controller timed shutdown command can have a delay time of T+X. Similarly, the time-delay shutdown command of the virtualization service manager may have a delay time T. Thus, the time-delay shutdown command may be similar to the time-delay shutdown command illustrated in FIG. 9.1 and described in the attached description.

[00131] In particular, the shutdown manager may administer the shutdown sequence using timed shutdown commands, as illustrated below in the example of FIG. 12. With the shutdown process, the drilling control network can perform a graceful shutdown, which can allow the network to resume operations later with minimal risk of data and system damage.

[00132] Referring to FIG. 12, in FIG. 12 shows an example of a shutdown sequence Q (1200). The following example is given solely for the purpose of explanation and not limitation of the scope of the invention. In FIG. 12, the completion sequence Q (1200) contains successive series of events (for example, event A (1205), event B (1210), event C (1220), event D (1230), event E (1240), event F (1250) and event G (1260) At event A (1205), the shutdown manager X detects a consistent shutdown event, such as a rig power outage, a specified environmental condition for a location or device on the rig, etc. At event B (1210), shutdown manager X sends shutdown commands with a time delay to shutdown manager Y, various virtualization controllers, and host devices At event C (1220), various virtual machines and software containers running on the rig network are shut down On event D (1230), shutdown manager X ends operations On event E (1240), virtualization services manager Y finishes operations based on time according to to the current shutdown command with a time delay. As illustrated in FIG. 12, Virtualization Services Manager Y has been designated as Virtualization Services Manager to stop operation in time period X (1201). At event F (1250), the virtualization controllers stop operation according to the time in their respective shutdown commands with a time delay, for example, in time period Y (1202). At event G (1260), the host devices stop operation according to the time in their respective shutdown commands with a time delay, for example, in time period Z (1203). With respect to event E (1240), event F (1250) and event G (1260), they can be well-timed events where time periods (1201, 1202, 1203) provide some time for these components to gracefully shut down. However, when the components stop sending a response so that the service cannot be terminated, the shutdown sequence Q(1200) may move to the next event and terminate the unresponsive service accordingly. Thus, commands with a time delay for staged, consistent shutdown of a process after the shutdown manager has already completed operations. Thus, the completion of operations in Event C (1220), Event D (1230), Event E (1240), Event F (1250), and Event G (1260) may include graceful shutdowns and/or forced shutdowns.

[00133] While the shutdown sequence Q (1200) in FIG. 12 illustrates one sequence of events for consistent shutdown, another sequence of events is provided that contains events added to and/or removed from the shutdown sequence. Likewise, the operations of the various components may be completed in a different order from the shutdown sequence Q (1200).

[00134] Referring to FIG. 10, at block 1040, operations are completed in the shutdown manager, in accordance with one or more embodiments of the invention. After time-delayed shutdown commands are sent to various network devices, the shutdown manager can terminate any processes associated with it. For example, the shutdown manager may be a virtual machine or a software container that may be terminated by the virtualization services manager. If the shutdown manager is a hardware device, the shutdown manager may be subjected to a hard shutdown that cuts power to the shutdown manager. The shutdown manager may be similar to the shutdown manager shown above in FIG. 9.1 and in the attached description.

[00135] In step 1050, operations are terminated in the virtualization service manager based on a timed shutdown command, in accordance with one or more embodiments. During the shutdown associated with the timed shutdown command, the virtualization service manager may shut down any virtualization service running over the drilling control network and itself. The Virtualization Services Manager may be similar to the Virtualization Services Manager shown above in FIG. 2A, 2B and/or 2C and in the accompanying description.

[00136] At 1060, operations on one or more virtualization controllers are completed based on one or more time-delay shutdown commands, in accordance with one or more embodiments. The virtualization controllers may be similar to the virtualization controllers shown above in FIG. 9.1, 9.2 and/or 9.3 and in the accompanying description.

[00137] At 1070, operations are completed on one or more host devices based on one or more time-delay shutdown commands, in accordance with one or more embodiments. The host devices may be similar to the host devices shown above in FIG. 9.1, 9.2 and/or 9.3 and in the accompanying description.

[00138] While the operations at steps 1020, 1040, 1050, 1060, and 1070 may correspond to graceful shutdowns, one or more hard shutdowns may be used to complete the operations. For example, a timed shutdown command may force a forced shutdown of the virtualization controller with the host operating system terminating resources associated with the virtualization controller. Likewise, a timed shutdown command may also provide instructions to a power source that terminates power to any hardware associated with a host device, virtual machine, and/or software container.

[00139] Returning to FIG. 11 in FIG. 11 illustrates a block diagram in accordance with one or more embodiments of the invention. In particular, in FIG. 11 illustrates a method for starting a drilling control network. One or more steps in FIG. 11 may be performed by one or more components (eg, virtualization controller (933)), as illustrated in FIG. 1, 2, 9.1, 9.2 and/or 9.3. While the various steps in FIG. 11 are illustrated and described sequentially, it will be apparent to those skilled in the art that some or all of the steps may be performed in different order, may be combined or omitted, and some or all of the steps may be performed in parallel. In addition, steps can be performed actively or passively.

[00140] At 1100, operations are initiated on various host devices, in accordance with one or more embodiments of the invention. For example, host devices can be powered up and host operating systems can run on the host devices.

[00141] At 1110, operations are initiated on various virtualization controllers running on various host devices, in accordance with one or more embodiments of the invention. For example, virtualization controllers can run on host devices as a host operating system or as a standalone software script. Accordingly, the virtualization controller can transmit and receive information from other virtualization controllers over the drilling control network.

[00142] At 1120, a virtualization service manager is determined from among various virtualization controllers, in accordance with one or more embodiments of the invention. Based on communication among the virtualization controllers, one virtualization controller can be selected as the virtualization service manager. The selection process may be based on the types of control systems operating on the host devices via the drilling control network. For example, the virtualization controller on the host device with the least overhead might be selected as the virtualization service manager. The selected Virtualization Services Manager may be similar to the selected Virtualization Services Manager shown above in FIG. 9.3 and in the attached description.

[00143] At 1130, one or more service initialization times are determined for various virtualization controllers, in accordance with one or more embodiments of the invention. For example, the virtualization services manager may determine the startup sequence for the various virtualization services running on the drilling control network, such as the order in which virtual machines and/or software containers are generated to operate the various control systems. Accordingly, the initialization times may be similar to the shutdown times described in FIG. 10 so that the various start-up operations are staged. Accordingly, service initialization times may provide the virtualization service manager with the opportunity to verify that particular virtual machines and/or software containers are operating satisfactorily before the next group of virtual machines and/or software containers is formed.

[00144] At 1140, different time delay initialization commands are sent to different virtualization controllers based on different service initialization times, in accordance with one or more embodiments of the invention. The time delay initialization instructions may be similar to the time delay initialization instructions shown above in FIG. 9.3 and in the attached description.

[00145] At 1150, different virtual machines and/or software containers are generated based on different service initialization times, in accordance with one or more embodiments of the invention.

Structure of cybersecurity

[00146] In general, embodiments of the invention include a system and various methods for accessors in one or more security zones. In particular, one or more embodiments of the invention relate to a system that contains one or two channels connecting two or more security zones. For example, a channel may provide a communication path between network devices located in different security zones. In some embodiments of the invention, the channel is a temporary channel that is managed by an installation server or a virtual connection controller. With the help of a temporary channel, temporary virtual connections can be established and terminated in order to control authorized access to various control systems in the security zone. For example, a temporary channel may restrict access to a network device to certain periods of time and/or to specially authorized network devices.

[00147] Similarly, control systems in a drilling control network may publish data over one or more bearers. For example, a network device may subscribe to receive data from an associated management system that is provided by a particular bearer. When the respective control system broadcasts data, any data subscriber may receive the data over a bearer, respectively. However, the unidirectional channel may prevent subscribers from sending commands over the communication path in the opposite direction. Thus, subscribers are limited to a passive role in relation to receiving data from a bearer.

[00148] FIG. 13 illustrates a block diagram of a system in accordance with one or more embodiments of the invention. As illustrated in FIG. 13, the drilling control network (1310) may include a human machine interface (HMI) (e.g., HMI (1321)), an archive server, various network elements (e.g., network elements Q (1323), network elements R (1324) ) and/or various user devices (eg, user device M (1381)). The human-machine interface may be hardware and/or software associated with the drilling control network (1310) and which contains functionality for presenting data and/or receiving input from a user related to various drilling and/or drilling operations. maintenance performed on the drilling control network (1310). For example, the human-machine interface may include software for providing a graphical user interface (GUI) for presenting data and/or receiving control commands for operating a drilling rig. A network element may refer to various hardware components in a network, such as switches, routers, hubs, user equipment, or any other logical entity for connecting one or more physical devices in a network. User devices may include personal computers, smartphones, human-machine interfaces, and any other devices connected to a network that receive input from one or more users. In some embodiments, the drilling control network (1310) is connected to a user network (eg, user network (1330)). In particular, the user network (1330) may comprise various network elements (not shown), user devices (e.g., user device N (1382), user device O (1383), user device P (1384)), and/or user equipment on drilling site. For example, user equipment at a well site may include a telephone network, personal computers, printers, application servers, and/or file servers located near the drilling rig. The network elements, human-machine interface (1321), wellsite user equipment, user devices, and/or the archive server may be computing systems similar to computing system (3400) shown in FIG. 34.1 and 34.2, and described in the accompanying description.

[00149] In one or more embodiments, the drilling control network (1310) includes drilling equipment (eg, blowout preventer (99), drilling rig (12), and other components illustrated in FIG. 1 above and in the accompanying description). The drilling control network (1310) may further comprise control systems (eg, control systems (1322)), such as various drilling operations control systems and various maintenance control systems, which are deterministic parts of the network. Drilling operations control systems and/or maintenance management systems may include, for example, a programmable logic controller (PLC) that contains hardware and/or software with functionality to control one or more processes performed by a drilling rig, including, but, without being limited to the components illustrated in FIG. 1. In particular, the programmable logic controller may control valve states, fluid levels, pipe pressures, alarms, and/or depressurizations throughout the rig.

[00150] Further, the programmable logic controller may be a ruggedized computer system with functionality to withstand vibration, extreme temperatures, wet environments, and/or dusty environments, such as near a drilling rig. Drilling operations control systems and/or maintenance management systems may also refer to control systems that comprise a plurality of PLCs in a drilling control network (1310). In addition, the control system may be part of a drilling control feedback network that contains functionality to control operations within the system, block and/or sub-block illustrated above in FIG. 1 and in the accompanying description. The PLC may transmit PLC data (eg, PLC data (1317)) to one or more devices connected to the drilling control network (1310) and/or user network (1330). The PLC data may include: sensor measurements, status updates, and/or information related to drilling operations and/or maintenance operations performed on the drilling control network (1310) that come from the drilling control network (1310). Likewise, one or more control systems (1322) may include functionality to control and/or perform various drilling operations with respect to a mud circulation system, a rotary system, a pipe supply system, and/or various other drilling operations illustrated with respect to FIG. 1 and in the accompanying description.

[00151] In one or more embodiments of the invention, the drilling control network (1310) and/or user network (1330) is divided into different security zones (e.g., security zone A (1361), security zone B (1362), zone C (1363 ) security zone D (1364) security zone E (1365) security). In particular, the security zone may contain hardware and/or software that contains functionality to enforce one or more access control policies for non-communication facilities within a portion of the network. For example, an access control policy may designate which users and/or types of users may have access to the non-communication medium and/or the ability to perform one or more functions associated with the non-communication medium. In some embodiments of the invention, the access control policy refers to one or more time windows when given users have access to the corresponding non-communication facility. In some embodiments, an access control policy contains various rules that allow a network device to access one or more approved software applications, set which network ports can receive data over a channel, and/or assign network protocols to use approved Internet Protocol (IP) addresses in within the channel.

[00152] The non-communication media may correspond to human-machine interfaces, drilling equipment, user equipment, servers, personal computers, various network elements, and/or various network devices. Likewise, a security zone may implement an access control policy using various communication means. For example, the communications media may include hardware and/or software that contains functionality for transmitting data over a communications path, such as routers, switches, personal computers, and/or network elements. Enforcement of various access control policies may include enforcement using various network communication protocols and non-network enforcement, such as telecom closets that contain PLCs, servers, switches, firewalls, and other equipment.

[00153] In some embodiments of the invention, security zones are further subdivided into subzones. For example, each subzone within a security zone may have corresponding subzone-specific access control policies and general access control policies that apply to each subzone within the security zone. Subzones may be in separate broadcast domains within a particular security zone.

[00154] In one or more embodiments of the invention, one or more channels (e.g., Bearer A (1371), Bidirectional Channel B (1372), Temporary Channel (1373), Bidirectional Channel D (1375)) connecting different security zones. In particular, the channel may include communication means that implement one or more network communication protocols operating between different security zones. For example, a bidirectional channel (eg, bidirectional channel B (1372)) may implement an access control policy that enforces similar rules for transmitting and receiving data by network devices located in one of two security zones connected by a bidirectional channel. For example, user device M (1381) may transmit and request the same data on bi-directional channel B (1372) as user device O (1383), which is located in different security zones.

[00155] In some embodiments, the drilling control network (1310) and/or user network (1330) contains a bearer (eg, bearer A (1371)). A bearer may implement an access control protocol that restricts the transmission of certain types of data in one direction within a network. For example, a bearer may allow certain types of sensor data to be sent to a given security zone while preventing certain types of data, such as parameter settings, control commands, etc., from being received from the same security zone. As illustrated in FIG. 13, user device N (1382) can read PLC data (1317) from control systems (1322), but cannot transmit control commands affecting the type of PLC data sent by control systems (1322).

[00156] In some embodiments, the drilling control network (1310) and/or the user network (1330) comprises one or more time channels (eg, time channel C (1375)) connecting two or more safety zones. In one or more embodiments of the invention, the temporary channel is a switched virtual connection. For example, a switched virtual connection may include hardware and/or software in a security zone in the drilling control network (1310) and another security zone in the user network (1330) to implement the virtual connection. Thus, when the switched virtual connection is in the "open" state, the virtual connection cannot be established through the temporary channel. When a switched virtual connection is in the "closed" state, a virtual connection is formed that corresponds to a temporary virtual circuit. The temporary virtual circuit can then carry network traffic, such as PLC data, between the two security zones. In particular, the default switched virtual state may occur when two security zones are disconnected until an authorized user and/or user device requests access. In some embodiments of the invention, the virtual connection over the time channel is terminated during drilling operations performed by one or more control systems, and the virtual connection can be established when there are no drilling operations in the drilling control network.

[00157] In some embodiments of the invention, the temporary channel is controlled by a virtual connection controller (eg, virtual connection controller (1343)). The virtual connection controller may contain hardware and/or software that contains functionality for establishing a virtual connection over a time channel. A virtual connection may be, for example, a link layer connection between two adjacent communication media, such as, for example, a physical data link that contains switches located in different security zones. In other embodiments of the invention, the virtual connection may be a point-to-point connection through a plurality of network nodes. In addition, the virtual connection controller (1343) may be a virtual machine (VM) or a physical network element located in the drilling control network (1310) and/or the user network (1330). For example, the virtual connection controller (1343) may be an installation server or a network element that communicates with the installation server. In one or more embodiments of the invention, for example, the virtual connection controller (1343) contains the functionality to power on and/or power off the installation server that provides communication with network devices in a particular security zone.

[00158] In some embodiments of the invention, the security zone contains one or more internal channels (for example, internal channel E (1374)). For example, an internal channel may enforce one or more access control policies between two or more non-communicating entities within the same security zone, such as a communication governed by a particular access control policy between two software applications operating within the same security zone or one subzone. For example, an internal channel may enforce an access control policy between a control system controlled by the drilling control network and a network device provided by a third party vendor that is outside the control of the drilling control network.

[00159] In another embodiment of the invention, two control systems located in the same security zone or subzone communicate over an internal channel. For example, control systems within a security zone may be located in the same broadcast domain. Thus, it may not be possible to implement a firewall or other communications infrastructure that enforces an access control policy between two control systems. Therefore, the internal link may implement IP address filtering, port filtering, and/or other type of network filtering to enforce secure communication between the two control systems. Similarly, when the network devices' functional limitations do not allow the network devices to be divided into different zones or sub-zones, such as when the network devices are managed by different groups of third parties, communications can remain secure.

[00160] In some embodiments of the invention, the channel connects a security zone to another security zone that is located outside the drilling control network (1310) and the user network (1330). For example, as illustrated in FIG. 13, security zone F (1366) corresponds to the Internet (1350). In particular, a remote user device (1385) can communicate on a bi-directional channel D (1375) with a user device N (1382), which is located in a security zone C (1363) located in a user network (1330).

[00161] Although in FIG. 13 illustrates various component configurations, other configurations may be used without departing from the scope of the present invention. For example, various components according to FIG. 13 can be combined to create one component. As another example, functions performed by one component may be performed by two or more components.

[00162] Referring to FIG. 14, in FIG. 14 shows an example of a security zone design (1400) for one or more networks. The following example is given solely for the purpose of explaining and not limiting the scope of the invention. In FIG. 14, the security zone structure (1400) comprises a control network security zone (1461), which contains a control system subzone (1411) and a middleware protocol control subzone (1412). Systems in the control network security zone (1461) and corresponding subzones may operate in accordance with various access control policies, which include allocation of storage and computing power, and cannot be shared with any other security zone. In sub-zone (1411) control systems control systems may have fast control loops (for example, up to 1 kHz), which can be supported in a deterministic computing environment. The subzone (1411) of the control system may have the highest level of security within the structure (1400) of the security zone. For example, the control cycle deadlines in the control system subzone (1411) may affect the availability of data, whereby the data may be difficult to access due to increased network delay or network jitter. The link between the control system subzone (1411) and the middleware protocol control subzone (1412) can be implemented using a software-compatible PLC (IPC) or non-OS platform gateway that converts network protocols such as EtherNet/IP, Profinet, Profibus, Modbus TCP/IP or EtherCat to middleware protocol. The logic part of a software-compatible PLC can map local control bus memory addresses to and from middleware protocol sections, respectively, for example, following a white list approach. In the middleware protocol management subzone (1412), one or more middleware protocols may be used to coordinate various control systems. For example, various means in the middleware protocol control subzone (1412) may interact between equipment control and well construction process control. In this case, the control loops may be feedback loops that operate at high data rates (eg, up to 1 kHz) and may operate asynchronously in less harsh real time.

[00163] In addition, the security zone structure (1400) further comprises a control network supervisory and operator (CNSO, control network supervisory and operator) security zone (1462), which contains a subzone (1421) of the control system human-machine interface (CSHMI, control system human machine interface) and a middleware protocol control subzone (1422). The CNSO security zone (1462) may contain interfaces for supervisory control, for example, by human operators or algorithms, which are given the same access as human operators. Thus, the CSHMI subzone (1421) contains a control system interface for human operators, such as a joystick, touch pad and/or touch screens. In particular, the driller's seat may be located in the CSHMI subzone (1421). A channel connecting the CSHMI subzone (1421) and the middleware protocol control subzone (1412) may allow human operators to interact with hardware representations based on the middleware protocol (e.g., description, functionality, calibration, etc.) . The channel may respectively provide different control functionality to different network devices. Likewise, users of the middleware protocol can be authenticated with various security certificates. In this case, the subscription and/or data access functionality can be segmented using middleware protocol domains. For example, a bidirectional channel may connect the middleware protocol control subzone (1422) and the middleware protocol control subzone (1412). This bi-directional channel may provide coordinated control algorithms with differentiated access to sensor data and control functionality for one or more control systems.

[00164] In accordance with the CNSOS security zone (1462), the middleware protocol control subzone (1422) may contain various advanced coordinated control algorithms based on the middleware protocol that are executed in soft real time. With regard to access control policies in the middleware protocol control subzone (1422), different computing environments can be separated by virtualization hypervisor and/or physical separation. Control functionality and/or data access may also be segmented via middleware protocol domains.

[00165] Referring to FIG. 14, the security zone structure (1400) further comprises a secure security zone (1463), which contains a configuration management subzone (1431), a control support application subzone (1432), a voice communication subzone (1433), and a closed-circuit television system (1433). ; CCTV) and subzone (1434) of the personnel registration system. In particular, the protected security zone (1463) may contain a support infrastructure that complements the facilities in the control network security zone (1461) and the CNSOS security zone (1462). For example, security access control policies (1463) may include active operating system patching for devices with MAC addresses that are whitelisted at physical network connection points. Channels within the protected security zone (1463) and channels that leave that zone can be authenticated with security certificates (eg, middleware protocol, HTTPS) along with managed firewall packet sniffing.

[00166] In accordance with the protected zone (1463) security, subzone (1434) of the personnel registration system may be the place where local roles are defined and maintained for various zones and subzones of security. The management support application subarea (1432) may contain systems tasked with managing updates and modifications to management systems in the management network security area (1461). For example, the temporary channel may connect the control support application subzone (1432) and the control system subzone (1411). Upon approval (eg, an assigned time window), the time channel may be allowed to transmit software, firmware, and/or configuration updates from the control support application subzone (1432) to the control systems in the control system subzone (1411). Likewise, the temporary channel may include multi-factor authentication for access.

[00167] In addition, the security zone structure (1400) further comprises a process application security zone (1464), which contains a process information subzone (1441) and a process control subzone (1442). The process application security zone (1464) may contain network devices that make process control decisions involving users and non-rig related components. In some embodiments, the bearer may allow applications and processes in the process information subzone (1441) to use data from the middleware protocol control subzone (1412). In the process information subzone (1441), network devices can only subscribe to information transmitted by the middleware protocol control subzone (1412). For example, a sensor device or control system may emit data that is transmitted over a bearer and received by one or more subscribers in a process information subzone (1441). In particular, one or more network communication protocols associated with a bearer may implement a software architecture that provides a publish-subscribe model among various network devices residing in and/or connected to the middleware protocol subzone (1412). In the case where the respective network device or component of the respective network device is a subscriber for a particular sensor device or control system, data from the sensor device or control system may be transmitted over a unidirectional channel. In the case where the sensor device has five subscribers, for example, sensor data from the sensor device may be transmitted to each of the five subscribers each time the sensor data is broadcast on a bearer. Thus, the sensor device can act as a publisher in a publish-subscribe model. In some embodiments, the drilling control network uses a security certificate to authenticate a device before it is allowed to issue or subscribe on a bearer.

[00168] In the process control subzone (1442), network devices may implement control mechanism services that are provided with various control functionality. This zone may be limited by the control functionality provided through the middleware protocol domain.

[00169] The security zone structure (1400) further comprises a perimeter network security zone (1465), which contains a demilitarized (DMZ, demilitarized) configuration management subzone (1451), an infrastructure management subzone (1452), a voice communication subzone (1453), and a CCTV proxy and a local access subzone (1454). The perimeter network security zone (1465) may correspond to non-communication facilities located in the perimeter network. For example, a perimeter network may be a logical or physical subnet of a drilling control network and/or a user network that exposes the organization's external servers to an untrusted network, such as the Internet and/or a company network. The perimeter network security zone (1465) may have a relatively low security level within the security zone structure (1400) and may be connected to channels that interact with control systems in the drilling control network and non-rig components.

[00170] Still in accordance with FIG. 14, the security zone structure (1400) further comprises an enterprise network security zone (1466), which contains a corporate public cloud subzone (1455), a guest access subzone (1456), a network users subzone (1457), and a role fixed station subzone (1458). An enterprise network security zone (1466) may correspond to an enterprise network that may connect user devices and network devices in various departments and workgroup networks. For example, an enterprise network may be the backbone of an organization that provides communication and networking resources to employees and guests in many different departments. Outside the enterprise network security zone (1466) is the Internet security zone (1467), which contains an unauthenticated Internet subzone (1471) and a public cloud subzone (1472).

[00171] While with respect to the security zones and subzones of the security zone structure (1400) in accordance with FIG. 14 discusses various channels, one skilled in the art should be aware in light of the disclosed technology that one or more unidirectional channels, one or more bidirectional channels, and/or one or more time channels can connect any two security zones or subzones of the zone structure (1400). security. Similarly, one or more internal channels may be located in any security zone and/or security subzone of the security zone structure (1400).

[00172] Returning to FIG. 15, in FIG. 15 illustrates a block diagram in accordance with one or more embodiments of the invention. In particular, in FIG. 15 illustrates a method for accessors in one or more security zones located in a drilling control network and/or a user network. One or more steps in FIG. 15 may be performed by one or more components (eg, a virtual connection controller (1343)), as illustrated in FIG. 1, 2, 13 and/or 14. While the various steps in FIG. 15 are illustrated and described sequentially, it will be apparent to those skilled in the art that some or all of the steps may be performed in different order, may be combined or omitted, and some or all of the steps may be performed in parallel. In addition, steps can be performed actively or passively.

[00173] At 1500, a request to access data in security zone Y is received from a network device in security zone X, in accordance with one or more embodiments of the invention. For example, the network device may be a user device that sends a request to a virtual connection controller that manages the link between the specified zones. The user device may be locally connected to the user network and/or the drilling control network and/or remotely connected to the virtual connection controller, for example via the Internet. Similarly, the user device may be a control system or one or more network elements located in a user network or a drilling control network. For example, the control system may request data from one or more other control systems in order to execute an algorithm associated with a particular drilling operation. The security zone X and/or the security zone Y may be similar to the security zones shown above in FIG. 13 and 14 and in the accompanying description.

[00174] At 1510, the network device is authenticated to communicate over a temporary channel, in accordance with one or more embodiments of the invention. For example, a temporary channel may connect security zone X and security zone Y. In response to receiving the request, such as at 1500, the network device and/or the software application may determine if the network device has permission to access data from one or more non-communication media located in a particular security zone. For example, the virtual connection controller may access the account of the user associated with the user's device and/or the user operating the user's device. The user account may contain user credentials that define which PLC the user and/or the user's device can access. To complete authentication, the network device may require additional user credentials, which may be manually entered into the user account by an administrator and/or generated automatically based on various user and/or user device related information stored in the user account or elsewhere.

[00175] In addition, the user's credentials may also indicate one or more time windows when the user and/or user device may communicate via the time channel. Similarly, user credentials may be time window attributes, such as data fields that contain information related to start times, end times, specific days of the week, month, or year, and allotted time periods for various time windows assigned to the user and/or user device. In addition, time window attributes may describe general time windows and private time windows.

[00176] In one or more embodiments of the invention, for a temporary channel between two security zones, the virtual connection controller performs multi-factor authentication. For example, the user's device may log into the user's network using a username and password. Accordingly, after establishing a network connection with the user network, the virtual connection controller may request an additional password and/or identification to establish a virtual connection through a temporary channel. For example, the additional password and/or identification information may be a personal identification number, a biometric identifier such as a fingerprint, personal information relating to the user requesting access, and/or a network device code transmitted independently to the user's device.

[00177] In some embodiments of the invention, for example, a time-limited set of virtual connection credentials is generated for a temporary channel. For example, the virtual connection credentials may contain network and/or firewall configurations for communicating over the virtual connection. In addition, in response to the VC controller's determination that the user's device is authorized, the virtual connection credential may contain a network device code specially generated by the VC controller or other network element for the network device. The network device code may be a pseudo-random or otherwise defined alphanumeric sequence that allows the network device to communicate with a PLC and/or control system on the drilling control network.

[00178] At 1520, a virtual connection is established using a temporary channel between security zone X and security zone Y, in accordance with one or more embodiments of the invention. If it is determined, for example, that the user's device is authorized to access non-communication facilities in the security zone, the virtual connection controller may establish a virtual connection over a temporary channel. If a switched virtual connection exists between two security zones, the virtual connection controller may allow network communication over the switched virtual connection to establish a virtual connection. On the other hand, if it is determined by the virtual connection controller that the network device is not authorized to access one or more specific non-communication facilities in the security zone and/or the user device is not currently authorized, the connection cannot be established at the step 1520.

[00179] In one or more embodiments of the invention, the virtual connection controller is turned off and/or physically disconnected from the drilling control network and/or user network. After the network device is authenticated at 1510, the virtual connection controller may power up and establish a virtual connection over the time channel. In some embodiments, the virtual connection controller or other software application may terminate the virtual connection established at 1520. For example, the virtual connection controller may remove the link layer connection, thereby returning the temporary channel to a closed state. Similarly, firewall settings can be set by the virtual connection controller to block network traffic through the temporary channel. In the case of a switched virtual connection, the virtual connection controller may set the switched virtual connection to a state such that it represents an open circuit. In one or more embodiments of the invention, for example, the virtual connection controller turns off the power and disconnects after determining that the virtual connection is completed.

[00180] At 1530, data is transferred between security zone X and a network device in security zone Y over a virtual connection, in accordance with one or more embodiments of the invention. For example, a network device may receive PLC data from a control system located in security zone X. Similarly, the network device may send one or more control commands to adjust parameters and/or settings in one or more control systems in the security zone X. In other words, once a virtual connection has been established, the network device may have read and/or control access to one or more non-communication media in a particular security zone. For example, in one or more embodiments of the invention, access refers to control commands sent over a temporary channel for control and management in a security zone.

[00181] At step 1540, one or more packet analyzes are performed on data transmitted between security zone X and security zone Y, in accordance with one or more embodiments of the invention. When analyzing a packet, one or more pieces of data transmitted over the channel can be analyzed to determine if one or more access control policies are violated. For example, packet sniffing may be performed by the firewall and/or one or more network elements in the drilling control network and/or user network. For example, in some embodiments of the invention, deep packet analysis is performed on data transmitted over a time channel at 1520 or other channels operating in a drilling control network or user network.

[00182] Although above in FIG. 15 and the accompanying description mentions a temporary channel, in other embodiments of the invention, similar steps can be applied to unidirectional channels and/or bidirectional channels. Similarly, the embodiments of the invention described with reference to FIGS. 15 may also apply to internal channels operating within the same security zone. In addition, in the technologies shown above in FIG. 15, sub-zones may be used instead of security zones.

Cyber security control system

[00183] In general, embodiments of the invention include systems and methods for communicating with network devices in the control area of a drilling control network. In particular, one or more embodiments of the invention relate to a system that includes a firewall that links a control zone to a control zone. For example, control systems for drilling operations and maintenance operations may be located within the control zone, while the control zone contains network devices that are designed to control and administer processes using control systems. Similarly, a zero-trust network topology can be implemented within a zone of control that only allows network communication between pre-authorized devices.

[00184] In some embodiments of the invention, one or more security agents are located on various network devices in the control zone. The security agent may be a component within the host network device, where the security agent is responsible for managing communication with the host network device and devices located outside the control zone. For example, a security agent may monitor its host network device and network traffic to determine different time windows for data transmission. Due to the potentially large size of the network, it may be necessary for the security agent to determine specific times when data transmission does not interfere with management processes. For example, to perform a software installation, a security agent may need to arrange for a software installation file to be transferred to a host network device. Then, after receiving the file, the software agent can determine the appropriate time to perform the software installation using the file.

[00185] Returning to FIG. 16, in FIG. 16 illustrates a block diagram of a system in accordance with one or more embodiments of the invention. As illustrated in FIG. 16, the drilling control network (1600) may comprise various network zones (eg, control zone (1620) X, control zone (1670) Y) associated with a firewall (eg, firewall (1660) X). In one or more embodiments of the invention, the drilling control network contains a control zone (for example, control zone (1620) X) with various control systems (for example, control zone (1621) A, control system (1622) B, control system (1623) C ) and network elements (eg, network element A (1631), network element B (1632), network element C (1633)). In particular, the control zone may contain various deterministic systems, such as control systems that operate in the feedback portion of the drilling control network. Within the feedback part, the control systems can operate using high-speed data transmission and in accordance with the requirements of accurate timing. For example, status requests may be made between network devices in the control area at very high rates, such as microseconds to milliseconds.

[00186] In addition, control systems may include hardware and/or software with functionality to perform various drilling operations and/or various maintenance operations. For example, drilling operations control systems and/or maintenance management systems may include, for example, programmable logic controllers (PLCs) (e.g., PLC A (1627), PLC B (1628)) that contain hardware and/or software with functional means for controlling one or more processes performed by the drilling rig, including, but not limited to, the components illustrated in FIG. 1. With respect to the PLC, the PLC can control valve states, fluid levels, pipe pressures, alarms and/or depressurizations throughout the rig. Further, the programmable logic controller may be a ruggedized computer system with functionality to withstand vibration, extreme temperatures, wet environments, and/or dusty environments, such as near a drilling rig. Drilling operations control systems and/or maintenance management systems may also refer to control systems that comprise a plurality of PLCs in a drilling control network (1600). In addition, control systems may be associated with drilling equipment (eg, drilling equipment A (1629), blowout preventer (99), drilling rig (12) and other components illustrated above in Fig. 1 and discussed in the accompanying description).

[00187] Without loss of generality, the term "control system" can refer to a drilling operations control system used to operate and control equipment, a drilling data acquisition and monitoring system that is used to collect data on the drilling process and equipment, and to monitor the operation of the process. drilling, or a drilling interpretation software system that is used to analyze and understand the progress of drilling and events associated with drilling.

[00188] In some embodiments, one or more control zones are associated with a control zone (eg, control zone (1670) Y). For example, the Y control zone (1670) may be part of a drilling control network (1600) that contains various network elements (not illustrated), network devices (e.g., network devices (1672)), one or more configuration managers (e.g., manager ( 1671) configuration) and/or one or more application managers (eg, application manager (1673)). For example, a control zone may be a protected security zone outside of control zones. In particular, administration of network devices in a control zone may be transferred to other network devices located in one or more control zones.

[00189] Similarly, when using a firewall outside the control zone, packet filtering may have a limited impact on network response time within the control zone. Thus, the control zone, which works with a huge amount of data, can save its processing power, since it is not involved in packet processing by the firewall. For example, a search is made for packages that are included in the control zone, while packages in the control zone can move freely. For more information on packet filtering between the control zone and the control zone, see FIG. 18 and the accompanying description.

[00190] Referring to FIG. 17, in FIG. 17 provides an example of a security agent receiving a software update file. The following example is provided solely for the purpose of illustrating and not limiting the scope of the disclosed technology. In FIG. 17, the security agent R (1741) communicates with the controller (1771) of configuration X, acting as the home device, over the drilling control network (1700). In particular, the protection agent (1741) R runs on the destination device (1726) M, which is located in the control zone (1720) A. The security agent (1741) R receives the software update file (1775) X on the logical path S (1780) . Logical path S (1780) contains various network links (i.e., network link A (1781), network link B (1782), network link C (1783)), which cover the security gateway (1760) Q and commutator O (1731). Thus, security gateway (1760) Q detects that configuration manager (1771) X is authorized to send data to destination device (1726) M and sends packets associated with software update file (1775) X to zone (1720) control A. Within the control zone (1720) A, the switch O (1731) determines that the packets associated with the software update file (1775) X can be transmitted to the destination device (1726) M.

[00191] Referring to FIG. 17, when the security agent (1741) R receives the software update file (1775) X, the security agent (1741) R analyzes the control zone (1720) A and the destination device (1726) M to determine whether the network conditions exist to install the file (1775) software update X. Once the security agent (1741) R detects that there are network conditions for the available network state of the installation, the security agent (1741) R executes the software update file (1775) to update one or more programs of the system software running on the device (1726) destination M.

[00192] Referring to FIG. 16, in some embodiments, the control zone includes one or more configuration managers (eg, configuration manager (1671)). In particular, the configuration manager may include hardware and/or software that contains functionality for managing software installations and other software processes in one or more control zones. For example, the configuration manager can determine if there is a new software version for the software application running on the corresponding device in the control zone. Accordingly, the configuration manager can determine whether the new software version creates any conflicts with the control system and/or other network devices in the control zone, and whether the installation of the new software version on the corresponding device is guaranteed. Thus, the configuration manager may contain functionality for managing software updates and other software configuration settings. Similarly, setting up software configurations may include changing various software settings, such as computer resources associated with a software application, time settings for running software processes, and so on. In some embodiments, the configuration manager includes functionality for adding network devices to the control zone and/or removing network devices from the control zone, for example, by checking and/or unchecking a specific network device.

[00193] Moreover, the control zone may contain one or more application managers (eg, application manager (1673)). In particular, the application manager may comprise hardware and/or software with functionality for managing various feedback processes performed in the monitoring area. In particular, the application manager can be removed from control applications managed by control systems and thus is more flexible than control applications in terms of processing power and network resources. For example, an application manager may contain functionality for coordinating various control systems and other network devices to work together and operate without interference in a control area.

[00194] Referring to FIG. 16, control zones may further comprise various network devices (e.g., human machine interface (HMI) Y (1625), archive data server (1624) X, network device Z (1626)) and various network elements (e.g., network element A (1631), NE B (1632), NE C (1633)). Network devices may include personal computers, control systems, smartphones, human-machine interfaces, user devices, drilling equipment, user equipment at the well site, and any other devices connected to the drilling control network. The human-machine interface may be hardware and/or software associated with the drilling control network (1600) and which contains functionality for presenting data and/or receiving input from a user related to various drilling and/or drilling operations. maintenance performed on the drilling control network (1600). For example, the human-machine interface may include software for providing a graphical user interface (GUI) for presenting data and/or receiving control commands for operating a drilling rig. The historical data server may contain hardware and/or software for collecting and/or analyzing sensor data received within the control zone. A network element may refer to various hardware components in a network, such as switches, routers, hubs, user equipment, or any other logical entity for connecting one or more physical devices in a network. The network elements, human-machine interfaces, archive servers, network devices, and/or control systems may be computing systems like the computing system (3400) illustrated in FIG. 34.1 and 34.2, and described in the accompanying description.

[00195] While in FIG. 16 and 17 illustrate various component configurations, other configurations may be used without departing from the scope of the present invention. For example, the various components in FIG. 16 and 17 can be combined to create one component. As another example, functions performed by one component may be performed by two or more components.

[00196] Returning to FIG. 18, in FIG. 18 illustrates a block diagram in accordance with one or more embodiments of the invention. In particular, in FIG. 18 illustrates a method for communicating with one or more network devices in the control area of a drilling control network. One or more steps in FIG. 18 may be implemented by one or more components (eg, security firewall (1660) X) as illustrated in FIG. 1, 2, 16 and/or 17. While the various steps in FIG. 18 are illustrated and described sequentially, it will be apparent to those skilled in the art that some or all of the steps may be performed in different order, may be combined or omitted, and some or all of the steps may be performed in parallel. In addition, steps can be performed actively or passively.

[00197] At 1800, a network device is connected to a monitoring zone, in accordance with one or more embodiments of the invention. In particular, the network device may establish a network connection to a drilling control network that contains a control zone. The network connection can be manually established by a technician who includes one or more drilling control network ports connected to a network device. The network device may be similar to one of the network devices illustrated in FIG. 16 and described in the accompanying description, such as control system (1622) B, archive data server (1624) X, etc.

[00198] In step 1805, communication between the network device and other network devices in the control area is checked in accordance with one or more embodiments of the invention. In particular, the check can determine which devices can be authorized destination devices for the checked network device in the control zone. For example, a network device may have one or more sets of network credentials that grant communication access to various devices within a zone of control. Network credentials may be provided at the well site by a human operator who sets up a network device in the control area. Similarly, network credentials may be stored on a network device and verification may be performed automatically by one or more software protocols running on the network device and/or on the drilling control network. For example, the configuration manager may parse the network credentials for a network device to perform validation.

[00199] In some embodiments of the invention, the network device broadcasts the network credentials throughout the control zone to perform verification. Thus, each of the network devices in the control zone can parse the network credentials to determine if the network device can be an authorized source device. Thus, decentralized network protocols can be executed for checks in the control zone.

[00200] At step 1810, the control zone is reconfigured to take into account the network device check, in accordance with one or more embodiments of the invention. Depending on the destination devices for the verified network device, various network elements, firewalls, etc., can be reconfigured inside and/or outside the control area to allow communication between the verified network device and the destination devices.

[00201] In some embodiments of the invention, for example, a configuration manager in a monitoring zone receives verification information in connection with a verified network device. As such, the configuration manager may update one or more of the network tables stored on the various switches, routers, etc. in the drilling control network to ensure verified communications.

[00202] At 1815, a packet arrives from a network device in accordance with one or more embodiments of the invention. For example, one or more packets may be transmitted over a logical path that contains a firewall in the drilling control network. The logical path may contain various network nodes which, for example, provide a path through the drilling control network to the control zone. Thus, when a firewall, switch, or other network element along the logical path receives a packet, the corresponding intermediate device can perform further analysis of the packet.

[00203] At step 1820, a determination is made for the packet with respect to the destination device in the monitoring zone, in accordance with one or more embodiments of the invention. In particular, the packet or packet destination device may be analyzed to determine the desired destination device. For example, the packet may contain a destination network address that indicates the final location of the packet in the drilling control network. Likewise, the control zone and destination device may be similar to the control zones and/or destination devices illustrated above in FIG. 2 and 3 and in the accompanying description.

[00204] In some embodiments of the invention, a network device in the control area is associated with a corresponding device in the control area. Thus, the firewall can identify the appropriate destination device based on which device or application is sending the packet.

[00205] At 1825, it is determined if the network device is authorized to communicate with the destination device, in accordance with one or more embodiments of the invention. In particular, the drilling control network may implement various security protocols to ensure that network traffic across the control zone is limited to predetermined types and/or amounts of data. For example, restricting network traffic, even at the edge of a firewall, may not be typical. Thus, the firewall and/or other network elements associated with the control zone can apply a zero-trust approach to packets entering the control zone, as well as packets already moving inside the control zone. As such, control zones can provide a network topology that dynamically monitors and controls network traffic between authorized and unauthorized devices in terms of network feedback. If the process stops on a feedback part, for example, the network elements and/or the firewall may display the interruption of the process at a specific location within the control zone.

[00206] In some embodiments, the drilling control network may store network information such as network addresses, network protocols, network dependencies, and port numbers for each of the network devices connected to the drilling control network. Based on this network information, the control zone can restrict network communication to allowed locations in the drilling control network. For example, the firewall may analyze the packet's source and destination devices using a lookup table to determine if communication is authorized.

[00207] In some embodiments of the invention, the drilling control network determines a potential security threat by detecting a packet having unauthorized communication. For example, when a firewall receives a packet for transmission to an unauthorized destination, the firewall may provide an unauthorized communication alarm notification. Thus, various security violations in the control zone can be identified as an addition to security violations in the control zone.

[00208] At step 1830, the transmission of the packet is terminated in response to a determination that there is no authorized communication between the destination device and the network device, in accordance with one or more embodiments of the invention. Based on the determination that the packet is not authorized for transmission to the destination device, the firewall and/or other network elements may stop transmitting the packet. For example, a control zone may filter packets at the border of the control zone using a firewall or within the control zone using a switch or other network element.

[00209] In one embodiment of the invention, for example, if the pump PLC is required only to communicate with the HMI, then this communication may be the only communication allowed for the pump PLC within the control zone. If the packet tries to travel somewhere else within the control zone, the packet transmission is terminated. This termination process may be performed by switches (eg, network elements (1631, 1632, 1633) as illustrated in FIG. 16 between PLC A (1627) and archive data server X or network device Z (1626)) . Accordingly, in some embodiments of the invention, the device parses the header of the packet to determine if the packet is authorized to communicate with the destination device. For example, network elements in the control zone may ignore the content, ie payload data, of the packet and simply filter based on the destination network addresses and/or source network address of the packets. In another embodiment of the invention, the content may be viewed by a network device, such as a security agent running on a host network device. If the source device is authorized to communicate with the destination device, the firewall can scan the packet's source network address and destination network address to make an appropriate determination.

[00210] At 1840, the packet is transmitted to the destination device in response to determining that communication between the destination device and the network device is authorized, in accordance with one or more embodiments of the invention. In cases where a network device is authorized to communicate with a destination device within the control zone, the firewall and/or other network element may forward the packet through the control zone.

[00211] In some embodiments of the invention, the network architecture shown in FIG. 16, 17 and/or 18 allows the drilling control network to reduce the network resources for PLC control, i.e., to minimize the resources required to operate the pump, etc. On the other hand, control processes for controlling other control systems in control zone can operate and be placed behind the firewall. Figuratively, the human hand can be an analogue of PLC control systems in the control zone. The actual movement of the hand is functional, but how the hand moves and the destination the hand moves to can be determined by the brain, which corresponds to a location outside the control zone and behind the firewall. In other words, efforts to plan and organize control systems can be made outside the zone of control, and execution occurs inside the zone of control.

[00212] In addition, when accessing systems in the zone of control, there may be security risks. For example, remote access may be provided to troubleshoot devices, update control systems, and move files into and/or out of the drilling control network. In FIG. 18 and the accompanying description provide secure control protocols that can automatically transfer data in various automated ways to the control area or receive data from the control area without human intervention in the data transfer processes.

[00213] Returning to FIG. 19, in FIG. 19 illustrates a block diagram in accordance with one or more embodiments of the invention. In particular, in FIG. 19 shows a method for installing software on a network device in the control zone. For example, the block diagram illustrated in FIG. 19 may be performed in addition to the flowchart or separately from the flowchart shown in FIG. 18. One or more steps in accordance with FIG. 19 may be implemented by one or more components (eg, security agent (1643) C) as illustrated in FIG. 1, 2, 16 and/or 17. While the various steps in FIG. 19 are illustrated and described sequentially, it will be apparent to those skilled in the art that some or all of the steps may be performed in different order, may be combined or omitted, and some or all of the steps may be performed in parallel. In addition, steps can be performed actively or passively.

[00214] In step 1900, it is determined if there is a software installation for a network device in the control area of the drilling control network, in accordance with one or more embodiments of the invention. The network device may be a control system, an active data server, an HMI, or another network device as shown in FIG. 16 and in the accompanying description. For example, the configuration manager may store software version information regarding control systems and/or other network devices within the control area of the drilling control network. Accordingly, when a new software version is released, the configuration manager may be notified of the new software version. Thus, the configuration manager can automatically detect if a software update exists for the network device.

[00215] In addition, the configuration manager may receive a request, for example, from a human user or an automated process, to install a software application on one or more network devices in the area of control. Instead of replacing an existing version of the software, the configuration manager can arrange for a completely new installation of the software. For example, in the case where a control system is added to the control area, one or more software installations may be assigned to the added control system.

[00216] At 1910, one or more software installation files are received by a security agent, in accordance with one or more embodiments of the invention. For example, a configuration manager may communicate with a security agent located on a host network device. The configuration manager can transfer the software installation file to the device to update the software on the device. For example, a software installation file may be transferred from a configuration manager in a control zone to a host network device in a control zone in a manner similar to that shown above in FIG. 18 and in the accompanying description. In some embodiments of the invention or, for example, the firewall device may look for a software installation file before entering the control zone. In some embodiments of the invention, the security agent monitors network traffic in the zone of control until there is an available time window to transfer the software installation file to the host network device.

[00217] Once the security agent receives the software installation file, the file may be placed on the storage device until a predetermined execution time that is associated with a predetermined network state occurs. See steps 530 and 540 and the description below for more information on the specified network states.

[00218] At 1920, one or more network device operating conditions are determined with respect to the network device, in accordance with one or more embodiments of the invention. In some embodiments of the invention, for example, the security agent monitors the operation of the main network device, such as the implementation of drilling operations and/or maintenance operations. In this way, the operating conditions of the network device can correspond to the operation of the network master, determining, for example, whether the network master is currently occupied with control operations, and therefore not suitable for software installation. Likewise, network device terms may also denote operation within a control zone or drilling control network. For example, if other control systems require the host network device to be connected to the network to perform various processes, the security agent may identify dependent control systems among the operating conditions of the network device.

[00219] In step 1930, it is determined whether one or more network device operating conditions match a given network state to perform software installation in accordance with one or more embodiments of the invention. For example, a security agent may prevent the processing of a software installation file until the host network device meets certain network device conditions. In particular, once at step 1920 the security agent confirms that one or more conditions of the network device are consistent with the specified network state, the security agent may proceed to install the software. An example of a predetermined network state is when drilling operations and maintenance operations in the drilling control network are completed. Another set network state is associated with a short period of network traffic during the night. Another example of a given network state is when one or more control systems are offline for maintenance and thus provides other control systems with a time window to perform local operations.

[00220] In addition, once a predetermined state occurs, the security agent may communicate with the configuration manager and/or other network devices in the control zone or control zone to perform software installation. In some embodiments of the invention, the security agent determines the specified network state to obtain the software installation file at 1910.

[00221] At 1940, one or more software installation files are executed on a network device based on a predetermined network state, in accordance with one or more embodiments of the invention. For example, executing a software installation file may include changing one or more settings on a host network device, extracting content from a file, launching software applications using the file, scanning the file for viruses, and so on.

[00222] Once the target network state is determined, the software installation files can continue to be processed on the host network device while the host network device remains in the preset network state. In some embodiments of the invention, the security agent may detect a change in a predetermined state and thus automatically complete the installation of the software.

[00223] And further in accordance with Fig. 19 and the accompanying description of the control system in the drilling control network tend to remain static over time, that is, control systems may rarely be updated with new software. Thus, the functionality of the device in the control system may rarely change. Since the control systems on the rig are production systems, changing the software on the network device can result in huge production costs. Thus, changes in the field of industrial management are very slow.

[00224] However, as remote access to control systems, archive servers, and other network devices on the drilling control network is increasingly being provided, cybersecurity risks increase due to this level of access. Thus, the processes shown above in FIG. 18 and 19 provide embodiments of the invention both for providing security in the control zone of the drilling control network and for adding and/or updating security in the control zone. In this way, control system processes can be managed along with periodic software updates in the control zone, which prevents many cybersecurity threats.

Replication of protected data

[00225] In general, embodiments of the invention include a system and various methods for providing a data management architecture in a drilling control network. In particular, one or more embodiments of the invention relate to a system that includes a data controller that manages data communication between a drilling control network and remote devices. For example, in some embodiments of the invention, the network connection is a low bandwidth connection. Thus, the data controller can control the transmission of various data sets through a low bandwidth connection for a predetermined period of time. After the data transfer is completed, the data arrays are stored in different persistent storage devices based on predetermined data types such as software images, data models, etc. In some embodiments, persistent storage devices are separated based on data associated with different conditions. network operation, such as production conditions and technological preparation conditions. For example, the conditions of technological preparation may be that the software and/or hardware in the drilling control network is tested before being used in actual production conditions.

[00226] Once the data is stored in persistent storage devices, various security protocols can be implemented in the drilling control network to ensure that the data is securely used by network devices throughout the drilling control network. For example, by maintaining the data in an appropriate persistent storage device, the drilling control network can maintain redundancy of data in the event that a network device such as a virtual machine or a software container completes operations on the corresponding data. Accordingly, the data controller and persistent storage devices can provide a well-defined data chain in connection with how data enters the drilling control network and is transmitted to specific systems in the drilling control network. For example, when a certain version of the software application interferes with one or more processes in the control system, the data management controller may map the version-related data back from the installation of the software application to the corresponding persistent storage device and back to the data source and network arrival time.

[00227] Returning to FIG. 20.1, in fig. 20.1 illustrates a block diagram of a system in accordance with one or more embodiments of the invention. In one or more embodiments of the invention, a persistent storage device (e.g., persistent storage device (271) A, persistent storage device (272) N) is a virtual machine or software container that contains functionality for accessing data and/or providing data in connection with a given data type. For example, in some embodiments of the invention, the persistent storage device contains the functionality to provide data without using the data controller as an intermediate device, for example, the persistent storage device can directly receive requests for data from the drilling control network (for example, network (200) drilling control X). Thus, the persistent storage device can be decentralized and separated from the data management controller.

[00228] In some embodiments of the invention, the data control controller (eg, data control controller (210) A) manages time-controlled data transmissions of large volumes to the drilling control network. For example, the data controller may monitor network traffic to and from the network to determine a predetermined period of time when data transmission does not interfere with mining operations. Accordingly, since the remote network connection may be a low bandwidth connection, the data controller may perform data transmission for one or more time periods to complete the data transmission. Upon receipt of data on the drilling control network, the data management controller may comprise functionality to identify one or more predetermined data types associated with the data and store the data in a persistent storage device associated with the predetermined data type.

[00229] In one or more embodiments of the invention, the persistent storage device is associated with software images (eg, software images (2081)). For example, a persistent storage device may contain different software images for different software versions used by network devices throughout the drilling control network. For example, the drilling control network (2000) X may comprise a configuration manager (2055) that contains hardware and/or software with the functionality to determine if a software update exists for one or more network devices. Upon detection of a software update, the configuration manager (2055) can access persistent storage device (2071) A to obtain a software image for the corresponding software update. In another embodiment of the invention, the persistent storage device is associated with network configurations for various control systems and other network devices for various network conditions. Thus, the configuration manager may set up network persistence and/or set up network configuration for various virtual machines, software containers, and other network devices throughout the drilling control network using one or more persistent storage devices.

[00230] Referring to FIG. 20.1, the drilling control network (2000) X may further comprise various network devices (e.g., control systems (2015), virtual machines (2040), host devices (2050), virtualization service manager (2060) A). For example, network devices may comprise one or more host devices that contain hardware and/or software that is associated with drilling equipment (eg, one or more programmable logic controllers (PLCs)). The drilling equipment may include a blowout preventer (99), a drilling rig (12), and other components illustrated above in FIG. 1 and discussed in the accompanying description.

[00231] PLCs associated with host devices may form various control systems (eg, control systems (2015)), such as various drilling operations control systems and various maintenance management systems. In particular, PLCs may comprise hardware and/or software functionality for controlling one or more of the processes performed by the drilling rig, including but not limited to the components illustrated in FIG. 1. Specifically, the PLC can control valve states, fluid levels, pipe pressures, alarms and/or depressurizations throughout the rig. Further, the programmable logic controller may be a ruggedized computer system with functionality to withstand vibration, extreme temperatures, wet environments, and/or dusty environments, such as near a drilling rig.

[00232] With regard to persistent storage devices, in some embodiments of the invention, the persistent storage device is associated with data models (eg, data models (2082)). Data models can contain different databases for geological and production data, drilling data, 3D models, non-well data, received drilling operations data, etc. Similarly, data models can also contain different versions of the same the same data, such as data acquired over different time periods and/or updated versions of the data based on subsequent drilling operations. For example, one or more control processes performed by different control systems may use data models to perform one or more drilling operations. In another embodiment of the invention, the user analyzes past drilling operations using one or more data models obtained from persistent data storage devices.

[00233] Referring to FIG. 20.2, a virtualization services manager (e.g., virtualization services manager A (2060)) may contain hardware and/or software that contain functionality for creating, shutting down, monitoring, and/or controlling one or more virtual machines (e.g., a virtual machine). machine A (2041), virtual machine N (2042)) and/or software containers (for example, software container A (2046), software container N (2047)) operating at the drilling control network virtualization service level. In some embodiments of the invention, the virtualization services manager includes a hypervisor for managing one or more virtualized environments in the drilling control network. For example, virtualization services may be implemented at one or more network layers in a drilling control network, such as when virtual machines and/or software containers operate at the network layers. Instead of implementing a virtual machine or software container on a single host device, for example, a virtualization service may be implemented using a virtual machine or software container that runs on multiple host devices. Examples of virtualization services may include managing field data among PLCs and/or drilling equipment, managing a virtual machine, managing a software container, allocating memory resources among host devices in a drilling control network, various network processes for administering a drilling control network, etc. For example, the virtualization service manager may communicate with virtual machines and software containers to stop and/or start virtualization services that are running on the virtual machines and software containers.

[00234] In one or more embodiments of the invention, the host device comprises a virtualization controller (e.g., virtualization controller A (2031), virtualization controller N (2032) running on a host operating system (e.g., host operating system A (2021), operating system N (2022) host). The virtualization controller may include hardware and/or software that includes functionality for communicating with other virtualization controllers on the drilling control network and/or implementing various virtualization services on the drilling control network. For example, virtualization controllers can be virtual machines and/or software containers running on host devices (2011, 2012). Virtualization services may include network processes that run on multiple network devices (eg, host devices (2011, 2012), network elements (2005), host devices (2013)).

[00235] In addition, the software container may be a special case of user space implemented by a single host operating system kernel (eg, host operating system A (2021), host operating system N (2022). In particular, a software container may be an application layer abstraction that allows isolated processes to run within a software container. Similarly, multiple software containers can run on a single operating system core. Software containers may include Docker containers, Java™ containers, Windows ^Server® containers, etc. In contrast, a virtual machine may include hardware and/or software that may provide an abstraction of physical hardware. For example, the virtual machine may have an independent operating system that is separate from the host operating system, and the virtual machine may run on one or more host devices with dedicated memory and other computing resources.

[00236] In addition, the virtualization services manager (eg, virtualization services manager A (2060)) can administer and/or monitor various host device resources for virtual machines and/or software containers running at the virtualization services layer. Likewise, the overall drilling control network (2000) virtualization architecture may be the same as when the host operating system runs on a non-operating system platform (eg, a hardware computing system) or as a virtual machine. For example, virtual machines and software containers can communicate with each other at the virtualization service layer and start the virtualization services in a consistent manner.

[00237] In addition, the drilling control network may include user devices, which may include hardware and/or software connected to the drilling control network. User devices may be network devices that contain functionality for presenting data and/or receiving input from a user related to various drilling operations and/or maintenance operations performed on the drilling control network. For example, a user device may include personal computers, smartphones, human-machine interfaces, and any other network-connected devices that receive input from one or more users, such as by providing a graphical user interface (GUI). Likewise, the user device may present data and/or receive control commands from the user to control the drilling rig. A network element may refer to various software and/or hardware components in a network, such as switches, routers, hubs, user equipment, or any other logical entities for connecting one or more physical devices in a network.

[00238] While in FIG. 20.1 and 20.2 illustrate various component configurations, other configurations may be used without departing from the scope of this invention. For example, the various components in FIG. 20.1 and 20.2 can be combined to create one component. As another example, functions performed by one component may be performed by two or more components.

[00239] Returning to FIG. 21, in FIG. 21 illustrates a block diagram in accordance with one or more embodiments of the invention. In particular, in FIG. 21 shows a method for storing and/or providing data to network devices in a drilling control network. One or more steps in FIG. 21 may be performed by one or more components (eg, data controller A (2010)), as illustrated in FIG. 1, 2, 20.1 and 20.2. While the various steps in FIG. 21 are illustrated and described sequentially, it will be apparent to those skilled in the art that some or all of the steps may be performed in different order, may be combined or omitted, and that some or all of the steps may be performed in parallel. In addition, steps can be performed actively or passively.

[00240] At 2100, a network connection is established between the drilling control network and a remote device, in accordance with one or more embodiments of the invention. For example, the network connection may be a low bandwidth network connection that transmits certain rig data and/or general rig data to the drilling control network. The network connection may be established by a data controller operating on the drilling control network. In particular, a network connection may be established at predetermined times and intervals to allow data to be transmitted without interfering with drilling or production operations. For example, the predetermined time periods may correspond to periods when the control systems are offline and/or remote users are unlikely to access the drilling control network via a remote network connection.

[00241] At 2110, data is received over a network connection and in a drilling control network, in accordance with one or more embodiments of the invention. There may be various restrictions for transmitting data to the drilling control network. For example, a low bandwidth network connection may have high latency and limited downlink availability or uptime. Thus, small amounts of data can be transferred without problems, while large amounts of data may take many days to complete the data transfer. The data management controller may support continuous data transmission for one or more timeslots to receive data at 2110.

[00242] At 2120, one or more persistent storage devices are determined that are associated with a given data type, in accordance with one or more embodiments of the invention. For example, data received over a network connection can be identified based on a given set of data types. For example, the data may include nested metadata that defines one or more data types for the specified data. On the other hand, the data management controller or other network device may analyze the data based on the sender of the data to determine the types of data associated with said data.

[00243] At 2130, data is stored in one or more persistent storage devices associated with a given data type, in accordance with one or more embodiments of the invention. In response to determining the type of data associated with said data, the data may be transmitted over the drilling control network to an appropriate persistent storage device. The storage process may include recording a timestamp of when the data was transmitted by the source and/or received on the drilling control network. Similarly, data may be entered into one or more databases for later access. For example, if the data matches the software image, the data controller may store the software image based on the software version, as well as any control systems that use software applications based on the software image.

[00244] At 2140, data is provided to one or more network devices via one or more persistent storage devices, in accordance with one or more embodiments of the invention. For example, the data controller may act as an intermediary between receiving requests for data and granting access to network devices requesting data. In addition, once the data is stored in the persistent storage device, the persistent storage device can accordingly directly receive requests for data and grant access to the data.

[00245] In one or more embodiments of the invention, data is provided by a persistent storage device to network devices using an installation server. For example, the installation server may implement a temporary channel that is established and closed in order to manage authorized access to a persistent storage device. For example, a temporary channel may restrict access to a network device to certain periods of time and/or to specially authorized network devices. Thus, a temporary channel can provide a communication path between network devices located in different security zones during authorized periods of time. In one or more embodiments of the invention, the temporary channel is a switched virtual connection. For example, the switched virtual connection may include hardware and/or software in two security zones in the drilling control network to implement the virtual connection. Thus, when the switched virtual connection is in the "open" state, the virtual connection cannot be established through the temporary channel. When a switched virtual connection is in the "closed" state, a virtual connection is formed that corresponds to a temporary virtual circuit. The temporary virtual circuit can then provide network traffic, such as persistent data, between the two security zones.

[00246] At 2150, one or more data chains are determined for data provided to one or more network devices, in accordance with one or more embodiments of the invention. In particular, the data chain may include information about how data is received and used by network devices in the drilling control network. For example, the communication chain may be defined and/or stored by a persistent storage device, a data management controller, or other network device in the drilling control network. In some embodiments of the invention, the data chain describes the source (for example, identification information for the remote device that transmits specific data to the drilling control network), date information, such as one or more timestamps, and other information regarding when the data arrives. to the drilling control network and transmitted to one or more persistent storage devices. A data chain may also describe the use of data by various network devices accessing data from a corresponding persistent storage device. In some embodiments of the invention, the data communication chain includes information regarding the use of specific data in technological preparation operations, verification operations, and/or production operations.

[00247] In some embodiments of the invention, to determine the data transmission chain, the data controller records the timestamp, version information, data requests, edit history, and other metadata regarding data associated with one or more persistent storage devices. For example, the data management controller may log any data requests transmitted by the network devices to the persistent storage device. Likewise, the data management controller may record modifications to software and other data generated during pre-production operations, verification operations, and/or production operations. Thus, a persistent storage device may contain multiple versions of the same data based on changes made to the data when exiting the persistent storage device and/or returning to the persistent storage device.

[00248] In some embodiments of the invention, the network device or operator analyzes the communication chain to identify one or more problems in the drilling control network. For example, if the modified program code creates a faulty control system, the communication chain can determine when the program code has been modified by one or more network devices. Similarly, other software images that have had similar modifications can be identified using the data chain. Conversely, without a data chain, the date, type, and/or source of the modification may not be known at the time of analysis of the failed control system.

[00249] Returning to FIG. 22, in FIG. 22 illustrates a block diagram in accordance with one or more embodiments of the invention. In particular, in FIG. 22 illustrates a method for accessing data from one or more persistent storage devices in a drilling control network. One or more steps in FIG. 22 may be performed by one or more components (eg, data controller A (2010)), as illustrated in FIG. 1, 2, 20.1 and/or 20.2. While the various steps in FIG. 22 are illustrated and described sequentially, it will be apparent to those skilled in the art that some or all of the steps may be performed in different order, may be combined or omitted, and some or all of the steps may be performed in parallel. In addition, steps can be performed actively or passively.

[00250] At 2200, a request for data is received from a network device in a drilling control network, in accordance with one or more embodiments of the invention. For example, a user may provide user input on a user device on a drilling control network to access data on a persistent storage device. The request may be a message that identifies the data, a data persistence device, and/or a data type associated with said data. Thus, the request can be transferred directly to the appropriate persistent storage device. In another embodiment of the invention, the data management controller may identify a persistent storage device with data, for example, based on a predetermined data type, and send a request accordingly.

[00251] At step 2210, it is determined whether one or more network conditions for the drilling control network correspond to one or more production conditions in accordance with one or more embodiments of the invention. For example, the data controller, persistent storage device, and/or other network device may monitor the drilling control network to determine if network conditions identify drilling operations or production operations occurring on the network. For example, the virtualization service manager may determine whether drilling operations and/or production operations are present in the network and send a notification that the network conditions are production conditions.

[00252] At 2220, it is determined which persistent storage devices are associated with one or more network conditions, in accordance with one or more embodiments of the invention. In one or more embodiments of the invention, for example, persistent data storage devices can be separated based on whether the data is used for processing conditions or production conditions. In particular, production persistence data storage devices may contain software images, data models, and other types of data that are used in drilling or production operations. Thus, data can be verified and validated by one or more control systems as permanent for use by one or more control systems. Similarly, intermediate persistent storage devices may contain unverified data and/or data subject to verification by the drilling control network.

[00253] For example, in some embodiments of the invention, a plurality of persistent storage devices are located in a data repository. In a data repository, intermediate persistent storage devices are separated from persistent production stores. For example, during normal operation of a drilling rig, the control systems on the drilling rig are linked to permanent production storage facilities. During intermediate testing, control systems are switched to intermediate persistent storage devices to prevent damage to production data and compromise the security of software versions during the testing phase. Moreover, during production preparation, permanent production storages can become a backup copy of data for various control systems and network devices in the drilling control network.

[00254] At 2230, data is transferred to the network device using one or more persistent storage devices associated with one or more network conditions, in accordance with one or more embodiments of the invention.

[00255] Referring to FIG. 23, in FIG. 23 provides an example of a software upgrade through a storage architecture for a drilling control network. The following example is provided solely for the purpose of illustrating and not limiting the scope of the disclosed technology.

[00256] FIG. 23 illustrates a data management controller Z (2310) associated with a production virtual machine R (2342) running on a virtualization services manager O (2360), various management systems Q (2315), a staging store (2371) for software images, and a production storage (2372) for software images. The data controller Z (2310) monitors the control systems Q (2315) to detect various network conditions (2305) associated with a drilling control network (not illustrated). Initially, the data controller Z (2310) receives a request to update the software in the production virtual machine R (2342). The intermediate virtual machine R (2341) or the virtualization services manager O (2360) may send a request to the data controller Z (2310). In another embodiment, the data controller Z (2310) automatically detects the initial software update (2325) for the software application running in the production virtual machine R (2342), for example, via Internet access.

[00257] In response to receiving a software update request, the data management controller Z (2310) and/or the virtualization services manager O (2360) determine whether production operations are occurring on the drilling control network. As soon as mining operations stop, the virtualization services manager O (2360) shuts down the production R virtual machine (2342) and creates an intermediate R virtual machine (2341). The intermediate virtual machine R (2341) may be a virtual machine instance with functionality similar to the production virtual machine R (2342). For example, the intermediate virtual machine R (2341) may contain additional functionality for debugging and/or monitoring software processes or hardware processes running in connection with the intermediate virtual machine R (2341).

[00258] Thus, the virtualization services manager O (2360) may experience an initial software update (2325) on the staging R virtual machine (2341) before implementation in the production R virtual machine (2342). Thus, the virtualization services manager O(2360) can check whether the software version on the R(2341) staging virtual machine is stable and capable of performing various control processes under test conditions before implementation in actual production conditions. Similarly, the program code in the initial software update (2325) can be modified on the intermediate virtual machine R (2341), for example, by changing the configuration settings, customizing the processes associated with the software update, in accordance with the operations performed by one or more control systems, etc.

[00259] Once the intermediate virtual machine R (2341) is created, the data controller Z (2310) accesses the intermediate storage (2371) where the initial software update (2325) is stored. The data controller Z (2310) then transfers the initial software update (2325) to the intermediate virtual machine R (2341) for installation. The staging virtual machine R (2341) can manage the updated software, make changes to the initial software update (2325) and perform various tests on the replacement virtual machine until it is determined that the updated software can be used in the production virtual machine.

[00260] In addition, the initial software update (2325) or modified software update can be further verified by the operator, other network devices, other intermediate virtual machines, etc. After verification, the verified software update (2326) can be placed in intermediate storage (2371) and/or production storage (2372) if the update is ready for use in drilling operations. Thus, the data controller Z (2310) can then send copies of the verified software update (2326) to network devices in the drilling control network.

[00261] Sensor Smart Device Integration

[00262] In general, embodiments of the invention include a system, a sensor device, and various methods for transmitting sensor data over a drilling control network. Returning to FIG. 24, in FIG. 24 illustrates a block diagram of a system in accordance with one or more embodiments of the invention. As illustrated in FIG. 24, the drilling control network (2430) may include a human machine interface (HMI) (for example, HMI (2433)), an archive server (for example, an archive server (2437)) and various network elements (for example, elements (2431) networks). The human-machine interface may be hardware and/or software associated with the drilling control network (2430). For example, the HMI (2433) may allow an operator to interact with the drilling system, such as sending a command to control the equipment or viewing sensor information from the drilling equipment. The human-machine interface may include functionality for presenting data and/or receiving user input regarding various drilling and/or maintenance operations. For example, the human-machine interface may include software for providing a graphical user interface (GUI) for presenting data and/or receiving control commands for operating a drilling rig. A network element may refer to various hardware components in a network, such as switches, routers, hubs, or any other logical entity for connecting one or more physical devices in a network. In particular, the network element, the human-machine interface, and/or the archive server may be a computing system similar to the computing system (3400) illustrated in FIG. 34.1 and 34.2, and described in the accompanying description.

[00263] In one or more embodiments of the invention, a sensor smart device (eg, sensor smart device X (2420)) is connected to the drilling control network (2430). In particular, the sensor smart device may comprise hardware and/or software that contains functionality for obtaining one or more sensor measurements, eg, sensor measurements with respect to the state of the environment in close proximity to the sensor smart device. The sensor smart device can process the sensor measurements into various types of sensor data (eg, sensor data (2417)). For example, the sensor smart device X (2420) may include functionality for converting sensor measurements received from a sensor system (e.g., sensor system (2424)) into a communication protocol format that can be transmitted over the drilling control network (2430) via a communication interface. (eg, communication interface (2421)). Sensor smart devices can include pressure sensors, torque sensors, rotary switches, weight sensors, position sensors, microswitches, etc.

[00264] Further, the sensor smart device may include a processor (e.g., processor (2421)), a communication interface (e.g., communication interface (2422)), a storage device (e.g., memory (2423)) and a sensor system (e.g., sensor system (2424). The processor may be similar to the computer processor (3402) shown in FIG. 34.1 and in the accompanying description. The communication interface (2422) may be similar to the communication interface (3412) shown below in FIG. 34.1 and in the accompanying description. The storage device (2423) may be similar to the non-persistent storage device (3404) and/or the persistent storage device (3406) shown below in FIG. 34.1 and in the accompanying description. The sensor system (2424) may be similar to various sensors (eg, hook load sensor (94), block sensor (95), pressure sensor (92), etc.) shown in FIG. 1 and in the accompanying description.

[00265] In one or more embodiments, the drilling control network (2430) may include drilling equipment (e.g., drilling equipment (2432)), such as a drawworks (60), top drive, mud pumps, and other components shown above in fig. 1 and in the accompanying description). The drilling management network (2430) may further comprise various drilling operations management systems (eg, drilling operations management systems (2435)) and various maintenance management systems (eg, maintenance management systems (2436)). Drilling operations control systems and/or maintenance management systems may include, for example, a programmable logic controller (PLC) that contains hardware and/or software with functionality to control one or more processes performed by a drilling rig, including, but, without being limited to the components illustrated in FIG. 1. In particular, the programmable logic controller may control valve states, fluid levels, pipe pressures, alarms, and/or depressurizations throughout the rig. In particular, the programmable logic controller may be a ruggedized computer system with functionality to withstand vibration, extreme temperatures, wet environments, and/or dusty environments, such as near a drilling rig. Without loss of generality, the term "control system" may refer to a drilling operations control system used to operate and control equipment, a drilling data acquisition and monitoring system that is used to collect data on the drilling process and equipment, and to monitor the operation of the drilling process, or a drilling interpretation software system that is used to analyze and understand drilling progress and events associated with drilling.

[00266] Additionally, drilling operations control systems and/or maintenance management systems may refer to control systems that comprise a plurality of PLCs in the drilling control network (2430). For example, the control system may include functionality for control operations within the system, block, and/or sub-block illustrated above in FIG. 1 and in the accompanying description. Thus, one or more drilling control systems (2435) may include functionality for monitoring and/or performing various drilling operations in relation to a mud circulation system, a rotary system, a lifting system, a pipe supply system, and/or various other drilling operations, shown in FIG. 1 and in the accompanying description. Similarly, one or more maintenance management systems (2436) may include functionality to monitor and/or perform various maintenance activities related to drilling equipment located near the drilling rig. While drilling operations control systems and maintenance management systems are illustrated as separate devices in FIG. 24, in one or more embodiments of the invention, a programmable logic controller and other drilling equipment (2432) on a drilling rig may be used simultaneously in a drilling operations control system and a maintenance management system.

[00267] In one or more embodiments of the invention, the sensor smart device comprises the functionality to establish a network connection (e.g., network connection (2440)) with one or more devices and/or systems (e.g., network controller (2438), systems (2435 ) drilling operation management, maintenance management systems (2436) in the drilling management network. For example, in one or more embodiments of the invention, the network connection (2440) may be an Ethernet connection that establishes an Internet Protocol (IP) address for the smart device X (2420) of the sensor. Accordingly, one or more devices and/or systems in the drilling control network (2430) may transmit data packets to the sensor smart device X (2420) and/or receive data packets from the sensor smart device X (2420) using the Ethernet network protocol. For example, sensor data (eg, sensor data (2415)) may be sent over the drilling control network (2430) in data packets using a communication protocol. Sensor data may include sensor measurements, processed sensor data based on one or more underlying measurements or sensor parameters, sensor device related metadata such as timestamps and sensor device identification information, content attributes, sensor configuration information such as offset , conversion factors, etc. Thus, the sensor smart device X (2420) can act as a host device in the drilling control network (2430), for example, as a network node and/or terminal in the drilling control network (2430). In one embodiment of the invention, one or more smart sensors may be connected to the drilling control network via a Power over Ethernet network.

[00268] In one or more embodiments of the invention, the drilling control network (2430) may comprise a communication bus (eg, communication bus (2439)). For example, the communication bus (2439) may include hardware, such as network components, wires, optical fibers, etc., that may connect one or more network elements in the drilling control network (2430). Similarly, the communication bus (2439) may contain software, such as one or more communication protocols, that contain the functionality to transfer sensor data between devices, such as a sensor smart device X (2420) and various control systems in the control network (2430). drilling. In addition, the drilling control network (2430) may comprise various network elements (eg, network elements (2431)) and/or user equipment at the wellsite (eg, user equipment (2434) at the wellsite). For example, user equipment at the well site may include a telephone network, personal computers for different users, printers, application servers, and/or file servers located near the drilling rig.

[00269] The drilling control network (2430) may further comprise a network controller (2438). For example, in one or more embodiments of the invention, the network controller (2438) includes software and/or hardware that includes functionality for receiving requests from control systems to subscribe to appropriate sensor devices. Similarly, the network controller (2438) may implement one or more communication protocols to communicate sensor data throughout the drilling control network (2430). For example, the network controller (2438) may be a software-defined network (SDN) controller implemented on multiple network elements in the drilling control network (2430).

[00270] Although in FIG. 24 illustrates various component configurations, other configurations may be used without departing from the scope of the present invention. For example, various components according to FIG. 24 can be combined to create one component. As another example, functions performed by one component may be performed by two or more components.

[00271] Returning to FIG. 25 in FIG. 25 illustrates a block diagram in accordance with one or more embodiments of the invention. In particular, in FIG. 25 illustrates a method for transmitting sensor data. One or more steps in FIG. 25 may be implemented by one or more components (eg, sensor smart device X (2420)), as illustrated in FIG. 1, 2 and/or 24. While the various steps in FIG. 25 are illustrated and described sequentially, it will be apparent to those skilled in the art that some or all of the steps may be performed in different order, may be combined or omitted, and that some or all of the steps may be performed in parallel. In addition, steps can be performed actively or passively.

[00272] At 2500, a network connection is established between the sensor device and the drilling control network, in accordance with one or more embodiments of the invention. For example, the sensor device may form a network connection, such as an Ethernet connection, to a drilling control network. The network connection may be authenticated with a password and/or other identification information from the sensor device. For example, in one or more embodiments of the invention, the sensor device has "ready to use" functionality, wherein the sensor device can communicate directly with various network elements and/or control systems in the drilling control network. In addition, the sensor device may be similar to the smart sensor device X (2420) shown in FIG. 24 and in the accompanying description. In one or more embodiments of the invention, the sensor device is connected to the drilling control network without a middle layer, such as a middle layer computer, interworking between the sensor device and the drilling control network. In one embodiment of the invention, a drilling control network may use middleware communication software, such as a publisher and receiver, to exchange data between various network nodes. An example of middleware communication software is a distributed data service (DDS). The smart sensor can support this communication middleware so that the information it contains can be easily transferred to other network nodes when connected to the drilling control network.

[00273] At 2510, one or more sensor measurements are generated by a sensor system in accordance with one or more embodiments of the invention. In particular, the sensor device may use the sensor system to detect one or more environmental conditions, such as temperature, pressure, torque, etc., in the vicinity of the sensor device. The sensor measurements may be digital and/or analog readings obtained by the sensor device.

[00274] At 2520, one or more sensor measurements are processed by one or more pre-stored algorithms to obtain sensor data, in accordance with one or more embodiments of the invention. For example, in one or more embodiments of the invention, the sensor device converts sensor measurements (eg, mA or electrical voltage) into sensor data (eg, lbf or psi). In particular, sensor measurements and/or sensor data may be converted into a predetermined communication protocol format for transmission over a drilling control network. For example, a pre-stored algorithm may correspond to different blocks of data in a particular type of network packet. In one or more embodiments of the invention, one or more PLC functionality (eg, data calculation and/or data transmission) is integrated into the sensor device. Thus, sensor data processing can be implemented at the sensor level to enable integration with the drilling control network.

[00275] In addition, the sensor device may insert other information along with the sensor measurements into the sensor data. For example, the sensor data may contain publisher information such as hardware identification information regarding the sensor device, source addresses, etc. In one or more embodiments of the invention, for example, the sensor device may insert information that the communication protocol uses to identify subscribers. , such as tags, metadata, content attributes, and other data.

[00276] In one or more embodiments of the invention, the previously stored algorithm is an equation with multiple variables. For example, a pre-stored algorithm may receive multiple inputs for one or more variables to generate sensor data. The sensor measurements at step 2510 may be one input to the previously stored algorithm, while other inputs may correspond to other parameters. For example, a pre-stored algorithm may be a pressure equation, with force and surface area as input in the pressure equation. The sensor system may receive force measurements while the surface area may be static and/or dynamic input to the pressure equation. These static and/or dynamic inputs may be pre-configured on the sensor device before it computes and transmits sensor data to the drilling control network. For example, a user may remotely log into the sensor device via the drilling control network and update the surface area value in the equation. The sensor data may be the output of a pressure equation using the updated surface area and the current force value detected by the sensor system.

[00277] To calculate the fluid volume, the sensor device may measure the height of the fluid level in the reservoir, while the dimensions of the reservoir may be static values set before operation. The sensor data to be transmitted to the drilling control network may include, among other things, both fluid volume and fluid level. Similarly, the sensor device may receive sensor measurements with respect to temperature from a sensor system on the sensor device or from an external sensor device connected to the drilling control network. Similarly, a relevant value for volume calculation, such as reservoir dimensions, may be data values stored on the sensor device that may be updated when reservoir dimensions change, such as when a different mud reservoir is used in the drilling system.

[00278] At 2530, sensor data is transmitted over the drilling control network via one or more communication protocols, in accordance with one or more embodiments of the invention. For example, using a communication interface, a sensor device may communicate sensor data to one or more control systems, one or more sensor devices, and/or one or more network elements in a drilling control network. In some embodiments, the sensor data includes sensor device identification information, sensor quality information, and/or sensor device configuration information. For example, the communication protocol may allow a sensor device to send sensor data over IP multicast to various control systems and network elements in the drilling control network. Thus, the communication protocol can allow various devices such as sensor devices and software applications running on network elements to operate in a ready-to-use mode. For example, in one or more embodiments of the invention, the communication protocols include a Distributed Data Service (DDS) communication protocol.

[00279] Referring to FIG. 26.1 and 26.2, in Fig. Figures 26.1 and 26.2 show an example of transmitting sensor data over a drilling control network. The following example is provided solely for the purpose of illustrating and not limiting the scope of the disclosed technology.

[00280] Referring to FIG. 26.1, in fig. 26.1 illustrates a sensor arrangement Y (2621) with a network connection to the drilling control network A (2630). As illustrated in FIG. 26.1, there is a communication path X (2681) over drilling control network A (24630) between sensor device Y (2621) and PLC A (2661). In particular, the sensor device Y (2621) transmits sensor data Y (2616) to programmable logic controller A (2661), wherein the sensor data Y (2616) can be used for one or more applications performed by programmable logic controller A (2661) and/ or a midrange computer (2640) that is connected to programmable logic controller A (2661). Thus, sensor device Y (2621) can communicate directly with programmable logic controller A (2661) or any other network elements such as a midrange computer (2640) connected to drilling control network A (2630).

[00281] Referring to FIG. 26.1, PLC A (2661) may process the sensor measurements received from the sensor device X (2614) and output them to the middle-level computer (2640) in an acceptable format other than the sensor data communication protocol Y (2616) format. Without the mid-level computer (2640), sensor measurements from sensor device X (2614) cannot be transmitted over the drilling control network (2630) in a recognizable communication protocol format for use by other network devices, such as sensor device Y (2621). Conversely, the sensor device Y (2621) can convert the sensor measurements into a communication protocol format that can be interpreted by any device having a network connection to the drilling control network A (2630).

[00282] Referring to FIG. 26.2, in fig. 26.2 illustrates a control system X (2635) that receives sensor data from a sensor device M (2622) and a sensor device N (2623). In particular, the sensor data M (2617) can be transmitted from the sensor device M (2622) to the control system X (2635) via the communication path I (2682). Similarly, sensor data N (2618) may be transmitted from sensor device N (2623) to control system X (2635) over communication path J (2683). As illustrated in FIG. 26.1 and 26.2, the communication paths (2681, 2682, 2683) may be logical paths passing through various network nodes on the drilling control network A (2630). For example, communication paths (2681, 2682, 2683) may contain the same and/or different network elements, a common communication bus, and/or varying network topology between sensor devices (2622, 2623) and control system X (2635).

[00283] Returning to FIG. 27 in FIG. 27 illustrates a block diagram in accordance with one or more embodiments of the invention. In particular, in FIG. 27 illustrates a method for transmitting sensor data. One or more steps in FIG. 27 may be performed by one or more components (eg, a drilling control network (2430)), as illustrated in FIG. 1, 2, 24, 26.1 and/or 26.2. While the various steps in FIG. 27 are illustrated and described sequentially, it will be apparent to those skilled in the art that some or all of the steps may be performed in different order, may be combined or omitted, and some or all of the steps may be performed in parallel. In addition, steps can be performed actively or passively.

[00284] At 2700, a network connection is established between one or more sensor devices and a drilling control network, in accordance with one or more embodiments of the invention. Step 2700 may be similar to step 2500 shown above in FIG. 25 and in the accompanying description.

[00285] At 2710, one or more requests are received from one or more control systems to subscribe to sensor data, in accordance with one or more embodiments of the invention. For example, via a communication protocol, the control system may request that the control system be identified as a subscriber for a particular sensor device and/or sensor data type in a particular virtual network or domain in the drilling control network. Thus, sensor smart devices publishing data in that particular virtual network or domain can be subscribed to by that management system. However, sensor smart devices published in another virtual network or domain may not be visible to this management system and cannot be subscribed to by this management system.

[00286] At 2720, one or more control systems are designated as sensor data subscribers, in accordance with one or more embodiments of the invention. For example, one or more communication protocols may implement a software architecture that provides a publish-subscribe model among various network elements residing in the drilling control network and/or connected to the drilling control network. If the corresponding control system or component of the corresponding control system is a subscriber for a particular sensor device in a particular virtual network or domain, sensor data from the sensor device can be transferred to the corresponding control system or the corresponding control system component, respectively. If the sensor device has five subscribers, for example, sensor data from the sensor device may be transmitted to each of the five subscribers each time the sensor data is broadcast over the drilling control network. Thus, the sensor device can act as a publisher in a publish-subscribe model. In some embodiments, the drilling control network uses a security certificate to authenticate a device before it is allowed to publish or sign on the network.

[00287] In addition, when assigning a control system as a subscriber, the communication protocol may implement a topic-based system and/or a content-based system. In a topic-based system, sensor data is transmitted over the drilling control network through one or more logical channels. In response to a request to become a subscriber, for example, the control system may be assigned to receive sensor data assigned to a particular channel associated with the subscription. Thus, the communication protocol can identify the subscribers of a particular channel according to IP addresses, hardware addresses, and other identification information, and transmit sensor data to the channel subscribers.

[00288] In a content-based system, a subscriber defines one or more content attributes to analyze sensor data. In one or more embodiments of the invention, for example, the content attribute corresponds to a sensor data class. For example, sensor data classes may include various types of sensor data such as temperature data, pressure data, alerts, and so on. In addition, a class may be defined according to a particular piece of equipment, such as a mud pump. Thus, a sensor data class may include any sensor data received in relation to a mud pump. Similarly, the communication protocol, subscriber, and/or other network element may analyze the sensor data to determine if the sensor data matches one or more content attributes. For example, content attributes may be stored in sensor database metadata. Likewise, the content attributes may include time-based attributes, such as data related to sensor measurements that have been acquired over a certain period of time. In another example, content attributes may correspond to various types of sensor data such as pressure data, temperature data, torque data, etc. Content attributes may also indicate a specific type of equipment on a drilling rig, such as sensor data related to a mud pump. For example, in one or more embodiments of the invention, a maintenance management system subscribes to temperature data near a drilling rig. Thus, the maintenance management system can receive any sensor data that relates to temperature data.

[00289] At 2725, one or more sensor devices and/or one or more control systems are authenticated as a publisher and/or subscriber in accordance with one or more embodiments of the invention. In some embodiments of the invention, for example, in a drilling control network, various security procedures and/or security protocols may be provided that ensure that only trusted and authenticated participants (for example, , publishers and/or subscribers). In addition, sensor devices and/or control systems may receive security certificates that identify the respective device as a publisher and/or subscriber in the drilling control network. For example, a security certificate may be a digital key that authorizes a sensor device and/or control system to communicate over a virtual network to other authorized sensor devices and/or control systems. In some embodiments, a network controller in a drilling control network may act as a network broker in the process of adding to and/or desubscribing various sensor data types and/or issuing security certificates to various devices. In some embodiments of the invention, the control system may send a request to unsubscribe from a particular sensor data type and/or sensor device.

[00290] At 2730, sensor data is obtained from one or more sensor devices, in accordance with one or more embodiments of the invention. For example, a drilling control network may receive sensor data over a network connection to a sensor device.

[00291] At 2740, a control system is selected in the drilling control network, in accordance with one or more embodiments of the invention. For example, the control system may be selected by a communication protocol running on the network, or by a network controller to administer the communication protocol.

[00292] At 2750, it is determined if the control system is a sensor data subscriber, in accordance with one or more embodiments of the invention. For example, the communication protocol may iteratively select control systems associated with a particular type of sensor data and/or sensor device. In some embodiments, the sensor data subscription corresponds to a virtual network in the drilling control network. Thus, a communication protocol running on the drilling control network can parse various security certificates stored in the control system to determine if the control system or sensor device has the appropriate security certificate to access the virtual network. If the management system has a subscriber security certificate, the management system can receive sensor data over the virtual network. Similarly, if a sensor device has a publisher security certificate, the sensor device can communicate to other devices in the virtual network.

[00293] For example, using the sensor data in step 2730, the drilling control network can select a control system that is a subscriber to the sensor data. Similarly, at steps 2740 and 2750, different control systems may be selected to determine if the corresponding control system is a sensor data subscriber. When the control system is determined to be a subscriber, the process may proceed to block 2760. When it is determined that the control system is not a subscriber, the process may return to block 2780.

[00294] At 2760, sensor data is transmitted to a control system in accordance with one or more embodiments of the invention. For example, sensor data may be transmitted in a manner similar to that set forth above in connection with block 2530 and in the accompanying description. In addition, sensor data may be directed to one or more components in the control system. For example, a control system may contain several PLCs. Thus, for example, two PLCs in the control system can use the sensor data, while a third PLC in the control system can ignore the sensor data. Similarly, although the control system may be a publisher or a subscriber, or both, one or more components, such as individual PLCs, may also be publishers and/or subscribers in a drilling control network.

[00295] At 2770, one or more drilling operations are performed on the control system using sensor data, in accordance with one or more embodiments of the invention. For example, sensor data may be used in one or more drilling operations and/or maintenance operations on a drilling rig. By communicating directly with the sensor device, various sensor operations can be performed on the sensor device and/or in connection with the sensor device. For example, other drilling equipment in the drilling control network may be calibrated with sensor data received from the sensor device.

[00296] In addition, by obtaining sensor data directly from the sensor device, the productive life and downtime of the drilling rig can be reduced. For example, if a system that contains a sensor device, a mid-range computer, and a programmable logic controller experiences a hardware or software failure, it may be necessary to independently verify the failure among the system components. On the other hand, when the sensor data identifies a hardware or software failure, diagnosis can be made of said failure in the sensor device generating the sensor data. For example, a network controller or a remote user may analyze the sensor to determine if the sensor system meets one or more specified criteria or not. In response to the analysis of sensor data, for example, various settings in the sensor device can be adjusted to correct the failure and meet predetermined criteria. Thus, obtaining sensor data directly from the sensor device can reduce non-productive time resulting from sensor device failure. Other possibilities may also exist, such as preventive maintenance of the sensor device.

[00297] For example, in some embodiments, the subscriber management system automatically reconfigures the publisher's sensor device in response to analysis of sensor data received from the publisher's sensor device. The predetermined criterion may be an error interval for sensor measurements obtained by the sensor system in the publisher's sensor device. By analyzing the published sensor data, the subscriber management system can detect an offset error using the sensor system. Thus, the control system may connect directly to the publisher's sensor device over the drilling control network to automatically adjust one or more of the publisher's sensor device settings so that sensor measurements from the sensor device satisfy an error margin.

[00298] At step 2780, it is determined if another subscriber exists in the drilling control network, in accordance with one or more embodiments of the invention. When it is determined that the sensor data has not been sent to one or more subscribers, the process may proceed to block 2740. When it is determined that there are no more subscribers for the sensor data, the process may end.

[00299] In addition, in one or more embodiments of the invention, the processes described above in FIG. 25 and 27 can provide sensor data transmission and transmission without the use of a programmable logic controller. For example, in a oriented system, various logical channels may need to be installed, configured, and maintained throughout the drilling process to transfer data, such as from a sensor device to a software application. Thus, the maintenance of such an oriented system can increase costs. In particular, whether the costs include adding network elements, removing or replacing a network element, the associated costs can grow exponentially. Thus, the processes illustrated in FIG. 25 and 27 may allow the sensor devices and/or the drilling control network to decentralize the transmission of sensor data.

[00300] While in FIG. 24, 25, 26.2 and/or 27 above illustrate various control systems in connection with the disclosed technology, in some embodiments of the invention, the various processes described above may also be applied to data acquisition systems, performance monitoring system and/or interpretation software systems. data. For example, the same sensor data from a sensor smart device may be transmitted to a control system, an operation monitoring system, a data acquisition system, and a data interpretation software system.

Commissioning of intelligent drilling control system

[00301] In general, embodiments of the invention include a system and various methods for generating and/or using a rig control system knowledge graph. In one or more embodiments of the invention, the knowledge graph includes nodes corresponding to components of the rig control system and links connecting the nodes to represent interactions between respective pairs of components. In one or more embodiments of the invention, each link represents at least a predetermined data transmission and resource utilization characteristic of a respective pair of components.

[00302] In one or more embodiments of the invention, the drilling rig control system has a hierarchical structure and includes a first hierarchical level and a second hierarchical level. The first hierarchical level contains the subsystems and hardware components (eg, drilling equipment and auxiliary tools), while the second hierarchical level contains the software components installed in each of the subsystems. In one or more embodiments of the invention, each subsystem with installed software components is associated with some aspect of the drilling operation and is used to control a portion of the hardware components dedicated to a particular aspect of the drilling operation.

[00303] In one or more embodiments of the invention, the knowledge graph comprises a general rig control system knowledge graph and a number of subsystem knowledge graphs. The general knowledge graph of the drilling rig control system corresponds to the first hierarchical level, and the knowledge graphs of the subsystem correspond to the second hierarchical level. In one or more embodiments of the invention, a knowledge graph is created by applying machine learning algorithms to a drilling rig control system during a normal drilling operation. In one or more embodiments of the invention, a knowledge graph is used as a standard for performing control tasks of a drilling rig control system. In one or more embodiments of the invention, a knowledge graph is used to assist in the commissioning of a drilling rig, in particular in the commissioning of a drilling rig control system. As used herein, the term "commissioning" refers to bringing the drilling rig into operation, which may be performed at any time before or during operation of the drilling rig, and may be performed once or periodically throughout the operation of the drilling rig.

[00304] FIG. 28 is a block diagram of a system in accordance with one or more embodiments of the invention. In one or more embodiments of the present invention, one or more of the elements illustrated in FIG. 28 may be omitted, repeated and/or replaced. Accordingly, embodiments of the invention should not be construed as being limited to the particular module arrangements illustrated in FIG. 28.

[00305] As illustrated in FIG. 28, the rig control system (2800) is connected to a human machine interface (HMI) (2820) that allows the user to control the operation of the drilling system described above with reference to FIG. 1. The human-machine interface may be hardware and/or software associated with the rig control system (2800) and which contains functionality for presenting data and/or receiving user input regarding various drilling and/or operations. maintenance performed within the drilling rig control system (2800). For example, the human-machine interface may include software for providing a graphical user interface (GUI) for presenting data and/or receiving control commands for operating a drilling rig.

[00306] In one or more embodiments, the drilling rig control system (2800) comprises multiple subsystems (e.g., subsystem A (2801a), subsystem B (2801b)) and hardware components (e.g., hardware component A (2802a), hardware component B (2802b), hardware component C (2802c). The hardware components may include drilling equipment and other tools associated with the drilling rig (12), as described above with reference to FIG. 1. For example, hardware component A (2802a) may correspond to a mud circulation subsystem, hardware component B (2802b) may correspond to a rotating subsystem, and hardware component C (2802c) may correspond to a network element. A network element may include physical devices on the network such as switches, routers, hubs, or any other logical entities for establishing communication connections between subsystems and other hardware components.

[00307] Subsystems (e.g. subsystem A (2801a), subsystem B (2801b)) may comprise, for example, programmable logic controllers (PLCs) having hardware and/or software with functionality to control one or more processes running drilling rig (12), including, but not limited to, the components shown in FIG. 1. In particular, the PLC may be a computer system with increased resistance to adverse environmental conditions with functional means to withstand vibrations, extreme temperatures, wet environmental conditions and/or dusty environmental conditions, for example, near a drilling rig (12). In particular, the PLC may control valve states, fluid levels, pipe pressures, alarms and/or depressurizations throughout the rig (12) and the associated hardware component A (2802a), hardware component B (2802b), etc. e. Thus, one or more components of the rig control system (2800) may include functionality for monitoring and/or performing various drilling operations in relation to a mud circulation system, a rotary system, a pipe supply system, and/or other various drilling operations, described above with reference to FIG. 1. In one or more embodiments of the invention, subsystems (e.g., subsystem A (2801a), subsystem B (2801b)) and hardware components (e.g., hardware component A (2802a), hardware component B (2802ba), component C (2802c) hardware) are collectively referred to as the components of the first hierarchical level, forming the first hierarchical level in the rig control system (2800). Accordingly, the underlying hardware and/or software elements of each first hierarchical level component are collectively referred to as the second hierarchical level components constituting the second hierarchical level in the drilling rig control system (2800). In this context, the rig control system (2800) comprises a hierarchical structure of components.

[00308] In one or more embodiments of the invention, the components of the drilling rig control system (2800) are communicatively connected to and controlled by the drilling rig commissioning system (2810), which is a computing system configured to perform one or more tasks of the system (2800 ) drilling rig control. In one or more embodiments of the invention, the drilling rig commissioning system (2810) provides a single commissioning (or other control tasks) of all components in the drilling rig control system (2800) through a single HMI (2820). In other words, the use of the rig commissioning system (2810) reduces the complexity of multiple separate commissioning of each component in the rig control system (2800) by multiple disintegrated HMIs.

[00309] In one or more embodiments, the control tasks include a software commissioning task, a network commissioning task, a diagnostics task, etc. In one or more embodiments, the drilling rig commissioning system (2810) creates a knowledge graph that describes the normal operation of the rig control system (2800). The knowledge graph has a hierarchical structure corresponding to the hierarchical structure of the components of the drilling rig control system (2800). In one or more embodiments of the invention, the rig commissioning system (2810) uses machine learning algorithms to create a knowledge graph during normal operation of the rig control system (2800). Machine learning algorithms may be based on one or more of the methods of stochastic, numerical and statistical analysis. In one or more embodiments of the invention, the knowledge graph is used to perform diagnostic tasks during abnormal operation of the drilling rig control system (2800). In one or more embodiments of the invention, the knowledge graph of the rig control system (2800) is used to perform software and network commissioning tasks to configure a new rig control system separate from the rig control system (2800) on which the system (2810) is learning. ) Commissioning of the drilling rig. For example, a new drilling rig control system commissioned by the drilling rig commissioning system (2810) may be used to control another drilling rig separate from the drilling rig (12) controlled by the drilling rig control system (2800).

[00310] In one or more embodiments of the invention, the rig commissioning system (2810) performs the various functions described above using the method described below with reference to FIG. 29. An example of a knowledge graph is described below with reference to FIG. 31-32. In one or more embodiments of the invention, the drilling rig commissioning system (2810), the human-machine interface (2820), and various components of the drilling rig control system (2800) may be a computing system similar to the computing system (3400) described with reference to in fig. 34.1 and 34.2. In one or more embodiments of the invention, the rig commissioning system (2810) is separate from and communicates with the rig control system (2800). In one or more embodiments of the invention, the rig commissioning system (2810) and the rig control system (2800) are combined into a single system.

[00311] FIG. 29 illustrates a block diagram in accordance with one or more embodiments of the invention. In one or more embodiments of the invention, the method may be based on the systems illustrated above in FIG. 1, 2 and 28. One or more of the steps illustrated in FIG. 29 may be omitted, repeated, and/or performed in a different order in various embodiments of the invention. Accordingly, embodiments of the invention should not be construed as being limited to the specific number and order of the steps illustrated in FIG. 29.

[00312] In one or more embodiments of the invention, the block diagram illustrated in FIG. 29 uses a drilling rig commissioning system to commission a drilling rig control system or otherwise control said system. Initially, at step 2900, components of the drilling rig control system are located at the well site. In one or more embodiments of the invention, the components are discovered when the individual subsystems and hardware components are powered up and in operation, that is, they begin to communicate over the network. The operational components must be commissioned and communicatively connected to each other before being used to control the drilling operation at the newly developed well site.

[00313] In one or more embodiments of the invention, the components are detected in response to an alert during a drilling operation at an established well site. The alert may indicate an abnormal operation or other event/emergency detected by the rig control system or by the user supervising the drilling operation. The alert may include a request, provided automatically or by a user categorizing the alert, to the rig commissioning system to perform diagnostics on the rig control system at the installed well site.

[00314] In step 2910, a knowledge graph is obtained. In one or more embodiments of the invention, the knowledge graph is created by the drilling rig commissioning system during the machine learning preparation period when the normal drilling operation is performed by the drilling rig control system at the installed well site. One or more stochastic, numerical, and statistical analysis methods may be used during the training period through machine learning. In one or more embodiments of the invention, the knowledge graph is created using the method described below with reference to FIG. 29.

[00315] In one or more embodiments of the invention, the statistical information stored in the nodes and links of the knowledge graph represents predetermined targets/references for the computing operations of the respective subsystems and/or data transfer operations between each pair of components of the drilling rig control system. For example, a predetermined score may include mean, median, mode, correlation, ranking, score, category, and/or other statistics. In other words, the statistical information stored in the nodes and links of the knowledge graph may correspond to the mean, median, mode, ranking, score, etc. of the use of computing resources and/or communication actions of the corresponding pair of components. In addition, the statistical information may also include a correlation between the use of computing resources and the communication activities of the respective pair of components.

[00316] In one or more embodiments of the invention, the links also contain ranking information, which is calculated based on various types of artificial intelligence (AI, artificial intelligence) depending on the conditions of the drilling rig, operational factors, stages of operation and overall system availability. For example, the target value represented by a particular relationship may be low, a particular relationship may rank higher than other relationships in the knowledge graph due to the production need for a particular relationship. In one or more embodiments of the invention, the production requirement for each node/link is determined based on one or more rig operating conditions, operating factors, operating stages, and overall system availability. An example of ranking node/link calculation during rig operation is described below with reference to FIG. 33.

[00317] In one or more embodiments of the invention, the knowledge graph is input to the drilling rig commissioning system as a target operating condition for commissioning a newly developed drilling site or drilling rig. In one or more embodiments of the invention, the knowledge graph is provided to the rig commissioning system as a reference standard for diagnosing potential problems at the installed well site or rig.

[00318] In step 2920, a rig control system control task is performed based on the knowledge graph by the rig commissioning system. In one or more embodiments of the invention, a software commissioning task is performed based on a knowledge graph. For example, a software commissioning task may include one or more of the following: software installation, software to service connection, software to software connection, license check, user and network port configuration check. In one or more embodiments of the invention, the software commissioning task refers to software installed in subsystems of a drilling rig control system at a newly developed well site or drilling rig. For example, a software commissioning task may be performed on a software component at a second hierarchical level of a drilling rig control system.

[00319] In one or more embodiments of the invention, installing the software includes one or more tasks of checking the software version, checking the type or model of hardware, checking the functionality of the hard drive, checking the memory capacity of the computer, checking the operating system version, checking the firmware version , firewall installation and configuration checks, network bandwidth and throughput checks, and other system settings checks. In one or more embodiments of the invention, one of these validation tasks corresponds to nodes in the knowledge graph that are connected, for example, through links to a software application. These associations represent the requirements for the software application to carry out the process properly. If any of these nodes are missing, the software application may not work properly. At this point, the commissioning system may determine that the system is not compliant and the application cannot run.

[00320] In one or more embodiments of the invention, a data connection between a pair of rig control system components is established based on a knowledge graph. For example, a data connection may be established between a pair of components at a first hierarchical level and/or a second hierarchical level of a drilling rig control system at a newly developed well site or drilling rig.

[00321] In one or more embodiments of the invention, the task of diagnosing a drilling rig control system is performed based on a knowledge graph. In particular, during an ongoing drilling operation at an established drilling site, a setpoint of computational operations and/or data exchange between a pair of drilling rig control system components is generated. For example, the predetermined metric may correspond to communication between a pair of components at a first hierarchical level and/or a second hierarchical level of a drilling rig control system. The setpoint is compared with the corresponding target setpoint of the component pair stored in the knowledge graph to generate a result. For example, the result may indicate the difference between a setpoint obtained during the current drilling operation and a corresponding target setpoint obtained during a previous conventional drilling operation, such as in a machine learning preparation step. In other words, the difference represents the deviation of the current drilling operation from the previous conventional drilling operation. For example, a deviation may be due to an outdated software component, software license expiration, software configuration error, etc. Accordingly, a diagnostic task is performed by analyzing the difference to determine the root cause of the deviation and determine the applicable corrective action.

[00322] FIG. 30 illustrates a block diagram in accordance with one or more embodiments of the invention. In one or more embodiments of the invention, the method may be based on the systems illustrated above in FIG. 1, 2 and 28. One or more of the steps illustrated in FIG. 30 may be omitted, repeated, and/or performed in a different order in various embodiments of the invention. Accordingly, embodiments of the invention should not be construed as being limited to the specific number and order of the steps illustrated in FIG. thirty.

[00323] In one or more embodiments of the invention, the block diagram illustrated in FIG. 30 is used in the preparation phase through machine learning to generate a knowledge graph of the rig control system during a drilling operation. Each iteration of the flowchart is performed as the individual subsystems and hardware components are powered up and operational, that is, they begin to communicate over the network. Live components are discovered through multiple iterations of the block diagram to create and extend the knowledge graph of the rig control system.

[00324] Initially, in step 3001, the rig control system is scanned to detect any subsystem or hardware component that is operational, that is, communicating over the network. In one or more embodiments of the invention, scanning is performed by a rig commissioning system using network communication protocols. In one or more embodiments of the invention, the rig commissioning system includes an artificial intelligence (AI) module that controls all processes running on computers that are part of the drilling control system. When a new process (such as an application, services, script, etc.) is launched on any of the computers, the new module is detected by the AI module. Once a new process is discovered, a dependency tree is created as a knowledge graph. For example, as described below in connection with steps 3002-3012, the AI module may determine all necessary software components such as DLLs, configuration files, database, network ports, network connections, etc. that are required by the process. Because multiple processes or services or scripts are running on the computer(s), the AI module calculates the importance of each software component against operational data. Operational data is provided during the training phase, when the system is trained to detect various operational information. In the case of drilling operations, most of the operational steps are already defined. Given that these production steps are repeated during the drilling operation, the AI module can use the knowledge that a certain production step is in progress and apply numerical algorithms to determine or recalculate the importance of certain software components (or nodes). Since the start time of the next operational phase is not determined, stochastic ranking calculation methods can be applied. Depending on the upcoming operational phase, the ranking of nodes and boundaries changes depending on the importance of each node and boundary. In other words, the rankings change depending on the importance of nodes and boundaries for certain stages of drilling operations. For example, while drilling, certain applications must be running and available to drill the well. The rank of these applications is high before and during this operational phase. There are also less important system components. To calculate the rank of these components, you can apply a statistical or probabilistic approach.

[00325] In step 3002, it is determined if a subsystem or hardware component has been detected. If the determination is negative, the method returns to block 3001 to continue scanning. If the determination is positive, the method proceeds to step 3003 where the detected component is classified, for example, as one of a plurality of first hierarchical level components and second hierarchical level components of the rig control system. At block 404, it is determined if the detected bean class is valid. If the determination fails, the detected component is discarded and the method returns to block 3001 to continue scanning. If the determination is positive, the method proceeds to block 3005 where another determination is made as to whether the already discovered component is included in the knowledge graph. If the determination is positive, the method returns to block 3001 to continue scanning. If the determination fails, the method proceeds to block 3006 where the score and rank of the detected component is calculated.

[00326] In one or more embodiments of the invention, the score is a specified measure of computational operations of the detected component. In one or more embodiments of the invention, a score is a predetermined measure of communication activities between a discovered component and another component in the knowledge graph. Once a score is computed, it is compared with the scores of the other components in the knowledge graph to obtain the rank of the newly discovered component. The method then proceeds to block 3007 where another determination is made as to whether the discovered component can be connected to the knowledge graph. If the determination fails, the method proceeds to block 3008, where the discovered component is placed as an idle node in the knowledge graph, before the method returns to block 3001 to continue scanning. If the determination is positive, the method proceeds to step 3009, where the detected component is connected to other node(s) in the knowledge graph to expand the knowledge graph.

[00327] The method then proceeds to block 3010, which determines if the graph needs to be adjusted, for example, if a newly discovered component can connect to a previously discovered idle node. If the determination is positive, the method proceeds to block 3013 to traverse the knowledge graph and idle nodes. At a subsequent step 3007, one or more idle nodes are identified that can connect due to the newly discovered component. If the determination at block 3010 fails, the execution of the method proceeds to block 3012, where it is determined whether the training has been completed by machine learning. For example, the determination may be performed using a machine learning algorithm. If the determination fails, the method returns to block 3001 to enter the next iteration. If the determination gives a positive result, the execution of the method ends and the knowledge graph is saved. In one or more embodiments of the invention, the stored knowledge graph is subsequently used by the rig commissioning system to perform the control task of the rig control system.

[00328] FIG. 31-33 illustrate examples in accordance with one or more embodiments of the invention. In one or more embodiments of the invention, the examples may be based on the systems illustrated above in FIG. 1, 2 and 28 and/or the flow diagrams of the method illustrated above in FIGS. 29-30. In one or more embodiments of the invention, one or more of the elements illustrated in FIG. 31-33 may be omitted, repeated and/or replaced. Accordingly, embodiments of the invention should not be construed as being limited to the particular module arrangements illustrated in FIG. 31-33.

[00329] In the example illustrated in FIG. 31-33, there are many subsystems that make up a rig control system. There is a drilling control subsystem that controls the machines for drilling the well. There is a drilling fluid subsystem that mixes the drilling fluid which is pumped downhole by the pumping subsystem. There is a cementing subsystem that mixes and pumps cement. In addition to the aforementioned key drilling subsystems, there are many other subsystems, such as the rig's generator power system, that coexist to form the overall rig control system. Each of these subsystems performs specific functions, using heavy machinery and sophisticated control systems to safely drill oil and gas wells. Often there is minimal integration between these subsystems, mainly because these subsystems are meant to be used standalone. Different vendors may produce these subsystems, and so far there has been very little collaborative effort to ensure the smooth integration of these subsystems. The level of integration between different subsystems depends on the degree of cooperation between the various subsystem vendors. In the case where these subsystems are applied at a rig site, one or more rig commissioning engineers physically interconnect these subsystems to configure the entire rig control system. Due to the vast number of types and configurations of rig subsystems, commissioning engineers must have extensive knowledge and experience with many types of rig subsystems in order to perform rig commissioning tasks. The job of integrating heterogeneous rig subsystems is often complex, time-consuming and error-prone.

[00330] As noted above, an intelligent drilling rig commissioning system is used to automatically commission drilling rig control systems. The rig subsystem is brought online when all mechanical connections, equipment installation, electrical wiring, and any other physical connections have been made. When the subsystem is brought into operation, the computer devices are brought into action. At this stage, the intelligent rig commissioning system takes over and performs all the software commissioning tasks required by the subsystem to perform all of its functions. As part of software commissioning tasks, the intelligent commissioning system performs software installation, license verification, user verification, network port configuration, and any other actions necessary for the proper functioning of the subsystem management system. The intelligent commissioning system performs these actions based on the knowledge graph of the rig subsystem. The subsystem knowledge graph contains all the information necessary for the intelligent system to validate and validate the software installation and configuration at the subsystem level.

[00331] FIG. 31 illustrates an exemplary subsystem knowledge graph (3100) corresponding to subsystem A (2801a) illustrated above in FIG. 28. On the knowledge graph (3100) of the subsystem, the nodes are indicated in the form of cubes, and the connections are in the form of double arrows. Each node and each link is assigned a score representing a given measure of computational work and/or communication activity in connection with the node/link. For example, AppA (3100a) corresponds to an application software that is installed in subsystem A (2801a) and assigned a score of 0.97, with nodes labeled AppB and AppC corresponding to additional application software components that are respectively assigned scores of 0. .90 and 0.89. These scores indicate that AppA (3100a) is more computationally intensive than AppB, which in turn is more computationally intensive than AppC. In another example, ServicesG (3100b) corresponds to operating system software service G in subsystem A (2801a), with additional nodes designated ServicesH, ServicesJ, ServicesK, ServicesL, and ServicesP corresponding to software services H, J, K, L, and P, respectively. In addition, the firewall (3100c) corresponds to the firewall software in subsystem A (2801a). Similarly, the nodes labeled PortX and PortY correspond to the communications network ports in subsystem A (2801a). In addition, the nodes labeled IPAddress2 and IPAddress3 correspond to network nodes with specific IP address 2 and IP address 3. Note that the links between AppA (3100a) and ServicesH, ServicesL and PortX are respectively assigned scores of 0.69 , 0.69 and 0.89. These scores indicate that AppA (3100a) is communicating with ServicesH and ServicesL with similar performance/frequency, which have a lower score (i.e. less active or less frequent) than the communication activities between AppA (3100a) and PortX. The scores assigned to all nodes and links in the knowledge graph (3100) of the subsystem are aggregated into a total score (3100d), which is a target score (i.e. 0.99) of the aggregated internal computing/communication activities within subsystem A ( 2801a) during a drilling operation. For example, the overall score (3100d) could be a weighted average of the scores assigned to all nodes and links. In another example, the overall score (3100d) may be calculated using a different statistical formula based on the scores assigned to all nodes and links.

[00332] In the exemplary scenario, subsystem A (2801a) is a stand-alone computer such as a laptop or computer server that contains the aforementioned software applications, software services, firewall, communication network ports, network nodes, etc. Graph The subsystem knowledge (3100) also contains a commissioning rule (3101) that defines installation, connection, communication, and port configuration rules regarding the application software ApplA (3100a).

[00333] Upon completion of the commissioning of each subsystem, the intelligent commissioning system automatically detects and performs further software configuration to ensure that all subsystems in the rig control system interact with each other. In addition, the intelligent commissioning system scans and tests for compatibility with any equipment that is part of the rig equipment, and ensures that the equipment control software is present and properly configured. When discrepancies are found, the intelligent commissioning system connects to the cloud and downloads any missing software components or software configuration components required to fully install and properly configure the software for a given rig control system installation. The intelligent commissioning system performs these actions based on the overall knowledge graph of the rig control system. In one or more embodiments of the invention, the intelligent commissioning system also stores the type of drilling rig as part of a knowledge graph, such as a type mapping and knowledge graph database that can be used later to commission new drilling rigs of the same type.

[00334] FIG. 32 illustrates an exemplary general rig control system knowledge graph (3200) corresponding to the rig control system (2800) illustrated above in FIG. 28. On the general graph (3200) of knowledge of the drilling rig control system, the nodes are indicated in the form of cubes, and the links are in the form of double arrows. Each node and each link is assigned a score representing a given measure of computational work and/or communication activity in connection with the node/link. For example, the node labeled SubsystemX corresponds to the subsystem knowledge graph (3100) illustrated above in FIG. 31, with the nodes labeled SubsystemY and SubsystemZ corresponding to additional subsystem knowledge graphs that are respectively assigned overall scores of 0.89 and 0.99. Although the subsystem knowledge graph (3100) corresponds to subsystem A (2801a) illustrated above in FIG. 28, SubsystemY and SubsystemZ may correspond to other subsystems illustrated above in FIG. 28. For example, SubsystemY may correspond to subsystem B (2801b). SubsystemX (ie, 0.99) and SubsystemY (ie, 0.89) scores indicate that subsystem A (2801a) performs more intensive aggregate internal computing/communication work than subsystem B (2801b).

[00335] In another example, the nodes labeled EquipmentX, EquipmentY, EquipmentZ, Tool1, Tool2, and Tool3 correspond to the drilling equipment and other tools illustrated above in FIG. 1, with each separately assigned score representing statistics on the use of the respective equipment/tool during a drilling operation. In addition, the nodes labeled ConnectionA, ConnectionB, and ConnectionC correspond to network elements in the rig control system. The nodes labeled AppAA and AppBB correspond to the cloud-based software applications available to the various subsystems and hardware components in the rig control system. It should be noted that the links of SubsystemX with EquipmentX, ApplicationBB and Tool3 are assigned quantitative indicators of 0.09, 0.25 and 0.88, respectively. These scores indicate that SubsystemX rarely contacts HardwareX, relatively rarely contacts AppBB, and frequently communicates with Tool3.

[00336] Without using a common rig control system knowledge graph (3200), each subsystem of the rig control system is commissioned separately by a team of specialists who collaborate with other groups with different experience in commissioning the entire rig control system. The problem lies in the vast amount of information that few commissioning engineers master before they can effectively and efficiently perform all software commissioning tasks. There is a competition between rig commissioning engineers mastering the training material to perform their tasks, and the continuous development of the subsystems of each rig. The subsystems of each rig continue to evolve as new methods and technologies are introduced. As improvements and new technologies are introduced, rig commissioning engineers are trained. It has become difficult for lead rig commissioning engineers to absorb the amount of information needed for training in a reasonable amount of time. As a result, the knowledge gap continues to widen as new technologies are introduced into the subsystems of each drilling rig. With the overall rig control system knowledge graph (3200) described above, one team of engineers has enough experience to fully commission the entire rig control system without involving multiple subsystem teams.

[00337] FIG. 33 illustrates an example of performing a ranking on a rig sequence (3320) that includes steps (3321)-(3326) and additional steps that are not explicitly illustrated. In particular, the same operation step ABC is performed at different times during operation (3321) and operation (3324), the same operation step X is performed at different times during operation (3322) and operation (3326), technical equipment maintenance is performed during operation (3325) and operation (3323) represents downtime due to the drilling operation. In the example illustrated in FIG. 33, during each of the operations of the rig operation sequence (3320), AI algorithms are used to determine the rank of items in the knowledge graph such as Node ABC, Equipment Maintenance Application, and Operation X. As described above, the rank is determined based on one or more rig operating conditions, operational factors, operational milestones and overall system availability. In particular, since each operation is performed in the drilling rig sequence (3320) illustrated in FIG. 33, the rank of Node ABC changes as follows: 0.99999, 0.352, 0.8599, 0.90012, 0.0012, 0.00102, and so on. putting the drilling rig into operation continuously brings the drilling rig into operation, which may occur at any time before or during the drilling operation, and may occur once or periodically during the entire drilling operation.

Configuration Manager and Coordinated Controller

[00338] In some embodiments, the operations network comprises a configuration manager, which may be hardware and/or software built and running on one or more processing systems, such as one or more network appliances. The configuration manager may be a program implemented by a software program written and compiled in a high-level programming language such as C/C++ or the like. As described in more detail below, the configuration manager is configured to convert communication from various communication protocols to a common protocol. communication and creating a communication converted to a common communication protocol accessible via a common data bus, and vice versa. The common data bus may comprise an application program interface (API) of the configuration manager and/or a common data virtual network (VN-DATA) implemented in one or more processing systems such as network appliances such as switches. .

[00339] The configuration manager may have predefined classes for objects to implement the link transformation. Created objects in the configuration manager for subsystems can be used to support communication with subsystems according to the respective (and possibly different) communication protocols implemented by the subsystems, and to convert the communication to a common protocol that is available on a common data bus, and vice versa. Classes can define objects at the subsystem level (for example, drilling control system, mud circulation system, cementing system, etc.), equipment level (for example, top drive, drawworks, mud pump, etc.), and /or data level (eg command type, sensor data and/or status data). Therefore, an object can be created for each instance of a subsystem, equipment, and/or data type, depending on how the object class has been defined. In addition, classes may define objects based on communication protocols to be implemented by subsystems. Hypothetically, assuming that two subsystems are identical except that each implements a different communication protocol, the configuration manager can instantiate objects for subsystems from different classes that have been defined based on different communication protocols. Objects can be created when setting up a network of operations and/or by dynamically discovering one or more equipment controllers (EC, equipment controller) and/or subsystems.

[00340] As will become clear from the description below, the use of a configuration manager can provide, for example, easier deployment of subsystems in a well construction system and associated communications equipment. The use of software compiled in a high-level language can ensure that an updated version of the configuration manager is deployed when an additional, previously undefined subsystem is deployed, which can facilitate the deployment of physical components associated with the configuration manager (for example, when adding equipment/subsystems to a well construction system). In addition, applications that access data from the configuration manager (for example, via a shared data bus) can be updated by updating the software when new data becomes available by adding a new subsystem, so that the updated application can use the data generated by the new subsystem. .

[00341] One or more operations network processing systems, such as one or more switches and/or other network appliances, are configured to implement one or more subsystem virtual networks (e.g., VLANs), such as a first subsystem first virtual network (VN- S1), the second subsystem virtual network (VN-S2), and the Nth subsystem virtual network (VN-SN). More or fewer virtual networks of subsystems can be implemented. Subsystem virtual networks (for example, VN-S1, VN-S2, and VN-SN) are logically separated from each other. Subsystem virtual networks can be implemented in accordance with the IEEE 802.1Q standard, another standard, or your own implementation. Each subsystem virtual network can communicate with the corresponding subsystem EC based on various protocols such as Ethernet based network protocol (e.g. ProfiNET, OPC, OPC/UA, Modbus TCP/IP, EtherCAT, UDP multicast, Siemens S7 communication, etc. .p.), proprietary communication protocol, and/or another communication protocol. In addition, subsystem virtual networks can implement a publish-subscribe relationship. Subsystem virtual networks can implement the same protocol, each subsystem virtual network can implement a different protocol or a combination of protocols.

[00342] In addition, processing systems that process data to manage various subsystems may have resources dedicated to such processing. For example, one or more processing systems running a coordinated controller, one or more processing systems running a configuration manager, one or more processing systems that are configured to implement virtual networks, and/or other processing systems may have resources dedicated to processing and transmitting commands and/or sensor and/or status data used to determine the appropriate commands to issue. With this allocation of resources, the processes in the well construction system can be controlled in real time. Other messages and processing may be transmitted/performed in non-real time without using dedicated resources.

[00343] The coordinated controller may also implement a logic portion to control the operations of the well construction system. The coordinated controller may monitor various states of the components and/or sensors and may issue commands to the various ECs to control the operation of the controlled components in one or more subsystems. The sensor data and/or status data may be controlled by the co-ordinated controller via a common data bus, and the co-ordinated controller may issue commands to one or more ECs via the respective EC subsystem virtual network.

[00344] The coordinated controller may implement logic to generate commands based on the work plan from one or more process applications and to issue these commands to one or more ECs in one or more subsystems. One or more process applications may communicate a generic command to a coordinated controller, such as through a common data bus. The generic command may include the intended overall operation (eg, drilling a reservoir) and certain parameter constraints that may affect the operation. For example, certain constraints on a drilling operation may include the required rate of penetration (ROP) function associated with top power drive RPM and weight on bit (WOB) . The co-ordinated controller can interpret the generic command and translate it into special commands (which can be interpreted by the respective ECs), which are then passed to the EC to control the various managed components.

[00345] In addition, the coordinated controller may monitor the status of various equipment and/or sensor data to optimize the operation of subsystem equipment based on the status and/or sensor data that is transmitted on the feedback channel. By feedback and monitoring of the well construction environment data, the coordinated controller can continuously update the commands in response to the changing environment. For example, if the ROP is greater or less than planned, the coordinated controller may make calculations and issue commands to increase or decrease one or both of the following: top power drive RPM and WOB.

[00346] Likewise, one or more process applications may monitor status and/or sensor data available via a common data bus to track the progress of an operation and/or update the work plan depending on the changing environment. If the operation is proceeding as planned, eg, subject to various constraints, then the process applications may not update the work plan and may allow operations to continue based on the work plan being implemented. If an operation does not proceed as planned, as may be indicated by the state and/or sensor data, the process applications may modify the work plan and pass the modified work plan to the coordinated controller for implementation.

[00347] The method may include developing a work plan, for example, by one or more process applications. The work plan may be developed based on geological and/or geophysical data measured or estimated to describe the target formation(s) of the well, and/or one or more geological, geophysical and/or engineering databases. The developed work plan may include details related to the well trajectory, drilling fluid to be used during drilling, casing design, drill bits, BHA components, etc.

[00348] The method may include implementing the work plan, for example, by a coordinated controller, as described above. Implementation of the work plan may include operating (and/or maintaining) the well construction system to form the well in accordance with the developed work plan. Details of the operation (eg WOB, top drive RPM, mud flow rate, etc.) can be determined during the development and/or implementation of the work plan.

[00349] The method also includes monitoring status and/or sensor data, such as by one or more process applications and a coordinated controller, as operations progress. The method also includes determining whether to update the work plan implementation method based on the monitored status and/or sensor data. The coordinated controller can make such a determination. The determination may be based on one or more indications of (or derived from) monitored status and/or sensor data indicating that operations are deviating from the planned progress of the work plan and/or that, in the light of new data, the original implementation of the work plan was in error. . If it is determined that the implementation method will not be updated, operations continue while monitoring the state and/or sensor data, for example by a coordinated controller. If it is determined that the implementation method will be updated, the existing implementation of the work plan is updated based on the monitored status and/or sensor data, for example, by a coordinated controller. It then continues monitoring (406) the status and/or data of the sensor and operation.

[00350] The method also includes determining whether the work plan should be updated based on the monitored status and/or sensor data. One or more process applications may make the specified determination. The determination may be based on one or more indications of (or derived from) monitored status and/or sensor data indicating that operations are deviating from the expected performance of the work plan and/or that, in light of new data, the originally developed work plan was erroneous. If it is determined that the work plan will not be updated, operations continue while monitoring status and/or sensor data, for example, through one or more process applications. If it is determined that the work plan will be updated, the work plan is updated (based on the monitored status and/or sensor data) and implemented by, for example, one or more process applications. It then continues to monitor the status and/or data of the sensor and operation. The method may continue until the original or updated work plan is completed.

[00351] A work plan may require a lot of computation to develop and therefore may be developed over a longer period of time, which may not be real-time for operations. The coordinated controller (e.g., one or more processing systems on which the coordinated controller operates) may have resources (e.g., processing resources) dedicated to control various systems that allow such control to be performed in real time (e.g., for a known, determinable period of time). In addition, the implementation method can be updated using simpler processes that can allow real-time updates to be implemented. Real-time updates can provide streamlined management of work plan operations.

[00352] The coordinated controller may control the issuance of EC commands generated in response to an influencing entity outside the virtual networks of the respective EC subsystems. Thus, for example, an HMI may issue a command to one or more ECs in a subsystem via a common data bus under the control of a coordinated controller and via the virtual network of that subsystem's subsystem. For example, the user can enter commands through the HMI to control the operation of the subsystem. Commands for an EC subsystem issued by an influencing entity outside that subsystem may be prohibited in the operations network without a coordinated controller processing the command. The coordinated controller may implement a logic part to determine if a given influencing entity (eg, HMI and/or process applications) can cause a command to be issued to a given EC in the subsystem.

[00353] The coordinated controller may implement a logic part to make decisions on commands that will control the operation of a particular equipment or subsystem, for example, when there are several influencing objects (for example, work plans and / or HMI) trying to cause the issuance of commands at the same time to the same equipment or subsystem. The co-ordinated controller may implement a conflict resolver (eg, a logic part) to determine which of the conflicting commands from the HMI and/or work plans to issue to the EC. For example, if the first work plan attempts to issue a command issued by EC-SN-1 to increase the pumping rate of a pump, and the second work plan simultaneously tries to issue a command to EC-SN-1 to decrease the pumping rate of the same pump, the co-ordinated controller's contention resolver can resolve the conflict and determine which command is allowed to be issued. Further, as an example, if two HMIs issue conflicting commands at the same time, the coordinated controller can determine which command to inhibit and which command to issue.

[00354] The contention resolver of the coordinated controller may use a hybrid first-come-first-served and prioritization scheme in operation. For example, the first command issued is allowed to continue until the process terminates, or until the influencing entity that caused the command to be issued terminates the execution of the command. In some examples, a single stand-alone work plan, which must run on its own without executing another work plan, can advantageously be implemented without creating conflicting commands. However, a work plan can refer to another work plan, which can result in conflicting teams. For example, a work plan for a cementing process may refer to a work plan for a drilling process to operate a pump, and by executing a work plan for a cementing process that references a work plan for a drilling process, several conflicting commands may be generated for the pump with implementation of both work plans. The conflict resolver processes these commands by allowing the execution of the first command generated by one of the work plans, or until the creation of the work plan terminates the first command, even if the second subsequent and conflicting command is created by another work plan. The second command is queued until the first command completes or is terminated by the work plan that created it, and then the conflict resolver allows the second command to be issued and executed.

[00355] Some influencing entities in the operations network may be assigned a priority that allows these influencing entities to interrupt operations and/or commands regardless of the current state of the process. For example, the HMI may be assigned a high priority that allows a command from the HMI to abort an operation and/or command in progress. A command from an HMI can be executed, regardless of the current state of the process, until the command is completed or terminated by the HMI that sent it. After the command from the HMI has been executed, the process may return to its previous state or restart based on new conditions upon which the work plan and/or work plan implementation is based.

[00356] Another method may include receiving one or more commands created by one or more influencing objects that do not have priority. For example, the conflict resolver may receive one or more commands created based on one or more work plans, which may not have priority. The method includes issuing the earliest received, not issued command. For example, the conflict resolver can effectively queue commands from non-priority influencing entities, and the first command received from the non-priority influencing entity is the first command issued by the conflict resolver. The method includes executing the issued command until the command is executed or terminated by the issuing impactor. The execution of an issued command may be a discrete, fast-acting function of the equipment, a function performed by the equipment for a specified period of time, a function performed by the equipment until certain conditions are satisfied (which may be specified by the sending impactor), and/or other generic means. execution. The method then returns to issuing the earliest command received, not issued. During issuance and execution, commands may still be received from one or more non-priority influencing entities, with these commands being queued for issuance. Therefore, receiving, issuing, and executing can implement a first-in-first-out queue.

[00357] At the time of receiving, issuing, and executing, the method includes receiving a command from a priority influencing entity. Receiving a command from a priority influencing entity interrupts the flow of receiving, issuing, and executing commands from non-priority influencing entities, and therefore a command from a priority influencing entity takes precedence over commands from non-priority influencing entities. An example of priority influencing objects could be an HMI or other means. The method includes issuing a command received from a priority influencing entity and executing the issued command until the command is completed or terminated by the sending influencing entity. The execution of an issued command may be a discrete, fast-acting function of the equipment, a function performed by the equipment for a specified period of time, a function performed by the equipment until certain conditions are satisfied (which may be specified by the sending impactor), and/or other generic means. execution.

[00358] In various cases, after executing a command received from a priority influencing object, the execution of the method may resume. For example, after implementation, execution of the method may resume when receiving a command from a priority influencing entity interrupts the flow of receiving, issuing, and executing one or more commands received from one or more non-priority influencing entities. In addition, the execution of a command received from a priority influencing entity may change wellsite conditions to such an extent that non-priority influencing entities will withdraw previously sent commands and begin sending commands updated in response to conditions that have changed as a result of the execution of a command from the influencing entity. the priority of the influencing object. Thus, the execution of the method may resume upon receipt of one or more commands from one or more non-priority influencing entities, regardless of whether the command was received from the priority influencing entity.

[00359] In some embodiments of another exemplary method, the conflict resolver receives and issues commands, which commands may come from another logical part of the coordinated controller that implements one or more work plans received from one or more process applications. The conflict resolver may determine what commands the coordinated controller should issue to one or more ECs, and the EC may execute the commands, for example, by controlling various equipment of the well construction system at the well site. In other examples, other components and/or processing systems may implement different operations.

[00360] For more information on configuration managers and coordinated controllers, see U.S. Patent Application No. 15/621,180 entitled "Well Construction Communication and Control" filed June 13, 2017 and U.S. Patent Application No. 15/361,759 , entitled "Well Construction Communication and Control", which was filed November 28, 2016, both of which are hereby incorporated by reference in their entirety.

Computing system

[00361] Embodiments of the invention may be implemented in a computing system. Any combination of mobile, desktop, server, routing, switching, embedded devices, or other types of hardware may be used. For example, as shown in FIG. 34.1, the computing system (3400) may include one or more computer processors (3402), non-persistent storage (3404) (e.g., volatile storage such as random access memory (RAM), cache), read-only memory (3406 ) (for example, a hard disk drive, an optical disc drive such as a compact disc (CD) drive or a digital versatile disc (DVD) drive, flash memory, etc.), a communication interface (3412) (for example, Bluetooth interface, infrared interface, network interface, optical interface, etc.) and many other items and functions.

[00362] The computer processor(s) (3402) may be an integrated circuit for processing instructions. For example, the computer processor(s) may be one or more processor cores or microcores. The computing system (3400) may also include one or more devices (3410), such as a touch screen, keyboard, mouse, microphone, touch pad, electronic pen, or any other type of input device.

[00363] The communication interface (3412) may comprise an integrated circuit for connecting a computing system (3400) to a network (not shown) (e.g., a local area network (LAN), a wide area network (WAN) such as the Internet, a mobile communications network, or other type of network) and/or to another device such as another computing device.

[00364] In addition, the computing system (3400) may include one or more output devices (3408) such as a screen (e.g., liquid crystal (LCD) display, plasma display, touch screen, cathode ray tube (CRT) monitor, projector or other display device), printer, external storage device, or any other output device. One or more output devices may be the same or different from the output device(s). The input and output device(s) may be locally or remotely connected to the computer processor(s) (3402), non-persistent storage (3404), and persistent storage (3406). There are many types of computing systems, and the aforementioned input and output device(s) may take other forms.

[00365] Program instructions in the form of computer-readable program code for carrying out embodiments of the invention may be stored, in whole or in part, temporarily or permanently, on a volatile computer-readable medium such as a CD, DVD, external storage device, floppy disk, tape, flash memory , physical memory, or any other machine-readable storage medium. In particular, the program instructions may correspond to computer-readable program code that, when executed by the processor(s), is configured to implement one or more embodiments of the invention.

[00366] Computing system (3400) in FIG. 34.1 can be connected to a network or be part of a network. For example, as illustrated in FIG. 34.2, the network (3420) may contain multiple nodes (eg, node X (3422), node Y (3424)). Each node may correspond to a computing system, such as the computing system illustrated in FIG. 34.1, or the combined group of nodes may correspond to the computing system illustrated in FIG. 34.1. As an example, embodiments of the invention may be implemented on a distributed system node that connects to other nodes. As another example, embodiments of the invention may be implemented on a distributed computing system comprising a plurality of nodes, where each part of the invention may be located on a different node on the distributed computing system. In addition, one or more elements of the above computing system (3400) may be located at a remote location and connected to other elements via a network.

[00367] Although not illustrated in FIG. 34.2, a node may correspond to a board in a server chassis that connects to other nodes via a backplane. As another example, a node may correspond to a server in a data center. As another example, a node may correspond to a computer processor or microkernel of a computer processor with memory and/or resource sharing.

[00368] Nodes (eg, node X (3422), node Y (3424)) in the network (3420) may be configured to provide services to the client device (3426). For example, the nodes may be part of a cloud computing system. The nodes may contain functionality for receiving requests from the client device (3426) and transmitting responses to the client device (3426). The client device (3426) may be a computing system such as the computing system illustrated in FIG. 34.1. In addition, the client device (3426) may comprise and/or implement all or part of one or more embodiments of the invention.

[00369] The computing system or group of computing systems shown in FIG. 34.1 and 34.2 may contain functionality to perform many of the operations described in this application. For example, the computing system(s) may communicate between processes on the same or different systems. A variety of mechanisms using some form of active or passive communication can facilitate communication between processes on the same device. Examples relevant to these inter-process communications include, but are not limited to, the implementation of a file, signal, socket, message queue, pipeline, semaphore, shared memory, message passing, and memory-mapped file. Additional details relating to a couple of these non-limiting examples are given below.

[00370] Based on the client-server model of networking, sockets can serve as interfaces or endpoints of communication channels that provide bidirectional communication between processes on the same device. First of all, based on the client-server networking model, a server process (eg, a process that provides data) can create the first socket object. Next, the server process assembles the first socket object, thereby associating the first socket object with a unique name and/or address. After creating and matching the first socket object, the server process then waits and listens for incoming connection requests from one or more client processes (eg, processes that request data). At this point, when the client process seeks to receive data from the server process, the client process starts creating a second socket object. The client process then proceeds to generate a connection request that contains at least a second socket object and a unique name and/or address associated with the first socket object. The client process then passes the connection request to the server process. Depending on availability, the server process may accept a connection request, establish a communication channel with a client process, or a server process busy processing other operations may buffer the connection request queue until the server process is ready. The established connection informs the client process that communications can begin. In response, the client process may generate a data request specifying the data the client process seeks to obtain. The data request is serially passed to the server process. Upon receiving a request for data, the server process parses the request and collects the requested data. Finally, the server process generates a response containing at least the requested data and sends the response to the client process. Data may be transmitted, most commonly, as datagrams or a stream of characters (eg, bytes).

[00371] Shared memory refers to the allocation of virtual memory space to implement a mechanism for which data can be transferred and/or accessed by multiple processes. When implementing shared memory, the initialization process first creates a shared segment in persistent or non-persistent storage. Once created, the initialization process then mounts the shared segment, subsequently mapping the shared segment to the address space associated with the initialization process. Once mounted, the initialization process proceeds to identify and grant access to one or more authorized processes that can also write and read data to and from the shared segment. Changes made to data in a shared segment by one process can immediately affect other processes that are also associated with the shared segment. In addition, when one of the authorized processes accesses a shared segment, the shared segment is mapped to the address space of the authorized process. Often, a single authorized process can mount a shared segment, unrelated to the initialization process, at any given time.

[00372] Other algorithms may be used to share data between processes, such as the various data described in this application, without departing from the scope of this invention. The processes may be part of the same or a different application and may run on the same or a different computing system.

[00373] Instead of or in addition to sharing data between processes, a computing system implementing one or more embodiments of the invention may include functionality for receiving data from a user. For example, in one or more embodiments of the invention, a user may present data via a graphical user interface (GUI) on the user's device. Data may be presented via a graphical user interface by a user selecting one or more window interface elements or inserting text and other data into a GUI window interface element using a touch screen, keyboard, mouse, or any other input device. In response to selecting a particular element, information relating to the particular element may be obtained from the ROM or non-persistent storage device by the computer processor. After the user selects an item, the received data content related to the specific item can be displayed on the user's device in response to the user's selection.

[00374] As another example, a request for data relating to a particular item may be sent to a server operably linked to the user's device via a network. For example, a user may select a uniform resource locator (URL) reference in the user's device web client, thereby initiating a Hypertext Transfer Protocol (HTTP) or other protocol request to be sent to the host associated with the URL. In response to the request, the server may extract data related to the particular selected item and send the data to the device initiating the request. After the user's device has received data related to a particular item, the content of the received data related to the particular item may be displayed on the user's device in response to the user's selection. In addition to the above example, the data received from the server after the URL is selected can represent a Hyper Text Markup Language (HTML) web page that can be rendered by a web client and displayed on a user's device.

[00375] After receiving data, for example, using the algorithms described above or from a storage device, the computing system, in carrying out one or more embodiments of the invention, may extract one or more data elements from the received data. For example, extraction may be performed as described below by computer system (3400) in FIG. 34.1. First, an ordering scheme (eg, grammar, schema, format) of the data is determined, which may be based on one or more of the following: position (eg, bit or column position, Nth token in the data stream, etc.), attribute (where an attribute is associated with one or more values) or a hierarchical/tree structure (consisting of layers of nodes at different levels of detail, such as in nested package headers or nested document sections). The raw stream of data characters is then broken up in the context of an collation into a stream (or tiered structure) of tokens (where each token may have an associated token "type").

[00376] Further, extraction criteria are used to extract one or more data items from the token stream or structure, where the extraction criteria are processed in accordance with an ordering scheme to extract one or more tokens (or nodes from the layered structure). For position-based data, the token(s) are retrieved at the position(s) specified by the extraction criteria. For attribute/value-based data, the token(s) and/or node(s) associated with the attribute(s) that satisfy the extraction criteria are retrieved. For hierarchical/multilevel data, the token(s) associated with the node(s) that match the extraction criteria are retrieved. The retrieval criteria can be as simple as an identifier string or can be a query submitted to a structured data store (where the data store can be organized according to a database schema or data format such as XML).

[00377] The extracted data can be used for further processing by the computing system. For example, the computing system in FIG. 34.1, when implementing one or more embodiments of the invention, may perform a data comparison. Data comparison can be used to compare two or more data values (eg A, B). For example, one or more embodiments of the invention may determine whether A > B, A=B, A != B, A < B, etc. The comparison may be performed by passing A, B, and an opcode specifying the operation, associated with the comparison into an arithmetic logic unit (ALU) (i.e., a circuit that performs arithmetic and/or bitwise logical operations on two data values). The ALU outputs the numeric result of the operation and/or one or more status flags associated with the numeric result. For example, the status flags may indicate whether the numeric result is a positive number, a negative number, zero, etc. By selecting the correct opcode and then reading the numeric results and/or the status flags, a comparison can be made. For example, to determine if A > B, B can be subtracted from A (i.e., A - B), and status flags can be read to determine if the result is positive (i.e., if A > B, then A - B > 0). In one or more embodiments of the invention, B may be considered a threshold, and A is considered to satisfy the threshold if A=B or if A > B, as determined using the ALU. In one or more embodiments, A and B may be vectors, and comparing A to B includes comparing the first element of vector A with the first element of vector B, the second element of vector A with the second element of vector B, and so on. In one or more embodiments, implementation of the invention, if A and B are strings, the binary values of the strings can be compared.

[00378] The computing system illustrated in FIG. 34.1 may implement a data repository and/or connect to a data repository. For example, one type of data store is a database. The database is a collection of information designed to facilitate the search, modification, reorganization and deletion of data. A database management system (DBMS) is a software application that provides an interface for users to define, create, query, update, or administer databases.

[00379] The user or software application may submit an operator or query to the DBMS. The DBMS then interprets the statement. The statement can be a select statement for querying information, an update statement, a create statement, a delete statement, etc. In addition, the statement can contain parameters that define data, or a data container (database, table, record, column, view, etc.). etc.), identifier(s), conditions (comparison operators), functions (eg, union, full union, count, average, etc.), sorting (eg, ascending, descending), or others. The DBMS can be executed by the operator. For example, a DBMS may access a memory buffer, refer to, or index a file for reading, writing, deleting, or any combination of these in order to respond to a statement. The DBMS can load data from persistent or non-persistent storage and perform calculations to answer the query. The DBMS may return result(s) to the user or software application.

[00380] The computing system illustrated in FIG. 34.1 may contain functionality for representing raw and/or processed data, such as the results of comparisons and other processing. For example, the presentation of data may be performed using various presentation methods. In particular, the data may be presented using a user interface provided on the computing device. The user interface may include a GUI that displays information on a display device such as a computer monitor or touch screen on a handheld computing device. A GUI can contain various GUI elements that organize what data will be displayed as well as how the data is presented to the user. In addition, the GUI may present data directly to the user, such as data presented as actual data values in the form of text, or rendered by a computing device into a visual representation of the data, such as by rendering a data model.

[00381] For example, the GUI may first receive a notification from a software application requesting that a particular data object be presented to the GUI. The GUI can then determine the data object type associated with a particular data object, for example by getting data from a data attribute in the data object that identifies the data object type. The GUI can then define any rules intended to represent that data object type, such as rules defined by the environment for the data object class, or according to any local options defined by the GUI to represent that data object type. Finally, the GUI can receive data values from a particular data object and visually present the data values on a display device according to the assigned rules for that type of data object.

[00382] The data can also be represented using various sound reproduction methods. In particular, the data may be played back in audio format and presented as sound via one or more speakers operatively associated with the computing device.

[00383] Data may also be presented to the user through tactile presentation techniques. For example, tactile presentation methods may include: vibrations or other physical signals generated by a computing system. For example, data may be presented to a user using a vibration generated by a handheld computer device with a predetermined duration and vibration intensity for data transmission.

[00384] The above description of functions represents only a few examples of functions performed by the computing system illustrated in FIG. 34.1 as well as the nodes and/or client device illustrated in FIG. 34.2. Other functions may be performed using one or more embodiments of the invention.

[00385] Although the invention has been described in relation to a limited number of embodiments, it will be apparent to those skilled in the art taking advantage of this invention that other embodiments may be devised that do not depart from the scope of the invention described in this application. Accordingly, the scope of the invention is to be limited only by the appended claims.

Claims (55)

1. The system of interaction between the drilling control network and the user network, containing: a first control system connected to a plurality of network elements forming a drilling control network, the first control system comprising one or more programmable logic controllers (PLCs) that perform drilling operations; a virtualization service manager connected to the first control system and a plurality of network elements, the virtualization services manager implementing at least one virtualization service in the drilling control network that controls the drilling operation; a virtual connection controller connected to a plurality of network elements, the virtual connection controller establishing a virtual connection between the first control system and the user network; and a shutdown manager connected to the virtualization service manager, a plurality of network elements and the first management system, wherein the shutdown manager completes the operations of the first control system and the virtualization services manager in accordance with the shutdown sequence for the drilling control network. 2. The system according to claim 1, further comprising a set of virtual machines operating in the drilling control network and which are formed by the virtualization services manager, wherein a plurality of virtual machines perform a plurality of automated drilling operations, and wherein the shutdown manager communicates with the plurality of virtual machines to complete operations in accordance with the shutdown sequence. 3. The system according to claim 2, characterized in that the shutdown manager sends a plurality of shutdown commands with a time delay to the first management system, the plurality of virtual machines, and the virtualization service manager, and wherein the plurality of time delay shutdown instructions implement the shutdown sequence. 4. The system according to claim 1, characterized in that the virtual connection corresponds to a temporary channel between the first security zone and the second security zone, wherein the first security zone contains the first control system, and and the second security zone is located in the user network. 5. The system of claim. 4, further comprising a firewall connected to the first control system and a plurality of network elements, wherein the drilling control network reconfigures, in response to checking the network device, the first security zone to allow the network device to communicate with a destination device in the second security zone. 6. The system according to claim 1, further comprising a configuration manager connected to the plurality of network elements and the first control system, wherein the configuration manager detects and installs the software update on the first control system. 7. The system according to claim 6, further comprising security agent located in the first control system, wherein the configuration manager communicates with the security agent to install the software update on the first control system. 8. The system according to claim 6, further comprising: a coordinated controller connected to the virtualization services manager; and a plurality of control systems connected to a virtualization service manager and a coordinated controller, wherein the coordinated controller determines the prioritization of the plurality of maintenance operations for the plurality of control systems. 9. The system according to claim 1, further comprising: a plurality of persistent storage devices; a data management controller connected to a plurality of persistent storage devices and a first management system, wherein the data control controller receives data from the remote device through a network connection to the drilling control network, and wherein the data management controller stores data in the persistent data storage device among the plurality of persistent data storage devices associated with the predetermined data type. 10. The system according to claim 1, further comprising a sensor device connected to the first control system and a plurality of network elements, wherein the sensor device establishes a network connection with the first control system over the drilling control network, and wherein the sensor device transmits, using a communication protocol, sensor data from the sensor device to the first control system. 11. The system according to claim 1, further comprising: a second control system; a drilling rig commissioning system connected to the first control system, the second control system and a plurality of network elements, wherein the drilling rig commissioning system creates a drilling control network knowledge graph, and wherein the drilling rig commissioning system commissions the second control system to automatically perform the control task using the knowledge graph. 12. The system of interaction between the drilling control network and the user network, containing: a control system connected to the first plurality of network elements that forms a first security zone in the drilling control network, the control system comprising one or more programmable logic controllers (PLCs) that perform drilling operations; a virtualization service manager connected to the control system and the first plurality of network elements, the virtualization services manager implementing at least one virtualization service in the drilling control network that controls the drilling operation; and a firewall connected to the first security zone and the second security zone containing the second plurality of network elements, wherein one or more unidirectional channels, one or more bidirectional channels and/or one or more temporary channels connect the first and second security zones, moreover, the drilling control network reconfigures, in response to checking the network device, the first security zone, to allow the network device to communicate with the destination device in the second security zone, in accordance with one or more network communication protocols associated with one or more channels. 13. The system according to claim 12, further comprising virtual connection controller located in the second security zone, wherein the virtual connection controller establishes a virtual connection between the first security zone and the second security zone. 14. The system according to claim 12, further comprising a shutdown manager connected to the virtualization service manager, the first plurality of network elements and the first management system, wherein the shutdown manager terminates the operations of the first management system and the virtualization services manager in accordance with the plurality of shutdown commands with a time delay.

Images