CN112950153A - Centralized business arrangement method and system based on cloud edge collaborative environment - Google Patents
Centralized business arrangement method and system based on cloud edge collaborative environment Download PDFInfo
- Publication number
- CN112950153A CN112950153A CN202110204007.5A CN202110204007A CN112950153A CN 112950153 A CN112950153 A CN 112950153A CN 202110204007 A CN202110204007 A CN 202110204007A CN 112950153 A CN112950153 A CN 112950153A
- Authority
- CN
- China
- Prior art keywords
- component
- service
- edge
- cloud
- engine
- 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
- 238000000034 method Methods 0.000 title claims abstract description 30
- 230000008569 process Effects 0.000 claims abstract description 11
- 238000012790 confirmation Methods 0.000 claims description 22
- 238000004891 communication Methods 0.000 claims description 11
- 230000004044 response Effects 0.000 claims description 11
- 230000006978 adaptation Effects 0.000 claims description 9
- 238000012545 processing Methods 0.000 claims description 6
- 238000012546 transfer Methods 0.000 claims description 4
- 230000001360 synchronised effect Effects 0.000 claims description 3
- 230000006399 behavior Effects 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 125000000524 functional group Chemical group 0.000 description 2
- 230000004931 aggregating effect Effects 0.000 description 1
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000012216 screening Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- 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/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4482—Procedural
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Entrepreneurship & Innovation (AREA)
- General Physics & Mathematics (AREA)
- Operations Research (AREA)
- Tourism & Hospitality (AREA)
- Quality & Reliability (AREA)
- General Business, Economics & Management (AREA)
- Marketing (AREA)
- Economics (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- Multi Processors (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention discloses a centralized business arrangement method and a system based on a cloud edge collaborative environment, wherein the method comprises the following steps: (1) redefining the components in a mode of 'edge site name + original component name'; (2) component self-registration discovery: arranging an edge agent on an edge site, configuring service capacity corresponding to the components on the edge agent and sending the service capacity to an edge cloud cooperation engine at the cloud end, and sending the processed service capacity to the site after the engine is processed so as to finish a registration process; (3) and (3) service issuing: the cloud judges the type of the component, acquires a site corresponding to the component, and completes service delivery according to the type and the site. The invention adapts the service components at the edge end, converts the cloud information and the data, and then sends the cloud information and the data to the service components of the corresponding sites, thereby realizing that the centralized service arrangement system can be directly used in the cloud-edge computing environment.
Description
Technical Field
The invention relates to a business arrangement method and system, in particular to a centralized business arrangement method and system based on a cloud edge collaborative environment, belonging to the field.
Background
With the continuous development of enterprise services, cloud services are gradually expanded to cloud-edge cooperative services at present, edge services serve as a sentinel of cloud services, and play more and more important roles in data filtering and screening and edge pre-operation. In the current cloud service arrangement capacity, only a single cloud computing environment is arranged, but arrangement of edge cloud coordination capacity is lacked, and in an edge service operation environment, the problems that service calling fails or service flow is out of order and the like on an edge site in the traditional cloud service arrangement can be caused due to the fact that the network is unstable, the time delay is large and the like are different from those of a traditional data center, and finally the service fails; in addition, from the overall service operation environment, the number of edge sites is large, how to effectively execute the issued arranging service in batches is different from the task of executing the arranging service in the single cloud environment.
Disclosure of Invention
The purpose of the invention is as follows: the invention aims to provide a centralized arranging business method and a centralized arranging business system based on a cloud side collaborative environment, which can shield the influence of upper-layer business on an edge system and distributed multitask, so that the original arranging system aiming at the centralized cloud can be smoothly migrated to the cloud side environment for arranging.
The technical scheme is as follows: the invention discloses a centralized business arrangement method based on a cloud edge collaborative environment, which comprises the following steps:
(1) redefining the components in a mode of 'edge site name + original component name';
(2) component self-registration discovery: arranging an edge agent on an edge site, configuring service capacity corresponding to the components on the edge agent and sending the service capacity to an edge cloud cooperation engine at the cloud end, and sending the processed service capacity to the site after the engine is processed so as to finish a registration process;
(3) and (3) service issuing: the cloud judges the type of the component, acquires a site corresponding to the component, and completes service delivery according to the type and the site.
The step (2) specifically comprises the following steps:
(201) setting an edge proxy at an edge site, and configuring service capacity corresponding to the component on the edge proxy;
(202) the edge agent scans whether the service capability of the components at the site is ready in real time by reading the description file, and if so, the operation is executed (203);
(203) scanning a service component located at an edge site, acquiring a service component name and a site name, and sending the service capability of the component to a cloud service coordination engine at a cloud side;
(204) the edge cloud coordination engine receives the service component registration message, converts the service component registration message into an interface message format required by the centralized service arrangement system and registers the interface message format;
(205) returning the component name to the edge cloud cooperation engine by the component, decomposing the component name into a site name and a service name by the engine, searching whether the component with the same site name exists in a database, and acquiring communication information of the component;
(206) if the components with the same site name exist, the components are stored as the same service group;
(207) and the edge cloud engine forwards the component registration success message to the corresponding site.
In the steps (203) - (206), when the name of the service component is failed to be acquired, the name of the engine is failed to be decomposed, or the service group is failed to be divided, or any step cannot be successfully performed, the information of the failure of the site registration is fed back, and meanwhile, the failure reason is fed back.
In step (205), if there is no component with the same name, the component is stored in the new task group.
The step (3) specifically comprises the following steps:
(301) arranging components by the centralized business arranging system, judging whether the components are distributed components, if so, executing the step (302), otherwise, processing according to the original business;
(302) judging whether the component is a component group, if so, searching the database to obtain all components under the component group, otherwise, executing the step (308)
(303) Acquiring a site corresponding to each component;
(304) creating a task manager and issuing the service to all the components in the component group in parallel;
(305) each component returns a confirmation message after receiving the confirmation message, executes the task and sends a completion message after completing the task;
(306) the task manager monitors the tasks, if all the tasks are completed, the service adaptation is completed, the flow transfer is finished, and if not, the overtime task is retransmitted;
(307) if the retransmission fails, the service call fails, and the flow transfer is finished;
(308) if the component is a single component, the corresponding service is directly issued, and the process is ended after the response of the component is received.
The edge cloud collaborative arrangement engine is used for establishing a component agent, the component agent is responsible for service delivery, cache registration or cache of data and messages related to the service delivery, the communication condition of the site is monitored, if the site has a problem in communication with the cloud end, the message is delivered to the component agent, and the agent waits for the edge actual component to be online and then delivers the message.
The component shadow has the following adaptations to the service invocation:
synchronous waiting for messages: each time of service invocation, the edge cloud coordination engine sends a message to the component proxy, and the component proxy needs to wait for the service invocation to succeed after the actual component returns a confirmation message;
asynchronous waiting for messages: each time of service calling, the edge cloud coordination engine sends a message to the component proxy, the component proxy directly returns a service processing success, then the component proxy sends the message to the edge actual component and waits for the conditions of response or timeout of the edge actual component, and the proxy component calls different callback interfaces of the service engine according to the return condition to inform the service engine;
at least one message: each time of service calling, the edge cloud coordination engine sends a message to the component proxy, the edge cloud engine does not need the component to return a confirmation message, but the component proxy must ensure a response confirmation message returned to the component proxy by the edge component, the proxy component does not need to inform the service engine after receiving the confirmation message responded by the edge component, and an informing interface of the service engine does not need to be called.
Best effort message: and each time of service calling, the edge cloud coordination engine sends a message to the component proxy, the edge cloud engine does not need the component to return a confirmation message, the component proxy does not need to ensure the confirmation message of the edge component, the component can be configured with the maximum retransmission times, the message is directly discarded after the times are reached, and a notification interface of the service engine of the system does not need to be called. Best effort message: each service call does not need to return a message, but the component can configure the maximum retransmission times, and the message is directly discarded after the times are reached without notifying the service call of the system.
The centralized arrangement business system based on the cloud side collaborative environment comprises a centralized arrangement system and a side cloud collaborative engine arranged at the cloud side, wherein the side cloud collaborative engine is connected with a side cloud collaborative agent arranged at an edge site; the edge cloud cooperation engine is used for finishing the arrangement business method.
Has the advantages that: compared with the prior art, the invention has the following remarkable advantages:
the service is adaptively issued according to the scheme provided by the invention, the service components at the side end are adapted, cloud end information and data are converted and then issued to the service components of the corresponding sites, and the centralized service arrangement system can be directly used in a cloud side computing environment. The method can be used for service of business arrangement under a cloud computing platform, and has wide application scenes under a cloud computing management scene.
Drawings
FIG. 1 illustrates the interaction of the present invention with a peripheral system.
FIG. 2 is a schematic diagram illustrating an automatic service discovery process of an edge component according to the present invention.
FIG. 3 is a schematic diagram of a component business edge cloud collaboration flow of the present invention.
Detailed Description
The technical scheme of the invention is further explained by combining the attached drawings.
In business orchestration, several concepts are generally involved:
capability: refers to a single business behavior, such as web page, data access, etc., and the process is arranged, i.e., "ability", which can be performed by one or a group of execution components, and the component is the execution unit of the ability and the basis of the business execution.
Service identity: the unique id of a service is described, the identity of the service is uniquely determined through service behaviors (such as ordering, refunding and the like) and special attributes (such as commodity attributes, activity types and the like) extracted from the service, the service identity can be single dimension or aggregation of multiple dimensions, and only one service rule can be uniquely matched.
And (4) business rules: and aggregating the service capabilities, wherein one service identity corresponds to one service rule, the execution engine schedules each capability according to the service rule, the service rule can be interpreted into an instruction list in the execution engine, and the execution engine utilizes the instruction list to dynamically or preproduce an execution chain.
Flow arrangement: various capabilities are arranged to complete a certain service, and the various capabilities are orderly woven and aggregated into a specific execution chain.
In this embodiment, by redefining the execution engine of the service, the service rules and the service identities defined in the centralized cloud environment can be reapplied in the edge cloud collaborative environment.
The centralized business arrangement method based on the cloud edge collaborative environment comprises the following steps:
(1) redefining the components in a mode of 'edge site name + original component name';
in the cloud-side system, the definition of the component is not only a business behavior running in a cloud environment, but also the definition of the component exists in the edge environment, so that the component is defined in the component in a mode of 'edge site name + component name', the component of the cloud is an independent functional component in the arranging system, in a new definition engine, the edge site attribution of the component can be determined by analyzing the component name, and in addition, a self-registered functional component registration mechanism needs to be provided due to the fact that the number of edge functional components is large.
(2) Component self-registration discovery: arranging an edge agent on an edge site, configuring service capability corresponding to the component on the edge agent and sending the service capability to an edge cloud service cooperation engine at the cloud end, and sending the engine back to the site after processing to finish the registration process;
as shown in fig. 2, in this embodiment, the flow of the component self-registration discovery mechanism is as follows:
If not, the scanning is performed periodically, step 103.
And step 104, if the service components of the edge are scanned, acquiring the names of the service components, adding the names of the sites, and sending the service capabilities of the components to the cloud service coordination engine of the cloud edge.
And 105, the edge cloud coordination engine receives the service component registration message, converts the service component registration message into an interface message format required by the centralized service arrangement system and registers the interface message format.
And step 106, the edge cloud coordination engine receives a message format returned by the centralized business arrangement component.
And step 107, after the edge cloud cooperation engine decomposes the component name into a site name and a service name, searching in a local database.
Step 109, if the same name service group exists, adding the service of the site into the existing service group.
And step 110, otherwise, creating a service group by the name of the newly-built component.
In step 111, the edge cloud coordination engine will obtain the site name of the registered component by sending the name, search the local database and obtain the communication information (such as IP address) of the registered component,
and step 112, forwarding the message success/failure message to the corresponding site by the edge cloud engine.
In step 113, the process ends.
(3) And (3) service issuing: the cloud judges the type of the component, acquires a site corresponding to the component, and completes service delivery according to the type and the site.
After the components are registered in the edge cloud coordination engine, service delivery adaptation can be carried out on the components
And step 203, continuously judging whether the component group is a component group.
In step 207, each component returns an acknowledgement response after receiving it.
And step 208, the task manager monitors the tasks, if all the tasks are completed, the service adaptation is completed, and the flow is finished.
In step 211, the process ends after receiving the response.
At step 212, the process ends.
In step 201 and 212, the edge components may not be able to communicate due to network communication, which requires establishing a component agent in the edge cloud coordination to adapt to the scenario, where the component agent is an agent of each edge component in the cloud, and is independent of the state and can be used as an orchestration component of centralized business orchestration. The component agent is responsible for service delivery, cache registration or cache of data and messages involved in service delivery, thereby realizing adaptation to centralized arrangement. The building agent also monitors the communication condition of the site, if the site has a problem in communication with the cloud end, the building agent sends a message to the component agent, and the building agent sends the message after waiting for the edge actual component to be online.
The component shadow has several adaptations to the service invocation:
synchronous waiting for messages: each time of service invocation, the edge cloud coordination engine sends a message to the component proxy, and the component proxy needs to wait for the service invocation to succeed after the actual component returns a confirmation message;
asynchronous waiting for messages: each time of service calling, the edge cloud coordination engine sends a message to the component proxy, the component proxy directly returns a service processing success, then the component proxy sends the message to the edge actual component and waits for the conditions of response or timeout of the edge actual component, and the proxy component calls different callback interfaces of the service engine according to the return condition to inform the service engine;
at least one message: each time of service calling, the edge cloud coordination engine sends a message to the component proxy, the edge cloud engine does not need the component to return a confirmation message, but the component proxy must ensure a response confirmation message returned to the component proxy by the edge component, the proxy component does not need to inform the service engine after receiving the confirmation message responded by the edge component, and an informing interface of the service engine does not need to be called.
Best effort message: and each time of service calling, the edge cloud coordination engine sends a message to the component proxy, the edge cloud engine does not need the component to return a confirmation message, the component proxy does not need to ensure the confirmation message of the edge component, the component can be configured with the maximum retransmission times, the message is directly discarded after the times are reached, and a notification interface of the service engine of the system does not need to be called. Through the messages, the adaptation of the centralized service arrangement system to the distributed message scenes is ensured.
In a centralized orchestration system, components are only present in the local environment, while in a side cloud environment, components are geographically pulled away, resulting in unreliable communication, and therefore the side cloud coordination engine needs to build a reliable edge component channel.
Because there are many edge sites and most of the edge components have the same functional capability, components with the same capability of multiple sites need to be executed simultaneously on a business rule, and in a side cloud coordination engine, the components with the same functional business capability are grouped to form a functional group and then added into a centralized arrangement system, so that the centralized arrangement system operates a distributed functional group as an independent centralized functional component to carry out arrangement, and distributed centralized operation is realized, and therefore the cloud side coordination engine needs to provide a distributed distribution mechanism to guarantee.
Claims (8)
1. A centralized business arrangement method based on a cloud edge collaborative environment is characterized by comprising the following steps:
(1) redefining the component in a mode of edge site names and original component names;
(2) component self-registration discovery: arranging an edge agent on an edge site, configuring service capacity corresponding to the components on the edge agent and sending the service capacity to an edge cloud cooperation engine at the cloud end, and sending the processed service capacity to the site after the engine is processed so as to finish a registration process;
(3) and (3) service issuing: the cloud judges the type of the component, acquires a site corresponding to the component, and completes service delivery according to the type and the site.
2. The centralized orchestration business method based on the cloud-edge collaborative environment according to claim 1, wherein the step (2) specifically comprises the following steps:
(201) setting an edge proxy at an edge site, and configuring service capacity corresponding to the component on the edge proxy;
(202) the edge agent scans whether the service capability of the components at the site is ready in real time by reading the description file, and if so, the operation is executed (203);
(203) scanning a service component located at an edge site, acquiring a service component name and a site name, and sending the service capability of the component to a cloud service coordination engine at a cloud side;
(204) the edge cloud coordination engine receives the service component registration message, converts the service component registration message into an interface message format required by the centralized service arrangement system and registers the interface message format;
(205) returning the component name to the edge cloud cooperation engine by the component, decomposing the component name into a site name and a service name by the engine, searching whether the component with the same site name exists in a database, and acquiring communication information of the component;
(206) if the components with the same site name exist, the components are stored as the same service group;
(207) and the edge cloud engine forwards the component registration success message to the corresponding site.
3. The method for centralized orchestration of services based on cloud-edge collaborative environment according to claim 2, wherein in steps (203) - (206), when obtaining a service component name fails, engine name resolution fails or service group division fails, or any one of the steps fails to be performed successfully, a message of site registration failure is fed back and a failure reason is fed back at the same time.
4. The method for centralized orchestration of services based on cloud-edge collaborative environment according to claim 2, wherein in step (205), if there is no component with the same name, the component is saved into a new task group.
5. The centralized orchestration business method based on the cloud-edge collaborative environment according to claim 1, wherein the step (3) specifically comprises the following steps:
(301) arranging components by the centralized business arranging system, judging whether the components are distributed components, if so, executing the step (302), otherwise, processing according to the original business;
(302) judging whether the component is a component group, if so, searching the database to obtain all components under the component group, otherwise, executing the step (308)
(303) Acquiring a site corresponding to each component;
(304) creating a task manager and issuing the service to all the components in the component group in parallel;
(305) each component returns a confirmation message after receiving the confirmation message, executes the task and sends a completion message after completing the task;
(306) the task manager monitors the tasks, if all the tasks are completed, the service adaptation is completed, the flow transfer is finished, and if not, the overtime task is retransmitted;
(307) if the retransmission fails, the service call fails, and the flow transfer is finished;
(308) if the component is a single component, the corresponding service is directly issued, and the process is ended after the response of the component is received.
6. The centralized orchestration business method based on cloud-edge collaborative environment according to claim 1, wherein a component agent is established in the edge cloud collaborative orchestration engine, the component agent is responsible for business delivery, cache registration or cache of data and messages involved in the business delivery, the communication condition of a site is monitored, if a problem occurs in the site and cloud communication, a message is delivered to the component agent, and the agent performs the delivery after waiting for an edge actual component to go online.
7. The method for centralized orchestration of business based on cloud edge collaborative environment according to claim 6, wherein the component shadow has the following adaptations for business invocation:
synchronous waiting for messages: each time of service invocation, the edge cloud coordination engine sends a message to the component proxy, and the component proxy needs to wait for the service invocation to succeed after the actual component returns a confirmation message;
asynchronous waiting for messages: each time of service calling, the edge cloud coordination engine sends a message to the component proxy, the component proxy directly returns a service processing success, then the component proxy sends the message to the edge actual component and waits for the conditions of response or timeout of the edge actual component, and the proxy component calls different callback interfaces of the service engine according to the return condition to inform the service engine;
at least one message: each time of service calling, the edge cloud coordination engine sends a message to the component proxy, the edge cloud engine does not need the component to return a confirmation message, but the component proxy must ensure a response confirmation message returned to the component proxy by the edge component, the proxy component does not need to inform the service engine after receiving the confirmation message responded by the edge component, and an informing interface of the service engine does not need to be called.
Best effort message: and each time of service calling, the edge cloud coordination engine sends a message to the component proxy, the edge cloud engine does not need the component to return a confirmation message, the component proxy does not need to ensure the confirmation message of the edge component, the component can be configured with the maximum retransmission times, the message is directly discarded after the times are reached, and a notification interface of the service engine of the system does not need to be called.
8. A centralized arrangement business system based on a cloud-side collaborative environment is characterized by comprising a centralized arrangement system and a side cloud collaborative engine arranged at a cloud end, wherein the side cloud collaborative engine is connected with a side cloud collaborative agent arranged at an edge site; the edge cloud cooperation engine is used for completing the business arrangement method of any one of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110204007.5A CN112950153B (en) | 2021-02-24 | 2021-02-24 | Centralized business arrangement method and system based on cloud edge collaborative environment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110204007.5A CN112950153B (en) | 2021-02-24 | 2021-02-24 | Centralized business arrangement method and system based on cloud edge collaborative environment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112950153A true CN112950153A (en) | 2021-06-11 |
| CN112950153B CN112950153B (en) | 2023-12-01 |
Family
ID=76245715
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110204007.5A Active CN112950153B (en) | 2021-02-24 | 2021-02-24 | Centralized business arrangement method and system based on cloud edge collaborative environment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112950153B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101039514A (en) * | 2006-03-14 | 2007-09-19 | 中兴通讯股份有限公司 | Method for accessing positioning engine of positioning service to service management platform |
| US20160380913A1 (en) * | 2015-06-26 | 2016-12-29 | International Business Machines Corporation | Transactional Orchestration of Resource Management and System Topology in a Cloud Environment |
| CN111682973A (en) * | 2020-08-17 | 2020-09-18 | 烽火通信科技股份有限公司 | Method and system for arranging edge cloud |
| CN111866170A (en) * | 2020-07-30 | 2020-10-30 | 南京甄视智能科技有限公司 | Method for sending synchronous message in IOT cluster |
| CN112087522A (en) * | 2020-09-18 | 2020-12-15 | 北京航空航天大学 | Edge cloud collaborative flow arrangement system for industrial robot data processing |
| CN112272238A (en) * | 2020-10-29 | 2021-01-26 | 国网山东省电力公司威海供电公司 | Cloud-edge service interaction method for power Internet of things |
-
2021
- 2021-02-24 CN CN202110204007.5A patent/CN112950153B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101039514A (en) * | 2006-03-14 | 2007-09-19 | 中兴通讯股份有限公司 | Method for accessing positioning engine of positioning service to service management platform |
| US20160380913A1 (en) * | 2015-06-26 | 2016-12-29 | International Business Machines Corporation | Transactional Orchestration of Resource Management and System Topology in a Cloud Environment |
| CN111866170A (en) * | 2020-07-30 | 2020-10-30 | 南京甄视智能科技有限公司 | Method for sending synchronous message in IOT cluster |
| CN111682973A (en) * | 2020-08-17 | 2020-09-18 | 烽火通信科技股份有限公司 | Method and system for arranging edge cloud |
| CN112087522A (en) * | 2020-09-18 | 2020-12-15 | 北京航空航天大学 | Edge cloud collaborative flow arrangement system for industrial robot data processing |
| CN112272238A (en) * | 2020-10-29 | 2021-01-26 | 国网山东省电力公司威海供电公司 | Cloud-edge service interaction method for power Internet of things |
Non-Patent Citations (1)
| Title |
|---|
| 乔爱锋;: "MEC规划方案及部署策略的探讨", 电信工程技术与标准化, no. 10 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112950153B (en) | 2023-12-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112788074B (en) | Data transmitting method, processing method, receiving method, apparatus thereof, and storage medium | |
| US10834033B2 (en) | Method and system for transferring messages between messaging systems | |
| US7363053B2 (en) | System for integrated mobile devices | |
| CN106411919B (en) | Web pushing method based on event bus | |
| CN112527523A (en) | Distributed message transmission method and system for high-performance computing multiple clouds | |
| CN116319732A (en) | Message queue centralized configuration management system and method based on RabbitMQ | |
| CN116382943A (en) | Sequential message processing method, bus system, computer device, and storage medium | |
| CN111401837A (en) | Event processing method and system, computer readable storage medium | |
| CN113824653A (en) | Method and system compatible with multi-protocol service access | |
| CN109491767A (en) | The processing method and distributed system of distributed transaction | |
| CN112950153A (en) | Centralized business arrangement method and system based on cloud edge collaborative environment | |
| CN201854301U (en) | Middleware system for sharing data on mobile phones | |
| CN114338584B (en) | Message withdraw method and message transmission system | |
| CN110381143A (en) | Operation, which is submitted, executes method, apparatus, equipment and computer storage medium | |
| CN111416889B (en) | Communication method and system adapted through GATT and exception handling | |
| US7757235B2 (en) | Trigger support for a bi-directional broker | |
| CN113407611B (en) | Data integration distribution platform and system | |
| CN113886043B (en) | Simulation task scheduling system for comprehensively deploying public cloud and private cloud | |
| CN115550439B (en) | Event management system and method | |
| CN113204434B (en) | Planned task execution method and device based on k8s and computer equipment | |
| CN110620778B (en) | Method for simultaneously supporting synchronous and asynchronous communication modes of socket | |
| CN118509440A (en) | Message synchronization method between heterogeneous systems based on distributed coordination | |
| CN101035320B (en) | Full users broadcasting method and system | |
| CN117640659A (en) | Unified message data processing method, device and storage medium | |
| CN117950829A (en) | Task scheduling method based on message queue and computer readable storage medium |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |