CN113014656B - Private cloud information synchronization method and device - Google Patents

Private cloud information synchronization method and device Download PDF

Info

Publication number
CN113014656B
CN113014656B CN202110255623.3A CN202110255623A CN113014656B CN 113014656 B CN113014656 B CN 113014656B CN 202110255623 A CN202110255623 A CN 202110255623A CN 113014656 B CN113014656 B CN 113014656B
Authority
CN
China
Prior art keywords
information
synchronization
type
new
determining
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.)
Active
Application number
CN202110255623.3A
Other languages
Chinese (zh)
Other versions
CN113014656A (en
Inventor
刘成乾
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Baidu Netcom Science and Technology Co Ltd
Original Assignee
Beijing Baidu Netcom Science and Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Baidu Netcom Science and Technology Co Ltd filed Critical Beijing Baidu Netcom Science and Technology Co Ltd
Priority to CN202110255623.3A priority Critical patent/CN113014656B/en
Publication of CN113014656A publication Critical patent/CN113014656A/en
Application granted granted Critical
Publication of CN113014656B publication Critical patent/CN113014656B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45587—Isolation or security of virtual machine instances
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45595—Network integration; Enabling network access in virtual machine instances

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Synchronisation In Digital Transmission Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The disclosure discloses a private cloud information synchronization method and device, relates to the technical field of cloud computing, and further relates to the technical field of cloud networks. The specific implementation scheme is as follows: the method comprises the steps of firstly receiving an information synchronization request sent by a first control node, determining synchronization information of a target number based on the synchronization type and the synchronization identification, finally determining a new synchronization identification and a new synchronization type based on the synchronization information of the target number, and sending the synchronization information of the target number, the new synchronization identification and the new synchronization type to the first control node. The information synchronization of the sub-batches is realized, only the information synchronization of the target quantity is carried out each time, so that the request response of the information synchronization initiator does not cause overtime, and the blocking of other coroutines can be avoided.

Description

Private cloud information synchronization method and device
Technical Field
The disclosure relates to the technical field of cloud computing, and further relates to the technical field of cloud networks.
Background
In a virtual machine network of cloud computing, a Virtual Private Cloud (VPC) provides an isolation form of resources, different VPCs realize isolation of resources such as security groups, subnets and the like, and isolation of a Domain Name System (DNS) is realized, and a DNS resolution domain configured in each VPC does not have any influence on other VPCs. For some public services (such as cloud database RDS), a domain name is automatically generated when the domain name is provided for a user, and the domain name is resolved into a certain address in the VPC where the RDS is located. When the local end VPC and other cluster VPCs are connected in a peer-to-peer mode, the public service domain name in the local end VPC is synchronized to the opposite end VPC, so that the opposite end VPC can access the public service through the domain name.
When the public service domain name and the IP information need to be synchronized between the two VPCs, the VPC of the local end sends a synchronization request to the control node of the VPC of the opposite end, and after the control node of the VPC of the opposite end receives the synchronization request, the control node directly encapsulates the whole public service domain name and the whole IP information and then returns the encapsulated public service domain name and the IP information as a return value to the VPC of the local end.
Disclosure of Invention
The disclosure provides a private cloud information synchronization method and device, electronic equipment and a storage medium.
According to an aspect of the present disclosure, there is provided a private cloud information synchronization method, including: receiving an information synchronization request sent by a first control node, wherein the information synchronization request comprises a synchronization type and a synchronization identifier; determining a target number of synchronization information based on the synchronization type and the synchronization identifier; and determining a new synchronization identifier and a new synchronization type based on the target number of synchronization information, and sending the target number of synchronization information, the new synchronization identifier and the new synchronization type to the first control node.
According to another aspect of the present disclosure, there is provided a private cloud information synchronization method, including: in response to determining that the synchronization type is a preset type for representing sending of the information synchronization request, sending the information synchronization request comprising the synchronization type and the synchronization identifier to the second control node; and receiving the target quantity of synchronous information, the new synchronous identification and the new synchronous type which are returned by the second control node based on the information synchronous request.
According to another aspect of the present disclosure, there is provided a private cloud information synchronizing apparatus, the apparatus including: the device comprises a receiving module, a sending module and a receiving module, wherein the receiving module is configured to receive an information synchronization request sent by a first control node, and the information synchronization request comprises a synchronization type and a synchronization identifier; a determination module configured to determine a target number of synchronization information based on the synchronization type and the synchronization identifier; a sending module configured to determine a new synchronization identifier and a new synchronization type based on the target number of synchronization information, and send the target number of synchronization information, the new synchronization identifier, and the new synchronization type to the first control node.
According to another aspect of the present disclosure, there is provided a private cloud information synchronizing apparatus, the apparatus including: a sending module configured to send an information synchronization request including a synchronization type and a synchronization identifier to the second control node in response to determining that the synchronization type is a preset type for characterizing sending the information synchronization request; and the receiving module is configured to receive the target amount of synchronization information, the new synchronization identifier and the new synchronization type returned by the second control node based on the information synchronization request.
According to another aspect of the present disclosure, there is provided an electronic device comprising at least one processor; and a memory communicatively coupled to the at least one processor; the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the private cloud information synchronization method.
According to another aspect of the present disclosure, a computer-readable medium is provided, on which computer instructions are stored, and the computer instructions are used for enabling a computer to execute the private cloud information synchronization method.
According to another aspect of the present disclosure, a computer program product is provided, which includes a computer program, and when the computer program is executed by a processor, the computer program implements the private cloud information synchronization method described above.
It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present disclosure, nor do they limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.
Drawings
The drawings are included to provide a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:
FIG. 1 is an exemplary system architecture diagram in which the present disclosure may be applied;
fig. 2 is a flow diagram of one embodiment of a private cloud information synchronization method according to the present disclosure;
fig. 3 is a schematic diagram of an application scenario of a private cloud information synchronization method according to the present disclosure;
FIG. 4 is a flow diagram for one embodiment of determining synchronization information, according to the present disclosure;
FIG. 5 is a flow diagram for one embodiment of determining synchronization information based on a synchronization identifier, according to the present disclosure;
fig. 6 is a flow diagram of one embodiment of a private cloud information synchronization method according to the present disclosure;
fig. 7 is a schematic diagram of one embodiment of a private cloud information synchronization apparatus, according to the present disclosure;
fig. 8 is a schematic diagram of one embodiment of a private cloud information synchronization apparatus, according to the present disclosure;
fig. 9 is a block diagram of an electronic device for implementing the private cloud information synchronization method of the present disclosure.
Detailed Description
Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which various details of the embodiments of the disclosure are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
It should be noted that, in the present disclosure, the embodiments and features of the embodiments may be combined with each other without conflict. The present disclosure will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.
Fig. 1 illustrates an exemplary system architecture 100 to which embodiments of the private cloud information synchronization method of the present disclosure may be applied.
As shown in fig. 1, system architecture 100 may include Virtual Private Clouds (VPCs) 101, 102 and a network 103. Network 103 is used to provide a medium for communication links between Virtual Private Cloud (VPC) 101 and Virtual Private Cloud (VPC) 102. Network 103 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
The Virtual Private Cloud (VPC) 101 and 102 may be virtual networks supporting user customization, and are cloud service systems providing dedicated services for a single client, the Virtual Private Cloud (VPC) 101 may include multiple cloud hosts 1011, modules such as a data center and a virtual gateway may be deployed on the cloud hosts 1011, the Virtual Private Cloud (VPC) 102 may include multiple cloud hosts 1021, and modules such as a data center and a virtual gateway may be deployed on the cloud hosts 1021.
A cloud host 1011 in the Virtual Private Cloud (VPC) 101 serves as a first control node of the Virtual Private Cloud (VPC) 101, while a cloud host 1021 in the Virtual Private Cloud (VPC) 102 can serve as a second control node of the Virtual Private Cloud (VPC) 102. A first control node of Virtual Private Cloud (VPC) 101 may issue an information synchronization request to a second control node of Virtual Private Cloud (VPC) 102.
Before a first control node of a Virtual Private Cloud (VPC) 101 sends an information synchronization request to a Virtual Private Cloud (VPC) 102, the first control node of the Virtual Private Cloud (VPC) 101 may determine whether a synchronization type of the information synchronization request is a preset type for representing that information synchronization request is stopped to be sent, and if it is determined that the synchronization type is not the preset type for representing that information synchronization request is stopped to be sent, send an information synchronization request including a synchronization type and a synchronization identifier to a second control node. And the first control node of the Virtual Private Cloud (VPC) 101 can receive the synchronization information, the new synchronization identifier, and the new synchronization type returned by the second control node based on the information synchronization request, and the first control node can continuously determine whether the new synchronization type is a preset type for representing that the sending of the information synchronization request is stopped, so as to determine whether to continuously send the information synchronization request to the Virtual Private Cloud (VPC) 102.
The second control node of the Virtual Private Cloud (VPC) 102 may receive the information synchronization request sent by the first control node of the Virtual Private Cloud (VPC) 101, determine the synchronization information of the target quantity according to the synchronization type and the synchronization identifier in the information synchronization request, determine a new synchronization identifier and a new synchronization type according to the determined synchronization information of the target quantity, send the synchronization information of the target quantity, the new synchronization identifier, and the new synchronization type to the first control node, and can continue to receive the information synchronization request sent next time by the first control node.
It should be noted that the private cloud information synchronization method provided by the embodiment of the present disclosure may be executed by the cloud host 1021 in the Virtual Private Cloud (VPC) 102. Accordingly, the private cloud information synchronization apparatus may be provided in the cloud host 1021 in the Virtual Private Cloud (VPC) 102. A private cloud information synchronization method provided by another embodiment of the present disclosure may be performed by a cloud host 1011 in a Virtual Private Cloud (VPC) 101. Accordingly, the private cloud information synchronization apparatus may be provided in the cloud host 1011 in the Virtual Private Cloud (VPC) 101.
It should be understood that the number of cloud hosts and virtual private clouds in fig. 1 is merely illustrative. There may be any number of cloud hosts and virtual private clouds, as desired for implementation.
Referring to fig. 2, fig. 2 shows a flowchart diagram 200 of an embodiment of a private cloud information synchronization method that may be applied to the present disclosure. The private cloud information synchronization method comprises the following steps:
step 210, receiving an information synchronization request sent by a first control node.
In this embodiment, an execution subject of the private cloud information synchronization method (e.g., the cloud host 1021 in the Virtual Private Cloud (VPC) 102 in fig. 1) may receive, through the network, an information synchronization request sent by the first control node, where the information synchronization request may be expressed in the form of an API request. The information synchronization request may include a synchronization type and a synchronization identifier of synchronization information required by the first control node in the information synchronization process.
The synchronization type in the information synchronization request may represent an information type of synchronization information that needs to be acquired by the first control node in the information synchronization process. The information is classified according to the same rule in both the Virtual Private Cloud (VPC) 101 where the first control node is located and the Virtual Private Cloud (VPC) 102 where the execution subject is located, so as to obtain a plurality of information types, and different information may be classified according to the content of the information, for example, the information may be classified into an IP information type, a domain name information type, a synchronization completed type, and the like. Corresponding priorities may also be set for multiple information types, for example, the priority of the IP information type is greater than the priority of the domain name information type, which is greater than the priority of the completed synchronization type.
The synchronization identifier in the information synchronization request may be a start identifier of the current synchronization information, an end identifier of the synchronization information in the last synchronization process, or an initialization identifier for characterizing the first information in the information list corresponding to the obtained synchronization type. If the synchronization mark is the start mark of the synchronization information, the information corresponding to the synchronization mark can be directly used as the first synchronization information to start to acquire in the synchronization process; if the synchronization mark is the end mark of the synchronization information in the last synchronization process, the next information of the information corresponding to the synchronization mark can be used as the first synchronization information to start to obtain in the synchronization process; if the synchronization identifier is an initialization flag, the first information in the information list corresponding to the synchronization type can be directly used as the first synchronization information in the synchronization process to start to acquire.
Based on the synchronization type and the synchronization identifier, a target amount of synchronization information is determined, step 220.
In this embodiment, after receiving the information synchronization request sent by the first control node, the execution main body obtains the synchronization type and the synchronization identifier in the information synchronization process from the information synchronization request. The execution body may determine the target number of synchronization information belonging to the synchronization type according to the synchronization identifier in the information synchronization request.
As an example, if the synchronization identifier is a start flag of the current synchronization information, the information corresponding to the synchronization identifier may be directly acquired as the first synchronization information in the current synchronization process. The execution body may use information corresponding to the synchronization identifier belonging to the synchronization type as first synchronization information, so as to start to acquire the target number of pieces of information as the synchronization information.
As an example, if the synchronization identifier is an end flag of the synchronization information in the last synchronization process, the next information of the information corresponding to the synchronization identifier may be started to be acquired as the first synchronization information in the current synchronization process. The execution body may use next information of information corresponding to the synchronization identifier belonging to the synchronization type as first synchronization information, so as to start to acquire the target number of information as synchronization information.
As an example, if the synchronization identifier is an initialization flag, the first information in the information list corresponding to the synchronization type may be directly used as the first synchronization information in the synchronization process to start to be acquired. The execution body may use first information belonging to the synchronization type as first synchronization information to start acquiring the target number of information as the synchronization information.
And step 230, determining a new synchronization identifier and a new synchronization type based on the target number of synchronization information, and sending the target number of synchronization information, the new synchronization identifier and the new synchronization type to the first control node.
In this embodiment, after the execution main body acquires the synchronization information of the target number, a new synchronization identifier and a new synchronization type that represent the next synchronization required are determined according to the acquired synchronization information. The execution main body sends the determined target number of synchronization information, the new synchronization identification and the new synchronization type to the first control node, so that the Virtual Private Cloud (VPC) 101 where the first control node is located performs information synchronization, therefore, the first control node can continuously send the next information synchronization request, and the execution main body can continuously receive the information synchronization request sent by the first control node next time.
As an example, after the execution main body acquires the target number of pieces of synchronization information, a new synchronization identifier may be set for the last piece of information in the synchronization information, so that the new synchronization identifier can represent an end mark of the synchronization information in the synchronization process of this time, and when the information synchronization process is performed next time, the execution main body may start to acquire the next piece of information corresponding to the new synchronization identifier as the first piece of synchronization information.
As an example, after the execution main body obtains the target number of pieces of synchronization information, a new synchronization identifier may be set for information next to the last piece of information in the synchronization information, so that the new synchronization identifier can represent a start flag of the synchronization information in the next synchronization process, and when the information synchronization process is performed next time, the execution main body may start obtaining information corresponding to the new synchronization identifier as the first piece of synchronization information.
With continued reference to fig. 3, fig. 3 is a schematic diagram of an application scenario of the private cloud information synchronization method according to the present disclosure.
In the application scenario of fig. 3, a first control node of a Virtual Private Cloud (VPC) 301 may issue an information synchronization request to a Virtual Private Cloud (VPC) 302, where the information synchronization request includes a synchronization type and a synchronization identifier. After receiving the information synchronization request sent by the first control node of the Virtual Private Cloud (VPC) 301, the second control node of the Virtual Private Cloud (VPC) 302 determines the synchronization information of the target quantity according to the synchronization type and the synchronization identifier in the information synchronization request, determines a new synchronization identifier and a new synchronization type according to the determined synchronization information of the target quantity, sends the synchronization information of the target quantity, the new synchronization identifier and the new synchronization type to the first control node of the Virtual Private Cloud (VPC) 301, and can continue to receive the information synchronization request sent next time by the first control node of the Virtual Private Cloud (VPC) 301.
According to the private cloud information synchronization method provided by the embodiment of the disclosure, an information synchronization request sent by a first control node is received, the information synchronization request comprises a synchronization type and a synchronization identifier, then the synchronization information of a target number is determined based on the synchronization type and the synchronization identifier, finally a new synchronization identifier and a new synchronization type are determined based on the synchronization information of the target number, and the synchronization information of the target number, the new synchronization identifier and the new synchronization type are sent to the first control node to continuously receive the information synchronization request sent next time by the first control node, so that the information synchronization of sub-batches is realized, only the information synchronization of the target number is carried out each time, and therefore, the request response of an information synchronization initiator does not cause overtime, other protocols can be prevented from being blocked, the data volume of each request can be adjusted, and the flexibility and the accuracy of the information synchronization are improved.
With further reference to fig. 4, which illustrates step 220 of fig. 2 of the present disclosure, determining a target number of synchronization information based on the synchronization type and the synchronization identifier may include the steps of:
based on the synchronization type, an information list corresponding to the synchronization type is determined, step 410.
In this step, after receiving the information synchronization request sent by the first control node, the execution main body obtains the synchronization type in the information synchronization process from the information synchronization request. The execution main body may determine, according to the synchronization type in the information synchronization request, an information list corresponding to the synchronization type and stored locally. For example, the execution main body compares the synchronization type with the information type stored this time, and sets an information list corresponding to the information type that is the same as the synchronization type as an information list corresponding to the synchronization type.
Based on the synchronization identifier, a target number of synchronization information is determined in the information list, step 420.
In this step, the execution main body may obtain the synchronization identifier in the information synchronization process from the information synchronization request, and after determining the information list corresponding to the synchronization type, determine the synchronization information of the target number in the information list according to the synchronization identifier in the information synchronization request.
For example, if the synchronization flag is a start flag of the current synchronization information, the execution main body may start to acquire information corresponding to the synchronization flag in the information list as the first synchronization information, so as to start to acquire the target number of information as the synchronization information.
As an example, if the synchronization identifier is an end flag of the synchronization information in the last synchronization process, the execution main body may start to acquire information next to the information corresponding to the synchronization identifier in the information list as the first synchronization information, so as to start to acquire the target number of information as the synchronization information.
As an example, if the synchronization flag is an initialization flag, the execution body may start to acquire the first information in the information list as the first synchronization information, so as to start to acquire the target number of information as the synchronization information.
In the embodiment, the target number of the synchronization information is determined based on the synchronization type and the synchronization identifier, and the preset type of the target number of the synchronization information can be used as the synchronization information of the synchronization process, so that the classification and batch synchronization of the information is realized, and the flexibility and the accuracy of the information synchronization are improved.
As an optional implementation manner, the executing body may further execute the following steps: and in response to receiving the information synchronization request sent by the first control node, determining the target number corresponding to the information synchronization request.
Specifically, after receiving the information synchronization request sent by the first control node, the execution main body may obtain the synchronization type and the synchronization identifier in the information synchronization process from the information synchronization request, and further obtain the information list corresponding to the synchronization type. The execution main body may determine a target number corresponding to the information synchronization request according to the information transmission bandwidth and the information number in the information list, where the target number may represent the number of synchronization information that needs to be transmitted in the information synchronization process.
In the implementation mode, the data volume transmitted each time is determined by determining the target number corresponding to the information synchronization request, so that the data volume transmitted each time accords with the transmission bandwidth, the blockage is avoided, and the information synchronization fluency is improved.
With further reference to fig. 5, which illustrates step 420 in fig. 4 of the present disclosure, determining a target number of synchronization information in the information list based on the synchronization identification may include the steps of:
step 510, based on the synchronization identifier, determining whether the information amount of the remaining information in the information list is greater than or equal to the target amount.
In this step, after receiving the information synchronization request and determining the target number, the execution main body obtains the synchronization type and the synchronization identifier in the information synchronization process from the information synchronization request, and further obtains an information list corresponding to the synchronization type. And the execution main body judges the information quantity of the residual information in the information list according to the synchronous identification and judges whether the information quantity of the residual information in the information list is more than or equal to the target quantity.
For example, if the synchronization flag is a start flag of the current synchronization information, the execution main body may use information corresponding to the synchronization flag and all information following the information in the information list as remaining information, and obtain the information amount of the remaining information. The execution main body judges whether the information quantity of the residual information is larger than or equal to the target quantity.
As an example, if the synchronization identifier is an end flag of the synchronization information in the last synchronization process, the execution main body may use all information following the information corresponding to the synchronization identifier in the information list as the remaining information, and obtain the information amount of the remaining information. The execution main body judges whether the information quantity of the residual information is larger than or equal to the target quantity.
As an example, if the synchronization flag is an initialization flag, the execution body may use all information in the information list as remaining information, and obtain the information amount of the remaining information. The execution main body judges whether the information quantity of the residual information is larger than or equal to the target quantity.
In response to determining that the information amount of the remaining information in the information list is greater than or equal to the target amount, a target amount of synchronization information is determined in the remaining information in the information list, step 520.
In this step, the execution main body determines, by judging that the information amount of the remaining information in the information list is greater than or equal to the target amount, that is, the information amount of the remaining information in the information list can satisfy the target amount of the synchronization information that needs to be acquired in the information synchronization process, and then determines the synchronization information of the target amount from the remaining information in the information list.
As an optional implementation manner, the step 520, in response to determining that the information amount of the remaining information in the information list is greater than or equal to the target amount, determining the target amount of synchronization information in the remaining information in the information list, may include the following steps: in response to determining that the amount of information of the remaining information in the information list is greater than the target amount, a target amount of synchronization information is determined in the remaining information in the information list.
Specifically, the executing body determines, by judging that the information amount of the remaining information in the information list is greater than the target amount, that is, the information amount of the remaining information in the information list can satisfy the target amount of the synchronization information that needs to be acquired in the information synchronization process, and then determines the target amount of the synchronization information in the remaining information in the information list. And
the step 230 of determining a new synchronization id and a new synchronization type based on the target number of synchronization information may include the following steps: and setting a new synchronization identifier based on the target number of synchronization information, and taking the synchronization type as a new synchronization type.
Specifically, after determining the synchronization information of the target number in the remaining information of the information list, the execution main body determines a new synchronization identifier and a new synchronization type representing the next synchronization required according to the synchronization information. Since the information amount of the remaining information in the information list is greater than the target amount, the execution main body may continue to use the synchronization type corresponding to the information list as a new synchronization type.
As an example, after the execution main body obtains the target number of pieces of synchronization information, a new synchronization identifier may be set for the last piece of information in the synchronization information, so that the new synchronization identifier can represent an end flag of the synchronization information in the current synchronization process, and when the information synchronization process is performed next time, the execution main body may start obtaining the next piece of information corresponding to the new synchronization identifier as the first piece of synchronization information.
As an example, after the execution main body obtains the target number of pieces of synchronization information, a new synchronization identifier may be set for information next to the last piece of information in the synchronization information, so that the new synchronization identifier can represent a start flag of the synchronization information in the next synchronization process, and when the information synchronization process is performed next time, the execution main body may start obtaining information corresponding to the new synchronization identifier as the first piece of synchronization information.
In the implementation mode, the synchronization information is determined in the information list with the information quantity of the residual information larger than the target quantity so as to obtain the new synchronization identification and the synchronization type, the information with the target quantity of the synchronization type can be used as the synchronization information of the synchronization process, the classification and batch synchronization of the information is realized, the next information synchronization process is realized, and the flexibility and the accuracy of the information synchronization are improved.
As an alternative implementation manner, the step 520, in response to determining that the information amount of the remaining information in the information list is greater than or equal to the target amount, determining the target amount of synchronization information in the remaining information in the information list, may include the following steps: in response to determining that the number of information remaining in the information list is equal to the target number, all remaining information of the information list is treated as synchronization information.
Specifically, the executing body determines, through judgment, that the information amount of the remaining information in the information list is equal to the target amount, that is, determines that the information amount of the remaining information in the information list just meets the target amount of the synchronization information that needs to be acquired in the information synchronization process, and then takes all the remaining information in the information list as the synchronization information. And
the step 230 of determining a new synchronization id and a new synchronization type based on the target number of synchronization information may include the following steps: and based on the priority of the information type stored locally, taking the information type of the next priority of the synchronization type as a new synchronization type, and setting the synchronization identifier as initialization.
Specifically, since the information amount of the remaining information in the information list is equal to the target amount, after the execution main body determines the target amount of synchronization information in the remaining information in the information list, all information in the information list has already completed information synchronization, and it can be determined that other types of information need to be synchronized in the next information synchronization process. The execution main body may obtain an information type of a next priority of the synchronization type in the current information synchronization request according to the priority of the locally stored information type, and use the information type as a new synchronization type. And since all the information in the information list has been completely synchronized, the next information synchronization process needs to start to acquire from the first information in the information list corresponding to the new synchronization type, and the synchronization flag may be set to be initialized, so that the execution main body starts to acquire from the first information in the information list corresponding to the new synchronization type in the next information synchronization process.
In the implementation mode, the synchronization information is determined in the information list with the information quantity of the residual information equal to the target quantity, the information with the target quantity of the synchronization type can be used as the synchronization information of the synchronization process, the classification and batch synchronization of the information is realized, the next information synchronization process is started with a new synchronization type, and the flexibility and the accuracy of the information synchronization are improved.
In this embodiment, by determining the relationship between the information amount of the remaining information in the information list and the target amount, and implementing different update modes of the synchronization identifier and the synchronization type according to different determination results, the next information synchronization process can be performed more accurately, and the flexibility and accuracy of information synchronization are improved.
As an alternative implementation manner, step 420 in fig. 4, determining a target number of synchronization information in the information list based on the synchronization identifier, may further include the following steps: in response to determining that the information quantity of the remaining information in the information list is smaller than the target quantity, determining a new information list corresponding to the information type of the next priority of the synchronization type based on the priority of the locally stored information type; a target number of synchronization information is determined in the remaining information of the information list and the new information list.
Specifically, the execution main body determines that the information amount of the remaining information in the information list is smaller than the target amount through judgment, that is, it is determined that the information amount of the remaining information in the information list cannot meet the target amount of the synchronization information that needs to be obtained in the information synchronization process, information of other information types needs to be obtained as the synchronization information, so that the remaining information in the information list and the information of other information types together serve as the synchronization information. And after the execution main body determines that the information quantity of the residual information in the information list is less than the target quantity, determining the information type of the next priority of the synchronous type in the information types according to the priority of the locally stored information types, and determining a new information list corresponding to the information type. The execution main body determines the difference amount between the target amount and the information amount of the remaining information, acquires the difference amount information as partial synchronization information from the first information in the new information list, and takes all the remaining information in the synchronization type information list and the difference amount information in the new information list as the target amount of synchronization information. And
the step 230 of determining a new synchronization id and a new synchronization type based on the target number of synchronization information may include the following steps: and taking the information type of the next priority of the synchronization type as a new synchronization type, and setting a new synchronization identifier based on the synchronization information in the new information list.
Specifically, since the information amount of the remaining information in the information list is smaller than the target amount, after the execution main body uses all the remaining information in the synchronization type information list and the information of the difference amount in the new information list as the synchronization information of the target amount, all the information in the information list has already completed information synchronization, and then the next information synchronization process needs to acquire synchronization information from the new information list corresponding to the information type of the next priority of the synchronization type. The execution body may regard an information type of a next priority of the sync type among the information types as a new sync type. And determining a new synchronization identifier representing the next synchronization required according to the partial synchronization information because the execution main body takes the information of the difference number in the new information list as the partial synchronization information.
As an example, after the execution main body acquires part of the synchronization information, a new synchronization identifier may be set for the last information in the part of the synchronization information, so that the new synchronization identifier can represent an end mark of the synchronization information in the current synchronization process, and when the information synchronization process is performed next time, the execution main body may start acquiring the next information of the information corresponding to the new synchronization identifier as the first synchronization information.
For example, after the execution main body acquires part of the synchronization information, a new synchronization identifier may be set for information next to the last information in the synchronization information, so that the new synchronization identifier can represent a start flag of the synchronization information in the next synchronization process, and when the information synchronization process is performed next time, the execution main body may start acquiring information corresponding to the new synchronization identifier as the first synchronization information.
In the implementation mode, the synchronization information is determined in the information list of which the information quantity of the residual information is less than the target quantity, the information in the information list and the new information list can be used as the synchronization information in the synchronization process, the condition that the information quantity of the residual information in the information list is insufficient is avoided, the next information synchronization process is started by a new synchronization type and a new synchronization identifier, and the flexibility and the accuracy of information synchronization are improved.
Referring to fig. 6, fig. 6 shows a flowchart diagram 600 of an embodiment of a private cloud information synchronization method that may be applied to the present disclosure. The private cloud information synchronization method comprises the following steps:
step 610, judging whether the synchronization type of the information synchronization request is a preset type for representing the transmitted information synchronization request.
In this embodiment, an execution subject of the private cloud information synchronization method (e.g., the cloud host 1011 in the Virtual Private Cloud (VPC) 101 in fig. 1) may preset a synchronization type of the information synchronization request, where the synchronization type may be a synchronization type returned by the last information synchronization request, or may be an initial type. The execution main body judges the synchronization type of the information synchronization request, and determines whether the synchronization type of the information synchronization request is a preset type used for representing and sending the information synchronization request, wherein the preset type can be an information type which needs to be synchronized in the information types, namely an IP information type and a domain name information type in the information types.
The synchronization type in the information synchronization request may represent an information type of synchronization information that needs to be acquired by the first control node in the information synchronization process. The information is classified according to the same rule in both the Virtual Private Cloud (VPC) 101 where the first control node is located and the Virtual Private Cloud (VPC) 102 where the execution subject is located, and different information may be classified according to the content of the information, for example, the information may be classified into an IP information type, a domain name information type, a synchronization completed type, and the like. Corresponding priorities may also be set for various information types, for example the IP information type has a higher priority than the domain name information type.
If the synchronization type is determined to be the preset type for representing sending of the information synchronization request, step 620 is executed, and in response to determining that the synchronization type is the preset type for representing sending of the information synchronization request, the information synchronization request including the synchronization type and the synchronization identifier is sent to the second control node.
In this embodiment, if the executing entity determines that the synchronization type is the preset type for representing sending of the information synchronization request, the executing entity encapsulates the synchronization type and the synchronization identifier into the information synchronization request, and sends the encapsulated information synchronization request to the second control node (the cloud host 1021 in the Virtual Private Cloud (VPC) 102), so that the second control node determines the target number of synchronization information, the new synchronization type, and the new synchronization identifier according to the synchronization type and the synchronization identifier in the information synchronization request through the steps in fig. 2, and sends the determined target number of synchronization information, the new synchronization type, and the new synchronization identifier to the executing entity (the cloud host 1011 in the Virtual Private Cloud (VPC) 101).
Step 630, receiving the target amount of synchronization information, the new synchronization identifier and the new synchronization type returned by the second control node based on the information synchronization request.
In this embodiment, after sending the information synchronization request to the second control node, the execution main body receives the target number of synchronization information, the new synchronization identifier, and the new synchronization type, which are returned by the second control node based on the information synchronization request. And if the new synchronization type is the preset type for representing the information sending synchronization request, continuously encapsulating the new synchronization identifier and the new synchronization type into the information synchronization request, and sending the encapsulated information synchronization request to the second control node.
According to the private cloud information synchronization method provided by the embodiment of the disclosure, by judging and determining that the synchronization type is a preset type for representing the sending of the information synchronization request, the information synchronization request including the synchronization type and the synchronization identifier is sent to the second control node, and the target amount of synchronization information, the new synchronization identifier and the new synchronization type returned by the second control node based on the information synchronization request are received, so that the information synchronization in batches is realized, only the target amount of information synchronization is performed each time, therefore, the request response of the information synchronization initiator does not cause timeout, other corotation can be avoided being blocked, the data volume of each request can be adjusted, and the flexibility and the accuracy of the information synchronization are improved.
As an optional implementation manner, the private cloud information synchronization method in fig. 6 further includes the following steps: and stopping sending the information synchronization request to the second control node in response to determining that the synchronization type is a preset type for characterizing stopping sending the information synchronization request.
Specifically, the execution main body determines that the synchronization type is a preset type used for representing that the sending of the information synchronization request is stopped, where the preset type may be a completed synchronization type in the information types, that is, it may be determined that all information in the second control node is completed in synchronization, and then the sending of the information synchronization request to the second control node is stopped.
In the implementation mode, the synchronization type is judged to determine whether to send the information synchronization request to the second control node, so that the condition that the information synchronization request is still sent after all information is synchronized can be avoided, resources are saved, and the accuracy of information synchronization is improved.
With further reference to fig. 7, as an implementation of the methods shown in the above-mentioned figures, the present disclosure provides an embodiment of a private cloud information synchronization apparatus, where the apparatus embodiment corresponds to the method embodiment shown in fig. 2, and the apparatus may be specifically applied to various electronic devices.
As shown in fig. 7, the private cloud information synchronization apparatus 700 of the present embodiment includes: a receiving module 710, a determining module 720, and a transmitting module 730.
The receiving module 710 is configured to receive an information synchronization request sent by a first control node, where the information synchronization request includes a synchronization type and a synchronization identifier;
a determining module 720 configured to obtain a target number of synchronization information based on the synchronization type and the synchronization identifier;
a sending module 730 configured to determine a new synchronization identifier and a new synchronization type based on the target number of synchronization information, and send the target number of synchronization information, the new synchronization identifier and the new synchronization type to the first control node.
In some optional manners of this embodiment, the determining module includes: a first determination unit configured to determine an information list corresponding to a synchronization type based on the synchronization type; a second determination unit configured to determine a target number of synchronization information in the information list based on the synchronization flag.
In some optional aspects of this embodiment, the determining module is further configured to: and in response to receiving the information synchronization request sent by the first control node, determining the target number corresponding to the information synchronization request.
In some optional aspects of this embodiment, the second determining unit is further configured to: and in response to determining that the information quantity of the remaining information in the information list is greater than or equal to the target quantity, determining a target quantity of synchronization information in the remaining information in the information list.
In some optional manners of this embodiment, the second determining unit is further configured to: determining a target number of synchronization information in the remaining information of the information list in response to determining that the information amount of the remaining information in the information list is greater than the target number; and a sending module further configured to: and setting a new synchronization identifier based on the target number of synchronization information, and taking the synchronization type as a new synchronization type.
In some optional aspects of this embodiment, the second determining unit is further configured to: in response to determining that the information quantity of the remaining information in the information list is equal to the target quantity, taking all of the remaining information of the information list as synchronization information; and a sending module further configured to: and based on the priority of the locally stored information type, taking the information type of the next priority of the synchronization type as a new synchronization type, and setting the synchronization identifier as initialization.
In some optional aspects of this embodiment, the second determining unit is further configured to: in response to determining that the information quantity of the remaining information in the information list is smaller than the target quantity, determining a new information list corresponding to the information type of the next priority of the synchronization type based on the priority of the locally stored information type; determining the synchronization information of the target quantity in the residual information of the information list and the new information list; and a sending module further configured to: and taking the information type of the next priority of the synchronization type as a new synchronization type, and setting a new synchronization identifier based on the synchronization information in the new information list.
The private cloud information synchronization device provided by the embodiment of the disclosure receives an information synchronization request sent by a first control node, wherein the information synchronization request comprises a synchronization type and a synchronization identifier, then determines synchronization information of a target number based on the synchronization type and the synchronization identifier, and finally determines a new synchronization identifier and a new synchronization type based on the synchronization information of the target number, and sends the synchronization information of the target number, the new synchronization identifier and the new synchronization type to the first control node to continuously receive an information synchronization request sent next time by the first control node, so that information synchronization of a sub-batch is realized, and only the information synchronization of the target number is performed each time, so that a request response of an information synchronization initiator does not cause timeout, other protocols can be prevented from being blocked, the data volume of each request can be adjusted, and the flexibility and the accuracy of the information synchronization are improved.
With further reference to fig. 8, as an implementation of the methods shown in the above-mentioned figures, the present disclosure provides an embodiment of a private cloud information synchronization apparatus, where the apparatus embodiment corresponds to the method embodiment shown in fig. 6, and the apparatus may be specifically applied to various electronic devices.
As shown in fig. 8, the private cloud information synchronization apparatus 800 of the present embodiment includes: a transmitting module 810 and a receiving module 820.
The sending module 810 is configured to, in response to determining that the synchronization type is a preset type for characterizing sending of the information synchronization request, send the information synchronization request including the synchronization type and the synchronization identifier to the second control node;
a receiving module 820 configured to receive the target number of synchronization information, the new synchronization identifier and the new synchronization type returned by the second control node based on the information synchronization request.
In some optional manners of this embodiment, the apparatus further includes: a termination module configured to stop sending the information synchronization request to the second control node in response to determining that the synchronization type is a preset type for characterizing the stop of sending the information synchronization request.
According to the private cloud information synchronization device provided by the embodiment of the disclosure, by judging and determining that the synchronization type is the preset type for representing the sending of the information synchronization request, the information synchronization request including the synchronization type and the synchronization identifier is sent to the second control node, and the target amount of synchronization information, the new synchronization identifier and the new synchronization type returned by the second control node based on the information synchronization request are received, so that the information synchronization in batches is realized, only the target amount of information synchronization is performed each time, and therefore, the request response of the information synchronization initiator does not cause timeout, other coroutines can be prevented from being blocked, the data volume of each request can be adjusted, and the flexibility and the accuracy of the information synchronization are improved.
The present disclosure also provides an electronic device, a readable storage medium, and a computer program product according to embodiments of the present disclosure.
FIG. 9 illustrates a schematic block diagram of an example electronic device 900 that can be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the disclosure described and/or claimed herein.
As shown in fig. 9, the electronic apparatus 900 includes a computing unit 901, which can perform various appropriate actions and processes in accordance with a computer program stored in a Read Only Memory (ROM) 902 or a computer program loaded from a storage unit 908 into a Random Access Memory (RAM) 903. In the RAM 903, various programs and data required for the operation of the device 900 can also be stored. The calculation unit 901, ROM 902, and RAM 903 are connected to each other via a bus 904. An input/output (I/O) interface 905 is also connected to bus 904.
A number of components in the electronic device 900 are connected to the I/O interface 905, including: an input unit 906 such as a keyboard, a mouse, and the like; an output unit 907 such as various types of displays, speakers, and the like; a storage unit 908 such as a magnetic disk, optical disk, or the like; and a communication unit 909 such as a network card, a modem, a wireless communication transceiver, and the like. The communication unit 909 allows the device 900 to exchange information/data with other devices through a computer network such as the internet and/or various telecommunication networks.
The computing unit 901 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of the computing unit 901 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various dedicated Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, and so forth. The computing unit 901 performs the respective methods and processes described above, such as the private cloud information synchronization method. For example, in some embodiments, the private cloud information synchronization method may be implemented as a computer software program tangibly embodied in a machine-readable medium, such as storage unit 908. In some embodiments, part or all of the computer program may be loaded and/or installed onto device 900 via ROM 902 and/or communications unit 909. When the computer program is loaded into the RAM 903 and executed by the computing unit 901, one or more steps of the private cloud information synchronization method described above may be performed. Alternatively, in other embodiments, the computing unit 901 may be configured to perform the private cloud information synchronization method by any other suitable means (e.g., by means of firmware).
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), and the Internet.
The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
It should be understood that various forms of the flows shown above, reordering, adding or deleting steps, may be used. For example, the steps described in the present disclosure may be executed in parallel, sequentially, or in different orders, as long as the desired results of the technical solutions disclosed in the present disclosure can be achieved, and the present disclosure is not limited herein.
The above detailed description should not be construed as limiting the scope of the disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present disclosure should be included in the scope of protection of the present disclosure.

Claims (18)

1. A private cloud information synchronization method comprises the following steps:
receiving an information synchronization request sent by a first control node, wherein the information synchronization request comprises a synchronization type and a synchronization identifier, and the synchronization identifier comprises a start identifier of the current synchronization information;
determining the target quantity corresponding to the information synchronization request according to the information transmission bandwidth and the information quantity in the information list corresponding to the synchronization type;
determining a target number of synchronization information based on the synchronization type and the synchronization identifier;
and determining a new synchronization identifier and a new synchronization type based on the target number of synchronization information, and sending the target number of synchronization information, the new synchronization identifier and the new synchronization type to the first control node, so that the first control node continues to send a next information synchronization request based on the new synchronization identifier and the new synchronization type.
2. The method of claim 1, wherein the determining a target number of synchronization information based on the synchronization type and the synchronization identification comprises:
determining an information list corresponding to the synchronization type based on the synchronization type;
and determining a target number of synchronous information in the information list based on the synchronous identification.
3. The method of claim 2, wherein said determining a target number of synchronization information in the information list based on the synchronization identifier comprises:
and in response to determining that the information quantity of the residual information in the information list is greater than or equal to the target quantity, determining a target quantity of synchronization information in the residual information in the information list.
4. The method of claim 3, wherein the determining a target number of synchronization information in the remaining information of the information list in response to determining that the amount of information of the remaining information of the information list is greater than or equal to the target number comprises:
in response to determining that the information quantity of the remaining information in the information list is greater than the target quantity, determining a target quantity of synchronization information in the remaining information in the information list; and
the determining a new synchronization identifier and a new synchronization type based on the target number of synchronization information includes:
setting a new synchronization identifier based on the target number of synchronization information, and taking the synchronization type as a new synchronization type.
5. The method of claim 3, wherein the determining a target number of synchronization information in the remaining information of the information list in response to determining that the amount of information of the remaining information of the information list is greater than or equal to the target number comprises:
in response to determining that the information amount of the remaining information in the information list is equal to the target amount, taking all of the remaining information of the information list as synchronization information; and
the determining a new synchronization identifier and a new synchronization type based on the target number of synchronization information includes:
and based on the priority of the locally stored information type, taking the information type of the next priority of the synchronization type as a new synchronization type, and setting the synchronization identifier as initialization.
6. The method of claim 3, wherein said determining a target number of synchronization information in said list of information based on said synchronization identifier further comprises:
in response to determining that the information quantity of the remaining information in the information list is smaller than the target quantity, determining a new information list corresponding to an information type of a next priority of the synchronization type based on a priority of a locally stored information type;
determining a target number of synchronization information in the remaining information of the information list and the new information list; and
the determining a new synchronization identifier and a new synchronization type based on the target number of synchronization information includes:
and taking the information type of the next priority of the synchronization type as a new synchronization type, and setting a new synchronization identifier based on the synchronization information in the new information list.
7. A private cloud information synchronization method comprises the following steps:
in response to the fact that the synchronization type is determined to be a preset type used for representing and sending an information synchronization request, sending the information synchronization request comprising the synchronization type and a synchronization identifier to a second control node, so that the second control node determines a target number corresponding to the information synchronization request according to an information transmission bandwidth and an information number in an information list corresponding to the synchronization type, wherein the synchronization identifier comprises a start identifier of the current synchronization information;
receiving the target quantity of synchronization information, new synchronization identification and new synchronization type returned by the second control node based on the information synchronization request;
and continuing to send the next information synchronization request based on the new synchronization identification and the new synchronization type.
8. The method of claim 7, wherein the method further comprises:
and stopping sending the information synchronization request to the second control node in response to determining that the synchronization type is a preset type for representing stopping sending the information synchronization request.
9. A private cloud information synchronization apparatus, comprising:
the system comprises a receiving module, a sending module and a processing module, wherein the receiving module is configured to receive an information synchronization request sent by a first control node, the information synchronization request comprises a synchronization type and a synchronization identifier, and the synchronization identifier comprises a start identifier of current synchronization information;
a determining module configured to determine a target number corresponding to the information synchronization request according to an information transmission bandwidth and an information number in an information list corresponding to the synchronization type; determining a target number of synchronization information based on the synchronization type and the synchronization identifier;
a sending module configured to determine a new synchronization identifier and a new synchronization type based on the target number of synchronization information, and send the target number of synchronization information, the new synchronization identifier and the new synchronization type to the first control node, so that the first control node continues to send a next information synchronization request based on the new synchronization identifier and the new synchronization type.
10. The apparatus of claim 9, wherein the means for determining comprises:
a first determination unit configured to determine an information list corresponding to the synchronization type based on the synchronization type;
a second determining unit configured to determine a target number of synchronization information in the information list based on the synchronization flag.
11. The apparatus of claim 10, wherein the second determining unit is further configured to:
and in response to determining that the information quantity of the residual information in the information list is greater than or equal to the target quantity, determining a target quantity of synchronization information in the residual information in the information list.
12. The apparatus of claim 11, wherein the second determining unit is further configured to: in response to determining that the information quantity of the remaining information in the information list is greater than the target quantity, determining a target quantity of synchronization information in the remaining information in the information list; and
the sending module further configured to: and setting a new synchronization identifier based on the synchronization information of the target number, and taking the synchronization type as a new synchronization type.
13. The apparatus of claim 11, wherein the second determining unit is further configured to: in response to determining that the information amount of the remaining information in the information list is equal to the target amount, taking all of the remaining information of the information list as synchronization information; and
the sending module further configured to: and based on the priority of the locally stored information type, taking the information type of the next priority of the synchronization type as a new synchronization type, and setting the synchronization identifier as initialization.
14. The apparatus of claim 11, wherein the second determining unit is further configured to: in response to determining that the information quantity of the remaining information in the information list is smaller than the target quantity, determining a new information list corresponding to an information type of a next priority of the synchronization type based on a priority of a locally stored information type; determining a target number of synchronization information in the remaining information of the information list and the new information list; and
the sending module further configured to: and taking the information type of the next priority of the synchronization type as a new synchronization type, and setting a new synchronization identifier based on the synchronization information in the new information list.
15. A private cloud information synchronization apparatus, comprising:
a sending module configured to send an information synchronization request including a synchronization type and a synchronization identifier to a second control node in response to determining that the synchronization type is a preset type for representing sending of the information synchronization request, so that the second control node determines a target number corresponding to the information synchronization request according to an information transmission bandwidth and an information number in an information list corresponding to the synchronization type, wherein the synchronization identifier includes a start identifier of the current synchronization information;
a receiving module configured to receive a target number of synchronization information, a new synchronization identifier and a new synchronization type, which are returned by the second control node based on the information synchronization request;
the sending module is further configured to continue sending the next information synchronization request based on the new synchronization identifier and the new synchronization type.
16. The apparatus of claim 15, wherein the apparatus further comprises:
a termination module configured to stop sending the information synchronization request to the second control node in response to determining that the synchronization type is a preset type for characterizing stop sending the information synchronization request.
17. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-8.
18. A non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any one of claims 1-8.
CN202110255623.3A 2021-03-09 2021-03-09 Private cloud information synchronization method and device Active CN113014656B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110255623.3A CN113014656B (en) 2021-03-09 2021-03-09 Private cloud information synchronization method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110255623.3A CN113014656B (en) 2021-03-09 2021-03-09 Private cloud information synchronization method and device

