WO2015188781A1 - 信息处理方法、装置和系统 - Google Patents

信息处理方法、装置和系统 Download PDF

Info

Publication number
WO2015188781A1
WO2015188781A1 PCT/CN2015/081349 CN2015081349W WO2015188781A1 WO 2015188781 A1 WO2015188781 A1 WO 2015188781A1 CN 2015081349 W CN2015081349 W CN 2015081349W WO 2015188781 A1 WO2015188781 A1 WO 2015188781A1
Authority
WO
WIPO (PCT)
Prior art keywords
information processing
external application
data
rule
interface adapter
Prior art date
Application number
PCT/CN2015/081349
Other languages
English (en)
French (fr)
Inventor
王敏骅
哈维C
Original Assignee
海克斯康方案应用与系统集成（青岛）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 海克斯康方案应用与系统集成（青岛）有限公司 filed Critical 海克斯康方案应用与系统集成（青岛）有限公司
Priority to US15/316,906 priority Critical patent/US10176024B2/en
Priority to EP15806031.9A priority patent/EP3156898A4/en
Publication of WO2015188781A1 publication Critical patent/WO2015188781A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/541—Interprogram communication via adapters, e.g. between incompatible applications
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/20—Software design
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25—Integrating or interfacing systems involving database management systems
    • G06F16/258—Data format conversion from or to a database
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
    • G06F16/38—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
    • G06F16/387—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually using geographical or spatial information, e.g. location
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs

Definitions

  • the present invention relates to the field of data processing, and in particular, to an information processing method, apparatus, and system.
  • ERP Enterprise Resource Planning
  • EAI Enterprise Application Integration
  • FIG 1 and Figure 2 are schematic diagrams of the ERP system and the EAI system.
  • the ERP system focuses on the tight integration of enterprise applications in a centralized manner, and the EAI system proposes to pass the enterprise service bus (ESB (Enterprise Service Bus) integrates enterprise applications to form a loosely distributed integration mechanism; for example, a Service Oriented Architecture (SOA).
  • ESB Enterprise Service Bus
  • SOA Service Oriented Architecture
  • ERP enterprise integration
  • EAI enterprise integration
  • EAI enterprise integration
  • EAI focuses on the standardization of business processing
  • EAI focuses on mapping and distributing business processing.
  • EAI needs more than ERP.
  • FIG. 3 and FIG. 4 are schematic diagrams of interface settings when different applications are integrated in the prior art.
  • 12 interfaces need to be set.
  • FIG. 4 even if each interface is bidirectional, six interfaces need to be set up, so this integration technology wastes a lot of time and resources due to the need to establish different interaction interfaces between every two applications.
  • the vendor provides an updated version of the application, it needs to update or modify the established interface, which also requires a lot of resources, and After the introduction of a new application, the number of interfaces increases exponentially, resulting in too many interfaces, low scalability, and poor user experience.
  • FIG. 5 is a schematic diagram of a structure of the integrated system, as shown in FIG. 5, in the traditional platform integration method, due to the supplier
  • the interfaces used to connect the platform and each application are also diverse, and each interface can only be used by a separate application. Therefore, the data interaction between the application and the platform can only be performed through a specific interface.
  • EAI mostly uses proprietary standards based on specific implementation of EAI companies.
  • the advantage of the private standard is that the EAI middle layer can reduce the pressure on the application message translation conversion to a certain extent, and the overall performance of the EAI can be improved in the case of fewer application systems, but the private standard is also flexible and scalable for enterprise integration.
  • the loss of sex when the enterprise introduces new applications, or when an application needs to make relatively large changes, the adaptability of the entire EAI bus will become very fragile.
  • the integration difficulty of newly introduced applications will increase exponentially due to the inconsistency of standards.
  • Enterprise application integration through EAI the adapters, middle-layer message conversion rules and message routing developed are tightly coupled. When new applications are to be integrated in EAI, they need to convert existing partial adapters and middle-layer messages. Rules and message routing are modified and cannot be reused.
  • the embodiment of the invention provides an information processing method, device and system. By redesigning the common interface and control rules, application integration can be realized more easily, and the scalability is strong without affecting the independence of each application system, thereby solving the above technical problems.
  • an information processing apparatus comprising:
  • One or more interface adapters each of which is connected to an external application system for implementing data interaction and function calls between the plurality of external application systems;
  • a centralized rules engine that connects the one or more interface adapters for controlling data interactions and function calls between a plurality of the external application systems connected to the interface adapter using pre-set rules.
  • an information processing method comprising:
  • the interface adapter receives data and control information transmitted by the external application system
  • the interface adapter converts data and control information from the external application system into a predefined data structure; and sends it to a centralized rules engine, so that the centralized rule engine controls according to preset rules Data interaction and function calls between multiple external application systems connected to multiple interface adapters.
  • an information processing method comprising:
  • the centralized rules engine receives a predefined data structure sent by the interface adapter to convert data and control information from the external application system;
  • the centralized rules engine controls data interactions and function calls between a plurality of the external application systems connected to the plurality of interface adapters according to pre-set rules.
  • an information processing system comprising at least one information processing apparatus as in the first aspect;
  • the information processing device is connected to a plurality of external application systems through an interface adapter, and is controlled by using preset rules to implement data interaction and function calling between the plurality of external application systems.
  • the beneficial effects of the embodiments of the present invention are that the information processing method, apparatus, and system of the embodiments of the present invention can implement application integration more easily, and the scalability is strong without affecting the independence of each application system.
  • FIG. 1 is a schematic view showing the structure of an ERP in the prior art
  • FIG. 2 is a schematic view showing the structure of EAI in the prior art
  • FIG. 3 is a schematic diagram of interface settings when different applications are integrated in the prior art
  • FIG. 6 is a block diagram showing the structure of an information processing apparatus according to Embodiment 1 of the present invention.
  • FIG. 7 is a schematic diagram showing the configuration of an interface adapter 601 in Embodiment 1 of the present invention.
  • Embodiment 8 is a schematic diagram of data flow between an external application system and the information processing apparatus in Embodiment 1 of the present invention.
  • FIG. 9 is a schematic diagram of a connection mode of the interface adapter 601 in Embodiment 1 of the present invention.
  • FIG. 10 is a schematic diagram of a connection mode of the interface adapter 601 in Embodiment 1 of the present invention.
  • FIG. 11 is a schematic diagram of communication between a plurality of interface adapters 601 in Embodiment 1 of the present invention.
  • FIG. 12 is a schematic diagram showing a rule set by the setting unit 6021 in the first embodiment of the present invention.
  • FIG. 13 is a schematic diagram showing a rule set by the setting unit 6021 in the first embodiment of the present invention.
  • FIG. 14 is a schematic diagram of synchronization implemented by the centralized rule engine 602 in Embodiment 1 of the present invention.
  • Embodiment 15 is a schematic diagram of Embodiment 1 of a general attribute integrator in Embodiment 1 of the present invention.
  • Embodiment 16 is a schematic diagram of Embodiment 1 of a data publisher in Embodiment 1 of the present invention.
  • Embodiment 17 is a schematic diagram of Embodiment 1 of a data publisher in Embodiment 1 of the present invention.
  • FIG. 18 is a schematic diagram of a connection mode of a gateway connector in Embodiment 1 of the present invention.
  • FIG. 19 is a schematic diagram showing a connection manner of a gateway connector in Embodiment 1 of the present invention.
  • FIG. 20 is a schematic diagram showing a connection manner of a gateway connector in Embodiment 1 of the present invention.
  • FIG. 21 is a flowchart of an information processing method in Embodiment 1 of the present invention.
  • Figure 22 is another flowchart of the information processing method in Embodiment 1 of the present invention.
  • Figure 24 is a block diagram showing the structure of a landslide safety management device according to Embodiment 1 of the present invention.
  • 25 to 28 are schematic diagrams of control rules between respective external application systems set in a centralized rule engine according to an embodiment of the present invention
  • FIG. 29 is a schematic diagram showing the configuration of an information processing system in Embodiment 2 of the present invention.
  • Figure 30 is a block diagram showing the configuration of an information processing system in Embodiment 2 of the present invention.
  • Figure 31 is a schematic view showing the constitution of a reservoir safety management system in Embodiment 2 of the present invention.
  • Figure 32 is a diagram showing the configuration of an enterprise management system in Embodiment 2 of the present invention.
  • Embodiment 1 of the present invention provides an information processing apparatus.
  • FIG. 6 is a schematic diagram of a configuration of an information processing apparatus according to Embodiment 1 of the present invention. Referring to FIG. 6, the information processing apparatus 600 includes:
  • a centralized rules engine 602 which is coupled to one or more interface adapters 601 for controlling data interactions and functions between a plurality of external application systems connected to the interface adapter 601 using pre-set rules transfer.
  • the information processing apparatus 600 may be referred to as a platform
  • the interface adapter 601 may be referred to as a Smart Interface Adapter (SIA)
  • the centralized rule engine 602 may be referred to as an RE (Rules Engine). ).
  • the information processing apparatus 600 can include one or more interface adapters 601, each of which is used to connect an external application system to implement data interaction and function calls between the external application system and other application systems.
  • the interface adapter 601 performs data interaction and function calls with different application systems provided by different vendors through different protocols.
  • the interface adapter 601 is centralized with the information processing device 600 through a predefined communication mechanism.
  • the rules engine 602 communicates.
  • the interface adapter 601 can be connected to the external application system through an application programming interface (API) or a dynamic link library (DLL) of an external application.
  • API application programming interface
  • DLL dynamic link library
  • the external application system may exchange its operation data, status data, and the like with other external application systems through the interface adapter 601, or may call the functions of other external application systems to which the interface adapter 601 has been connected, its own The function can also be called by other applications through the interface adapter 601.
  • the interface adapter 601 includes: a first interaction unit 6011 that converts data from an external application system into a first predefined data structure; and a second interaction unit 6012 that will control from an external application system The information is converted into a second predefined data structure.
  • the data from the external application system may be a data format specified by a Transmission Control Protocol (TCP), a User Datagram Protocol (UDP), an Internet Protocol (IP), or other transmission protocol.
  • TCP Transmission Control Protocol
  • UDP User Datagram Protocol
  • IP Internet Protocol
  • the first interaction unit 6011 may convert the data into a first predefined data structure and output, thereby different externalities connected to the information processing device. After the data of the application system passes through the first interaction unit 6011, the data is output as a unified data format to facilitate communication between the external application systems.
  • the function call of the external application system may be converted into a second predefined data structure by the second interaction unit 6012, implemented by the interface adapter 601, or directly passed through the API or DLL of the external application system. Implement the call.
  • FIG. 7 is a schematic diagram of the configuration of the interface adapter 601. As shown in FIG. 7, in the interface adapter 601, data and functions are implemented through different interaction units. 8 is a schematic diagram of data flow between an external application system and an information processing device. As shown in FIG. 8, information such as an operating state of the external application system is output through the interface adapter 601, and operation state information of other external application systems is called by function or The way the web service is called is input to the external application system through the API or DLL of the external application system.
  • the interface adapter 601 can be connected to the application by wire or wirelessly, so the information processing apparatus can implement remote control of the application to form a distributed system architecture.
  • FIG. 9 and FIG. 10 are schematic diagrams showing two connection modes of the interface adapter 601. As shown in FIG. 9, the interface adapter communicates with the external application system through networking, as shown in FIG. 10, the interface adapter is remotely implemented. The data and functions are transmitted to the information processing device through the LAN or WAN for information interaction with other external application systems.
  • the specific connection manner may be determined according to the API type of the external application system. The above is merely an illustrative description, and the embodiment is not limited thereto.
  • the interface adapter 601 can be implemented based on a configuration file, and the behavior of the interface adapter 601 can be dynamically controlled by modifying the configuration of the configuration file.
  • FIG. 11 is a schematic diagram of communication between a plurality of interface adapters of the information processing apparatus in the embodiment. As shown in FIG. 11, since the first and second interaction units through the interface adapter can output the same data structure, it is convenient for each Different external application systems implement data interaction and capability calls.
  • the centralized rule engine 602 includes: a setting unit 6021 and a processing unit 6022, where the setting unit 6021 is configured to preset the rule, where the rule includes a trigger condition and corresponding processing performed; The unit 6022 is configured to perform corresponding processing according to the rule when the trigger condition is met.
  • 12 is a schematic diagram of a rule set by the setting unit 6021. As shown in FIG. 12, information from each external application system is input into the centralized rule engine 602. When the trigger condition is met, the corresponding rule is performed according to the rule. Processing.
  • the setting unit 6021 sets the rules according to one of the following information or a combination thereof: result driving, event driving, time driving, and state driving information.
  • FIG. 13 is the rule setting unit 6021 setting a schematic diagram
  • the setting unit 6021 sets the driving state in accordance with the rule
  • the rule can be set to the state of the external application system S 1 is P1
  • trigger processing unit 6022 performs corresponding processing P2 and P3 on external application systems S 2 and S 3 .
  • the setting unit 6021 can also perform more complicated conditions and processing settings according to logic and/or manner, and the embodiment is not limited thereto.
  • the information processing device can perform data synchronization, thereby eliminating the need for the information processing device or the like.
  • the application sets up an extra database for storing data from the application, and also improves the efficiency of the information processing device.
  • FIG. 14 is a schematic diagram of the synchronization of the centralized rule engine 602 in the embodiment. As shown in FIG. 14, when the external application system S k has an attribute X, the centralized rule engine 602 sets the S N according to a preset rule. The property is set to Y.
  • the information processing apparatus 600 may further include a general-purpose attribute integrator 603 for Data or control information transmitted by the plurality of interface adapters 601 is received, and the data or control information is converted into a third predefined data structure.
  • the format of the third predefined data structure may satisfy any industry standard or published protocol, such as XML, JSON or other standard protocol defined formats.
  • 15 is a schematic diagram of an embodiment of the universal attribute integrator. As shown in FIG. 15, data from each independent external application system can be converted into a third predefined data structure by a common attribute integrator.
  • the information processing apparatus 600 further includes a data publisher 604. And used to publish the converted data structure of the universal attribute integrator 603 to provide services to multiple external clients.
  • the data publisher can publish data in a broadcast or customized manner for use by other external clients, wherein the broadcast mode can save transmission bandwidth, and the customized manner can enable the independent external application system according to the It needs to customize the data itself.
  • FIGS. 16 and 17 are schematic diagrams showing a first embodiment of the data publisher. As shown in FIGS. 16 and 17, data or functions from an external application system are converted by the general attribute integrator and transmitted to the data publisher to be used for multiple External clients such as wired clients, wireless clients, and remote clients provide services.
  • the information processing apparatus 600 further includes a gateway connector 605 connected to the interface adapter 601 and other information processing devices to implement data interaction and function calls between different information processing devices.
  • the gateway connector 605 can be connected to one or a plurality of other information processing devices at the same time.
  • FIGS 18, 19, and 20 are schematic diagrams of several implementations of the gateway connector
  • FIG. 19 is an example of a gateway connector connecting different information processing devices in a point-to-point manner
  • FIG. 20 is a gateway connector.
  • the universal attribute integrator 603 may be referred to as CAI (Common Attribute Integration); the data publisher 604 may be referred to as DPS (Data Publishing Server); the gateway connector 605 may be referred to as a PG (Platform Gateway) .
  • CAI Common Attribute Integration
  • DPS Data Publishing Server
  • PG Platinum Gateway
  • the information processing apparatus apparatus 600 further includes a display operator for displaying and operating the data and control information output by the interface adapter 601.
  • the display operator may be implemented using a GUI, and the rules in the setting unit 6021 may be set by a display operator, or the presentation manner of the converted data by the universal attribute integrator 603 may be set by the display operator.
  • This embodiment is not limited to this.
  • the universal interface and the control rule are redesigned, and the application integration can be realized more easily, and the scalability is strong without affecting the independence of each application system.
  • FIG. 21 is a flowchart of an information processing method according to an embodiment of the present invention. The method is applied to the real information processing apparatus. As shown in FIG. 21, the method includes:
  • Step 2101 the external application system a transmits its own operational data, status data, functions and other information to the interface adapter a;
  • Step 2102 the interface adapter a converts data from the external application system a into a first or second predefined data structure
  • Step 2103 the first or second predefined data structure is passed to the interface adapter b through a centralized rules engine (not shown);
  • Step 2104 the interface adapter b converts the data into a data structure of the external application system b;
  • step 2105 the interface adapter b delivers the data to the external application system b, so that the external application system b can conveniently obtain the information of the external application system a.
  • FIG. 22 is another flow chart of an information processing method according to an embodiment of the present invention, which is applied to the above-described real information processing apparatus. As shown in FIG. 22, the method can also perform the following steps:
  • Step 2201 Send the first or second predefined data structure converted by the interface adapter a to the universal attribute integrator;
  • Step 2202 the universal attribute integrator converts the data structure sent by the interface adapter a into a third predefined data structure
  • Step 2203 sending a third predefined data structure to the data publisher
  • step 2204 the data publisher publishes the received data in a broadcast or customized manner.
  • FIG. 23 is another flowchart of an information processing method according to an embodiment of the present invention, which is applied to the above-described real information processing apparatus. As shown in FIG. 23, the method can also perform the following steps:
  • Step 2301 the first or second predefined data structure converted by the interface adapter a is sent to the gateway connector through an interface adapter c (not shown) connected to the gateway connector;
  • the gateway connector sends the received data structure to other information processing devices.
  • FIG. 24 is a schematic diagram of the landslide safety management apparatus
  • FIG. 25-28 is a centralized type.
  • TPS Total Position Station
  • the relevant emergency occurs.
  • the system is connected by an interface adapter a that receives data from the GeoMoS store (step 2101), converts it into a predefined data structure (step 2102), and passes it to other applications connected to the interface adapter b of the information processing device.
  • the data converted by the interface adapter a is sent to a common sensor interface (CSI, equivalent to a common attribute integrator) (step 2201), and the CSI converts the received data into a third pre-
  • CSI Geographic Information System
  • the defined data structure such as the JavaScript Object Notation stream (step 2202) will publish the converted JSON stream to a Geographic Information System (GIS) map client (steps 2203 and 2204).
  • GIS Geographic Information System
  • the converted data of the interface adapter a can be transmitted to the security management application connected to the interface adapter c of the information processing device, and sent to the security client through the UDP broadcast, and after the security client verifies the alarm, the security agent
  • the confirmed alarm is transmitted to the I/CAD application connected to the interface adapter d through the interface adapter d of the information processing device, and the I/CAD application notifies the client and the gateway (Gateway, GW) in time after receiving the event.
  • Step 2301 (corresponding to the gateway connector), and the event is reported to the information processing apparatus of the upper stage by the GW (step 2302).
  • the information processing method of the embodiment enables the landslide management system to more easily implement various existing application integrations, and has strong scalability without affecting the independence of each system.
  • Embodiment 2 of the present invention provides an information processing system
  • FIG. 29 is a schematic diagram of the structure of an information processing system according to Embodiment 2 of the present invention.
  • the information processing system 2900 includes at least one information processing as described in Embodiment 1.
  • the device 2901 is configured to connect a plurality of external application systems and control using preset rules to implement data interaction and function calls between the plurality of the external application systems.
  • the information processing device is two or more; two or more of the information processing devices are connected to each other through a gateway connector to implement data interaction and function call between different information processing devices. .
  • FIG. 30 is a schematic diagram of a configuration of the information processing system, wherein the plurality of external application systems may also be the information processing system 2901 in the second embodiment.
  • FIG. 31 is a schematic diagram of the reservoir security management system.
  • the system includes multiple business applications, such as a CAD scheduling application, an emergency response application, and a file. Management application, etc.
  • Figure 31 is a schematic diagram of the structure of a multi-level reservoir safety management system. Through the system shown in Figure 31, real-time monitoring information can be obtained when the reservoir discovers water, rain, conditions, weather, disasters and other information. And resource information and other timely sharing, reporting, easy emergency command and dispatch.
  • FIG. 32 is a schematic diagram of the enterprise management system.
  • the system includes multiple service applications, such as Customer Relationship Management (CRM).
  • CRM Customer Relationship Management
  • the information processing device can enable data sharing of each application connected to the device to implement data sharing, and can release data of each application to an individual customer.
  • the enterprise can be mastered by enterprise users in a timely manner, thereby improving the efficiency of enterprise management.
  • the system, device, module or unit illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product having a certain function.
  • the present application can be implemented by means of software plus a necessary general hardware platform. Based on such understanding, portions of the technical solution of the present application that contribute substantially or to the prior art may be embodied in the form of a software product.
  • the computing device includes one or more processors (CPU ), input / output interface, network interface and memory.
  • the computer software product can include instructions for causing a computer device (which can be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present application or portions of the embodiments.
  • the computer software product can be stored in a memory, which may include non-persistent memory, random access memory (RAM), and/or nonvolatile memory in a computer readable medium, such as read only memory (ROM) or Flash memory.
  • RAM random access memory
  • ROM read only memory
  • Memory is an example of a computer readable medium.
  • Computer readable media includes both permanent and non-persistent, removable and non-removable media.
  • Information storage can be implemented by any method or technology.
  • the information can be computer readable instructions, data structures, modules of programs, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), EEPROM, flash memory or Other memory technologies, CD-ROMs, digital versatile discs (DVDs) or other optical storage, magnetic cassettes, magnetic tape storage or other magnetic storage devices or any other non-transportable media, available Stores information that can be accessed by the computing device.
  • PRAM phase change memory
  • SRAM static random access memory
  • DRAM Dynamic Random Access Memory
  • RAM Random Access Memory
  • ROM Read Only Memory
  • EEPROM Electrically erasable programmable read-only memory
  • flash memory or Other memory technologies
  • CD-ROMs compact discs
  • DVDs digital versatile discs
  • magnetic cassettes magnetic tape storage or other magnetic storage devices or any other non-transportable media
  • available Stores information that can be accessed by the computing device stores information that can be accessed by the computing device.
  • computer readable media does not include
  • This application can be used in a variety of general purpose or special purpose computer system environments or configurations.
  • the application can be described in the general context of computer-executable instructions executed by a computer, such as a program module.
  • program modules include routines, programs, objects, components, data structures, and the like that perform particular tasks or implement particular abstract data types.
  • the present application can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are connected through a communication network.
  • program modules can be located in both local and remote computer storage media including storage devices.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • Library & Information Science (AREA)
  • Computer And Data Communications (AREA)

