CN114840329A - Cloud and native hybrid integration method based on block chain - Google Patents
Cloud and native hybrid integration method based on block chain Download PDFInfo
- Publication number
- CN114840329A CN114840329A CN202210083778.8A CN202210083778A CN114840329A CN 114840329 A CN114840329 A CN 114840329A CN 202210083778 A CN202210083778 A CN 202210083778A CN 114840329 A CN114840329 A CN 114840329A
- Authority
- CN
- China
- Prior art keywords
- service
- integration
- api
- cloud
- data
- 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.)
- Pending
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/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5061—Partitioning or combining of resources
- G06F9/5077—Logical partitioning of resources; Management or configuration of virtualized resources
-
- 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/24—Querying
- G06F16/245—Query processing
- G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
- G06F16/2471—Distributed queries
-
- 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/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- 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/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
-
- 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
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- 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
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
-
- 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
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The invention discloses a cloud and native hybrid integration method based on a block chain, which relates to the technical field of service integration and comprises the following steps: a cloud native distributed gateway is constructed, and identity and authority verification service of API access, high availability, fusing, degrading and elastic expansion service of API service are realized; under a multi-cloud environment, a unified integrated service is built on a heterogeneous virtualization resource pool based on container, kata and kubernetes technologies, and the built integrated service is automatically registered to a cloud native distributed gateway; creating a designer based on a web interface, wherein the designer can realize the arrangement and the scheduling of the integration capacity and finally provide an application-oriented service API; and the user uses various integration capabilities through the block chain and calls the integrated service registered in the distributed gateway through the service API provided by the designer, and finally, the access of the metadata in the distributed gateway is realized. The invention can realize the business cooperation with the user and the application as the center, and realize the instant data flow and data cooperation under the cross-department and cross-network conditions.
Description
Technical Field
The invention relates to the technical field of service integration, in particular to a cloud-native hybrid integration method based on a block chain.
Background
The hybrid integration platform realizes organic combination of application programs, data, files, messages and the like based on multiple modes such as cross-cloud and local links. With the development of technical evolution, the modes such as cross-cloud and cross-domain are evolved to cross-end, and the method is widely popularized in application scenes such as edge computing.
In the actual production environment, the hybrid integrated platform faces a variety of problems in the promotion process:
1) the standards differ: the data and service standards of all application developers are different, and short-term unification cannot be realized;
2) the network is complex: the phenomena of government affair internal and external networks, each business private network, network-in-network and the like exist;
3) multi-protocol conversion: RPC, RMI, SOAP, CORBA, JMS, MQTT, Restful and other protocols;
4) elastic expansion: under a high concurrency scene, the data integration and message integration elasticity can be rapidly expanded;
5) safety problems are as follows: potential safety transmission hazards exist in the collaborative process of cross-department data, service, information and the like.
Disclosure of Invention
Aiming at the requirements and the defects of the prior art development, the invention provides a cloud-native hybrid integration method based on a block chain.
The invention discloses a cloud and native hybrid integration method based on a block chain, which solves the technical problems by adopting the following technical scheme:
a cloud-native hybrid integration method based on a block chain comprises the following implementation processes:
step S1, a cloud native distributed gateway is constructed, and identity and authority verification service of API access, high availability, fusing, degrading and elastic expansion service of API service are achieved;
step S2, under a multi-cloud environment, constructing a unified integration service on the heterogeneous virtualization resource pool based on container, kata and kubernetes technologies, and automatically registering the constructed integration service to the cloud native distributed gateway;
step S3, creating a designer based on the web interface, wherein the designer can realize the arrangement and the scheduling of the integration capability and finally provide an application-oriented service API;
and step S4, the user uses various integration capabilities through the block chain, and calls the integrated services registered in the distributed gateway through the service API provided by the designer, and finally the access of the metadata in the distributed gateway is realized.
Optionally, step S1 is executed, and the specific operation of constructing the cloud native distributed gateway includes:
s1.1, constructing an adapter through a micro service architecture development protocol for accessing services in different forms;
s1.2, uniformly managing metadata of the adapter access service;
and S1.3, constructing a container mirror image through the container to realize the rapid deployment of the cloud native distributed gateway.
Further optionally, all externally provided APIs of the constructed cloud native distributed gateway support synchronous calling and asynchronous calling, and when the access side system selects an asynchronous calling mode according to actual service needs, the asynchronous calling gateway performs result callback through a callback address provided by a user after the API is executed;
the constructed cloud native distributed gateway records all API call logs, provides an API metering system, and provides an API collaborative statistical analysis function, wherein the logs comprise information such as a calling party, an APICode, an input parameter, an output parameter, response time, a success failure mark and the like.
Optionally, step S2 is executed to construct the data integration service, where the construction process is as follows:
s2.1.1, realizing uniform adaptation of heterogeneous data sources through a data persistence engine;
s2.1.2, building a logic + physical data resource pool through a data access function;
step S2.1.3, realizing the subscription/promotion management of the data integration service directory through the data subscription function;
after the data integration service is constructed, data from different sources are accessed in an adaptive mode, and the data are pushed to a subscriber in a publishing/subscribing mode, so that cross-department and cross-network data real-time flow and data collaboration are realized.
Optionally, step S2 is executed to construct the message integration service, where the construction process is as follows:
step S2.2.1, adapting to the underlying infrastructure resources through the adapter, and adapting to the virtualization/container resource pool through the adapter to realize the rapid construction of the multi-tenant message queue based on virtualization;
step S2.2.2, using the application as the tenant, as the message service instance of the open message integration service;
s2.2.3, the application development realizes the application of data/service through a subscription/push mode;
through the constructed message integration service, firstly, asynchronous call service is provided for the same access party, at the moment, a call request is transmitted in a message form, the cloud native distributed gateway monitors the message, performs task processing, and sends a notification to a message middleware after the processing is finished, and secondly, the decoupling of computing tasks is realized, so that the message-based streaming computing service is realized.
Optionally, step S2 is executed to construct the service integration service, where the construction process is as follows:
step S2.3.1, realizing registration access management of different services by adapting different http/tcp/socket protocols;
step S2.3.2, automatically issuing a service directory of the distributed gateway after realizing service registration approval by calling the API of the distributed gateway;
step S2.3.3, the developer realizes the subscription and application of the required service through the distributed gateway;
the API of the service integration service runs on the access side system, the distributed gateway is routed to the subsystem through the API Code and carries out request/response conversion, meanwhile, because the API is finally called to the access side system, the distributed gateway needs to carry out load balancing according to the configuration of the access side system, and for the query type API, result caching is carried out according to the type and frequency of the API, so that efficient calling of the API is ensured.
Optionally, when step S3 is executed, the created designer provides a visualization panel to create an integrated orchestration task, and supports the visualization orchestration of the data, service, and application-class related components;
the created designer provides components of basic flow, data conversion, script execution, message queue and flow event, supports integration conversion between cross networks and cross applications, supports a timing and real-time integration mode, supports packaging the results of the existing service and hybrid integration arrangement into a Restful API which is open to the outside, and combines multiple modes of data authentication and user authorization to realize unified authorization management.
Optionally, step S4 is performed, the access party system is mapped to the users within the organization, at which point,
the access side system can deploy the chaincode according to the self requirement, provide sdk for calling the integrated service,
the access side system can also apply for creating a channel, joining the channel and creating a user, after approval, the channel, joining the channel or creating the user can be created, and the user can download the CA certificate and access the block chain.
Preferably, all API authorization, data authorization process information and result information are stored in the blockchain.
Compared with the prior art, the cloud and native hybrid integration method based on the block chain has the beneficial effects that:
the method is suitable for intelligent scheduling of resource requests in a cross-network environment, unified integrated management is carried out on multiple networks, multiple platforms and multiple resources, application scenes such as cross-department, cross-network and cross-platform data collaboration, service collaboration, message collaboration, equipment collaboration and the like are realized through hybrid integrated arrangement and intelligent scheduling, and a standard solution is provided for rapid cloud-going and cross-department service collaboration of out-of-cloud applications.
Drawings
FIG. 1 is a flow chart of the method of the present invention.
Detailed Description
In order to make the technical scheme, the technical problems to be solved and the technical effects of the present invention more clearly apparent, the following technical scheme of the present invention is clearly and completely described with reference to the specific embodiments.
The first embodiment is as follows:
with reference to fig. 1, the present embodiment provides a block chain-based cloud-native hybrid integration method, which includes:
and step S1, constructing a cloud native distributed gateway, and realizing identity and authority verification service of API access, high availability, fusing, degrading and elastic expansion service of API service.
The specific operation of constructing the cloud native distributed gateway comprises the following steps:
s1.1, constructing an adapter through a micro service architecture development protocol for accessing services in different forms;
s1.2, uniformly managing metadata of the adapter access service;
and S1.3, constructing a container mirror image through the container to realize the rapid deployment of the cloud native distributed gateway.
In this embodiment, all the APIs provided by the cloud native distributed gateway externally support synchronous call and asynchronous call, and when the access side system selects an asynchronous call mode according to actual service needs, the asynchronous call gateway performs result callback through a callback address provided by a user after the API is executed.
In this embodiment, the cloud native distributed gateway records all API call logs, provides an API metering system, and provides an API collaborative statistical analysis function, where the logs include information such as a calling party, an APICode, an entry parameter, an exit parameter, response time, a success/failure flag, and the like.
Step S2, under a multi-cloud environment, a unified integrated service is built on the heterogeneous virtualization resource pool based on container, kata and kubernetes technologies, and the built integrated service is automatically registered to the cloud native distributed gateway.
Step S2 is executed to construct integration services, including data integration services, message integration services, and service integration services.
(A) The process of constructing the data integration service is as follows:
s2.1.1, realizing uniform adaptation of heterogeneous data sources through a data persistence engine;
s2.1.2, building a logic + physical data resource pool through a data access function;
and S2.1.3, realizing the subscription/promotion management of the data integration service directory through the data subscription function.
After the data integration service is constructed, data from different sources are accessed in an adaptive mode, and the data are pushed to a subscriber in a publishing/subscribing mode, so that cross-department and cross-network data real-time flow and data collaboration are realized.
(B) The process of constructing the message integration service is as follows:
step S2.2.1, adapting to the underlying infrastructure resources through the adapter, and adapting to the virtualization/container resource pool through the adapter to realize the rapid construction of the multi-tenant message queue based on virtualization;
step S2.2.2, using the application as the tenant, as the message service instance of the open message integration service;
step S2.2.3, the application development realizes the application of data/service through the subscription/push mode.
Through the constructed message integration service, firstly, asynchronous call service is provided for the same access party, at the moment, a call request is transmitted in a message form, the cloud native distributed gateway monitors the message, performs task processing, and sends a notification to a message middleware after the processing is finished, and secondly, the decoupling of computing tasks is realized, so that the message-based streaming computing service is realized.
(C) The process of constructing the service integration service is as follows:
step S2.3.1, realizing registration access management of different services by adapting different http/tcp/socket protocols;
step S2.3.2, automatically issuing a service directory of the distributed gateway after realizing service registration approval by calling the API of the distributed gateway;
and S2.3.3, the developer realizes the subscription and application of the required service through the distributed gateway.
The API of the service integration service runs on the access side system, the distributed gateway is routed to the subsystem through the API Code and carries out request/response conversion, meanwhile, because the API is finally called to the access side system, the distributed gateway needs to carry out load balancing according to the configuration of the access side system, and for the query type API, result caching is carried out according to the type and frequency of the API, so that efficient calling of the API is ensured.
Step S3, creating a designer based on the web interface, the designer being able to implement the orchestration and scheduling of integration capabilities and finally providing an application-oriented service API.
A designer created based on a web interface provides a visual panel to create an integrated arrangement task and support the visual arrangement of related components of data, service and application classes; and secondly, components of basic processes, data conversion, script execution, message queues and process events are provided to support integration conversion between cross-networks and cross-applications, a timing and real-time integration mode is supported, the existing service and mixed integration arrangement result is packaged into a Restful API which is open to the outside, and the unified authorization management is realized by combining multiple modes of data authentication and user authorization.
And step S4, the user uses various integration capabilities through the block chain, and calls the integrated services registered in the distributed gateway through the service API provided by the designer, and finally the access of the metadata in the distributed gateway is realized.
In this step, the access side system is mapped to users within the organization, at which point,
the access side system can deploy the chaincode according to the self requirement, provide sdk for calling the integrated service,
the access side system can also apply for creating a channel, joining the channel and creating a user, after approval, the channel, joining the channel or creating the user can be created, and the user can download the CA certificate and access the block chain.
Preferably, all API authorization, data authorization process information and result information are stored in the blockchain.
In summary, the cloud and native hybrid integration method based on the block chain solves the problem that data integration, service integration, message integration, equipment integration, application integration and hybrid arrangement are completed between different networks and different departments in a block chain trusted environment in an inter-network environment.
The principles and embodiments of the present invention have been described in detail using specific examples, which are provided only to aid in understanding the core technical content of the present invention. Based on the above embodiments of the present invention, those skilled in the art should make any improvements and modifications to the present invention without departing from the principle of the present invention, and therefore, the present invention should fall into the protection scope of the present invention.
Claims (9)
1. A cloud-native hybrid integration method based on a block chain is characterized in that the implementation process comprises the following steps:
step S1, a cloud native distributed gateway is constructed, and identity and authority verification service of API access, high availability, fusing, degrading and elastic expansion service of API service are achieved;
step S2, under a multi-cloud environment, constructing a unified integration service on the heterogeneous virtualization resource pool based on container, kata and kubernetes technologies, and automatically registering the constructed integration service to the cloud native distributed gateway;
step S3, creating a designer based on the web interface, wherein the designer can realize the arrangement and the scheduling of the integration capability and finally provide an application-oriented service API;
and step S4, the user uses various integration capabilities through the block chain, and calls the integrated services registered in the distributed gateway through the service API provided by the designer, and finally the access of the metadata in the distributed gateway is realized.
2. The method for cloud-native hybrid integration based on block chain according to claim 1, wherein step S1 is executed, and the specific operation of constructing the cloud-native distributed gateway includes:
s1.1, constructing an adapter through a micro service architecture development protocol for accessing services in different forms;
s1.2, uniformly managing metadata of the adapter access service;
and S1.3, constructing a container mirror image through the container to realize the rapid deployment of the cloud native distributed gateway.
3. The cloud-native hybrid integration method based on the block chain according to claim 2, characterized in that all externally provided APIs of the constructed cloud-native distributed gateway support synchronous call and asynchronous call, and when the access side system selects an asynchronous call mode according to actual service needs, the asynchronous call gateway performs result callback through a callback address provided by a user after the API is executed;
the constructed cloud native distributed gateway records all API call logs, provides an API metering system, and provides an API collaborative statistical analysis function, wherein the logs comprise information such as a calling party, an APICode, an input parameter, an output parameter, response time, a success failure mark and the like.
4. The method for cloud-native hybrid integration based on block chains according to claim 1, wherein step S2 is executed to build the data integration service, and the process is as follows:
s2.1.1, realizing uniform adaptation of heterogeneous data sources through a data persistence engine;
s2.1.2, building a logic + physical data resource pool through a data access function;
s2.1.3, realizing the subscription/promotion management of the data integration service directory through the data subscription function;
after the data integration service is constructed, data from different sources are accessed in an adaptive mode, and the data are pushed to a subscriber in a publishing/subscribing mode, so that cross-department and cross-network data real-time flow and data collaboration are realized.
5. The method for cloud-native hybrid integration based on block chains according to claim 4, wherein step S2 is executed to construct the message integration service, and the construction process is as follows:
step S2.2.1, adapting to the underlying infrastructure resources through the adapter, and adapting to the virtualization/container resource pool through the adapter to realize the rapid construction of the multi-tenant message queue based on virtualization;
step S2.2.2, using the application as the tenant, as the message service instance of the open message integration service;
s2.2.3, the application development realizes the application of data/service through a subscription/push mode;
through the constructed message integration service, firstly, asynchronous call service is provided for the same access party, at the moment, a call request is transmitted in a message form, the cloud native distributed gateway monitors the message, performs task processing, and sends a notification to a message middleware after the processing is finished, and secondly, the decoupling of computing tasks is realized, so that the message-based streaming computing service is realized.
6. The block chain-based cloud-native hybrid integration method according to claim 5, wherein step S2 is executed to construct the service integration service, and the construction process is as follows:
step S2.3.1, realizing registration access management of different services by adapting different http/tcp/socket protocols;
step S2.3.2, automatically issuing a service directory of the distributed gateway after realizing service registration approval by calling the API of the distributed gateway;
step S2.3.3, the developer realizes the subscription and application of the required service through the distributed gateway;
the API of the service integration service runs on the access side system, the distributed gateway is routed to the subsystem through the API Code and carries out request/response conversion, meanwhile, because the API is finally called to the access side system, the distributed gateway needs to carry out load balancing according to the configuration of the access side system, and for the query type API, result caching is carried out according to the type and frequency of the API, so that efficient calling of the API is ensured.
7. The method for cloud-native hybrid integration based on block chains according to claim 1, wherein when step S3 is executed, the created designer provides a visualization panel to create an integrated orchestration task, which supports visual orchestration of data, service, and application-class related components;
the created designer provides components of basic flow, data conversion, script execution, message queue and flow event, supports integration conversion between cross networks and cross applications, supports a timing and real-time integration mode, supports packaging the results of the existing service and hybrid integration arrangement into a restful API (application program interface) which is open to the outside, and realizes unified authorization management by combining multiple modes of data authentication and user authorization.
8. The method for cloud-native hybrid integration based on block chain as claimed in claim 1, wherein step S4 is executed, the access system is mapped to the user in the organization, at this time,
the access side system can deploy the chaincode according to the self requirement, provide sdk for calling the integrated service,
the access side system can also apply for creating a channel, joining the channel and creating a user, after approval, the channel, joining the channel or creating the user can be created, and the user can download the CA certificate and access the block chain.
9. The method according to claim 8, wherein the blockchain stores all API authorization, data authorization process information and result information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210083778.8A CN114840329A (en) | 2022-01-21 | 2022-01-21 | Cloud and native hybrid integration method based on block chain |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210083778.8A CN114840329A (en) | 2022-01-21 | 2022-01-21 | Cloud and native hybrid integration method based on block chain |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114840329A true CN114840329A (en) | 2022-08-02 |
Family
ID=82562770
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210083778.8A Pending CN114840329A (en) | 2022-01-21 | 2022-01-21 | Cloud and native hybrid integration method based on block chain |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114840329A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116032918A (en) * | 2022-11-14 | 2023-04-28 | 广西壮族自治区信息中心(广西壮族自治区大数据研究院) | Method and flow of multi-cloud adapter abstraction technology |
-
2022
- 2022-01-21 CN CN202210083778.8A patent/CN114840329A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116032918A (en) * | 2022-11-14 | 2023-04-28 | 广西壮族自治区信息中心(广西壮族自治区大数据研究院) | Method and flow of multi-cloud adapter abstraction technology |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9479400B2 (en) | Servlet API and method for XMPP protocol | |
| CN102255934B (en) | Cloud service dissemination method and cloud service intermediary | |
| US8539097B2 (en) | Intelligent message processing | |
| JP4199670B2 (en) | Communication application server for converged communication services | |
| Baumer et al. | Grasshopper—A universal agent platform based on OMG MASIF and FIPA standards | |
| EP2888868B1 (en) | Calling an unready terminal | |
| CN111290865A (en) | Service calling method and device, electronic equipment and storage medium | |
| US8719780B2 (en) | Application server with a protocol-neutral programming model for developing telecommunications-based applications | |
| US20060101474A1 (en) | System, method and apparatus for an extensible distributed enterprise integration platform | |
| EP2838243B1 (en) | Capability aggregation and exposure method and system | |
| CN109639782A (en) | Message sends platform, method | |
| CN111200606A (en) | Deep learning model task processing method, system, server and storage medium | |
| US8924988B2 (en) | Collocation in a Java virtual machine of JSLEE and Java EE | |
| CN115733746A (en) | Service grid unit deployment method, device, equipment and storage medium | |
| CN114840329A (en) | Cloud and native hybrid integration method based on block chain | |
| CN112711625B (en) | Bidirectional self-adaptive multi-source heterogeneous big data dynamic processing method | |
| CN115550354A (en) | Data processing method and device and computer readable storage medium | |
| Fragkos et al. | 5g vertical application enablers implementation challenges and perspectives | |
| US20130013760A1 (en) | Method for Coordinating the Provision of a Composite Services | |
| Venezia et al. | Communication web services composition and integration | |
| Zhu et al. | Enhancing ESB based execution platform to support flexible communication Web services over heterogeneous networks | |
| US20100223626A1 (en) | Mechanism for Improved Integration of JSLEE and SIP Servlets in a JAVA Virtual Machine | |
| US20230139834A1 (en) | Asynchronous network inventory system | |
| Palacios et al. | IP Telephony Applicability in Cloud Computing | |
| CN109743393B (en) | Broadcast cloud platform for transmitting instructions, real-time streams and file streams |
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 |