CN108600357A - A kind of foster management system of oil and gas equipment dimension and working method based on SOA - Google Patents

Abstract

The invention relates to an SOA-based oil and gas equipment maintenance management system and working method. The system includes Internet of Things application components, SOA middleware and equipment. The equipment is divided into traditional equipment and DPWS equipment. The SOA middleware includes business service layer, service Management layer, device service layer, information extraction module and event collaboration interaction module. The present invention serves the function of the Internet of Things terminal equipment through the SOA middleware based on SOA, and shields heterogeneous technical details. Device service dynamic discovery and service lifecycle management functions are designed for SOA middleware to adapt to the dynamic characteristics of IoT terminals. Complex business service functions are realized through service composition. At the same time, an event-driven service collaboration mechanism is added to the basic SOA structure, which improves the collaborative perception ability of each service unit of the Internet of Things. In this way, the SOA-based oil and gas equipment maintenance management system and the working method of the system are realized, which are applied to the informatization and intelligence of oil and gas production equipment maintenance.

Description

A SOA-based oil and gas equipment maintenance management system and working method

technical field

This application relates to the technical field of using the Internet of Things to serve oilfields, and in particular to an SOA-based oil and gas equipment maintenance management system and working method.

Background technique

Smart oilfield is the need of oilfield informatization construction and the future of oilfield development. Oilfield enterprises are highly technology-intensive industries. At this stage, Internet of Things technology represented by high-intensity computing and massive information storage has been gradually applied to oil and gas development and production processes, and has become the mainstream direction of smart oilfield construction at home and abroad. However, in the whole process of oil and gas production, such as oil field and transportation management, all links are closely interdependent and relatively independent, and the information and intelligent construction of equipment and control in each production link has also achieved preliminary results. However, how to ensure that the oil and gas production equipment in each link The scientific rationalization of normal work and maintenance management has become a new problem in the construction of smart oilfields.

The oilfield Internet of Things takes oilfield sites such as seismic areas, well sites, and station depots as data collection sources. Through collection equipment and various communication transmission methods, massive data such as seismic data, downhole measured formation and wellbore data, and wellhead measurement data are collected in real time. Acquisition and storage, on this basis, knowledge integration through a large number of business models, through intelligent identification, data fusion, mobile computing, cloud computing and other technologies, support scientific research and online simulation of petroleum geology and reservoir analysis, and then support oilfield production comprehensive decision-making and control.

The construction and healthy development of oilfield Internet of Things needs the support and guarantee of Internet of Things management technology. The Internet of Things has many new characteristics, such as: a large number of access nodes, various network structures, frequent node activation and failure, and rapid network topology changes. These characteristics lead to new requirements for the management of the Internet of Things. The five functions of the traditional network management of the Internet and the Internet have already felt lagging behind and difficult to adapt to in the era of the Internet of Things. In particular, due to the particularity of smart oilfield construction, oilfield Internet of Things management still has some outstanding problems that need to be solved, such as: ① There are many types of oilfield data sources, the amount of information is too large and continues to grow rapidly, and it is necessary to study the corresponding data management, query and a shared management mechanism to avoid waste of storage resources; ②For tasks with a large amount of calculation, such as reservoir numerical simulation and seismic data interpretation, it is necessary to provide corresponding efficient and fast data processing calculation methods; ③Oilfield information involves multi-disciplinary, multi-disciplinary Fields require personnel from different professional and technical fields to work together on the same platform and at the same time to complete the same target task under different technical conditions. Due to the above reasons, IoT management of oilfield equipment is still a new job, so far there are few researches and developments dedicated to IoT management of oilfield equipment.

The Internet of Things includes various types of services, which can be divided into four categories according to their application types and technical characteristics: identity-related services, information aggregation services, collaborative perception services, and ubiquitous services. This IoT service classification represents the inevitable development trend of the continuous enhancement of IoT service functions. ① Identity-related services belong to the basic services of the Internet of Things. Using identification technologies such as automatic radio frequency identification, two-dimensional codes, and barcodes, and through the name resolution services provided by EPCglobal or uID Internet of Things architecture, such services based on identity information can be constructed. ②Information aggregation service is mainly manifested in collecting data through terminal sensors, and then aggregation of information after network transmission for use by upper-level application systems. ③Collaborative sensing service is manifested in the completion of information collaborative processing around the same target task through distributed information collection, communication, calculation and terminal control. This type of service requires intelligent information exchange between IoT terminals, and the ability to complement and comprehensively process perceptual information across systems and platforms. ④ Ubiquitous services are the ultimate services of the Internet of Things, supporting information exchange and services between people and things at any time and place.

Among the above-mentioned types of IoT services, collaborative sensing services play a central role in linking the past and the future, and are the key to realizing comprehensive perception, information sharing, and ultimate ubiquitous services. Internet, NFC (Near Field Communication) and embedded Web server technologies allow us to transform everyday objects into smart objects (Smart Objects) that can understand and interact with their own environment, making it possible to build efficient and real-time collaborative perception services.

my country's oilfield equipment Internet of Things has just started, and the operable and manageable oilfield Internet of Things has not yet formed. It is facing the difficulties of scattered core petroleum business information, lack of intelligent processing mechanisms and means for massive oilfield perception information, and the need for multidisciplinary petroleum engineering and technical personnel. Collaborative service support and many other issues. The current IoT device management system includes the following components: including IoT application components, SOA middleware and devices. The devices are divided into traditional devices and DPWS devices. SOA middleware includes business service layer, service management layer and device service layer There are three levels, and information transmission is passed and fed back in layer order among the three levels.

Collaborative sensing services represent the development trend of the Internet of Things, but the construction method of the Internet of Things that supports collaborative sensing services has not been studied in depth. Most of the existing perception services still stay at the level of information collection and communication, and do not have the functions of computing and terminal control, so they cannot complete information collaborative processing around the same target task. In addition, because the existing sensing services do not have terminal control, intelligent information exchange cannot be carried out between IoT terminals, let alone solve the problems of cross-system and cross-platform realization of complementary and comprehensive processing of sensing information.

Contents of the invention

The purpose of the embodiment of the present application is to provide a SOA-based oil and gas equipment maintenance management system and the working method of the system, so as to realize real-time monitoring, reminder and early warning of the oil and gas production equipment maintenance information of the entire system, and to provide The maintenance service equipment issues maintenance instructions and evaluates the maintenance effect, so as to achieve intelligent monitoring and management of the whole life cycle maintenance of the overall networked oil and gas equipment.

In order to achieve the above purpose, the present invention provides a SOA-based oil and gas equipment maintenance management system, including Internet of Things application components, SOA middleware and equipment, equipment is divided into traditional equipment and DPWS equipment, SOA middleware includes business service layer, The service management layer and the device service layer are special in that they also include an information extraction module and an event collaboration interaction module,

The information extraction module includes a transmission layer, a perception control layer, and a device layer, and provides information collection, transmission, and terminal control functions for the device; the information extraction module passes various types of sensors in the corresponding perception control layer to each parameter of the device Realize the intelligent perception of the device layer, and transmit the collected information to the SOA middleware through the transport layer; at the same time, reversely transmit the data, information or instructions of the computing and Internet of Things application components through the SOA middleware to the perception control layer, And through various intelligent control components of the perception control layer to operate and control the equipment, realize the interactive management and control between the application components of the Internet of Things and the equipment;

The event collaborative interaction module is used to provide DPWS devices and Internet of Things application components to realize cross-layer service interaction and collaborative perception service functions: the event collaborative interaction module is responsible for sending, receiving and processing events throughout each layer of SOA middleware, and this module constitutes an event The driven service coordination mechanism realizes the cross-layer service interaction and cooperative perception service function between DPWS equipment and IoT application components.

In the above-mentioned device service layer, traditional devices interact with SOA middleware, and then interact with DPWS plug-ins in the form of Web services; DPWS devices and SOA middleware directly interact with standard DPWS plug-ins in the form of Web services;

The service management layer includes service dynamic discovery, device monitoring and service lifecycle management components; the service dynamic discovery component uses the DPWS service discovery mechanism WS-Discovery to complete the device service discovery function, and stores all discovered services in a unified device In the service library, WS-Discovery is based on UDP multicast, and the service dynamic discovery component is repeatedly deployed at each local physical site; the device monitoring component is responsible for monitoring and recording the dynamic running status information of each current device service; the service lifecycle management component is responsible for Manage the static device data of all online and offline devices, and update the device service library according to the results of device monitoring and service discovery. After function expansion, service installation and upgrade can be realized; service logs are used for later intelligent analysis;

The business service layer includes a business model library, a business service and DPWS device service library, and a composite service workflow engine component: the business model library is responsible for storing the composite service model established in advance according to business logic and rules; the business service component and the DPWS device service The library is responsible for storing the existing runtime composite service information and DPWS device service information that can be used across layers; the composite service workflow engine runs the composite service process according to the business model, and calls the component service functions involved in the composite service compilation process.

The composite service workflow engine in the above business service layer runs the composite service process according to the business model, and calls the component service functions involved in the composite service preparation process. Since the online status of the Internet of Things terminal device is unstable, the service call proxy component is used to cache service call instructions, so that the combined service process can continue to be executed when the device service is available again.

The device monitoring component in the above service management layer is responsible for monitoring and recording the dynamic running status information of each current device service, while the service life cycle management component is responsible for managing the static device data of all online and offline devices, and according to the results of device monitoring and service discovery. The device service library is updated, and service installation and upgrade can be realized after function expansion.

A working method of the above-mentioned SOA-based oil and gas equipment maintenance management system, comprising the following steps:

1) The information extraction module collects and perceives the preset information of the device through the sensor control layer, and transmits it to the device service agent in the SOA middleware through the transport layer;

2) The traditional device passes the third-party plug-in or gateway/adapter to the DPWS plug-in to complete the information transfer to the device service agent in the SOA middleware;

3) The DPWS device directly transmits the information to the device service agent in the SOA middleware through the DPWS plug-in;

4) SOA middleware abstracts device functions and communication capabilities into device services, forms a service set and builds a service composition environment. The perception layer in the information extraction module contains a large number of heterogeneous perception terminals, with different access methods and functions. same. The device service proxy layer in the SOA middleware hides heterogeneous technical details, processes and external input and output message operations through standard Web service interfaces, and at the same time converts service calls into communication instructions for specific terminals;

5) The components of each layer of SOA middleware responsible for sending, receiving and processing events and their interactions constitute an event-driven service collaboration mechanism, which is an event collaboration interaction module; each information processing unit in the Internet of Things system is not only a provider of perceptual information who, at the same time, are consumers;

6) The event receiver and event subscription agent of the event consumer in the event collaboration interaction module set the event notification interface to adopt the WS-Brokered Notification standard;

7) The event processor of the event producer in the event collaboration interaction module sets the event subscription proxy interface, and the event subscription proxy supports two event distribution modes, Push and Pull. The event notification proxy only sends simple events, and no subscription interface is set;

8) After the event notification agent receives the data from the information extraction module, it submits it to the event processor for processing after being processed by the event receiver;

9) The event subscription agent sends the processed information to the event subscription system. After receiving the information, different subscription systems execute the corresponding next step process or processing.

Compared with prior art, the advantages of the present invention are:

The present invention serves the function of the Internet of Things terminal equipment through the SOA middleware based on SOA, and shields heterogeneous technical details. Device service dynamic discovery and service lifecycle management functions are designed for SOA middleware to adapt to the dynamic characteristics of IoT terminals. Complex business service functions are realized through service composition. At the same time, an event-driven service collaboration mechanism is added to the basic SOA structure, which improves the collaborative perception ability of each service unit of the Internet of Things. In this way, the SOA-based oil and gas equipment maintenance management system and the operation method of the system are realized, which are applied to the informatization and intelligence of oil and gas production equipment maintenance.

Description of drawings

Fig. 1 is a schematic diagram of the structural composition of an SOA-based oil and gas equipment maintenance management system provided by the present application;

Fig. 2 is a schematic structural diagram of an SOA-based oil and gas equipment maintenance management system in practical applications;

Fig. 3 is a schematic flowchart of an embodiment of event processing in an SOA-based oil and gas equipment maintenance management system provided by the present application.

Detailed ways

In order to enable those skilled in the art to better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described The embodiments are only some of the embodiments of the present application, not all of them. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without creative efforts shall fall within the scope of protection of this application. Although the present application provides the operation steps of the method described in the following embodiments or flowcharts, more or fewer operation steps may be included in the method based on routine or no creative effort. In the steps where logically there is no necessary causal relationship, the execution sequence of these steps is not limited to the execution sequence provided in the embodiment of the present application. When the method is executed by an actual device or terminal product, it can be executed sequentially or in parallel according to the methods shown in the embodiments or drawings.

See Figure 1, an SOA-based oil and gas equipment maintenance management system, including IoT application components, SOA middleware and equipment, equipment is divided into traditional equipment and DPWS equipment, SOA middleware includes business service layer, service management layer, equipment Service layer, information extraction module and event collaboration interaction module.

The information extraction module provides information collection, transmission and terminal control functions for the device: including the transmission layer, the perception control layer and the device layer, and the information extraction module realizes the device parameters for each parameter of the device through the relevant various sensors in the corresponding perception control layer. Layer intelligent perception, and transmit the collected information to the SOA middleware through the transport layer; at the same time, reversely transmit the data, information or instructions processed by the SOA middleware to the computing and Internet of Things application components to the perception control layer, and pass All kinds of intelligent control components in the perception control layer operate and control the equipment, and realize the interactive management and control between IoT application components and equipment;

The event collaborative interaction module is used to provide DPWS devices and Internet of Things application components to realize cross-layer service interaction and collaborative perception service functions: the event collaborative interaction module is responsible for sending, receiving and processing events throughout each layer of SOA middleware, and this module constitutes an event The driven service coordination mechanism realizes the cross-layer service interaction and cooperative perception service function between DPWS equipment and IoT application components.

In the device service layer, traditional devices interact with SOA middleware, and then interact with DPWS plug-ins in the form of Web services; DPWS devices and SOA middleware directly interact with standard DPWS plug-ins in the form of Web services.

The service management layer includes service dynamic discovery, device monitoring and service lifecycle management components; the service dynamic discovery component uses the DPWS service discovery mechanism WS-Discovery to complete the device service discovery function, and stores all discovered services in a unified device In the service library, WS-Discovery is based on UDP multicast, and the service dynamic discovery component is repeatedly deployed at each local physical site; the device monitoring component is responsible for monitoring and recording the dynamic running status information of each current device service; the service lifecycle management component is responsible for Manage the static device data of all online and offline devices, and update the device service library according to the results of device monitoring and service discovery. After function expansion, service installation and upgrade can be realized; service logs are used for later intelligent analysis;

The business management layer includes a business model library, a business service and DPWS device service library, and a composite service workflow engine component: the business model library is responsible for storing the composite service model established in advance according to business logic and rules; the business service and DPWS device service library Responsible for storing the existing runtime composition service information and DPWS device service information that can be used across layers; the composition service workflow engine runs the composition service process according to the business model, and makes service calls to the component service functions involved in the composition service compilation process.

The composite service workflow engine in the business service layer runs the composite service process according to the business model, and calls the component service functions involved in the composite service compilation process. Since the online status of the Internet of Things terminal device is unstable, the service call proxy component is used to cache service call instructions, so that the combined service process can continue to be executed when the device service is available again.

The device monitoring component in the service management layer is responsible for monitoring and recording the dynamic running status information of each current device service, while the service life cycle management component is responsible for managing the static device data of all online and offline devices, and according to the results of device monitoring and service discovery The device service library is updated, and the service installation and upgrade can be realized after the function is expanded.

In order to further describe the present invention, the functions and characteristics of each component are described in more detail below:

IoT application components: run on the device terminal, control and manage the terminal, and provide a unified programming interface for operating system software components. Each information processing unit is not only a provider of perceived information, but also a consumer; SOA-based selection It is convenient to hide the details of different technologies through SOA middleware in the Internet of Things system, simplify the development of new services and integrate existing technologies; abstract device functions and communication capabilities into device services, form a service set and build a service composition environment.

SOA middleware: It is divided into three levels: business service layer, service management layer and device service layer.

In the device service layer, the device service agent serves the IoT-aware terminal function and is responsible for interacting with the same layer or upper layer services in the form of Web services. DPWS equipment directly supports Web service standards, and its service proxy can be completed through standard DPWS plug-ins. Traditional devices can complete the service proxy through a third-party plug-in, or convert the communication mode through a gateway/adapter, and then complete the service proxy by the DPWS plug-in. This layer is also equipped with event notification agent and event subscription agent. The event notification agent sends the device operation state change event (such as start, stop, alarm, etc.) to the event library in the service management layer for other services to subscribe. At the same time, the device service learns the running status of related services, especially high-level business services, through the event subscription agent, and further interacts with related services driven by events to complete more intelligent data collection, aggregation and filtering strategy changes and its own status adjustments (such as entering power saving mode).

The service management layer and service dynamic discovery component use the DPWS service discovery mechanism WS-Discovery to complete the device service discovery function, and store all discovered services in a unified device service library. WS-Discovery is based on UDP multicast, so service dynamic discovery components need to be deployed repeatedly at each local physical site. The device monitoring component is responsible for monitoring and recording the dynamic running status information of each current device service, while the service lifecycle management component is responsible for managing the static device data of all online and offline devices, and updating the device service library according to the results of device monitoring and service discovery , service installation and upgrade can be realized after function expansion. Service logs are convenient for later intelligent analysis. The event receiver is responsible for receiving event notifications from business-level services and device-level services, and performing event filtering. The event processor is responsible for classifying, merging, and transforming the initial simple events, and recording the processed events into the event library for service subscription.

Business service layer, the business model library is responsible for storing the combined service model established in advance according to business logic and rules. This type of business model is a business process model established according to BPEL4WS, OWL-S or other standards, which can be static service binding It can also be an abstract business model without service binding. The business service and DPWS device service library is responsible for storing the existing runtime combined service information and DPWS device service information that can be used across layers, so as to facilitate service reuse and direct invocation of DPWS device services. The composite service workflow engine runs the composite service process according to the business model, and calls the component service functions involved in the composite service compilation process. Since the online status of the Internet of Things terminal device is unstable, the service call proxy component is used to cache service call instructions, so that the combined service process can continue to be executed when the device service is available again. The event notification agent and the subscription agent of this layer are responsible for publishing business execution state change events and subscribing related equipment service execution state change information. The business process can make coordinated execution process changes according to equipment service events, such as entering the emergency event processing process after receiving alarm information.

Equipment: including traditional equipment and DPWS equipment.

For traditional devices, the information is passed to the device service agent in the SOA middleware through third-party plug-ins or gateways/adapters to DPWS plug-ins;

DPWS devices, embedded devices with Web service standards, support minimal and seamless interaction with Web services running in devices. IoT applications and composite services can interact with DPWS devices across layers.

Information extraction module: as a device, it provides functions such as information collection, transmission and terminal control: including the transmission layer, perception control layer and device layer. Layer intelligent perception, that is, the collection of information, and the collected information is transmitted to the SOA middleware through the transport layer; at the same time, the data, information or instructions of the SOA middleware processing computing and Internet of Things application components are reversely transmitted to the perception Control layer, and operate and control the equipment through various intelligent control components of the perception control layer, so as to realize interactive management and control between IoT application components and devices.

The so-called transmission layer includes two methods of wired transmission and wireless transmission, and adopts different data transmission methods according to the location and nature of the device;

The so-called perception control layer includes pressure, flow, and temperature sensors, which can sense and automatically upload various parameters of the equipment in real time or in a planned way; Receive the state execution of the business release, or use it to enter the emergency event processing after receiving the alarm information; it also includes the alarm device, when the perceived data exceeds the predetermined threshold, upload the early warning according to the preset level or directly activate the control switch or start the alarm according to the predetermined threshold. stop device;

The so-called equipment layer includes various types of terminal equipment, oil production equipment, metering equipment, storage equipment, oil refining equipment, pipeline network equipment and oil sales equipment, etc.

Event collaboration interaction module: In Figure 3, the components of each layer of the SOA middleware platform responsible for sending, receiving and processing events and their interactions constitute an event-driven service collaboration mechanism. We adopt the WS-Notification standard to design related components, which includes three specifications: WS-Notification, WS-Brokered Notification and WS-Topic. Specifically, we use the WS-Brokered Notification standard as the event receiver of the event consumer and the event subscription agent to set the event notification interface, and as the event producer's event processor to set the event subscription interface. The event subscription agent supports both Push and Pull. An event distribution model. The event notification proxy only sends simple events, so the subscription interface is not set. The specific event coordination mechanism design is shown in Figure 3.

IoT-aware events are usually time-sensitive, and device services may issue event notifications at a relatively high frequency. Therefore, the event receiver needs to filter the initially received events according to preset rules, such as judging whether the event is expired or is a repeated event. Afterwards, the received initial event is formatted for further processing. Events are then prioritized based on specific system requirements, with alarm events generally having the highest priority. Finally, event scheduling and caching are performed according to the event priority. According to the event management model, an event handler first completes the event classification, merging, and transformation processes to transform simple events into high-level business events of interest to other services. The event management model complies with the WS-Topic standard. WS-Topic defines a hierarchical topic tree through which event types can be declared and events can be filtered when subscribing to events. Events are published and stored in a dynamic event library for service subscription. The subscription library mainly stores the subscription relationship between services and events. The subscription agent completes the event subscription function according to the subscription relationship in the subscription library, and actively pushes events that require high real-time processing.

The specific operation steps of a SOA-based oil and gas equipment maintenance management system working method provided by the present invention are as follows:

1) The information extraction module collects and perceives the preset information of the device through the sensor control layer, and transmits it to the device service agent in the SOA middleware through the transport layer;

2) The traditional device passes the third-party plug-in or gateway/adapter to the DPWS plug-in to complete the information transfer to the device service agent in the SOA middleware;

3) The DPWS device directly transmits the information to the device service agent in the SOA middleware through the DPWS plug-in;

4) SOA middleware abstracts device functions and communication capabilities into device services, forms a service set and builds a service composition environment. The perception layer in the information extraction module contains a large number of heterogeneous perception terminals, with different access methods and functions. same. The device service proxy layer in the SOA middleware hides heterogeneous technical details, processes and external input and output message operations through standard Web service interfaces, and at the same time converts service calls into communication instructions for specific terminals;

5) The components of each layer of SOA middleware responsible for sending, receiving and processing events and their interactions constitute an event-driven service collaboration mechanism, which is an event collaboration interaction module; each information processing unit in the Internet of Things system is not only a provider of perceptual information who, at the same time, are consumers;

6) The event receiver and event subscription agent of the event consumer in the event collaboration interaction module set the event notification interface to adopt the WS-Brokered Notification standard;

7) The event processor of the event producer in the event collaboration interaction module sets the event subscription proxy interface, and the event subscription proxy supports two event distribution modes, Push and Pull. The event notification proxy only sends simple events, and no subscription interface is set;

8) After the event notification agent receives the data from the information extraction module, it submits it to the event processor for processing after being processed by the event receiver;

9) The event subscription agent sends the processed information to the event subscription system. After receiving the information, different subscription systems execute the corresponding next step process or processing.

Although the present application has been described by way of example, those of ordinary skill in the art know that there are many variations and changes in the application without departing from the spirit of the application, and it is intended that the appended claims cover these variations and changes without departing from the spirit of the application.

Claims (5)

1. a kind of oil and gas equipment dimension based on SOA supports management system, including Internet of Things application component, SOA middlewares and equipment, if Back-up is traditional equipment and DPWS equipment, and SOA middlewares include application service layer, Service Management and device service layer, spy Sign is：Further include information extraction modules and event cooperation interaction module；

Described information extraction module includes transport layer, perception control layer and mechanical floor, provide the acquisition of information for equipment, transmit and Terminal control function；Described information extraction module passes through the corresponding all kinds of biographies of correlation perceived in control layer to the parameters of equipment Sensor realizes the Intellisense of mechanical floor, and collected information is transferred to SOA middlewares by transport layer；It will pass through simultaneously SOA middleware processes calculate and the data of Internet of Things application component, information or instruction carry out reverse transfer to perception control layer, and All kinds of intelligent control components by perceiving control layer are operated and are controlled to equipment, realize Internet of Things application component and equipment Between interactive supervision and control；

The event cooperation interaction module realizes cross-layer service interaction and association for providing DPWS equipment with Internet of Things application component With perception service function：Event cooperation interaction module is responsible for sending, receive and handling event, the mould through each layer of SOA middlewares Block constitutes event driven service coordination mechanism, realize DPWS equipment and Internet of Things application component cross-layer service interaction and Collaborative perception service function.

2. a kind of oil and gas equipment dimension based on SOA as described in claim 1 supports management system, it is characterised in that：The equipment In service layer, traditional equipment is interacted with SOA middlewares, then is interacted in a manner of Web service by DPWS plug-in units； DPWS Equipment is directly interacted by the DPWS plug-in units of standard in a manner of Web service with SOA middlewares；

The Service Management includes service Dynamic Discovery, equipment monitor and service lifecycle management assembly；Wherein service is dynamic State finds that component completes device service discovery feature using DPWS service discovery mechanisms WS-Discovery, and all will have found Service memory is in a unified device service library, and WS-Discovery is based on UDP multicasts, and service Dynamic Discovery component is every A Local physical website carries out repeating deployment；Equipment monitor component is responsible for monitoring and is transported with the dynamic for recording each current device service Row status information；Service lifecycle management assembly is responsible for the static equipment data of all online and offline equipment, and Device service library is updated according to equipment monitor and service discovery result, service installation can be achieved after Function Extension and is risen Grade；Serve log is for carrying out later stage intelligent analysis；

The application service layer includes business model library, business service and DPWS device services library, composite services workflow engine Component：Wherein business model library is responsible for storing the composite services model established previously according to service logic and rule；Business service Composite services information and can the DPWS equipment clothes that use of cross-layer when existing operation is responsible for storing in component and DPWS device services library Business information；Composite services workflow engine runs composite services process according to business model, is related to composite services compilation process Component service function carry out service call.

3. a kind of oil and gas equipment dimension based on SOA as claimed in claim 1 or 2 supports management system, it is characterised in that：The industry Composite services workflow engine runs composite services process according to business model in business service layer, is related to composite services compilation process And Component service function carry out service call；

Since the presence of internet-of-things terminal equipment is unstable, service call Agent components be used to carry out service call Instruction buffer continues to execute composite services process when can be used again in order to device service.

4. a kind of oil and gas equipment dimension based on SOA as claimed in claim 3 supports management system, it is characterised in that：The service Equipment monitor component is responsible for monitoring and records the dynamic state of run information of each current device service in management level, and waiter Life cycle management component is responsible for the static equipment data of all online and offline equipment, and according to equipment monitor and service It was found that result is updated device service library, service installation and upgrading can be achieved after Function Extension.

5. a kind of oil and gas equipment dimension according to claim 1 based on SOA supports the working method of management system, feature exists In：Include the following steps

1）Information extraction modules carry out preset information collection and perception by sensor control layer to equipment, and pass through transport layer Pass to the device service agency in SOA middlewares；

2）Traditional equipment passes to DPWS plug-in units completion information by third side plug or by gateway/adapter and passes to Device service agency in SOA middlewares；

3）DPWS equipment directly completes information by DPWS plug-in units and passes to the agency of the device service in SOA middlewares；

4）Functions of the equipments and communication capacity are abstracted as device service by SOA middlewares, are formed a set of service and are built one A Services Composition environment, the sensing layer in information extraction modules include the perception terminal of a large amount of isomeries, access way and function It is different；

Device service Agent layer in SOA middlewares conceals the technical detail of isomery, is handled by the Web service interface of standard With external input and output Message Opcode, while it converting service call to the communication instruction for particular terminal；

5）Each layer of SOA middlewares be responsible for send, receive and processing event component and its interactive relation constitute it is event driven Service collaboration mechanism, as event cooperation interaction module；Each information process unit in Internet of things system is both perception information Supplier, while being consumer again；

6）The Event receiver of event consumer and event subscription agency's setting event notification interface in event cooperation interaction module Using WS-Brokered Notification standards；

7）Event subscription proxy interface, event subscription generation is arranged in the event handler of event producer in event cooperation interaction module Reason supports two kinds of case distribution patterns of Push and Pull；

Event notification agent only does simple event transmission, and subscribing interface is not arranged；

8）After event notification agent receives the data from information extraction modules, submitted to after the processing of Event receiver Event handler is handled；

9）The information that processing is completed is sent to the ordering system of the event by event subscription agency, and different ordering systems receives letter After breath, corresponding next step flow or processing are executed.