Publications (2)

Publication Number Publication Date
CN113014656A CN113014656A (en) 2021-06-22
CN113014656B true CN113014656B (en) 2023-04-07

Family

ID=76402925

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110255623.3A Active CN113014656B (en) 2021-03-09 2021-03-09 Private cloud information synchronization method and device

Country Status (1)

Country Link
CN (1) CN113014656B (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109639834A (en) * 2019-01-25 2019-04-16 努比亚技术有限公司 A kind of synchronizing information processing method, system and mobile terminal
CN111628886A (en) * 2020-04-14 2020-09-04 苏宁金融科技(南京)有限公司 Method and device for building block chain network under private cloud environment, and computer equipment
CN112115203A (en) * 2020-09-29 2020-12-22 腾讯科技（深圳）有限公司 Asset management method, device, equipment and storage medium of cloud platform

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106657251A (en) * 2016-10-25 2017-05-10 广东欧珀移动通信有限公司 Data synchronizing method and apparatus
US20190075171A1 (en) * 2017-09-05 2019-03-07 EtherLabs, Inc. System and Method for Generating Marker Data

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109639834A (en) * 2019-01-25 2019-04-16 努比亚技术有限公司 A kind of synchronizing information processing method, system and mobile terminal
CN111628886A (en) * 2020-04-14 2020-09-04 苏宁金融科技(南京)有限公司 Method and device for building block chain network under private cloud environment, and computer equipment
CN112115203A (en) * 2020-09-29 2020-12-22 腾讯科技（深圳）有限公司 Asset management method, device, equipment and storage medium of cloud platform

Also Published As

Publication number Publication date
CN113014656A (en) 2021-06-22

Similar Documents

Publication Publication Date Title
CN114374703B (en) Cloud mobile phone information acquisition method, device, equipment and storage medium
CN113641388A (en) Cloud mobile phone updating method, related device and computer program product
CN113726881B (en) Communication connection establishment method, related device and computer readable storage medium
CN113014656B (en) Private cloud information synchronization method and device
CN113541987A (en) Method and device for updating configuration data
CN114070889B (en) Configuration method, traffic forwarding device, storage medium, and program product
CN115767786A (en) Multi-cluster communication method and device, electronic equipment and storage medium
CN114968170B (en) Floating point number determination and generation method, related device and computer program product
CN113420275B (en) Data connection processing method, related device and computer program product
CN113726883B (en) Cloud data processing method, related device and computer program product
CN113612643B (en) Network configuration method, device and equipment of cloud mobile phone and storage medium
CN113556394B (en) Cloud product network usage processing method, device, equipment, storage medium and product
CN115658290A (en) Message processing method, device, equipment and storage medium
CN115567602A (en) CDN node back-to-source method, device and computer readable storage medium
CN114095758A (en) Cloud image intercepting method, related device and computer program product
CN114546444A (en) Vehicle upgrading method and device, electronic equipment, medium and automatic driving vehicle
CN110661697B (en) Message synchronization method, device, readable storage medium, electronic device and system
CN113824689A (en) Edge computing network, data transmission method, device, equipment and storage medium
CN110661857A (en) Data synchronization method and device
CN114221906B (en) Flow control method and device, electronic equipment and storage medium
CN113472565B (en) Method, apparatus, device and computer readable medium for expanding server function
CN115150310B (en) Request generation method, request processing device, electronic equipment and storage medium
CN115080205B (en) Task execution method, device, electronic equipment and readable storage medium
CN115103019A (en) Access request forwarding method and device, electronic equipment and readable storage medium
CN118018522A (en) Network card configuration method, device, equipment and 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