Abstract

一种信息处理方法、装置和系统。该信息处理装置包括：一个或多个接口适配器，每个接口适配器连接一个外部应用系统，用于实现多个所述外部应用系统之间的数据交互和功能调用；集中式规则引擎，所述集中式规则引擎连接所述一个或多个接口适配器，用于使用预先设置的规则，来控制与所述接口适配器连接的多个所述外部应用系统之间的数据交互和功能调用。由此，重新设计了通用的接口和控制规则，能够更容易地实现应用集成，可扩展性强又不影响各个集成应用的独立性。

Description

信息处理方法、装置和系统 技术领域
本发明涉及数据处理领域，尤其涉及一种信息处理方法、装置和系统。
背景技术
近年来，各种供应商均提供有独立的软件应用(application)系统，当这些互相独立的应用系统需要交互时，通常使用应用集成的方式。企业资源计划(ERP，Enterprise Resource Plan)和企业应用集成(EAI，Enterprise Application Integration)是两种目前非常普及的用于集成企业应用的方法。
图1和图2分别是ERP系统和EAI系统的一构成示意图，如图1和2所示，ERP系统侧重于以集中化的方式将企业应用紧密地集成，EAI系统则提出通过企业服务总线(ESB，Enterprise Service Bus)将企业应用进行整合，形成松散的分布式的集成机制；例如形成以服务为中心的架构(SOA，Service Oriented Architecture)。
ERP和EAI的目标都是进行企业集成，包括数据交换和业务处理。由于ERP和EAI需要将不同的应用进行整合，因此需要花费大量的代价，其中，ERP集中于适应业务处理的标准化，而EAI集中于映射和分发业务处理，相比于ERP，EAI还需要更多地进行预先的业务分析。
应该注意，上面对技术背景的介绍只是为了方便对本发明的技术方案进行清楚、完整的说明，并方便本领域技术人员的理解而阐述的。不能仅仅因为这些方案在本发明的背景技术部分进行了阐述而认为上述技术方案为本领域技术人员所公知。
发明内容
发明人在实现上述内容时发现，现有技术中存在以下问题：
图3和图4是现有技术中不同应用集成时的接口设置示意图，如图3所示，为了使应用1、2、3、4之间能够互相通信，则需要设置12个接口。如图4所示，即便每一个接口是双向的，也仍需要设置6个接口，因此由于需要在每两个应用之间建立不同的交互接口，导致这种集成技术浪费大量的时间和资源，而当供应商的提供的应用更新版本后，需要对建立的接口进行更新或修改，这同样需要花费大量的资源，并且 在引入新的应用后，接口的数量呈指数上升，导致接口过多，扩展性低，用户体验差。
现有技术中为了解决交互接口过多的问题，提出了一种集成系统，图5是该集成系统的一构成示意图，如图5所示，在传统的平台集成方法中，由于供应商提供的应用不同，用于连接平台和各个应用的接口也多种多样，而每一个接口只能被一个独立的应用单独使用，因此应用和平台之间的数据交互也只能通过特定的接口进行，各个应用之间无法直接通信，这种方式同样消耗大量的资源，并且应用更新后的维护和移植均不容易。
例如，EAI大多使用基于具体实施EAI企业中制定的私有标准。基于私有标准的优点是可以在一定程度上减轻EAI中间层对应用消息翻译转换的压力，在应用系统较少的情况下可以提高EAI的整体性能，但私有标准同时也对企业整合的灵活可扩展性上带来损失，当企业引入新的应用，或当某个应用需要做比较大的改动时，整个EAI总线的适应性将变得十分脆弱。在企业规模不断增长的过程中，新引入应用的集成难度将因为标准的不统一而呈指数级上升。通过EAI方式实现企业应用集成，其开发的适配器、中间层消息转换规则和消息路由都是紧耦合的，当新应用要在EAI中进行集成，便需要对现有的部分适配器、中间层消息转换规则与消息路由进行改造，无法重用。
本发明实施例提出了一种信息处理方法、装置和系统。通过重新设计通用的接口和控制规则，既能够更容易地实现应用集成，可扩展性强又不影响各个应用系统的独立性，从而解决了上述技术问题。
根据本发明实施例的第一个方面，提供一种信息处理装置，该信息处理装置包括：
一个或多个接口适配器，每个该接口适配器连接一个外部应用系统，用于实现多个该外部应用系统之间的数据交互和功能调用；
集中式规则引擎，该集中式规则引擎连接该一个或多个接口适配器，用于使用预先设置的规则，来控制与该接口适配器连接的多个该外部应用系统之间的数据交互和功能调用。
根据本发明实施例的第二个方面，提供一种信息处理方法，该方法包括：
接口适配器接收外部应用系统传递的数据和控制信息；
该接口适配器将来自该外部应用系统的数据和控制信息转换为预定义的数据结构；并发送至集中式规则引擎，以便该集中式规则引擎根据预先设置的规则，来控制 与多个接口适配器连接的多个该外部应用系统之间的数据交互和功能调用。
根据本发明实施例的第三个方面，提供一种信息处理方法，该方法包括：
集中式规则引擎接收通过接口适配器发送的将来自该外部应用系统的数据和控制信息转换后的预定义的数据结构；
该集中式规则引擎根据预先设置的规则，来控制与多个该接口适配器连接的多个该外部应用系统之间的数据交互和功能调用。
根据本发明实施例的第四个方面，提供一种信息处理系统，该信息处理系统包括至少一个如第一方面的信息处理装置；
其中，该信息处理装置通过接口适配器连接多个外部应用系统，并使用预先设置的规则进行控制，以实现多个该外部应用系统之间的数据交互和功能调用。
本发明实施例的有益效果在于，通过本发明实施例的信息处理方法、装置和系统，能够更容易地实现应用集成，可扩展性强又不影响各个应用系统的独立性。
参照后文的说明和附图，详细公开了本发明的特定实施方式，指明了本发明的原理可以被采用的方式。应该理解，本发明的实施方式在范围上并不因而受到限制。在所附权利要求的精神和条款的范围内，本发明的实施方式包括许多改变、修改和等同。
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多个其他实施方式中使用，与其他实施方式中的特征相组合，或替代其他实施方式中的特征。
应该强调，术语“包括/包含”在本文使用时指特征、整件、步骤或组件的存在，但并不排除一个或更多个其他特征、整件、步骤或组件的存在或附加。
附图说明
参照以下的附图可以更好地理解本发明的很多方面。附图中的部件不是成比例绘制的，而只是为了示出本发明的原理。为了便于示出和描述本发明的一些部分，附图中对应部分可能被放大或缩小。在本发明的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其他附图或实施方式中示出的元素和特征相结合。此外，在附图中，类似的标号表示几个附图中对应的部件，并可用于指示多于一种实施方式中使用的对应部件。
在附图中：
图1是现有技术中ERP构成一示意图；
图2是现有技术中EAI构成一示意图；
图3是现有技术中不同应用集成时的接口设置一示意图；
图4是现有技术中不同应用集成时的接口设置一示意图；
图5是现有技术中集成系统的构成一示意图；
图6是本发明实施例1的信息处理装置构成示意图；
图7是本发明实施例1中接口适配器601的构成一示意图；
图8是本发明实施例1中外部应用系统与该信息处理装置之间数据流示意图；
图9是本发明实施例1中接口适配器601连接方式一示意图；
图10是本发明实施例1中接口适配器601连接方式一示意图；
图11是本发明实施例1中多个接口适配器601之间进行通信的示意图；
图12是本发明实施例1中设定单元6021设定的规则一示意图；
图13是本发明实施例1中设定单元6021设定的规则一示意图；
图14是本发明实施例1中集中式规则引擎602实现同步的一示意图；
图15是本发明实施例1中通用属性集成器实施方式一示意图；
图16是本发明实施例1中数据发布器实施方式一示意图；
图17是本发明实施例1中数据发布器实施方式一示意图；
图18是本发明实施例1中网关连接器连接方式一示意图；
图19是本发明实施例1中网关连接器连接方式一示意图；
图20是本发明实施例1中网关连接器连接方式一示意图；
图21是本发明实施例1中信息处理方法的一流程图；
图22是本发明实施例1中信息处理方法的另一流程图；
图23是本发明实施例1中信息处理方法的另一流程图；
图24是本发明实施例1中滑坡安全管理装置的构成示意图；
图25至图28是本发明实施例的集中式规则引擎中设定的各个外部应用系统之间的控制规则示意图；
图29是本发明实施例2中信息处理系统的构成一示意图；
图30是本发明实施例2中信息处理系统的构成一示意图；
图31是本发明实施例2中水库安全管理系统的构成一示意图；
图32是本发明实施例2中企业管理系统的构成一示意图。
具体实施方式
参照附图，通过下面的说明书，本发明实施例的前述以及其他特征将变得明显。这些实施方式只是示例性的，不是对本发明的限制。为了使本领域的技术人员能够容易地理解本发明的原理和实施方式，本发明实施例以该应用为独立于其他应用或系统的软件或硬件为例进行说明，但可以理解，本发明实施例并不限于上述定义的应用。
下面参照附图对本发明的优选实施方式进行说明。
实施例1
本发明实施例1提供了一种信息处理装置，图6是本发明实施例1的信息处理装置的一构成示意图，请参照图6，信息处理装置600包括：
一个或多个接口适配器601，每个接口适配器601连接一个外部应用系统，用于实现多个外部应用系统之间的数据交互和功能调用；
集中式规则引擎602，所述集中式规则引擎602连接一个或多个接口适配器601，用于使用预先设置的规则，来控制与接口适配器601连接的多个外部应用系统之间的数据交互和功能调用。
在本实施例中，信息处理装置600可以被称为平台(platform)，接口适配器601可以为称为智能接口适配器(SIA，Smart Interface Adapter)，集中式规则引擎602可以为称为RE(Rules Engine)。
信息处理装置600可以包含一个或多个接口适配器601，每一个接口适配器601用于连接一个外部应用系统，以实现该外部应用系统和其他应用系统之间的数据交互和功能调用。一方面，接口适配器601通过不同的协议与不同的供应商提供的应用系统进行数据交互和功能调用，另一方面，接口适配器601通过预定义好的通信机制，与该信息处理装置600的集中式规则引擎602进行通信。由此当对应的外部应用系统更新或需要移植时，这种松散的耦合特性有助于提高维护效率，便于外部应用系统移植。
在本实施例中，该接口适配器601可以通过外部应用的应用程序编程接口(API，Application Programming Interface)或动态链接库(DLL，Dynamic Link Library)与该外部应用系统连接。
在本实施例中，该外部应用系统可以将其运行数据、状态数据等通过接口适配器601与其他外部应用系统进行交互，或者可以调用接口适配器601已经连接的其他外部应用系统的功能，其自身的功能也可以通过接口适配器601被其他应用调用。
在一个实施方式中，接口适配器601包括：第一交互单元6011，其将来自外部应用系统的数据转换成第一预定义的数据结构；以及第二交互单元6012，其将来自外部应用系统的控制信息转换成第二预定义的数据结构。
例如，来自该外部应用系统的数据可以是传输控制协议(Transmission Control Protocol，TCP)、用户数据报协议(User Datagram Protocol，UDP)、网络协议(Internet Protocol，IP)或其他传输协议规定的数据格式，还可以是来自该外部应用系统数据库中存储的数据，第一交互单元6011可以将上述数据转换成第一预定义的数据结构并输出，由此，与该信息处理装置连接的各个不同的外部应用系统的数据经过第一交互单元6011后，都输出为统一的数据格式，以便于各个外部应用系统之间进行通信。
在本实施例中，该外部应用系统的功能调用可以通过第二交互单元6012转换成第二预定义的数据结构，通过接口适配器601实现调用，或者也可以直接通过该外部应用系统的API或DLL实现调用。
图7是该接口适配器601的构成一示意图，如图7所示，在该接口适配器601中，数据和功能通过不同的交互单元实现交互。图8是外部应用系统与信息处理装置之间数据流示意图，如图8所示，该外部应用系统的运行状态等信息通过该接口适配器601输出，其他外部应用系统的运行状态信息以功能调用或web service调用的方式通过该外部应用系统的API或DLL输入至该外部应用系统中。
在本实施例中，该接口适配器601可以通过有线或无线的方式与该应用连接，因此该信息处理装置可以实现对该应用进行远程控制，以便形成分布式的系统架构。
图9和图10是该接口适配器601两种连接方式示意图，如图9所示，该接口适配器与该外部应用系统之间通过联网实现通信，如图10所示，该接口适配器进行远程实施，数据和功能通过LAN或WAN的方式传送至该信息处理装置，以便与其他外部应用系统进行信息交互，在具体实施时可以根据该外部应用系统的API类型，确定具体的连接方式。以上仅为示例性的说明，本实施例并不限制于此。
在本实施例中，该接口适配器601可以是基于配置文件实现的，通过修改配置文件的设置，就可以动态对该接口适配器601的行为进行控制。
图11是本实施例中该信息处理装置的多个接口适配器之间进行通信的示意图，如图11所示，由于通过接口适配器的第一和第二交互单元能够输出相同的数据结构，便于各个不同的外部应用系统实现数据交互和能力调用。
在本实施例中，该集中式规则引擎602包括：设定单元6021和处理单元6022，设定单元6021，用于预先设定所述规则，所述规则包括触发条件以及进行的相应处理；处理单元6022，用于在满足所述触发条件时，根据所述规则进行相应的处理。图12是该设定单元6021设定的规则一示意图，如图12所示，来自各外部应用系统的信息输入至该集中式规则引擎602中，在满足触发条件时，根据所述规则进行相应的处理。
在本实施例中，设定单元6021根据如下信息的其中之一或其组合对所述规则进行设定：结果驱动、事件驱动、时间驱动和状态驱动的信息。例如，图13是该设定单元6021设定的规则一示意图，设定单元6021根据状态驱动设定该规则时，该规则可以设置为在外部应用系统S1的状态为P1时，触发处理单元6022对外部应用系统S2和S3执行相应的处理P2和P3。其中设定单元6021也可以根据逻辑和/或的方式执行更多复杂条件和处理的设定，本实施例并不以此作为限制。
通过本实施例的集中式规则引擎，即使连接到该信息处理装置的每一个外部应用保持其独立性，但该信息处理装置仍可以进行数据的同步，从而不需要在该信息处理装置中或其他应用中设置多余的数据库用于存储来自该应用的数据，另外还可以提高信息处理装置工作的效率。
图14是本实施例中集中式规则引擎602实现同步的一示意图，如图14所示，该外部应用系统Sk具有某属性X时，集中式规则引擎602根据预先设置的规则将SN某属性设置为Y。
在本实施例中，为了使连接到该信息处理装置的每一个外部应用的数据和功能能够可靠地动态地提供给其他信息处理装置，信息处理装置600还可以包括通用属性集成器603，用于接收多个所述接口适配器601发送的数据或控制信息，并将所述数据或控制信息转换成第三预定义的数据结构。其中，该第三预定义的数据结构的格式可以满足任意的行业标准或者发布的协议，例如XML,JSON或其他标准协议定义的格式。图15是该通用属性集成器实施方式一示意图，如图15所示，来自每个独立外部应用系统的数据均可以通过通用属性集成器转换成第三预定义的数据结构。
在本实施例中，为了避免其他客户端与该信息处理装置间的距离以及不同连接方式对数据传输的影响，而使其他客户端同时共享相同的数据，信息处理装置600还包括数据发布器604，用于发布所述通用属性集成器603转换后的数据结构，以对多个外部客户端提供服务。
在本实施例中，该数据发布器可以以广播或定制的方式发布数据，以供其他外部客户端使用，其中，广播的方式可以节约传输带宽，定制的方式可以使独立的外部应用系统根据其自身需要进行数据的定制。图16和图17是该数据发布器实施方式一示意图，如图16和17所示，来自外部应用系统的数据或功能经过通用属性集成器转换后，传送至该数据发布器，以对多个外部客户端如有线客户端、无线客户端、远程客户端提供服务。
在本实施例中，该信息处理装置600还包括网关连接器605，与所述接口适配器601以及其他信息处理装置相连接，以实现不同的所述信息处理装置之间的数据交互和功能调用。其中，网关连接器605可连接一个或同时连接多个其他信息处理装置。
图18、19、20分别为该网关连接器几种实施方式示意图，图19是一种网关连接器以点对点的方式将不同的信息处理装置连接起来的示例，图20是一种网关连接器以“父节点-子节点”的方式将不同的信息处理装置连接起来的示例。
在本实施例中，通用属性集成器603可以被称为CAI(Common Attribute Integration)；数据发布器604可以被称为DPS(Data Publishing Server)；网关连接器605可以被称为PG(Platform Gateway)。
在本实施例中，为了便于使用者对该信息处理装置进行操控，所述信息处理装置装置600还包括显示操作器，用于显示和操作所述接口适配器601输出的数据和控制信息。
例如，该显示操作器可以使用GUI实现，另外可以通过显示操作器对设定单元6021中的规则进行设定，也可以通过显示操作器对通用属性集成器603转换后的数据的呈现方式进行设置，本实施例并不限制于此。
通过本实施例的信息处理装置，重新设计了通用的接口和控制规则，能够更容易的实现应用集成，可扩展性强，又不影响各个应用系统的独立性。
图21是本发明实施例信息处理方法的一流程图，该方法应用于上述实信息处理装置，如图21所示，该方法包括：
步骤2101，外部应用系统a将其自身的运行数据、状态数据、功能等信息传递给接口适配器a；
步骤2102，接口适配器a将来自外部应用系统a的数据转换为第一或第二预定义的数据结构；
步骤2103，将第一或第二预定义的数据结构通过集中式规则引擎(未示出)传递接口适配器b；
步骤2104，接口适配器b将数据转换成外部应用系统b的数据结构；
步骤2105，接口适配器b将数据传递给外部应用系统b，以使外部应用系统b能够方便的获取外部应用系统a的信息。
图22是本发明实施例信息处理方法的另一流程图，该方法应用于上述实信息处理装置。如图22所示，该方法还可以进行如下步骤：
步骤2201，将接口适配器a转换后的第一或第二预定义的数据结构发送至通用属性集成器；
步骤2202，通用属性集成器将接口适配器a发送来的数据结构转换为第三预定义的数据结构；
步骤2203，将第三预定义的数据结构发送至数据发布器；
步骤2204，数据发布器通过广播或定制的方式将接收到的数据进行发布。
图23是本发明实施例信息处理方法的另一流程图，该方法应用于上述实信息处理装置。如图23所示，该方法还可以进行如下步骤：
步骤2301，将接口适配器a转换后的第一或第二预定义的数据结构通过与网关连接器连接的接口适配器c(未示出)发送至网关连接器；
步骤2302，网关连接器将接收到的数据结构发送至其他信息处理装置。
值得注意的是，以上附图21至23的流程可以单独进行，也可以结合起来进行，可以根据实际需要确定具体的实施方式。
以下将通过一个具体的实施方式对上述信息处理方法进行示例性的说明，其中，该信息处理装置可用于滑坡管理系统，图24是该滑坡安全管理装置的构成示意图，图25-28是集中式规则引擎中设定的各个外部应用系统之间的控制规则示意图，如图25-28所示，在全站仪定位应用系统(Total Position Station，TPS)检测出现山体滑坡时，相关的突发事件也会存储至GeoMoS数据库，该信息处理装置与GeoMoS应用 系统通过接口适配器a相连，接口适配器a接收来自GeoMoS存储的数据(步骤2101)，将其转换为预定义的数据结构(步骤2102)，传递至与该信息处理装置的接口适配器b相连的其他应用系统(步骤2103)中，将接口适配器a转换后的数据发送至通用传感器接口(Common Sensor Interface，CSI，相当于通用属性集成器)(步骤2201)，CSI将接收到的数据转换为第三预定义的数据结构，如JavaScript Object Notation流(步骤2202)，将并将转换后的JSON流发布至地理信息系统(Geographic Information System,GIS)地图客户端上(步骤2203和步骤2204)。
另外，接口适配器a转换后的数据可以传递至与该信息处理装置的接口适配器c相连的安保管理应用中，通过UDP广播的形式发送给安保客户端，在安保客户端证实该警报后，将该证实后的警报通过该信息处理装置的接口适配器d传递至与接口适配器d连接的I/CAD应用，I/CAD应用在接收到发生的事件后，及时通知其客户端和网关(Gateway，GW)(步骤2301)(相当于网关连接器)，并通过GW将事件上报至上一级的信息处理装置(步骤2302)。
由上述实施例可知，通过本实施例的信息处理方法，使得滑坡管理系统能够更容易的实现各种现有应用集成，可扩展性强，又不影响各个系统的独立性。
实施例2
本发明实施例2提供了一种信息处理系统，图29是本发明实施例2的信息处理系统构成示意图，请参照图29，该信息处理系统2900包括至少一个如实施例1所述的信息处理装置2901；其中，所述信息处理装置2901用于连接多个外部应用系统，并使用预先设置的规则进行控制，以实现多个所述外部应用系统之间的数据交互和功能调用。
在一种实施方式中，所述信息处理装置为两个以上；两个以上的所述信息处理装置通过网关连接器互相连接，以实现不同的所述信息处理装置之间的数据交互和功能调用。
在本实施例中，图30是该信息处理系统一构成示意图，其中，多个外部应用系统也可以是本实施例2中的信息处理系统2901。
本发明实施例的上述系统可以适用于多种实施场景，以下仅是示例性的说明，本实施例并不限制于此。
在一个实施场景中，该系统可用于水库安全管理，图31是该水库安全管理系统的构成示意图，如图31所示，该系统包括多个业务应用，例如CAD调度应用、紧急响应应用、文件管理应用等，图31是一种多层级水库安全管理系统的构成示意图，通过图31所示的系统，能够在水库发现水情、雨情、工情、气象、灾害等信息时将实时监测的信息以及资源信息等及时共享，上报，便于应急指挥调度。
在另一个实施场景中，该系统可用于企业管理，图32是该企业管理系统的构成示意图，如图32所示，该系统包括多个业务应用，例如客户关系管理(Customer Relationship Management,CRM)、财务资源管理应用、网络安全应用(Authentication Authorization Accounting,AAA)等，该信息处理装置可以使与该装置连接的各个应用的数据进行交互实现数据共享，并可将各个应用的数据发布至个人客户端以便企业用户及时掌握，从而提高了企业管理的效率。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。
为了描述的方便，描述以上装置时以功能分为各种单元分别描述。当然，在实施本申请时可以把各单元的功能在同一个或多个软件和/或硬件中实现。
通过以上的实施方式的描述可知，本领域的技术人员可以清楚地了解到本申请可借助软件加必需的通用硬件平台的方式来实现。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。该计算机软件产品可以包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例或者实施例的某些部分所述的方法。
该计算机软件产品可以存储在内存中，内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。
计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储 器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括短暂电脑可读媒体(transitory media)，如调制的数据信号和载波。
本说明书中，对于系统实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例的部分说明即可。
本申请可用于众多通用或专用的计算机系统环境或配置中。例如：个人计算机、服务器计算机、手持设备或便携式设备、平板型设备、多处理器系统、基于微处理器的系统、置顶盒、可编程的消费电子设备、网络PC、小型计算机、大型计算机、包括以上任何系统或设备的分布式计算环境等等。
本申请可以在由计算机执行的计算机可执行指令的一般上下文中描述，例如程序模块。一般地，程序模块包括执行特定任务或实现特定抽象数据类型的例程、程序、对象、组件、数据结构等等。也可以在分布式计算环境中实践本申请，在这些分布式计算环境中，由通过通信网络而被连接的远程处理设备来执行任务。在分布式计算环境中，程序模块可以位于包括存储设备在内的本地和远程计算机存储介质中。
虽然通过实施例描绘了本申请，本领域普通技术人员知道，本申请有许多变形和变化而不脱离本申请的精神，希望所附的权利要求包括这些变形和变化而不脱离本申请的精神。

Claims (20)

  1. 一种信息处理装置，其中，所述信息处理装置包括：
    一个或多个接口适配器，每个所述接口适配器连接一个外部应用系统，用于实现多个所述外部应用系统之间的数据交互和功能调用；
    集中式规则引擎，所述集中式规则引擎连接所述一个或多个接口适配器，用于使用预先设置的规则，来控制与所述接口适配器连接的多个所述外部应用系统之间的数据交互和功能调用。
  2. 根据权利要求1所述的信息处理装置，其中，所述接口适配器包括：
    第一交互单元，将来自所述外部应用系统的数据转换成第一预定义的数据结构；
    第二交互单元，将来自所述外部应用系统的控制信息转换成第二预定义的数据结构。
  3. 根据权利要求1所述的信息处理装置，其中，所述集中式规则引擎包括：
    设定单元，用于预先设定所述规则，所述规则包括触发条件以及进行的相应处理；
    处理单元，用于在满足所述触发条件时，根据所述规则进行相应的处理。
  4. 根据权利要求3所述的信息处理装置，其中，所述设定单元根据如下信息的其中之一或其组合对所述规则进行设定：结果驱动、事件驱动、时间驱动和状态驱动的信息。
  5. 根据权利要求1所述的信息处理装置，其中，所述信息处理装置还包括：
    通用属性集成器，用于接收多个所述接口适配器发送的数据或控制信息，并将所述数据或控制信息转换成第三预定义的数据结构。
  6. 根据权利要求5所述的信息处理装置，其中，所述信息处理装置还包括：
    数据发布器，用于发布所述通用属性集成器转换后的数据结构，以对多个外部客户端提供服务。
  7. 根据权利要求1所述的信息处理装置，其中，所述信息处理装置还包括：
    网关连接器，与所述接口适配器以及其他信息处理装置相连接，以实现不同的所述信息处理装置之间的数据交互和功能调用。
  8. 根据权利要求1所述的信息处理装置，其中，所述信息处理装置还包括：
    显示操作器，用于显示和操作所述接口适配器输出的数据和控制信息。
  9. 一种信息处理方法，其中，所述方法包括：
    接口适配器接收外部应用系统传递的数据和控制信息；
    所述接口适配器将来自所述外部应用系统的数据和控制信息转换为预定义的数据结构；并发送至集中式规则引擎，以便所述集中式规则引擎根据预先设置的规则，来控制与多个接口适配器连接的多个所述外部应用系统之间的数据交互和功能调用。
  10. 根据权利要求9所述的信息处理方法，其中，所述接口适配器将来自所述外部应用系统的数据和控制信息转换为预定义的数据结构包括：
    将来自所述外部应用系统的数据转换成第一预定义的数据结构；
    将来自所述外部应用系统的控制信息转换成第二预定义的数据结构。
  11. 根据权利要求9所述的信息处理方法，其中，所述方法还包括：
    所述接口适配器将转换后的预定义的数据结构发送至通用属性集成器；以便所述通用属性集成器将接收到的数据结构转换为第三预定义的数据结构并发送至数据发布器，使所述数据发布器通过广播或定制的方式将接收到的数据进行发布。
  12. 根据权利要求9所述的信息处理方法，其中，所述方法还包括：
    所述接口适配器将转换后的预定义的数据结构通过与网关连接器连接的第二接口适配器发送至网关连接器，以便所述网关连接器将接收到的数据结构发送至其他信息处理装置。
  13. 根据权利要求9所述的信息处理方法，其中，所述集中式规则引擎根据预先设置的规则，来控制与所述接口适配器连接的多个所述外部应用系统之间的数据交互和功能调用包括：预先设定所述规则，所述规则包括触发条件以及进行的相应处理；并在满足所述触发条件时，根据所述规则进行相应的处理。
  14. 根据权利要求13所述的信息处理方法，其中，所述规则根据如下信息的其中之一或其组合进行设定：结果驱动、事件驱动、时间驱动和状态驱动的信息。
  15. 一种信息处理方法，其中，所述方法包括：
    集中式规则引擎接收通过接口适配器发送的将来自所述外部应用系统的数据和控制信息转换后的预定义的数据结构；
    所述集中式规则引擎根据预先设置的规则，来控制与多个所述接口适配器连接的多个所述外部应用系统之间的数据交互和功能调用。
  16. 根据权利要求15所述的信息处理方法，其中，所述接口适配器发送的将来 自所述外部应用系统的数据和控制信息转换为预定义的数据结构包括：
    将来自所述外部应用系统的数据转换成第一预定义的数据结构；
    将来自所述外部应用系统的控制信息转换成第二预定义的数据结构。
  17. 根据权利要求15所述的信息处理方法，其中，所述集中式规则引擎根据预先设置的规则，来控制与所述接口适配器连接的多个所述外部应用系统之间的数据交互和功能调用包括：预先设定所述规则，所述规则包括触发条件以及进行的相应处理；并在满足所述触发条件时，根据所述规则进行相应的处理。
  18. 根据权利要求17所述的信息处理方法，其中，所述规则根据如下信息的其中之一或其组合进行设定：结果驱动、事件驱动、时间驱动和状态驱动的信息。
  19. 一种信息处理系统，其中，所述信息处理系统包括至少一个如权利要求1所述的信息处理装置；
    其中，所述信息处理装置通过接口适配器连接多个外部应用系统，并使用预先设置的规则进行控制，以实现多个所述外部应用系统之间的数据交互和功能调用。
  20. 根据权利要求19中所述的信息处理系统，其中，所述信息处理装置为两个以上；两个以上的所述信息处理装置通过网关连接器互相连接，以实现不同的所述信息处理装置之间的数据交互和功能调用。
PCT/CN2015/081349 2014-06-13 2015-06-12 信息处理方法、装置和系统 WO2015188781A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US15/316,906 US10176024B2 (en) 2014-06-13 2015-06-12 Information processing method, device and system
EP15806031.9A EP3156898A4 (en) 2014-06-13 2015-06-12 Information processing method, device and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410264516.7 2014-06-13
CN201410264516.7A CN105320440B (zh) 2014-06-13 2014-06-13 信息处理方法、装置和系统

Publications (1)

Publication Number Publication Date
WO2015188781A1 true WO2015188781A1 (zh) 2015-12-17

Family

ID=54832922

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/081349 WO2015188781A1 (zh) 2014-06-13 2015-06-12 信息处理方法、装置和系统

Country Status (4)

Country Link
US (1) US10176024B2 (zh)
EP (1) EP3156898A4 (zh)
CN (1) CN105320440B (zh)
WO (1) WO2015188781A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110784517A (zh) * 2019-09-20 2020-02-11 北京海益同展信息科技有限公司 基于区块链的业务应用集成方法、系统、终端及存储介质
US10599492B2 (en) 2017-10-27 2020-03-24 International Buisness Machines Corporation Context-aware connectors in integration
CN112883075A (zh) * 2021-01-22 2021-06-01 中国地质环境监测院(自然资源部地质灾害技术指导中心) 一种滑坡普适型地表位移监测数据缺失及异常值处理方法

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9961154B1 (en) 2014-04-28 2018-05-01 State Farm Mutual Automobile Insurance Company Web service gateway
CN107818010A (zh) * 2016-09-08 2018-03-20 北京嘀嘀无限科技发展有限公司 不同地图之间切换的方法和装置
EP3522015A1 (en) 2018-02-05 2019-08-07 Hexagon Technology Center GmbH Workflow generation
EP3522003A1 (en) 2018-02-05 2019-08-07 Hexagon Technology Center GmbH Workflow generation
EP3579174A1 (en) 2018-06-08 2019-12-11 Hexagon Technology Center GmbH Mobile vehicles in manufacturing
EP3579161A1 (en) 2018-06-08 2019-12-11 Hexagon Technology Center GmbH Workflow deployment
EP3605414B1 (en) 2018-08-02 2023-06-14 Hexagon Technology Center GmbH Power network management
EP3648030A1 (en) 2018-10-29 2020-05-06 Hexagon Technology Center GmbH Authenticity verification of a digital model
CN114519917A (zh) 2018-10-29 2022-05-20 赫克斯冈技术中心 移动监视系统
US11323447B2 (en) 2019-07-09 2022-05-03 Hexagon Technology Center Gmbh Digital data access control and automated synthesization of capabilities
EP4141668A1 (en) 2019-07-09 2023-03-01 Hexagon Technology Center GmbH System for controlling access to digital data and algorithms
EP3842946A1 (en) 2019-12-23 2021-06-30 Hexagon Technology Center GmbH Method and system for automatically identifying and synthesizing capabilities

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050091663A1 (en) * 2003-03-28 2005-04-28 Bagsby Denis L. Integration service and domain object for telecommunications operational support
US20100100809A1 (en) * 2008-10-21 2010-04-22 At&T Intellectual Property, I, L.P. Multi-modal/multi-channel application tool architecture
CN101706738A (zh) * 2009-10-29 2010-05-12 中国联合网络通信集团有限公司 流程应用系统
CN102760184A (zh) * 2012-06-12 2012-10-31 中国电力科学研究院 一种异构电力应用系统的信息交互方法
CN102938731A (zh) * 2012-11-22 2013-02-20 北京锐易特软件技术有限公司 一种基于代理缓存适配模型的交换集成装置及方法

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5646862A (en) * 1994-09-29 1997-07-08 Ford Motor Company Vendor-neutral integrated vehicle electrical design and analysis system and method
US5708828A (en) * 1995-05-25 1998-01-13 Reliant Data Systems System for converting data from input data environment using first format to output data environment using second format by executing the associations between their fields
US6208345B1 (en) * 1998-04-15 2001-03-27 Adc Telecommunications, Inc. Visual data integration system and method
US6453356B1 (en) * 1998-04-15 2002-09-17 Adc Telecommunications, Inc. Data exchange system and method
US20050038911A1 (en) * 1999-04-30 2005-02-17 Yoshikuni Watanabe Cooperative system and method therefor
WO2003027813A2 (en) * 2001-09-28 2003-04-03 Sap Ag Portable business information content and management system
US8438238B2 (en) * 2002-10-16 2013-05-07 Sap Ag Master data access
JP2005293047A (ja) * 2004-03-31 2005-10-20 Fujitsu Ltd データ交換システム、方法及びプログラム
US10657540B2 (en) * 2011-01-29 2020-05-19 Sdl Netherlands B.V. Systems, methods, and media for web content management
US20140316830A1 (en) * 2013-04-17 2014-10-23 CloudLogix, LLC Synchronized Resource Planning
US20150339339A1 (en) * 2014-05-23 2015-11-26 Salesforce.Com, Inc. Integrating data from data sources for assigning an entity to a database record

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050091663A1 (en) * 2003-03-28 2005-04-28 Bagsby Denis L. Integration service and domain object for telecommunications operational support
US20100100809A1 (en) * 2008-10-21 2010-04-22 At&T Intellectual Property, I, L.P. Multi-modal/multi-channel application tool architecture
CN101706738A (zh) * 2009-10-29 2010-05-12 中国联合网络通信集团有限公司 流程应用系统
CN102760184A (zh) * 2012-06-12 2012-10-31 中国电力科学研究院 一种异构电力应用系统的信息交互方法
CN102938731A (zh) * 2012-11-22 2013-02-20 北京锐易特软件技术有限公司 一种基于代理缓存适配模型的交换集成装置及方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3156898A4 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10599492B2 (en) 2017-10-27 2020-03-24 International Buisness Machines Corporation Context-aware connectors in integration
CN110784517A (zh) * 2019-09-20 2020-02-11 北京海益同展信息科技有限公司 基于区块链的业务应用集成方法、系统、终端及存储介质
CN112883075A (zh) * 2021-01-22 2021-06-01 中国地质环境监测院(自然资源部地质灾害技术指导中心) 一种滑坡普适型地表位移监测数据缺失及异常值处理方法
CN112883075B (zh) * 2021-01-22 2024-04-05 中国地质环境监测院(自然资源部地质灾害技术指导中心) 一种滑坡普适型地表位移监测数据缺失及异常值处理方法

