CN114285876A - Application interconnection framework for industrial manufacturing - Google Patents
Application interconnection framework for industrial manufacturing Download PDFInfo
- Publication number
- CN114285876A CN114285876A CN202111578995.6A CN202111578995A CN114285876A CN 114285876 A CN114285876 A CN 114285876A CN 202111578995 A CN202111578995 A CN 202111578995A CN 114285876 A CN114285876 A CN 114285876A
- Authority
- CN
- China
- Prior art keywords
- service
- platform
- application
- message
- interconnection bus
- Prior art date
- Legal status (The legal status 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 status listed.)
- Granted
Links
- 238000004519 manufacturing process Methods 0.000 title claims abstract description 54
- 230000005540 biological transmission Effects 0.000 claims abstract description 23
- 238000007726 management method Methods 0.000 claims description 81
- 238000012544 monitoring process Methods 0.000 claims description 34
- 238000006243 chemical reaction Methods 0.000 claims description 31
- 238000000034 method Methods 0.000 claims description 26
- 230000008569 process Effects 0.000 claims description 18
- 238000012545 processing Methods 0.000 claims description 18
- 230000004044 response Effects 0.000 claims description 17
- 230000002159 abnormal effect Effects 0.000 claims description 15
- 238000004364 calculation method Methods 0.000 claims description 13
- 238000011161 development Methods 0.000 claims description 13
- 238000013475 authorization Methods 0.000 claims description 12
- 238000004458 analytical method Methods 0.000 claims description 11
- 238000012423 maintenance Methods 0.000 claims description 11
- 238000004891 communication Methods 0.000 claims description 9
- 238000012795 verification Methods 0.000 claims description 5
- 238000010276 construction Methods 0.000 claims description 3
- 238000012937 correction Methods 0.000 claims description 3
- 238000013461 design Methods 0.000 claims description 3
- 230000002708 enhancing effect Effects 0.000 claims description 3
- 230000007246 mechanism Effects 0.000 claims description 3
- 238000004806 packaging method and process Methods 0.000 claims description 3
- 238000007619 statistical method Methods 0.000 claims description 3
- 238000012360 testing method Methods 0.000 claims description 3
- 230000003044 adaptive effect Effects 0.000 claims 1
- 230000002452 interceptive effect Effects 0.000 abstract 1
- 238000001514 detection method Methods 0.000 description 10
- 238000012546 transfer Methods 0.000 description 8
- GNFTZDOKVXKIBK-UHFFFAOYSA-N 3-(2-methoxyethoxy)benzohydrazide Chemical compound COCCOC1=CC=CC(C(=O)NN)=C1 GNFTZDOKVXKIBK-UHFFFAOYSA-N 0.000 description 6
- 239000000725 suspension Substances 0.000 description 6
- 230000009849 deactivation Effects 0.000 description 4
- 230000010354 integration Effects 0.000 description 4
- 230000008901 benefit Effects 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 239000002699 waste material Substances 0.000 description 2
- 238000013523 data management Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
Images
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]
Landscapes
- Computer And Data Communications (AREA)
Abstract
The application belongs to the technical field of information, and provides an application interconnection architecture for industrial manufacturing, which solves the problems of application interconnection and interoperability and interoperation for enterprises in a service form and breaks enterprise information islands. The problems of protocol inconsistency, format inconsistency, data transmission stability, data transmission safety and the like in the data exchange of the service system are solved. The complex network relation among the services is clarified, and the internal information exchange of the enterprise is presented clearly to realize an interactive architecture. Through realizing service management and control and service treatment, help the enterprise realize the manufacturing of wisdom, the production of intelligence.
Description
Technical Field
The invention relates to an application interconnection architecture for industrial manufacturing. The method solves the problems of application interconnection and intercommunication and interoperation for enterprises in the form of service, breaks through enterprise information islands, eliminates the problems of protocol inconsistency, format inconsistency, data transmission stability, data transmission safety and the like in data exchange of a business system, clarifies complex mesh relation among services, clearly presents the internal information exchange process of the enterprise, helps the enterprises to realize intelligent manufacturing and intelligent production by realizing service management and control and service management, and belongs to the technical field of information.
Background
With the development of the information era, manufacturing enterprises introduce a plurality of information application systems in order to coordinate and complete execution and management work of internal and external services, but the systems only pay attention to data management and service processing in the field of the systems, so that information resources of the enterprises are disorderly and dispersed, a plurality of information islands are formed, the information islands hinder cooperation among departments, services and organizations, operations such as plan out-of-control, excessive stock, blind purchase and the like which are not beneficial to normal development of the enterprises can also occur, and serious consequences such as ineffective labor, resource waste, benefit loss and the like are brought to the enterprises.
At present, known enterprises mainly manage information islands through point-to-point integration between systems, but due to the fact that internet technologies, development environments, development languages, technical standards, use platforms, tools and the like used by the systems in the enterprises are different, point-to-point integrated services are difficult to reuse, and a large amount of repeated development and joint debugging work is caused. With the increase of systems, complex mesh relationships are formed among services, and in a complete business chain, the relationship between the services is difficult to be combed, and whether the services depend on each other or not is difficult to be combed; because point-to-point integration has no unified specification and technical standard, the capability support of service management and service in multiple aspects of safety, logging, abnormal monitoring, routing, message publishing, subscription and the like is lacked, and the intelligent manufacturing and intelligent production of enterprises are not facilitated.
Disclosure of Invention
Aiming at the problems that at present, a plurality of information application systems are introduced to a manufacturing enterprise to coordinate and complete the execution and management work of internal and external services, and because the difference of communication protocols exists among different systems, the information resources of the enterprise are broken down and scattered, a plurality of information isolated islands are formed, the cooperation among cross-department, cross-service and cross-organization is blocked, the problems that plan is out of control, inventory is excessive, blind purchase and the like are not beneficial to the normal development of the enterprise, and ineffective labor, resource waste, benefit loss and the like are brought to the enterprise are easily caused, the invention provides an application interconnection architecture for industrial manufacturing, solves the problems of application interconnection and intercommunication and interoperation for the enterprise through the form of service, and helps the enterprise to realize intelligent manufacturing and intelligent production, and comprises the following steps:
A. establishing an application interconnection architecture model for industrial manufacturing;
B. establishing an industrial manufacturing application interconnection bus platform through an industrial manufacturing application interconnection architecture model;
C. and finishing the work flow of the application interconnection architecture model of the industrial manufacturing.
The step A is characterized in that: the application interconnection architecture for industrial manufacturing develops the design of an application interconnection bus core engine, a service management platform, a service release platform, a service shop platform and a service monitoring platform by an application service bus message flow operating environment, as shown in fig. 1, wherein the application service bus message flow operating environment is a message middleware for supporting the industrial manufacturing application interconnection bus platform and provides a message flow driving operating environment; the application interconnection bus core engine comprises a protocol adapter and a message flow template, and provides functions of security authentication, format conversion, protocol conversion, path selection, load balancing, flow control, log recording and message transmission, wherein the protocol adapter comprises a REST adapter, a WS adapter, an AMQP adapter, a RFC adapter, an SMTP adapter and an FTP adapter, and supported protocols comprise a presentation layer state transfer protocol REST, a simple object access protocol WS, a high-level message queue protocol AMQP, a remote function call protocol RFC, a simple mail transfer protocol SMTP and a file transfer protocol FTP; the service management platform has the functions of platform operation and maintenance, authorization management and life cycle management; the service publishing platform has the functions of service registration, service publishing and service management; the functions of the service store platform comprise a service directory, service subscription and service trial; the functions of the service monitoring platform comprise service transaction statistics, service quantity statistics, service quality analysis, service monitoring, platform monitoring and abnormal alarm.
The step A is characterized in that: the service management platform comprises platform operation and maintenance, authorization management and life cycle management, and specifically comprises the following functions:
(1) the platform operation and maintenance is used for maintaining an industrial manufacturing application interconnection bus platform by an administrator, and comprises log management, system registration and protocol adapter registration, wherein the log management is used for analyzing log records and searching the reason of the problem when the industrial manufacturing application interconnection bus platform is abnormal, and the managed logs comprise system logs, application program logs, safety logs and transaction logs of services; system registration for an administrator to register a related application system, the implementation of which comprises the steps of: firstly, the system basic information configuration comprises a system name, a system abbreviation, a system type, a system deployment area and a system description; generating a unique system identifier according to the application type and the deployment area of the system; thirdly, completing the configuration of the outbound/inbound protocol of the system according to the communication protocol supported by the system; realizing the safety certification of the system according to the application requirement, wherein the certification mode comprises binding of an MAC address, an IP black and white list, physical port binding, digital visa and session verification; storing system basic information, system identification, system outbound/inbound protocol and system security authentication information to a database; the protocol adapter registration is used for the administrator to register the relevant protocol adapter according to the parameter requirement of the protocol adapter;
(2) authorizing and managing a request authority for managing a login authority and a service of a user;
(3) lifecycle management is used to manage the lifecycle state of a service and to describe the relationships between the various phases of the service lifecycle,
1) the service lifecycle includes the following states:
in the creation, the service is not created completely, and the service shop platform does not display the service;
releasing to show that the service is created and the service shop platform does not display the service;
third, release, which represents that the service has been created, the service shop platform displays the service, and the service can be subscribed/requested by the service requester;
pause, which means that the service is executed with pause operation, the service shop platform does not display the service, and the service can not be subscribed/requested by the service requester;
deactivating, which means that the service has been deleted by the industrial manufacturing application interconnect bus platform, the service shop platform does not display the service, and the service cannot be subscribed/requested by the service requester;
2) the relationship of the changes in each phase of the service life cycle is shown in fig. 2, and includes the following relationships:
firstly, when a service application is issued and is not examined and approved, the service life cycle is changed from creation to release;
when the service application is not approved, the service life cycle is changed from to be issued to be created;
when the service application is approved, the service life cycle is changed from to be released;
when the suspension operation is executed on the published service, the service life cycle is changed from published to suspended;
when the release operation is executed on the suspended service, the service life cycle is changed from suspended to released;
when the suspension service reappears for release but is not approved, the service life cycle is changed from suspension to release;
when the service application to be issued is changed from pause to approval and fails, the service life cycle is changed from pause to issue;
when the pause service is executed with the deactivation operation, the service life cycle is changed from pause to deactivation.
The step A is characterized in that: the service publishing platform comprises service registration, service management and service publishing, and specifically comprises the following functions:
(1) service registration is used for a service provider to register various types of services, and comprises the following steps:
firstly, selecting a service provider and completing service basic information configuration, wherein the service basic information configuration comprises a service name, a service type, service request overtime and service description;
generating a unique service identifier according to the service provider and the service category;
completing service expansion configuration, including request parameter description, response parameter description, request message example and response message example;
completing special service setting including service priority, maximum request message and maximum transaction times TPS completed per second;
fifthly, configuring a service provider interface address and a request mode according to a service provider application program interface, wherein the interface address is the access path information of the service provider application program public resource;
sixthly, storing the service basic information, the service identification, the service expansion configuration, the service special setting, the service provider interface address and the request mode to a database;
(2) the service management is used for the service provider to manage the registered services, including modifying services, deleting services, testing services and releasing services;
(3) the service publishing is used for the service provider to publish and apply for the registered service, and the published service after application is passed is used for the service requester to subscribe/request.
The step A is characterized in that: the service store platform function comprises a service directory, service subscription and service trial, wherein the service directory is used for presenting published services in the service store platform in the form of a directory, and a service requester retrieves and views the services in the directory and performs trial and subscription on the services; the service subscription is used for the service requester to initiate a subscription application for the service which is not subscribed in the service store platform; the service trial is used for making online calls to the published service in the service store platform.
The step A is characterized in that: the application interconnection bus core engine function comprises security authentication, format conversion, protocol conversion, log recording, path selection, flow control, message transmission and load balancing, wherein the security authentication comprises the following steps: the system is used for realizing the safety certification of a service requester system according to application requirements, and the certification mode comprises binding of an MAC address, an IP black and white list, physical port binding, digital visa and session verification; format conversion: when the message formats of the service requester and the service provider are inconsistent, the application interconnection bus core engine autonomously realizes the format conversion of the message according to the message formats of the service requester and the service provider in the service registration information; protocol conversion: when the communication protocols of the service requester and the service provider are inconsistent, the application interconnection bus core engine autonomously selects a corresponding protocol adapter according to the corresponding communication protocols of the service requester and the service provider, so as to realize the transmission of messages among different protocols; logging: the system comprises a log component, a service monitoring platform and a data processing module, wherein the log component is used for applying a log component in an interconnection bus core engine, recording each transaction behavior of the service, and providing data for statistics and analysis for the service monitoring platform; path selection: the method comprises the steps that after a message enters an application interconnection bus core engine, an interface address provided by a service provider is selected autonomously, and the message is sent to the service provider through the selected address; flow control: firstly, setting a maximum request message M of service and a maximum transaction frequency TPS completed per second, secondly, obtaining a corresponding request message quantity M ' and a corresponding transaction frequency TPS completed per second by using an interconnection bus core engine according to a request provided by a service request party, and if M is less than M ' or TPS is less than TPS ', sending error information to the service request party by using the interconnection bus core engine; load balancing: the system comprises a service provider, a service request module and a service processing module, wherein the service provider is used for enhancing the concurrent processing capacity when the service provider receives the service request and relieving the processing pressure of a single interface address, and the service request represents that a service requester requests the service of the service provider through an application interconnection bus core engine; the load balancing operation steps are shown in fig. 3, and include the following steps:
starting a load function in service registration information;
inputting an interface address of a service provider;
selecting a load rule, and selecting one of a polling rule, a weight rule and a dynamic calculation rule;
and fourthly, when the weight rule is selected, setting a corresponding empirical weight coefficient for each interface address.
The step A is characterized in that: the load rules in the load balancing function include polling rules, weighting rules and dynamic calculation rules, and specifically include:
(1) and (3) polling rules: arranging interface addresses corresponding to each service according to an input sequence; when a service requester requests service, the service requester is sequentially taken out from the interface address arrangement corresponding to the service according to the request sequence and called;
(2) the weight rule is as follows: setting a corresponding weight coefficient for each interface address, when a service requester requests service, obtaining an effective weight coefficient through a calculation rule, and obtaining a maximum effective weight coefficient by combining a plurality of effective weight coefficient set self-adaptive iteration mechanisms, wherein the effective weight coefficient set is beta, beta', and then obtaining the corresponding interface address; in any single poll, the weight rule flow is shown in fig. 4, and includes the following steps:
get service F1N interface addresses;
② the interface address set is
Corresponding set of weighting coefficients as
Setting a weight coefficient sum
The set of valid weight coefficients with an initial value of 0 is
Wherein i is more than or equal to 1 and less than or equal to n, and m is more than or equal to 11≤n，SiFor the address of the i-th interface,
is m at1An interface address, SnFor the nth interface address, αiSetting a weight coefficient for the ith interface address,
is m at1Set weighting factor, alpha, of individual interface addressesnFor setting a weight coefficient, beta, for the nth interface addressiIs the effective weight coefficient of the ith interface address,
is m at1Effective weight coefficient of an interface address, betanEffective weight coefficient for nth interface address;
third, when the service request party requests service F1Traversing the interface address set S, sequentially adding the corresponding elements of the set weight coefficient set and the effective weight coefficient set, and if the selected interface address is S in the traversing processiThen its corresponding effective weight coefficient is β'i＝αi+βiThe interface address after traversal is corresponding to a valid weight coefficient set of β '═ β'1,β'2,β'3,...,β'n}；
Fourthly, obtaining the maximum effective weight coefficient beta 'through an effective weight coefficient set beta'max；
Is beta through'maxThe value of (b) obtains its corresponding set of maximum effective weight coefficients in β
Wherein m is more than or equal to 11＜m2＜...＜mn≤n；
Sixthly, passing through beta'mObtaining effective weight coefficients
And its corresponding interface address
Is obtained by
To interface address
Is given by
Is replaced by
When all the interface address effective weight coefficients are 0, finishing single polling, otherwise waiting for next service request party to request service F1。
(3) Dynamically calculating rules: as shown in FIG. 5, this is accomplished by first serving F2Setting an initial empirical weight coefficient eta for each interface address; then, the service requester requests service F2Then using the weight rule to obtain the corresponding interface address; second, when a single poll is complete, service F is acquired2Historical request information recorded in the log, which includes the smallest request message S within a single pollminMinimum response message MminAnd maximum successful response time TmaxAverage request message S corresponding to single interface addressavgAverage response message MavgTime-consuming average T of complete successful transactionavgAnd the transaction success rate R and the weight coefficient of the next polling of each interface address are obtained
Where μ is a correction factor (μ e N)*)；After that, every time when the single polling is finished, the weight coefficient of the next polling of each interface address is obtained through the history information recorded in the log; finally, when service F2When the interface address information is changed, the core engine of the application interconnection bus stops the current dynamic calculation rule.
The step B is characterized in that: the process of establishing the industrial manufacturing application interconnection bus platform through the industrial manufacturing application interconnection architecture model comprises the following steps: firstly, message middleware is used for realizing the transmission of messages among multi-source heterogeneous information systems; then abstracting and packaging the message transmission function in the message stream operating environment, realizing the construction of an application interconnection bus core engine, and completing security authentication, format conversion, protocol conversion, path selection, load balancing, flow control and log recording in the message transmission process; secondly, constructing a service management platform for managing an application interconnection bus core engine, and constructing a graphical report for statistical analysis provided by a service monitoring platform; and finally, constructing a service publishing platform and a service shop platform for the third-party system to use.
The step C is characterized in that: establishing an application interconnection architecture model work flow of industrial manufacturing, wherein the work flow comprises two stage flows of establishing an industrial manufacturing application interconnection bus platform and establishing service;
(1) the process for establishing the industrial manufacturing application interconnection bus platform comprises the following steps:
selecting a Message flow operating environment, wherein the Message flow operating environment specifically comprises an IBM Integration Bus, an IBM WebSphere Message Broker, an Oracle Service Bus, an Oracle Enterprise Service Bus and a Mule ESB;
completing the development of an application interconnection bus core engine in a message flow running environment, wherein the development specifically comprises a protocol adapter, a message flow template and components for providing security authentication, format conversion, protocol conversion, path selection, load balancing, flow control and diary recording;
developing a service management platform and a service monitoring platform, wherein the functions of the service management platform comprise platform operation and maintenance, authorization management and life cycle management; the functions of the service monitoring platform comprise service transaction statistics, service quantity statistics, service quality analysis, service monitoring, platform monitoring and abnormal alarm;
developing a service release platform and a service shop platform, wherein the functions of the service release platform comprise service registration, service release and service management; the functions of the service store platform comprise a service directory, service subscription and service trial;
deploying in a manner of public cloud deployment, private cloud deployment, community cloud deployment, hybrid cloud deployment and local deployment, wherein the deployment mode comprises a traditional mode, a virtualization mode and a container deployment mode;
and sixthly, completing platform configuration on the service management platform, completing service creation, release, viewing and subscription on the service release platform and the service store platform, and finally completing service message transmission through the application interconnection bus core engine.
(2) The service creation includes:
firstly, realizing system registration and protocol adapter configuration in a service management platform;
secondly, logging in the publishing platform, and the system defined in the service management platform realizes the registration, management and publishing of the service through the publishing platform. After the authorization of the service management platform for the approval task to be published passes, the life cycle state of the service is changed into published, and at the moment, the service can be subscribed by other systems;
logging in the service shop platform, issuing the service authorized to pass by the platform, presenting the service in the service shop platform in a catalog form, and checking the service and trying and subscribing the service by the system defined by the service management platform through the service shop platform. After the authorization of the service management platform for the examination and approval task to be subscribed is passed, a system defined by the service management platform can request for the service;
the service requester realizes the service request through the application interconnection bus core engine, and records the transaction behavior of each service through the log component in the application interconnection bus core engine, wherein the service request process is as follows: firstly, a service requester sends a request message to an application interconnection bus core engine, the request message is subjected to format detection, message initialization, security authentication, flow control and path selection to complete the operation processing of the request message, then, a service provider receives the request message after the operation processing and sends a response message to the application interconnection bus core engine, the application interconnection bus core engine converts the response message into a message format required by the service requester through a protocol adapter and sends the message format to the service requester to complete the service request, wherein the operation processing flow of the request message is shown in fig. 6 and specifically comprises the following steps:
a. b, the application interconnection bus core engine obtains a request message Q sent by a service request party and transfers to the step b;
b. carrying out format detection on the request message Q, if the detection is passed, turning to the step c, otherwise, turning to the step g;
c. b, initializing the request message Q, converting the message format of the request message Q into a standard message format, and turning to the step d, wherein the initialized request message is represented as Q';
d. detecting the request message Q' through a safety certification function, if the detection is passed, turning to the step e, otherwise, turning to the step g;
e. detecting the request message Q' through a flow control function, if the detection is passed, turning to f, otherwise, turning to the step g;
f. sending the request message Q' to a corresponding service provider through a path selection function, and ending the process;
g. generating prompt information, sending the prompt information to a requester system, and ending the process;
the service monitoring platform obtains the transaction log data generated in the application interconnection bus core engine, displays the transaction log data in the service management platform, the service release platform and the service shop platform in real time in an analysis report form, and carries out abnormal alarm through mail/short message/WeChat/telephone voice when abnormal transaction occurs in the application interconnection bus core engine.
Drawings
FIG. 1 model of an application interconnect architecture for industrial manufacturing
FIG. 2 service lifecycle diagram
FIG. 3 is a schematic diagram of a load rule usage flow
FIG. 4 is a flow chart of one-time weighting rules
FIG. 5 is a flow chart of a dynamic calculation rule
FIG. 6 is a flow chart of the operation process
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
Step 1, establishing an application interconnection architecture model for industrial manufacturing, and developing the design of an application interconnection bus core engine, a service management platform, a service release platform, a service shop platform and a service monitoring platform by an application service bus message flow operating environment, as shown in fig. 1, wherein the application service bus message flow operating environment is a message middleware for supporting the industrial manufacturing application interconnection bus platform and provides a message flow driving operating environment; the application interconnection bus core engine comprises a protocol adapter and a message flow template, and provides functions of security authentication, format conversion, protocol conversion, path selection, load balancing, flow control, log recording and message transmission, wherein the protocol adapter comprises a REST adapter, a WS adapter, an AMQP adapter, a RFC adapter, an SMTP adapter and an FTP adapter, and supported protocols comprise a presentation layer state transfer protocol REST, a simple object access protocol WS, a high-level message queue protocol AMQP, a remote function call protocol RFC, a simple mail transfer protocol SMTP and a file transfer protocol FTP; the service management platform has the functions of platform operation and maintenance, authorization management and life cycle management; the service publishing platform has the functions of service registration, service publishing and service management; the functions of the service store platform comprise a service directory, service subscription and service trial; the functions of the service monitoring platform comprise service transaction statistics, service quantity statistics, service quality analysis, service monitoring, platform monitoring and abnormal alarm.
Step 2, constructing a service management platform, wherein the service management platform has the functions of platform operation and maintenance, authorization management and life cycle management, and specifically comprises the following steps:
(1) the platform operation and maintenance is used for maintaining an industrial manufacturing application interconnection bus platform by an administrator, and comprises log management, system registration and protocol adapter registration, wherein the log management is used for analyzing log records and searching the reason of the problem when the industrial manufacturing application interconnection bus platform is abnormal, and the managed logs comprise system logs, application program logs, safety logs and transaction logs of services; system registration for an administrator to register a related application system, the implementation of which comprises the steps of: firstly, the system basic information configuration comprises a system name, a system abbreviation, a system type, a system deployment area and a system description; generating a unique system identifier according to the application type and the deployment area of the system; thirdly, completing the configuration of the outbound/inbound protocol of the system according to the communication protocol supported by the system; realizing the safety certification of the system according to the application requirement, wherein the certification mode comprises binding of an MAC address, an IP black and white list, physical port binding, digital visa and session verification; storing system basic information, system identification, system outbound/inbound protocol and system security authentication information to a database; the protocol adapter registration is used for the administrator to register the relevant protocol adapter according to the parameter requirement of the protocol adapter;
(2) authorizing and managing a request authority for managing a login authority and a service of a user;
(3) lifecycle management is used to manage the lifecycle state of a service and to describe the relationships between the various phases of the service lifecycle,
1) the service lifecycle includes the following states:
in the creation, the service is not created completely, and the service shop platform does not display the service;
releasing to show that the service is created and the service shop platform does not display the service;
third, release, which represents that the service has been created, the service shop platform displays the service, and the service can be subscribed/requested by the service requester;
pause, which means that the service is executed with pause operation, the service shop platform does not display the service, and the service can not be subscribed/requested by the service requester;
deactivating, which means that the service has been deleted by the industrial manufacturing application interconnect bus platform, the service shop platform does not display the service, and the service cannot be subscribed/requested by the service requester;
2) the relationship of the changes in each phase of the service life cycle is shown in fig. 2, and includes the following relationships:
firstly, when a service application is issued and is not examined and approved, the service life cycle is changed from creation to release;
when the service application is not approved, the service life cycle is changed from to be issued to be created;
when the service application is approved, the service life cycle is changed from to be released;
when the suspension operation is executed on the published service, the service life cycle is changed from published to suspended;
when the release operation is executed on the suspended service, the service life cycle is changed from suspended to released;
when the suspension service reappears for release but is not approved, the service life cycle is changed from suspension to release;
when the service application to be issued is changed from pause to approval and fails, the service life cycle is changed from pause to issue;
when the pause service is executed with the deactivation operation, the service life cycle is changed from pause to deactivation.
Step 3, constructing a service publishing platform, wherein the service publishing platform has the functions of service registration, service management and service publishing, and specifically comprises the following steps:
(1) service registration is used for a service provider to register various types of services, and comprises the following steps:
firstly, selecting a service provider and completing service basic information configuration, wherein the service basic information configuration comprises a service name, a service type, service request overtime and service description;
generating a unique service identifier according to the service provider and the service category;
completing service expansion configuration, including request parameter description, response parameter description, request message example and response message example;
completing special service setting including service priority, maximum request message and maximum transaction times TPS completed per second;
fifthly, configuring a service provider interface address and a request mode according to a service provider application program interface, wherein the interface address is the access path information of the service provider application program public resource;
sixthly, storing the service basic information, the service identification, the service expansion configuration, the service special setting, the service provider interface address and the request mode to a database;
(2) the service management is used for the service provider to manage the registered services, including modifying services, deleting services, testing services and releasing services;
(3) the service publishing is used for the service provider to publish and apply for the registered service, and the published service after application is passed is used for the service requester to subscribe/request.
Step 4, a service store platform is built, the service store platform comprises the functions of a service directory, service subscription and service trial, wherein the service directory is used for presenting published services in the service store platform in the form of a directory, and a service requester retrieves and views the services in the directory and performs trial and subscription on the services; the service subscription is used for the service requester to initiate a subscription application for the service which is not subscribed in the service store platform; the service trial is used for making online calls to the published service in the service store platform.
Step 5, constructing an application interconnection bus core engine, wherein the functions of the application interconnection bus core engine comprise security authentication, format conversion, protocol conversion, log recording, path selection, flow control, message transmission and load balancing, and the security authentication comprises the following steps: the system is used for realizing the safety certification of a service requester system according to application requirements, and the certification mode comprises binding of an MAC address, an IP black and white list, physical port binding, digital visa and session verification; format conversion: when the message formats of the service requester and the service provider are inconsistent, the application interconnection bus core engine autonomously realizes the format conversion of the message according to the message formats of the service requester and the service provider in the service registration information; protocol conversion: when the communication protocols of the service requester and the service provider are inconsistent, the application interconnection bus core engine autonomously selects a corresponding protocol adapter according to the corresponding communication protocols of the service requester and the service provider, so as to realize the transmission of messages among different protocols; logging: the system comprises a log component, a service monitoring platform and a data processing module, wherein the log component is used for applying a log component in an interconnection bus core engine, recording each transaction behavior of the service, and providing data for statistics and analysis for the service monitoring platform; path selection: the method comprises the steps that after a message enters an application interconnection bus core engine, an interface address provided by a service provider is selected autonomously, and the message is sent to the service provider through the selected address; flow control: firstly, setting a maximum request message M of service and a maximum transaction frequency TPS completed per second, secondly, obtaining a corresponding request message quantity M ' and a corresponding transaction frequency TPS completed per second by using an interconnection bus core engine according to a request provided by a service request party, and if M is less than M ' or TPS is less than TPS ', sending error information to the service request party by using the interconnection bus core engine; load balancing: the system comprises a service provider, a service request module and a service processing module, wherein the service provider is used for enhancing the concurrent processing capacity when the service provider receives the service request and relieving the processing pressure of a single interface address, and the service request represents that a service requester requests the service of the service provider through an application interconnection bus core engine; the load balancing operation steps are shown in fig. 3, and include the following steps:
starting a load function in service registration information;
inputting an interface address of a service provider;
selecting a load rule, and selecting one of a polling rule, a weight rule and a dynamic calculation rule;
and fourthly, when the weight rule is selected, setting a corresponding empirical weight coefficient for each interface address.
(1) and (3) polling rules: arranging interface addresses corresponding to each service according to an input sequence; when a service requester requests service, the service requester is sequentially taken out from the interface address arrangement corresponding to the service according to the request sequence and called;
(2) the weight rule is as follows: setting a corresponding weight coefficient for each interface address, when a service requester requests service, obtaining an effective weight coefficient through a calculation rule, and obtaining a maximum effective weight coefficient by combining a plurality of effective weight coefficient set self-adaptive iteration mechanisms, wherein the effective weight coefficient set is beta, beta', and then obtaining the corresponding interface address; in any single poll, the weight rule flow is shown in fig. 4, and includes the following steps:
get service F1N interface addresses;
② the interface address set is
Corresponding set of weighting coefficients as
Setting a weight coefficient sum
The set of valid weight coefficients with an initial value of 0 is
Wherein i is more than or equal to 1 and less than or equal to n, and m is more than or equal to 11≤n，SiFor the address of the i-th interface,
is m at1An interface address, SnFor the nth interface address, αiSetting a weight coefficient for the ith interface address,
is m at1Set weighting factor, alpha, of individual interface addressesnFor setting a weight coefficient, beta, for the nth interface addressiIs the effective weight coefficient of the ith interface address,
is m at1Effective weight coefficient of an interface address, betanEffective weight coefficient for nth interface address;
third, when the service request party requests service F1Traversing the interface address set S, sequentially adding the corresponding elements of the set weight coefficient set and the effective weight coefficient set, and if the selected interface address is S in the traversing processiThen its corresponding effective weight coefficient is β'i＝αi+βiThe interface address after traversal is corresponding to a valid weight coefficient set of β '═ β'1,β'2,β'3,...,β'n}；
Fourthly, obtaining the maximum effective weight coefficient beta 'through an effective weight coefficient set beta'max；
Is beta through'maxThe value of (b) obtains its corresponding set of maximum effective weight coefficients in β
Wherein m is more than or equal to 11＜m2＜...＜mn≤n；
L is through beta'mObtaining effective weight coefficients
And its corresponding interface address
Is obtained by
To interface address
Is given by
Is replaced by
When all the interface address effective weight coefficients are 0, finishing single polling, otherwise waiting for next service request party to request service F1。
(3) Dynamically calculating rules: as shown in FIG. 5, this is accomplished by first serving F2Setting an initial empirical weight coefficient eta for each interface address; then, the service requester requests service F2Then using the weight rule to obtain the corresponding interface address; second, when a single poll is complete, service F is acquired2Historical request information recorded in the log, which includes the smallest request message S within a single pollminMinimum response message MminAnd maximum successful response time TmaxAverage request message S corresponding to single interface addressavgAverage response message MavgTime-consuming average T of complete successful transactionavgAnd the transaction success rate R and the weight coefficient of the next polling of each interface address are obtained
Where μ is a correction factor (μ e N)*) (ii) a After that, every time when the single polling is finished, the weight coefficient of the next polling of each interface address is obtained through the history information recorded in the log; finally, when service F2When the interface address information is changed, the core engine of the application interconnection bus stops the current dynamic calculation rule.
And 7, establishing an industrial manufacturing application interconnection bus platform through an industrial manufacturing application interconnection architecture model, wherein the process comprises the following steps: firstly, message middleware is used for realizing the transmission of messages among multi-source heterogeneous information systems; then abstracting and packaging the message transmission function in the message stream operating environment, realizing the construction of an application interconnection bus core engine, and completing security authentication, format conversion, protocol conversion, path selection, load balancing, flow control and log recording in the message transmission process; secondly, constructing a service management platform for managing an application interconnection bus core engine, and constructing a graphical report for statistical analysis provided by a service monitoring platform; and finally, constructing a service publishing platform and a service shop platform for the third-party system to use.
Step 8, establishing an application interconnection architecture model working process of industrial manufacturing, wherein the working process comprises two stage processes of establishing an industrial manufacturing application interconnection bus platform and establishing service;
(1) the process for establishing the industrial manufacturing application interconnection bus platform comprises the following steps:
selecting a Message flow operating environment, wherein the Message flow operating environment specifically comprises an IBM Integration Bus, an IBM WebSphere Message Broker, an Oracle Service Bus, an Oracle Enterprise Service Bus and a Mule ESB;
completing the development of an application interconnection bus core engine in a message flow running environment, wherein the development specifically comprises a protocol adapter, a message flow template and components for providing security authentication, format conversion, protocol conversion, path selection, load balancing, flow control and diary recording;
developing a service management platform and a service monitoring platform, wherein the functions of the service management platform comprise platform operation and maintenance, authorization management and life cycle management; the functions of the service monitoring platform comprise service transaction statistics, service quantity statistics, service quality analysis, service monitoring, platform monitoring and abnormal alarm;
developing a service release platform and a service shop platform, wherein the functions of the service release platform comprise service registration, service release and service management; the functions of the service store platform comprise a service directory, service subscription and service trial;
fifthly, completing deployment of an industrial manufacturing application interconnection bus platform, wherein the deployment modes comprise public cloud deployment, private cloud deployment, community cloud deployment, hybrid cloud deployment and local deployment, and the deployment modes comprise a traditional mode, a virtualization mode and a container deployment mode;
and sixthly, completing platform configuration on the service management platform, completing service creation, release, viewing and subscription on the service release platform and the service store platform, and finally completing service message transmission through the application interconnection bus core engine.
(2) The service creation includes:
firstly, realizing system registration and protocol adapter configuration in a service management platform;
secondly, logging in the publishing platform, and the system defined in the service management platform realizes the registration, management and publishing of the service through the publishing platform. After the authorization of the service management platform for the approval task to be published passes, the life cycle state of the service is changed into published, and at the moment, the service can be subscribed by other systems;
logging in the service shop platform, issuing the service authorized to pass by the platform, presenting the service in the service shop platform in a catalog form, and checking the service and trying and subscribing the service by the system defined by the service management platform through the service shop platform. After the authorization of the service management platform for the examination and approval task to be subscribed is passed, a system defined by the service management platform can request for the service;
the service requester realizes the service request through the application interconnection bus core engine, and records the transaction behavior of each service through the log component in the application interconnection bus core engine, wherein the service request process is as follows: firstly, a service requester sends a request message to an application interconnection bus core engine, the request message is subjected to format detection, message initialization, security authentication, flow control and path selection to complete the operation processing of the request message, then, a service provider receives the request message after the operation processing and sends a response message to the application interconnection bus core engine, the application interconnection bus core engine converts the response message into a message format required by the service requester through a protocol adapter and sends the message format to the service requester to complete the service request, wherein the operation processing flow of the request message is shown in fig. 6 and specifically comprises the following steps:
a. b, the application interconnection bus core engine obtains a request message Q sent by a service request party and transfers to the step b;
b. carrying out format detection on the request message Q, if the detection is passed, turning to the step c, otherwise, turning to the step g;
c. b, initializing the request message Q, converting the message format of the request message Q into a standard message format, and turning to the step d, wherein the initialized request message is represented as Q';
d. detecting the request message Q' through a safety certification function, if the detection is passed, turning to the step e, otherwise, turning to the step g;
e. detecting the request message Q' through a flow control function, if the detection is passed, turning to f, otherwise, turning to the step g;
f. sending the request message Q' to a corresponding service provider through a path selection function, and ending the process;
g. generating prompt information, sending the prompt information to a requester system, and ending the process;
the service monitoring platform obtains the transaction log data generated in the application interconnection bus core engine, displays the transaction log data in the service management platform, the service release platform and the service shop platform in real time in an analysis report form, and carries out abnormal alarm through mail/short message/WeChat/telephone voice when abnormal transaction occurs in the application interconnection bus core engine.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. An application interconnection architecture model for industrial manufacturing, characterized by: the method comprises the steps that the design of an application interconnection bus core engine, a service management platform, a service release platform, a service shop platform and a service monitoring platform is developed based on an application service bus message flow operating environment, wherein the application service bus message flow operating environment is a message middleware for supporting an industrial manufacturing application interconnection bus platform and provides a message flow driving operating environment; the application interconnection bus core engine comprises a protocol adapter and a message flow template and provides the functions of security authentication, format conversion, protocol conversion, path selection, load balancing, flow control, log recording and message transmission; the service management platform has the functions of platform operation and maintenance, authorization management and life cycle management; the service publishing platform has the functions of service registration, service publishing and service management; the functions of the service store platform comprise a service directory, service subscription and service trial; the functions of the service monitoring platform comprise service transaction statistics, service quantity statistics, service quality analysis, service monitoring, platform monitoring and abnormal alarm.
2. The industrially manufactured application interconnect architecture model of claim 1, wherein: the realization process is as follows: firstly, an application interconnection architecture model of industrial manufacturing is established, then an application interconnection bus platform of industrial manufacturing is established, and finally, the working flow of the application interconnection architecture model of industrial manufacturing is completed.
3. The service management platform according to claim 1, wherein the functions include platform operation and maintenance, authorization management and lifecycle management, wherein the platform operation and maintenance is used for an administrator to maintain the industrial manufacturing application interconnection bus platform, and includes log management, system registration and protocol adapter registration, wherein the log management is used for analyzing log records and searching the cause of the problem when the industrial manufacturing application interconnection bus platform is abnormal, the managed logs include system logs, application program logs, security logs and transaction logs of services, the system registration is used for the administrator to register a relevant application system, and the protocol adapter registration is used for the administrator to register a relevant protocol adapter according to the parameter requirements of the protocol adapter; authorizing and managing a request authority for managing a login authority and a service of a user; lifecycle management is used to manage the lifecycle state of a service and to describe the relationships between the phases of the service lifecycle.
4. The service publishing platform of claim 1, wherein the functions include service registration, service management, and service publishing, wherein service registration is used by a service provider to register various types of services; the service management is used for the service provider to manage the registered services, including modifying services, deleting services, testing services and releasing services; the service publishing is used for the service provider to publish and apply for the registered service, and the published service after application is passed is used for the service requester to subscribe/request.
5. The service store platform of claim 1, wherein the functions comprise a service directory for presenting published services in the service store platform in the form of a directory in which service requesters retrieve and view services and try and subscribe to services, service subscription, service trial; the service subscription is used for the service requester to initiate a subscription application for the service which is not subscribed in the service store platform; the service trial is used for making online calls to the published service in the service store platform.
6. The application interconnect bus core engine of claim 1, whose functions include security authentication, format conversion, protocol conversion, logging, path selection, flow control, message transport, and load balancing, wherein security authentication: the system is used for realizing the safety certification of a service requester system according to application requirements, and the certification mode comprises binding of an MAC address, an IP black and white list, physical port binding, digital visa and session verification; format conversion: when the message formats of the service requester and the service provider are inconsistent, the application interconnection bus core engine autonomously realizes the format conversion of the message according to the message formats of the service requester and the service provider in the service registration information; protocol conversion: when the communication protocols of the service requester and the service provider are inconsistent, the application interconnection bus core engine autonomously selects a corresponding protocol adapter according to the corresponding communication protocols of the service requester and the service provider, so as to realize the transmission of messages among different protocols; logging: the system comprises a log component, a service monitoring platform and a data processing module, wherein the log component is used for applying a log component in an interconnection bus core engine, recording each transaction behavior of the service, and providing data for statistics and analysis for the service monitoring platform; path selection: the method comprises the steps that after a message enters an application interconnection bus core engine, an interface address provided by a service provider is selected autonomously, and the message is sent to the service provider through the selected address; flow control: firstly, setting a maximum request message M of service and a maximum transaction frequency TPS completed per second, secondly, obtaining a corresponding request message quantity M ' and a corresponding transaction frequency TPS completed per second by using an interconnection bus core engine according to a request provided by a service request party, and if M is less than M ' or TPS is less than TPS ', sending error information to the service request party by using the interconnection bus core engine; load balancing: the method is used for enhancing the concurrent processing capacity of the service provider when receiving the service request, and relieving the processing pressure of a single interface address, wherein the service request indicates that the service requester requests the service of the service provider through the application interconnection bus core engine.
7. Load balancing according to claim 1, wherein the supported load rules comprise polling rules, weighting rules and dynamic calculation rules, wherein the polling rules are: arranging the interface address corresponding to each service according to an input sequence, and when a service requester requests the service, sequentially taking out and calling the interface addresses corresponding to the service according to the request sequence; the weighting rule is: setting a corresponding weight coefficient for each interface address, obtaining an effective weight coefficient by a calculation rule when a service requester requests a service, and obtaining a maximum effective weight coefficient by combining a plurality of effective weight coefficient set adaptive iteration mechanisms, wherein the effective weight coefficient set is beta, beta', and then obtaining the corresponding interface address.
8. Load balancing according to claim 1, which supports dynamic calculation rules as: first, as a service F2Setting an initial empirical weight coefficient eta for each interface address; then, the service requester requests service F2Temporal use weight ruleObtaining a corresponding interface address; second, when a single poll is complete, service F is acquired2Historical request information recorded in the log, which includes the smallest request message S within a single pollminMinimum response message MminAnd maximum successful response time TmaxAverage request message S corresponding to single interface addressavgAverage response message MavgTime-consuming average T of complete successful transactionavgAnd the transaction success rate R and the weight coefficient of the next polling of each interface address are obtained
Where μ is a correction factor (μ e N)*) (ii) a After that, every time when the single polling is finished, the weight coefficient of the next polling of each interface address is obtained through the history information recorded in the log; finally, when service F2When the interface address information is changed, the core engine of the application interconnection bus stops the current dynamic calculation rule.
9. The industrial manufacturing application interconnection architecture model of claim 1, wherein the process of establishing the industrial manufacturing application interconnection bus platform through the industrial manufacturing application interconnection architecture model comprises: firstly, message middleware is used for realizing the transmission of messages among multi-source heterogeneous information systems; then abstracting and packaging the message transmission function in the message stream operating environment, realizing the construction of an application interconnection bus core engine, and completing security authentication, format conversion, protocol conversion, path selection, load balancing, flow control and log recording in the message transmission process; secondly, constructing a service management platform for managing an application interconnection bus core engine, and constructing a graphical report for statistical analysis provided by a service monitoring platform; and finally, constructing a service publishing platform and a service shop platform for the third-party system to use.
10. The industrial application interconnection architecture model of claim 1, wherein the workflow comprises two phases of building an industrial manufacturing application interconnection bus platform and creating a service, wherein the building an industrial manufacturing application interconnection bus platform flow comprises: firstly, selecting a message flow running environment, then completing development of an application interconnection bus core engine on the message flow running environment, then completing development of a service management platform and a service monitoring platform, then completing development of a service release platform and a service shop platform, and finally completing deployment of an industrial manufacturing application interconnection bus platform; service creation process: firstly, realizing system registration and protocol adapter configuration in a service management platform; then, logging in a service publishing platform, and realizing the registration, management and publishing of the service by a system defined in the service management platform through the service publishing platform; secondly, logging in a service store platform, and presenting the service authorized to pass by the service release platform in the service store platform in a catalog form; thirdly, the service requester realizes the service request through the application interconnection bus core engine and records each transaction behavior of the service through a log component in the application interconnection bus core engine; and finally, the service monitoring platform acquires transaction log data generated in the application interconnection bus core engine, displays the transaction log data in an analysis report form in the service management platform, the service release platform and the service shop platform in real time, and carries out abnormal alarm through mail/short message/WeChat/telephone voice when abnormal transactions occur in the application interconnection bus core engine.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111578995.6A CN114285876B (en) | 2021-12-22 | 2021-12-22 | Application interconnection architecture for industrial manufacturing |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111578995.6A CN114285876B (en) | 2021-12-22 | 2021-12-22 | Application interconnection architecture for industrial manufacturing |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114285876A true CN114285876A (en) | 2022-04-05 |
| CN114285876B CN114285876B (en) | 2024-01-16 |
Family
ID=80874310
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111578995.6A Active CN114285876B (en) | 2021-12-22 | 2021-12-22 | Application interconnection architecture for industrial manufacturing |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114285876B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117390105A (en) * | 2023-12-11 | 2024-01-12 | 中核武汉核电运行技术股份有限公司 | Service input method and system of industrial service open platform |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080225710A1 (en) * | 2007-03-12 | 2008-09-18 | Murali Raja | Systems and Methods for Load Balancing Based on User Selected Metrics |
| CN103873332A (en) * | 2014-03-28 | 2014-06-18 | 浪潮软件集团有限公司 | Method for providing enterprise service bus of unified service environment by tax system |
| US9356872B2 (en) * | 2012-04-27 | 2016-05-31 | Level 3 Communications, Llc | Load balancing of network communications |
| CN110020061A (en) * | 2018-08-21 | 2019-07-16 | 广州市城市规划勘测设计研究院 | A kind of smart city space time information cloud platform service-Engine |
| CN112925660A (en) * | 2021-02-26 | 2021-06-08 | 重庆斯欧智能科技研究院有限公司 | Industrial interconnected information interaction system |
-
2021
- 2021-12-22 CN CN202111578995.6A patent/CN114285876B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080225710A1 (en) * | 2007-03-12 | 2008-09-18 | Murali Raja | Systems and Methods for Load Balancing Based on User Selected Metrics |
| US9356872B2 (en) * | 2012-04-27 | 2016-05-31 | Level 3 Communications, Llc | Load balancing of network communications |
| CN103873332A (en) * | 2014-03-28 | 2014-06-18 | 浪潮软件集团有限公司 | Method for providing enterprise service bus of unified service environment by tax system |
| CN110020061A (en) * | 2018-08-21 | 2019-07-16 | 广州市城市规划勘测设计研究院 | A kind of smart city space time information cloud platform service-Engine |
| CN112925660A (en) * | 2021-02-26 | 2021-06-08 | 重庆斯欧智能科技研究院有限公司 | Industrial interconnected information interaction system |
Non-Patent Citations (2)
| Title |
|---|
| 周霞;丁海斌;: "分布式服务框架的设计与实现", 指挥信息系统与技术, no. 01 * |
| 过立新;: "一种新型企业应用系统EAI模型的构建", 电子科技, no. 11 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117390105A (en) * | 2023-12-11 | 2024-01-12 | 中核武汉核电运行技术股份有限公司 | Service input method and system of industrial service open platform |
| CN117390105B (en) * | 2023-12-11 | 2024-03-01 | 中核武汉核电运行技术股份有限公司 | Service input method and system of industrial service open platform |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114285876B (en) | 2024-01-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110738454B (en) | Enterprise management platform system | |
| CN111190730B (en) | Heterogeneous cloud management platform | |
| CN109559258B (en) | Educational resource public service system | |
| US9838370B2 (en) | Business attribute driven sizing algorithms | |
| US20140074540A1 (en) | Role assignments in a cloud infrastructure | |
| US20050060662A1 (en) | Process for creating service action data structures | |
| US20200236129A1 (en) | Systems and methods for vulnerability scorecard | |
| US20140075239A1 (en) | Failure handling in the execution flow of provisioning operations in a cloud environment | |
| US20050043979A1 (en) | Process for executing approval workflows and fulfillment workflows | |
| US9734466B2 (en) | Multi-tenancy engine | |
| JP2008535113A (en) | Method, system, and program for outsourcing resources in a grid computing environment | |
| US20190340562A1 (en) | Systems and method for project management portal | |
| US11645623B1 (en) | Resource management system | |
| US9870542B2 (en) | Managing information technology solution centers | |
| Keller | Challenges and directions in service management automation | |
| US20050044099A1 (en) | Process for creating an information services catalog | |
| CN109743192A (en) | A kind of container cluster configuration management method and device | |
| CN114285876A (en) | Application interconnection framework for industrial manufacturing | |
| US7657590B2 (en) | Load balancing system and method | |
| AU2012300188B2 (en) | A collaboration computer system | |
| US11829952B1 (en) | Resource management system | |
| US20050055224A1 (en) | System, method, and computer program product for managing interoperable data processing system services | |
| US20230153713A1 (en) | Method for cloud computing general contractor to subcontractor networking automation | |
| US11824848B2 (en) | On demand operations access to cloud customer resources | |
| US20240259430A1 (en) | Techniques for processing queries related to network security |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 401331 2nd floor, building 6, phase III, R & D building, Xiyong micro electronics industrial park, Shapingba District, Chongqing Applicant after: Chongqing Siou Intelligent Technology Research Institute Co.,Ltd. Applicant after: Zhongkoso (Hefei) Technology Co.,Ltd. Address before: 401331 2nd floor, building 6, phase III, R & D building, Xiyong micro electronics industrial park, Shapingba District, Chongqing Applicant before: Chongqing Siou Intelligent Technology Research Institute Co.,Ltd. Applicant before: CHONGQING SOA INFORMATION TECHNOLOGY Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20231127 Address after: Floor 31, Building A1, Phase I, Zhong'an Chuanggu Science Park, No. 900, Wangjiang West Road, High tech Zone, Hefei, China (Anhui) Pilot Free Trade Zone, Hefei, 230000 Applicant after: Zhongkoso (Hefei) Technology Co.,Ltd. Address before: 401331 2nd floor, building 6, phase III, R & D building, Xiyong micro electronics industrial park, Shapingba District, Chongqing Applicant before: Chongqing Siou Intelligent Technology Research Institute Co.,Ltd. Applicant before: Zhongkoso (Hefei) Technology Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |