CN116800736A

CN116800736A - Cross-cloud data processing method and device, public cloud equipment, medium and program product

Info

Publication number: CN116800736A
Application number: CN202210268594.9A
Authority: CN
Inventors: 李斌
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2022-03-18
Filing date: 2022-03-18
Publication date: 2023-09-22

Abstract

The embodiment of the application discloses a cross-cloud data processing method, a device, public cloud equipment, a medium and a program product, which are applied to the field of cloud technology. The method comprises the following steps: acquiring at least one service distribution data for a plurality of private cloud devices, adding the at least one service distribution data into a main data queue, respectively extracting the service distribution data of each private cloud device from the main data queue, and respectively adding the service distribution data of each private cloud device into a sub data queue corresponding to each private cloud device. By adopting the embodiment of the application, the reliability and the safety of cross-cloud data communication can be improved. The embodiment of the application can be applied to various scenes such as cloud technology, artificial intelligence, intelligent traffic, auxiliary driving and the like.

Description

Cross-cloud data processing method and device, public cloud equipment, medium and program product

Technical Field

The present application relates to the field of cloud technologies, and in particular, to a method and apparatus for processing cross-cloud data, a public cloud device, a medium, and a program product.

Background

The cross-cloud service represents data communication between public cloud devices and private cloud devices, and data transmission is usually achieved by calling a designated interface of the other party. For example, the public cloud device invokes a data interface on the private cloud device and sends data to enable data delivery. However, in this manner, the coupling degree between the devices is high, the interface is not easy to maintain, and the security of data transmission is low. Therefore, how to improve the reliability and security of cross-cloud data communication is a problem to be solved.

Disclosure of Invention

The embodiment of the application provides a cross-cloud data processing method, a device, public cloud equipment, a medium and a program product, which can improve the reliability and safety of cross-cloud data communication.

In one aspect, an embodiment of the present application provides a cross-cloud data processing method, where the method includes:

acquiring at least one service distribution data for a plurality of private cloud devices, and adding the at least one service distribution data into a main data queue;

respectively extracting service distribution data of each private cloud device from the main data queue;

the service distribution data of each private cloud device are respectively added into a sub-data queue corresponding to each private cloud device; each private cloud device is used for acquiring the service distribution data according to the corresponding sub-data queue.

In one aspect, an embodiment of the present application provides a cross-cloud data processing apparatus, including:

the processing module is used for acquiring at least one service distribution data aiming at a plurality of private cloud devices and adding the at least one service distribution data into the main data queue;

the extraction module is used for respectively extracting service distribution data of each private cloud device from the main data queue;

The processing module is further used for adding the service distribution data of each private cloud device to the corresponding sub-data queue of each private cloud device respectively; each private cloud device is used for acquiring the service distribution data according to the corresponding sub-data queue.

In one aspect, an embodiment of the present application provides a public cloud device, where the public cloud device includes a processor and a memory, where the memory is configured to store a computer program, where the computer program includes program instructions, and where the processor is configured to invoke the program instructions to perform some or all of the steps in the method described above.

In one aspect, embodiments of the present application provide a computer readable storage medium storing a computer program comprising program instructions for performing part or all of the steps of the above method when executed by a processor.

Accordingly, according to one aspect of the present application, there is provided a computer program product or computer program comprising program instructions stored in a computer readable storage medium. The processor of the computer device reads the program instructions from the computer-readable storage medium, and the processor executes the program instructions, so that the computer device performs the cross-cloud data processing method provided above.

In the embodiment of the application, at least one service distribution data for a plurality of private cloud devices can be acquired, the at least one service distribution data is added into a main data queue, the service distribution data of each private cloud device is respectively extracted from the main data queue, and the service distribution data of each private cloud device is respectively added into a sub data queue corresponding to each private cloud device. By the method, the service distribution data can be uniformly added to the main data queue and respectively added to the sub data queues, the coupling property of public cloud equipment and private cloud equipment in data communication can be reduced, the reliability and the safety of data transmission are improved, and when a plurality of private cloud equipment have the same service distribution data, the service distribution data can be only added once in the main data queue and respectively added to the corresponding sub data queues, and the data transmission efficiency can be improved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for the description of the embodiments will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a schematic diagram of an application architecture according to an embodiment of the present application;

fig. 2 is a schematic flow chart of a cross-cloud data processing method according to an embodiment of the present application;

FIG. 3 is a schematic diagram of a cross-cloud data processing framework according to an embodiment of the present application;

fig. 4 is a schematic flow chart of a cross-cloud data processing method according to an embodiment of the present application;

fig. 5 is a schematic flow chart of cross-cloud data transmission according to an embodiment of the present application;

fig. 6 is a schematic flow chart of cross-cloud data transmission based on data distribution according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a cross-cloud data processing device according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of public cloud equipment according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application.

The cross-cloud data processing method provided by the embodiment of the application is implemented in public cloud equipment, and the public cloud equipment can be a server. The server may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network ), basic cloud computing services such as big data and artificial intelligence platform, but is not limited thereto. The embodiment of the application can be applied to various scenes, including but not limited to cloud technology, artificial intelligence, intelligent transportation, auxiliary driving and the like.

Next, technical terms related to the technical field of possible application of the scheme of the embodiment of the present application are described in the following:

1. cloud technology:

cloud technology (Cloud technology) is a generic term of network technology, information technology, integration technology, management platform technology, application technology and the like based on Cloud computing business model application, and can form a resource pool, so that the Cloud computing business model application system is flexible and convenient as required. Cloud computing technology will become an important support. Background services of technical networking systems require a large amount of computing, storage resources, such as video websites, picture-like websites, and more portals. Along with the high development and application of the internet industry, each article possibly has an own identification mark in the future, the identification mark needs to be transmitted to a background system for logic processing, data with different levels can be processed separately, and various industry data needs strong system rear shield support and can be realized only through cloud computing.

In a possible implementation manner, the cross-Cloud data processing method provided by the embodiment of the application can be combined with Cloud applications in Cloud technology, for example, a distribution task of service distribution data in the technical scheme of the application can be specifically combined with Hybrid Cloud (Hybrid Cloud) to realize cross-Cloud communication. The hybrid Cloud fuses Public Cloud (Public Cloud) and Private Cloud (Private Cloud), and is a main mode and development direction of Cloud computing in recent years. Private clouds are mainly for enterprise users, and for safety reasons, enterprises prefer to store data in the private clouds, but at the same time wish to obtain computing resources of public clouds, in which case hybrid clouds are increasingly adopted, and mix and match the public clouds and the private clouds to obtain the best effect.

2. Cross-cloud communication:

cross-cloud communication is a concept in hybrid cloud, and refers to realizing data communication between public cloud equipment and private cloud equipment in a hybrid cloud mode. The technical scheme of the application can realize reliable data transmission between public cloud and private cloud. Among them, cross-cloud communication is roughly classified into two types: and data issuing and data reporting.

(1) And (3) data issuing: in the hybrid cloud mode, data (such as business data, configuration data, business service operation information and the like) on public cloud equipment is issued to private cloud equipment.

(2) And (3) data reporting: and in the hybrid cloud mode, reporting data (such as business data, index data and the like) on the private cloud equipment to the public cloud equipment. The application can realize the reliability and stability of the data transmission process.

3. Message queues:

the message queue is an important component in the distributed system, can solve the problems of application coupling, asynchronous message, flow cutting and the like, realizes a high-performance, high-availability, scalable and final consistency architecture, is an indispensable middleware in a large-scale distributed system, and the common message queue can comprise Kafka (a distributed, high-throughput and high-expansibility message queue system), rabbitMQ (an open source message queue system) and the like.

The message queue used in the service distribution task can be CMQ (Cloud Message Queue ), CMQ is a distributed message queue service, which can provide a reliable asynchronous communication mechanism based on messages, and can store the transmitted and received messages between different applications (or different components of the same application) in a reliable and effective CMQ queue to prevent the messages from being lost. CMQ supports multiple processes to read and write simultaneously, and the receiving and transmitting are not interfered with each other, and all applications or components are not required to be in an operation state all the time.

In some embodiments, please refer to fig. 1, fig. 1 is a schematic diagram of an application architecture provided in an embodiment of the present application, through which the cross-cloud data processing method provided in the present application may be executed. As shown in fig. 1, may include a public cloud device and a plurality of private cloud devices; the public cloud device can acquire one or more service distribution data aiming at a plurality of private cloud devices, add the one or more service distribution data to a main data queue, and correspondingly add the one or more service distribution data from the main data queue to a sub-data queue corresponding to the private cloud device, and the private cloud device can pull the service distribution data to the local area when detecting that the service distribution data exists in the corresponding sub-data queue so as to perform data processing according to the service distribution data. For example, the private cloud device may update a local database according to the pulled service distribution data, and so on. In fig. 1, only 3 private cloud devices are illustrated, and the number of private cloud devices is not limited in practice.

It should be understood that fig. 1 is merely exemplary to represent possible application architectures of the technical solution of the present application, and is not limited to specific architectures of the technical solution of the present application, that is, the technical solution of the present application may also provide other application architectures.

Optionally, in some embodiments, the public cloud device may execute the cross-cloud data processing method according to actual service requirements to improve reliability of cross-cloud data transmission. The technical scheme of the application can be applied to any communication scene of cross-cloud equipment, namely public cloud equipment can acquire service distribution data to be issued and is added into a main data queue, private cloud equipment corresponding to the service distribution data is determined, the service distribution data is added into a sub-data queue of the private cloud equipment, the private cloud equipment acquires the issued service distribution data from the sub-data queue, and the security of cross-cloud communication and the efficiency of data transmission can be improved.

Optionally, the data related to the present application, such as service distribution data, may be stored in a database of public cloud devices, or may be stored in a blockchain, for example, stored by a blockchain distributed system, which is not limited by the present application.

It can be understood that the above scenario is merely an example, and does not constitute a limitation on the application scenario of the technical solution provided by the embodiment of the present application, and the technical solution of the present application may also be applied to other scenarios. For example, as one of ordinary skill in the art can know, with the evolution of the system architecture and the appearance of new service scenarios, the technical solution provided by the embodiment of the present application is also applicable to similar technical problems.

Based on the above description, the embodiments of the present application provide a cross-cloud data processing method, which may be performed by the public cloud device mentioned above. Referring to fig. 2, fig. 2 is a flow chart of a cross-cloud data processing method according to an embodiment of the present application. As shown in fig. 2, the flow of the cross-cloud data processing method according to the embodiment of the present application may include the following:

s201, acquiring at least one service distribution data for a plurality of private cloud devices, and adding the at least one service distribution data into a main data queue.

In some embodiments, the public cloud device and the private cloud device may be devices in any cross-cloud scenario, for example, the private cloud device may be a terminal device, and the terminal device has an application program therein, and the public cloud device may be a background server corresponding to the application program. For another example, the private cloud device may be an application server, and the application server has an application program, where the private cloud device may be used as a background server corresponding to a front end having the application program, and the public cloud device may be a central server corresponding to the private cloud device, and may be used to uniformly manage application data in the private cloud device. Specific types of public cloud devices and private cloud devices are not limited herein. The traffic distribution data may be any traffic data related to a cross-cloud scenario. For example, the private cloud device is an application server with an application program, the public cloud device is a corresponding central server, and the service distribution data may be update program data of the application program, such as version update data of a certain component in the application program, update data of a certain service in the application program, and the like. The type of service distribution data is not limited here. For convenience of explanation, the private cloud device is taken as an application server, and the public cloud device is taken as a central server corresponding to the private cloud device for explanation

In some embodiments, if the plurality of private cloud devices each have an application program, the at least one service distribution data for the plurality of private cloud devices acquired by the public cloud device may include update program data of the application program, where the update program data belongs to the service distribution data of each private cloud device. The update program data can be configured by relevant service personnel corresponding to public cloud equipment. Optionally, if some private cloud devices in the plurality of private cloud devices have an application program, the at least one service distribution data acquired by the public cloud device may include update program data of the application program, and the update program data only belongs to service distribution data of each private cloud device in the some private cloud devices having the application program. Wherein, the application program of one private cloud device can be one or more.

For example, the plurality of private cloud devices are all application servers with an application program a, the public cloud device is a corresponding central server, and application update operation is performed on the public cloud device on the application program a to obtain update program data for the application program a, such as configuration data of a certain newly added service in the application program a, where the update program data belongs to service distribution data of each private cloud device in the plurality of private cloud devices.

For another example, if the application program a and the application program B have an association relationship, for example, the application program a is shopping software, the application program B is rebate software for the application program a, the private cloud device 1 and the private cloud device 2 are set as application servers corresponding to the application program a, the private cloud device 3 and the private cloud device 4 are application servers corresponding to the application program B, and the public cloud device may be a central server corresponding to the private cloud devices 1-4, so as to uniformly manage part of application data (such as merchandise information) in the application program a and the application program B; (1) Setting the update program data as the price of commodity A in the application program A and the application program B is modified from 10 to 20, wherein the plurality of private cloud devices are provided with the application program indicated by the update program data (namely the application program A or the application program B) and the service distribution data of each private cloud device; (2) Let the update program data be modified from 10 to 20 for the price of commodity a in the application program a, then only the private cloud device 1 and the private cloud device 2 in the plurality of private cloud devices have the application program indicated by the update program data (i.e., the application program a), and the update program data belong to the service distribution data of the private cloud device 1 and the private cloud device 2.

In one possible implementation manner, if the plurality of private cloud devices all have the same or different application programs, N private cloud devices in the plurality of private cloud devices subscribe to a target service in the application programs, the at least one service distribution data may include subscription data indicated by the target service, and the subscription data at this time only belongs to service distribution data of the private cloud devices subscribed to the target service. Therefore, the public cloud device acquires at least one service distribution data for the plurality of private cloud devices, specifically, when a service distribution event of the target service is triggered, subscription data indicated by the target service is acquired.

Wherein the target service may be any service in the application program, for example, the target service may be an update program service, and the subscription data may be update program data; as another example, the target service may be a program check-in service, and the subscription data may be check-in prompt information or the like. The specific type of targeted traffic and subscription data is not limited herein. The service distribution event may be any type of event, for example, may be a timed subscription event, that is, may be that when the public cloud detects that a subscription time point arrives, subscription data is acquired and issued, for example, when the public cloud detects that a preset time point arrives, sign-in prompt information is generated and issued; for example, the instruction issuing event may be an instruction issuing event, that is, when an instruction issuing for subscription data is detected, the subscription data is acquired and issued; the issuing instruction can be generated by touch control of related business personnel through related issuing control, or can be generated automatically when public cloud equipment detects subscription data generation, for example, after the related business personnel detects updating operation of an application program, updating program data is generated according to the updating operation, and the issuing instruction is generated.

In some embodiments, applications of different private cloud devices may be different, target services subscribed to by private cloud devices having the same application may be different, service distribution events corresponding to private cloud devices subscribed to the same target service may be different, and service distribution data corresponding to private cloud devices subscribed to the same target service may include the same subscription data. When the service distribution event of the same target service is detected to be triggered at the same time point, the subscription data corresponding to at least two private cloud devices exist at the same time point, and the subscription data can be combined to obtain subscription data at the time point and serve as the service distribution data of the at least two private cloud devices.

In some embodiments, assuming any one of the plurality of private cloud devices as the target private cloud device, the at least one service distribution data may further include data requested by the target private cloud device. Therefore, at least one service distribution data for the plurality of private cloud devices is acquired, specifically, when a data request sent by the target private cloud device is received, the data request carries a data identifier of the requested data, the request data associated with the data identifier is acquired, and the request data is taken as at least one service distribution data. The data identifier may be set by the relevant service personnel according to the service scenario to which the request data belongs, for example, the request data is identity information of the user a, and the data identifier may be an identifier representing the user or the user a or user information or identity information, etc. The specific type of data identification is not limited herein.

Therefore, the at least one service distribution data includes service distribution data which only belongs to one private cloud device and service distribution data which can belong to more than one private cloud device, and the public cloud device can add the at least one service distribution data into the main data queue when acquiring the at least one service distribution data. When two or more private cloud devices have the same service distribution data at the moment, the service distribution data is added once to a main data queue. The service distribution data in the subsequent main data queue can be simultaneously and respectively added to a plurality of sub data queues.

S202, service distribution data of each private cloud device are respectively extracted from the main data queue.

In some embodiments, the public cloud device sequentially determines one or more private cloud devices to which each service distribution data in the main data queue belongs, and extracts the service distribution data to be respectively distributed to the one or more private cloud devices to which each service distribution data belongs.

Based on the description, the public cloud device sequentially determines one or more private cloud devices to which each service distribution data belongs in the main data queue, and if the service distribution data is update program data of an application program, the private cloud device to which the service distribution data belongs is the private cloud device with the application program; if the service distribution data is the subscription data of the target service, the private cloud device to which the service distribution data belongs is the private cloud device subscribed to the target service; and if the service distribution data is the data requested by the target private cloud device, the private cloud device to which the service distribution data belongs is the target private cloud device.

S203, the service distribution data of each private cloud device are respectively added into the sub-data queues corresponding to each private cloud device.

In one possible implementation manner, the public cloud device may sequentially add the service distribution data in the main data queue to the sub data queue corresponding to the allocated private cloud device. One private cloud device may correspond to one child data queue. Each private cloud device can be used for acquiring the service distribution data according to the corresponding sub-data queue.

In some embodiments, the private cloud device may obtain the service distribution data from the corresponding sub-data queue, which may be actively obtained by the private cloud device, or may be forwarded by the public cloud device. When the private cloud devices actively acquire, each private cloud device has access rights to a corresponding sub-data queue in the public cloud device, and each private cloud device is used for respectively pulling the service distribution data from the corresponding sub-data queue according to the access rights to the corresponding sub-data queue; the private cloud equipment has a monitoring mechanism aiming at the corresponding sub-data queue, and when the fact that the data exists in the corresponding sub-data queue is monitored, service distribution data added by the public cloud equipment can be obtained. When the public cloud equipment forwards the data, the private cloud equipment can send a data query instruction to the public cloud equipment in real time or periodically, and when the public cloud equipment queries that the added service distribution data exists in the indicated sub-data queue according to the data query instruction, the service distribution data is forwarded to the corresponding private cloud equipment.

In some embodiments, when the private cloud device acquires the service distribution data, data processing may be performed based on the service distribution data. For example, the plurality of private cloud devices each have an application program, service distribution data of the plurality of private cloud devices each include update program data of the application program, and each private cloud device is configured to update the application program according to the pulled update program data. If the update program data is to change the price of the commodity A to 20 yuan, the private cloud device can update the price of the commodity A in the locally stored application program.

In one possible implementation manner, the above-described cross-cloud data issuing process from the public cloud device to the private cloud device may also be a cross-cloud communication process between a plurality of private cloud devices. When public cloud equipment acquires a data forwarding request sent by the first private cloud equipment, the data forwarding request carries forwarding service data and equipment identifiers of the second private cloud equipment, wherein the forwarding service data can be data belonging to at least one service distribution data or other data; and adding the forwarding service data into a sub-data queue corresponding to the second private cloud device, so that the second private cloud device obtains the forwarding service data from the corresponding sub-data queue. The public cloud device may directly add the forwarding service data to the sub-data queue corresponding to the second private cloud device, or may first add the forwarding service data to the main data queue, and when the main data queue sequentially performs data addition, the forwarding service data is added from the main data queue to the sub-data queue corresponding to the second private cloud device, and at this time, the forwarding service data located in the main data queue may be understood to be service distribution data of the second private cloud device. The number of the second private cloud devices can be one or more, and when the number of the second private cloud devices is a plurality of, the data forwarding request carries device identifiers of the plurality of second private cloud devices, and the public cloud devices respectively add forwarding service data to sub-data queues corresponding to the plurality of second private cloud devices.

In some embodiments, the above procedure may also be followed when the private cloud device performs data reporting to the public cloud device. Taking any private cloud device in the plurality of private cloud devices as a target private cloud device as an example, the target private cloud device sends a data reporting request, wherein the data reporting request carries reporting service data, and the public cloud device can receive the reporting service data for storage or processing and the like; or the report service data is added into the corresponding sub-data queue of the public cloud equipment, and the public cloud equipment pulls the report service data from the corresponding sub-data queue; the report service data may be added to a main data queue (the main data queue used in reporting data and the main data queue used in transmitting data may be the same queue or different queues), and the report service data is added from the main data queue to a sub data queue corresponding to the public cloud device, where the report service data in the main data queue may be understood as service distribution data for the public cloud device. The public cloud device can judge which sub-data queue the reported service data belongs to and then adds the reported service data into the affiliated sub-data queue. The judging rule may be any rule, for example, may be determined according to a service type of the reported service data, for example, when the reported service data is user identity data, the sub-data queue to which the reported service data belongs is a sub-data queue a; when the reported service data is user payment data, the sub-data queue is a sub-data queue B and the like. And are not limited herein. Subsequently, the public cloud device can pull different reporting service data according to different sub-data queues and store the reporting service data in corresponding positions or process the reporting service data correspondingly, and the public cloud device can be set by related service personnel according to actual application scenes.

Optionally, the above process may be implemented by a cross-cloud service, where both public cloud devices and private cloud devices may have a cross-cloud service, and data reporting and data issuing may be performed by the cross-cloud service.

For example, as shown in fig. 3, fig. 3 is a schematic diagram of a cross-cloud data processing framework according to an embodiment of the present application; the cross-cloud service can comprise a data sending service and a data receiving service, and public cloud equipment, private cloud equipment A (such as management and control equipment for providing service) and private cloud equipment B (such as service processing equipment for providing service) are provided with the cross-cloud service, so that cross-cloud data interaction between the public cloud equipment and the private cloud equipment and cross-cloud data interaction between the private cloud equipment can be realized through the cross-cloud service; (1) When public cloud equipment performs data issuing, the public cloud equipment can call a data sending service in cross-cloud service to add service distribution data to a main data queue in CMQ, and sequentially add the service distribution data in the main data queue to a sub data queue A corresponding to private cloud equipment A and a sub data queue B corresponding to private cloud equipment B, the private cloud equipment A calls a data receiving service in the cross-cloud service to pull the service distribution data from the sub data queue A, and the private cloud equipment B calls a data receiving service in the cross-cloud service to pull the service distribution data from the sub data queue B; (2) When the private cloud device a performs data reporting, the private cloud device a may call a data sending service to send a data reporting request to add reporting service data to a main data queue in CMQ, and the public cloud device sequentially adds the reporting service data in the main data queue to a sub data queue corresponding to the public cloud device and calls a data receiving service to pull; (3) When the private cloud device a performs data communication with the private cloud device B, the private cloud device a may call a data sending service to send a data forwarding request to add forwarding service data to a main data queue in CMQ, the public cloud device adds forwarding service data in the main data queue to a sub data queue corresponding to the private cloud device B, and the private cloud device B calls a data receiving service to pull.

In the embodiment of the application, at least one service distribution data for a plurality of private cloud devices can be acquired, the at least one service distribution data is added into a main data queue, the service distribution data of each private cloud device is respectively extracted from the main data queue, and the service distribution data of each private cloud device is respectively added into a sub data queue corresponding to each private cloud device. By the method, the coupling performance of public cloud equipment and private cloud equipment in data communication can be reduced, the reliability and the safety of data transmission are improved, and when a plurality of private cloud equipment have the same service distribution data, the service distribution data can be added into a main data queue only once and are respectively added into corresponding sub data queues, so that the occupied space of the data can be reduced, and the data transmission efficiency is improved.

Referring to fig. 4, fig. 4 is a flow chart of a cross-cloud data processing method according to an embodiment of the present application, where the method may be performed by the public cloud device mentioned above. As shown in fig. 4, the flow of the cross-cloud data processing method in the embodiment of the present application may include the following steps:

s401, acquiring at least one service distribution data for a plurality of private cloud devices, and adding the at least one service distribution data into a main data queue. The specific implementation manner of step S401 may be referred to the related description of the above embodiments, which is not repeated herein.

S402, respectively extracting service distribution data of each private cloud device from the main data queue.

In some embodiments, when service distribution data is acquired by the public cloud device, a data identifier is added to the service distribution data, the service distribution data added with the data identifier is added to the main data queue, and when the service distribution data of each private cloud device is extracted, the service distribution data corresponding to each private cloud device can be determined according to the data identifier of the service distribution data. The data identifier may be related to a service scenario of service distribution data, may be related to private cloud devices to be distributed, may also be related to a type of service distribution data, and a specific generation rule of the data identifier may be set by related service personnel, which is not limited herein. Thus illustratively:

(1) When the service distribution data is actively issued by public cloud equipment, such as update program data, any private cloud equipment with an application program where the update program data is located can acquire the service distribution data, the data identification of the service distribution data can be generated based on a service scene, and if the service distribution data is update data of a commodity, the data identification can be commodity information; in another example, the service distribution data is identity update data of the user a, and the data identifier may be identity information or the like.

(2) When the service distribution data is subscription data of the target service, any private cloud device subscribed to the target service can acquire the service distribution data, and the data identifier of the service distribution data can be generated based on the target service.

(3) When the service distribution data is service data requested by a certain private cloud device, only the private cloud device sending the request can acquire the service distribution data at the moment, and the data identifier of the service distribution data can be generated based on the device identifier of the private cloud device (optionally, can also be generated based on the service scene and the device identifier of the service distribution data together), which indicates that the service distribution data belongs to the private cloud device with the device identifier.

(4) When the service distribution data is forwarding service data that a certain private cloud device requests to forward to another private cloud device, only the other private cloud device can acquire the service distribution data at this time, a data identifier of the service distribution data may be generated based on a device identifier of the other private cloud device (optionally, may also be generated jointly based on a service scene and a device identifier of the service distribution data), which indicates that the service distribution data belongs to the other private cloud device.

(5) When the service distribution data is reported service data of the private cloud device, the public cloud device acquires the service distribution data at the moment, and the data identifier of the service distribution data can be generated based on the device identifier of the public cloud device (optionally, can also be generated based on the service scene and the device identifier of the service distribution data), which means that the service distribution data is acquired by the public cloud device.

Therefore, it can be understood that when the private cloud device has the right to acquire the service distribution data under a certain data identifier, the service distribution data can be extracted from the main data queue as the service distribution data corresponding to the private cloud device. The data identifier can be understood as a data topic (topic) of service distribution data, the service distribution data can be distributed and added through the data topic, the service distribution data can be uniformly processed in a main data queue, the service distribution data can be respectively added into a sub-data queue according to a data topic to be acquired, which is set by private cloud equipment, the private cloud equipment can be pulled to only interested service distribution data without adding full service distribution data into a corresponding sub-data queue, and the efficiency and convenience of cross-cloud communication are improved.

S403, the service distribution data of each private cloud device are respectively added into the sub-data queues corresponding to each private cloud device.

Each private cloud device can be used for acquiring the service distribution data according to the corresponding sub-data queue.

In some embodiments, the public cloud device may determine service distribution data belonging to each private cloud device according to the data identifier of the service distribution data in the main data queue, and add the service distribution data (or may be the service distribution data carrying the data identifier) to the corresponding sub data queue. The at least one service distribution data comprises target service distribution data, such as subscription data indicated by the target service, the target service belongs to the service subscribed in the application program, the application program is provided by the plurality of private cloud devices, and N private cloud devices in the plurality of private cloud devices subscribe the target service, so that the public cloud devices can add the target service distribution data (subscription data) into sub-data queues respectively corresponding to the N private cloud devices.

In some embodiments, the private cloud device may poll the corresponding sub-data queue in real time or periodically, and when detecting that there is added service distribution data, pull the service distribution data from the corresponding sub-data queue to the private cloud device. Optionally, the private cloud device may have at least one local data queue therein, and when the private cloud device pulls the service distribution data, the private cloud device may add the service distribution data to the local data queue, and the private cloud device consumes the service distribution data from the local data queue.

S404, after the service distribution data is successfully added into the sub-data queue corresponding to each private cloud device, deleting the service distribution data successfully added into the main data queue.

In some embodiments, the at least one service distribution data includes target service distribution data, and the service distribution data of N private cloud devices in the plurality of private cloud devices includes target service distribution data, so that the public cloud device may delete the target service distribution data in the main data queue after the target service distribution data is successfully added to the sub data queues corresponding to the N private cloud devices, respectively.

In some embodiments, after the private cloud device successfully obtains the service distribution data from the corresponding sub-data queue, the public cloud device may also obtain a successful data deletion from the corresponding sub-data queue. Setting any private cloud equipment identifier in the plurality of private cloud equipment as target private cloud equipment, and deleting the service distribution data indicated by the acquisition success prompt information in the sub-data queue corresponding to the target private cloud equipment if the acquisition success prompt information for the service distribution data sent by the target private cloud equipment is acquired.

Therefore, the technical scheme of the application can realize cross-cloud communication of the hybrid cloud model, and can realize reliable bidirectional synchronization, safe communication and stability of data between public cloud equipment and private cloud equipment through various data queues. The public cloud equipment can establish a communication relationship with a plurality of private cloud equipment, and is suitable for one-to-one or one-to-many communication scenes among the equipment. The data queue CMQ is used as an intermediate component for data distribution and storage, has the core functions of data buffering and abnormal retry, can perform abnormal detection and data retention, can perform data retransmission when the data distribution fails so as to ensure that data is not missed, can prevent data loss when the data transmission is abnormal, provides a complete and reliable compensation mechanism for the data transmission, can provide data delivery capability for the main data queue, can add service distribution data into corresponding sub-data queues according to a data subject so as to determine the accuracy of data not to be lost and transmitted, and adds the service distribution data into the data queue; compared with the method that data is directly sent by calling a data transmission interface, the method reduces the coupling between devices and realizes high reusability, and when new private cloud devices exist to carry out cross-cloud communication with public cloud devices, the new private cloud devices can be rapidly integrated and communication relations can be established in the mode, maintenance and configuration of interactive interface information are not needed, and convenience is improved.

In some embodiments, the cross-cloud communication of the present application may be implemented by invoking an RPC (Remote Procedure Call ) interface corresponding to the internal cross-cloud service to initiate the cross-cloud service. The interface is used for calling the cross-cloud service to report or send data, so that lightweight data communication can be realized, and the communication process between devices is decoupled, so that the public cloud device side or the private cloud device side can only need to be in butt joint with the corresponding cross-cloud service, and the cross-cloud service can complete data transmission, thereby paying attention to related services in the public cloud device side or the private cloud device side. The cross-cloud service may include a data transmission service and a data reception service, among others.

Thus: (1) When the public cloud equipment side is used, the service distribution data can be added to the main data queue through the data transmission service by calling the RPC interface corresponding to the data transmission service in the public cloud equipment, the service distribution data can be sequentially added to the corresponding sub-data queues from the main data queue, the private cloud equipment can call the RPC interface corresponding to the data receiving service in the private cloud equipment, the service distribution data can be pulled from the corresponding sub-data queues through the data receiving service, the pulled service distribution data can be forwarded to the local data queue, and the service distribution data can be acquired from the local data queue through different service services in the private cloud equipment side. (2) When the public cloud equipment side is used as the private cloud equipment side, the reporting service data can be added to the main data queue through the data transmission service by calling the RPC interface corresponding to the data transmission service in the private cloud equipment, and the public cloud equipment calls the RPC interface corresponding to the data receiving service, so that the reporting service data can be sequentially added to the sub data queue corresponding to the public cloud equipment from the main data queue, and the reporting service data can be acquired from the sub data queue through the data receiving service.

Based on the above description, as shown in fig. 5, fig. 5 is a schematic flow chart of cross-cloud data transmission according to an embodiment of the present application; wherein, this fig. 5 describes the data reporting and data issuing process: the producer (public cloud equipment or private cloud equipment) adds service distribution data into a main data queue through cross-cloud service, adds the service distribution data into a corresponding sub-data queue according to a data subject from the main data queue, and a consumer (private cloud equipment or public cloud equipment) polls the corresponding sub-data queue to consume data, namely pulls the service distribution data. As shown in fig. 6, fig. 6 is a schematic flow chart of cross-cloud data transmission based on data transmission according to an embodiment of the present application; the public cloud device obtains service distribution data and performs RPC call on a data sending service on the public cloud device to add the service distribution data to a main data queue of CMQ, and adds the service distribution data to a corresponding sub data queue according to a data subject of the service distribution data in CMQ, the private cloud device performs RPC call on a data receiving service to pull added service distribution data from the corresponding sub data queue to a local data queue, and service on the private cloud device can pull corresponding required service distribution data from the local data queue.

In the embodiment of the application, at least one service distribution data aiming at a plurality of private cloud devices can be acquired, the at least one service distribution data is added into a main data queue, the service distribution data of each private cloud device is respectively extracted from the main data queue, the service distribution data of each private cloud device is respectively added into a sub data queue corresponding to each private cloud device, after the service distribution data is successfully added into the sub data queue corresponding to each private cloud device, the successful service distribution data added into the main data queue is deleted, and if the successful prompt information for acquiring the service distribution data sent by the target private cloud device in the plurality of private cloud devices is acquired, the service distribution data indicated by the successful prompt information is deleted from the sub data queue corresponding to the target private cloud device. By the method, the coupling performance of public cloud equipment and private cloud equipment in data communication can be reduced, the reliability and the safety of data transmission are improved, and when a plurality of private cloud equipment have the same service distribution data, the service distribution data can be added into a main data queue only once and are respectively added into corresponding sub data queues, so that the occupied space of the data can be reduced, and the data transmission efficiency is improved.

Referring to fig. 7, fig. 7 is a schematic structural diagram of a cross-cloud data processing apparatus according to the present application. It should be noted that, the cross-cloud data processing apparatus shown in fig. 7 is configured to perform the method of the embodiment shown in fig. 2 and fig. 4, and for convenience of explanation, only a portion relevant to the embodiment of the present application is shown, and specific technical details are not disclosed, and reference is made to the embodiment shown in fig. 2 and fig. 4 of the present application. The cross-cloud data processing apparatus 700 may include: a processing module 701 and an extracting module 702. Wherein:

a processing module 701, configured to obtain at least one service distribution data for a plurality of private cloud devices, and add the at least one service distribution data to a main data queue;

the extracting module 702 is configured to extract service distribution data of each private cloud device from the main data queue respectively;

the processing module 701 is further configured to add service distribution data of each private cloud device to a sub-data queue corresponding to each private cloud device; each private cloud device is used for acquiring the service distribution data according to the corresponding sub-data queue.

In one possible implementation manner, each of the plurality of private cloud devices has an application program, and the at least one service distribution data includes update program data of the application program;

The processing module 702 is specifically configured to, when being configured to add service distribution data of each private cloud device to a sub-data queue corresponding to each private cloud device, respectively:

and adding the updated program data into the sub-data queues corresponding to each private cloud device respectively.

In one possible implementation manner, each of the plurality of private cloud devices has an application program, N private cloud devices in the plurality of private cloud devices subscribe to a target service in the application program, and the at least one service distribution data includes subscription data indicated by the target service;

the processing module 701, when configured to obtain at least one service distribution data for a plurality of private cloud devices, is specifically configured to:

acquiring subscription data indicated by a target service when a service distribution event of the target service is triggered;

the processing module 701 is specifically configured to, when configured to add service distribution data of each private cloud device to a sub-data queue corresponding to each private cloud device, respectively:

and adding the subscription data into the sub data queues corresponding to the N private cloud devices respectively.

In one possible implementation manner, the plurality of private cloud devices include a first private cloud device and a second private cloud device; the processing module 701 is further configured to:

Acquiring a data forwarding request sent by first private cloud equipment; the data forwarding request carries forwarding service data;

and adding the forwarding service data to a sub-data queue corresponding to the second private cloud device, so that the second private cloud device obtains the forwarding service data from the corresponding sub-data queue.

In one possible implementation manner, any one of the plurality of private cloud devices is represented as a target private cloud device;

the processing module 701 is further configured to:

and if the acquisition success prompt information for the service distribution data sent by the target private cloud equipment is acquired, deleting the service distribution data indicated by the acquisition success prompt information from the sub-data queue corresponding to the target private cloud equipment.

In one possible implementation manner, the at least one service distribution data includes target service distribution data, and the service distribution data of N private cloud devices in the plurality of private cloud devices includes target service distribution data; the processing module 701 is further configured to:

and after the target service distribution data are successfully added into the sub data queues corresponding to the N private cloud devices respectively, deleting the target service distribution data in the main data queue.

In one possible implementation manner, each private cloud device has access rights to a corresponding sub-data queue in the public cloud device, and each private cloud device is configured to pull the service distribution data of the corresponding sub-data queue according to the access rights to the corresponding sub-data queue;

the plurality of private cloud devices are provided with application programs, service distribution data of the plurality of private cloud devices comprise update program data of the application programs, and each private cloud device is used for updating the application programs according to the pulled update program data.

In the embodiment of the application, a processing module acquires at least one service distribution data for a plurality of private cloud devices and adds the at least one service distribution data into a main data queue; the extraction module extracts service distribution data of each private cloud device from the main data queue respectively; and the processing module adds the service distribution data of each private cloud device to the sub-data queue corresponding to each private cloud device respectively. Through the device, the service distribution data can be uniformly added to the main data queue and respectively added to the sub data queues, the coupling property of public cloud equipment and private cloud equipment in data communication can be reduced, the reliability and the safety of data transmission are improved, and when a plurality of private cloud equipment have the same service distribution data, the service distribution data can be only added once in the main data queue and respectively added to the corresponding sub data queues, so that the data occupation space can be reduced and the data transmission efficiency can be improved.