Also Published As

Publication number Publication date
US10176024B2 (en) 2019-01-08
US20170123865A1 (en) 2017-05-04
CN105320440A (zh) 2016-02-10
CN105320440B (zh) 2020-06-16
EP3156898A4 (en) 2018-02-21
EP3156898A1 (en) 2017-04-19

Similar Documents

Publication Publication Date Title
WO2015188781A1 (zh) 信息处理方法、装置和系统
Hammoudeh et al. A service-oriented approach for sensing in the Internet of Things: Intelligent transportation systems and privacy use cases
US9781189B2 (en) Managed device-to-device communication in business computing systems
EP2378741B1 (en) Systems and Methods for Conducting Communications Among Components of Multidomain Industrial Automation System
US20150163179A1 (en) Execution of a workflow that involves applications or services of data centers
TWI519965B (zh) Flexible assembly system and method for cloud service service for telecommunication application
US8984533B2 (en) Systems and methods for conducting communications among components of multidomain industrial automation system
US8484401B2 (en) Systems and methods for conducting communications among components of multidomain industrial automation system
JP2010231759A (ja) モバイルクラウドプラットホームを具備したモバイル端末装置
US20140201418A1 (en) Net-centric adapter for interfacing enterprises systems to legacy systems
WO2018116933A1 (ja) Ｒｐｃ変換処理システムおよびｒｐｃ変換方法
CN103747004A (zh) 物联网平台通信协议的实现方法
US20210034338A1 (en) Communications Enablement Platform, System, and Method
JP6901290B2 (ja) クラウド中継装置、クラウド接続処理方法、及びプログラム
US12003404B2 (en) Information centric network protocol for federated learning
US20100241712A1 (en) Method and System for a Distributed and Extensible Communication Framework
KR101587500B1 (ko) 클라우드 기반 스마트 디바이스 협업 플랫폼 구축 시스템 및 그 시스템을 이용한 스마트 디바이스 협업 서비스 제공 방법
US10432448B2 (en) Systems and methods for stream-based, protocol-agnostic messaging
Di Modica et al. SNPS: an OSGi-based middleware for Wireless Sensor Networks
CN112953992A (zh) 网络系统、通信与组网方法、设备及存储介质
Emeakaroha et al. Contemporary analysis and architecture for a generic cloud-based sensor data management platform.
Joshi et al. The industrial internet of things connectivity framework
US10659385B2 (en) Provisioning insight services in a data provider landscape
KR101603531B1 (ko) 클라우드 컴퓨팅 기반 SaaS 형태의 동영상 서비스 시스템 및 그 방법
Zamkovyi et al. Algorithmic Support for Building a Distributed IoT System in a Cloud Service

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15806031

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 15316906

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2015806031

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2015806031

Country of ref document: EP