The functional modules in the embodiments of the present application may be integrated into one processing module, or each module may exist alone physically, or two or more modules may be integrated into one module. The integrated modules may be implemented in hardware or in software functional modules, which is not limited by the present application.

Referring to fig. 8, fig. 8 is a schematic structural diagram of a public cloud device according to an embodiment of the present application. As shown in fig. 8, the public cloud device 800 includes: at least one processor 801, a memory 802. Optionally, the public cloud device may further include a network interface. Data may be interacted among the processor 801, the memory 802, and a network interface, the network interface is controlled by the processor 801 to send and receive messages, the memory 802 is used for storing a computer program, the computer program includes program instructions, and the processor 801 is used for executing the program instructions stored in the memory 802. Wherein the processor 801 is configured to invoke the program instructions to perform the above-described method.

The memory 802 may include a volatile memory (RAM), such as a random-access memory (RAM); the memory 802 may also include a non-volatile memory (non-volatile memory), such as a flash memory (flash memory), a Solid State Drive (SSD), etc.; memory 802 may also include combinations of the above types of memory.

The processor 801 may be a central processing unit (central processing unit, CPU). In one embodiment, the processor 801 may also be a graphics processor (Graphics Processing Unit, GPU). The processor 801 may also be a combination of a CPU and a GPU.

In one possible implementation, the memory 802 is used to store program instructions that the processor 801 may call to perform the following steps:

the processing module 701 is further configured to:

In a specific implementation, the cross-cloud data processing apparatus 700, the processor 801, the memory 802, and the like described above may perform the implementation described in the foregoing method embodiments, and may also perform the implementation described in the embodiment of the present application, which is not described herein again.

In an embodiment of the present application, there is further provided a computer (readable) storage medium storing a computer program, where the computer program includes program instructions, where the program instructions, when executed by a processor, cause the processor to perform some or all of the steps performed in the method embodiment described above. The computer storage medium may be volatile or nonvolatile. The computer-readable storage medium may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function, and the like; the storage data area may store data created from the use of blockchain nodes, and the like.

Embodiments of the present application also provide a computer program product comprising computer instructions which, when executed by a processor, implement some or all of the steps of the above-described method.

References herein to "a plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.

Those skilled in the art will appreciate that implementing all or part of the above-described embodiment methods may be accomplished by way of a computer program for instructing related hardware, and the above-described program may be stored in a computer storage medium, which may be a computer-readable storage medium, and the program may include the embodiment flow of each of the above-described methods when executed. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), or the like.

The above disclosure is only a few examples of the present application, and it is not intended to limit the scope of the present application, but it is understood by those skilled in the art that all or a part of the above embodiments may be implemented and equivalent changes may be made in the claims of the present application.

Claims

1. A cross-cloud data processing method, wherein the method is applied to public cloud equipment, the method comprising:

the service distribution data of each private cloud device are respectively added into a sub-data queue corresponding to each private cloud device; and each private cloud device is used for acquiring the service distribution data according to the corresponding sub-data queue.

2. The method of claim 1, wherein each of the plurality of private cloud devices has an application, and wherein the at least one service distribution data comprises update data for the application;

The adding the service distribution data of each private cloud device to the sub-data queue corresponding to each private cloud device includes:

3. The method of claim 1, wherein each of the plurality of private cloud devices has an application, N private cloud devices of the plurality of private cloud devices are subscribed to a target service in the application, and wherein the at least one service distribution data comprises subscription data indicated by the target service;

acquiring at least one service distribution data for a plurality of private cloud devices, comprising:

when a service distribution event of the target service is triggered, acquiring the subscription data indicated by the target service;

and adding the subscription data to the sub-data queues respectively corresponding to the N private cloud devices.

4. The method of claim 1, wherein the plurality of private cloud devices comprises a first private cloud device and a second private cloud device; the method further comprises the steps of:

Acquiring a data forwarding request sent by the first private cloud device; the data forwarding request carries forwarding service data;

5. The method of claim 1, wherein any one of the plurality of private cloud devices is represented as a target private cloud device;

the method further comprises the steps of:

and if acquiring the acquisition success prompt information for the service distribution data sent by the target private cloud equipment, deleting the service distribution data indicated by the acquisition success prompt information in the sub-data queue corresponding to the target private cloud equipment.

6. The method of claim 1, wherein the at least one service distribution data comprises target service distribution data, and wherein the service distribution data of N private cloud devices of the plurality of private cloud devices each comprise target service distribution data; the method further comprises the steps of:

7. The method of claim 1, wherein each private cloud device has access rights to a corresponding sub-data queue in the public cloud device, and each private cloud device is configured to pull the service distribution data from the corresponding sub-data queue according to the access rights to the corresponding sub-data queue;

8. A cross-cloud data processing apparatus, the apparatus comprising:

the processing module is further configured to add the service distribution data of each private cloud device to a sub-data queue corresponding to each private cloud device; and each private cloud device is used for acquiring the service distribution data according to the corresponding sub-data queue.

9. A public cloud device comprising a processor and a memory, wherein the memory is for storing a computer program comprising program instructions, the processor being configured to invoke the program instructions to perform the method of any of claims 1-7.

10. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program comprising program instructions which, when executed by a processor, cause the processor to perform the method of any of claims 1-7.

11. A computer program product comprising computer instructions which, when executed by a processor, implement the method of any of claims 1-7.