A tag synchronization method, system, device and computer-readable storage medium

Abstract

The present application discloses a label synchronization method, system, device and computer-readable storage medium, which are applied to a target mimicking device, obtain and save an LDP Hello message sent by a neighboring device connected to the target mimicking device; distribute the LDP Hello message to all online target executors of the target executor, so that the target executor discovers and maintains neighboring devices based on the LDP Hello message; obtain a TCP link state management message, and manage the TCP link between the target executor and the neighboring device based on the TCP link state management message; obtain an LDP session management message, and manage the LDP session between the target executor and the neighboring device based on the LDP session management message; obtain a neighbor address management message, and manage the neighbor address information in the target executor based on the neighbor address management message; obtain label management information, and synchronize the label between the target executor and the neighboring device based on the label management information.

Description

Technical Field

[0001] The present application relates to the field of Internet communication technology, and more specifically, to a tag synchronization method, system, device and computer-readable storage medium. Background Art

[0002] With the continuous growth of network scale, the security of cyberspace has been paid more and more attention. In this process, mimetic defense, as a security defense mechanism, has become one of the current hot spots in network security innovation research. With the help of mimetic devices, the theory of mimetic defense is applied to traditional network devices, and multiple heterogeneous redundant executors are introduced. Through heterogeneous methods such as platform heterogeneity, system heterogeneity, and application heterogeneity, the probability of vulnerability can be greatly reduced, and the security of network devices can be greatly improved. And mimetic devices usually have multiple executors, including a master executor and multiple slave executors. It supports multiple routing control protocols. To realize the mimeticization of routing protocols, it is necessary to maintain the status of each executor and ensure the consistency of the status of multiple executors. For example, the Label Distribution Protocol (LDP) is used to ensure the consistency of the status of multiple executors.

[0003] However, since the main executor, the slave executor and other executors in the mimic device are affected by their own work, it may not be possible to ensure that the labels saved by themselves are consistent with those in other executors.

[0004] In summary, how to ensure the consistency of labels in mimicking devices is an urgent problem to be solved by those skilled in the art. Summary of the invention

[0005] The purpose of the present application is to provide a tag synchronization method, which can solve the technical problem of how to ensure the consistency of tags in mimicking devices to a certain extent. The present application also provides a tag synchronization system, device and computer-readable storage medium.

[0006] In order to achieve the above objectives, this application provides the following technical solutions:

[0007] A tag synchronization method, applied to a target mimic device, includes:

[0008] Obtain and save an LDP Hello message sent by a neighboring device connected to the target mimic device;

[0009] Distribute the LDP Hello message to all online target executors of the target executor, so that the target executor discovers and maintains the neighbor device based on the LDP Hello message;

[0010] Obtaining a TCP link state management message, and managing the TCP link between the target execution body and the neighbor device based on the TCP link state management message;

[0011] Obtaining an LDP session management message, and managing an LDP session between the target execution entity and the neighbor device based on the LDP session management message;

[0012] Obtaining a neighbor address management message, and managing the neighbor address information in the target executable body based on the neighbor address management message;

[0013] The tag management information is acquired, and the tags between the target execution body and the neighbor device are synchronized based on the tag management information, so that the tags between the target execution bodies are synchronized.

[0014] Preferably, the TCP link state management message includes a link establishment or link teardown message;

[0015] The obtaining of the TCP link state management message, and managing the TCP link between the target execution body and the neighbor device based on the TCP link state management message, includes:

[0016] If the TCP link state management message sent by the neighboring device is monitored, the TCP link state management message is cached; the TCP link state between the main execution body in the target execution body and the neighboring device is obtained, and the TCP link between the slave execution body in the target execution body and the neighboring device is managed based on the TCP link state and the TCP link state management message;

[0017] If the TCP link state management message sent by the main execution body is monitored, the TCP link between the target execution body and the neighbor device is managed based on the TCP link state management message;

[0018] If the TCP link state management message sent by any of the slave execution bodies is monitored, it is determined whether the link establishment between the neighboring device and the main execution body is completed. If so, the TCP link between any of the slave execution bodies and the neighboring device is managed based on the TCP link state management message; if not, the TCP link state management message is discarded.

[0019] Preferably, the message types in the LDP session management message include an Initialization message and a keepalive message;

[0020] The obtaining of the LDP session management message, and managing the LDP session between the target execution body and the neighbor device based on the LDP session management message, includes:

[0021] When the target mimic device is the passive party establishing the LDP session:

[0022] If the Initialization message and / or the keepalive message sent by the neighboring device is monitored, the Initialization message and / or the keepalive message is cached, and the Initialization message and / or the keepalive message is sent to the target execution body that completes the TCP link establishment;

[0023] If a SYN+ACK message sent by any of the target execution bodies is monitored, a corresponding ACK message is sent to the any execution body, and the cached Initialization message of the neighbor device is sent to the any execution body;

[0024] If the Initialization+keepalive message sent by any of the execution bodies is monitored, a corresponding ACK message is sent to the any of the execution bodies, and the cached keepalive message of the neighbor device is sent to the any of the execution bodies.

[0025] Preferably, the message types in the LDP session management message include an Initialization message and a keepalive message;

[0026] The obtaining of the LDP session management message, and managing the LDP session between the target execution body and the neighbor device based on the LDP session management message, includes:

[0027] When the target mimic device is the active party in establishing the LDP session:

[0028] If an Initialization+keepalive message sent by the neighboring device is monitored, the Initialization+keepalive message is cached, and the Initialization+keepalive message is sent to the target execution body that completes the TCP link establishment;

[0029] If the Initialization message sent by any of the target execution bodies is monitored, a corresponding ACK message is sent to the any execution body, and the cached Initialization+keepalive message of the neighboring device is sent to the any execution body;

[0030] If the keepalive message sent by any of the execution bodies is monitored, a corresponding ACK message is sent to the any of the execution bodies.

[0031] Preferably, the acquiring of the neighbor address management message and managing the neighbor address information in the target executable body based on the neighbor address management message includes:

[0032] If an Address Message message sent by the neighbor device is monitored, the neighbor class is obtained based on the srcIp, dstIp, and routeId in the AddressMessage message, and all Addresses in the Address Message message are added to the address hash table corresponding to the neighbor class;

[0033] If an Address Withdraw Message message sent by the neighbor device is monitored, all cached Addresses are queried based on the neighbor class, and all Addresses that are the same as the Address in the Address Message message are deleted from the address hash table corresponding to the neighbor class;

[0034] If the neighbor address management message sent by the target executor that successfully establishes the LDP session is monitored, an Address Message message is created based on the address information locally cached by the target mimic device and sent to the target executor.

[0035] Preferably, the acquiring of the tag management information and synchronizing the tag between the target execution body and the neighbor device based on the tag management information includes:

[0036] If the Label Mapping Message message sent by the neighbor device is monitored, the neighbor class is queried based on the srcIp, dstIp, and routeId in the LabelMapping Message message, all first FEC / Label mappings of the neighbor device are obtained according to the neighbor query cache dictionary, and the second FEC / Label mapping in the Label Mapping Message message is cyclically obtained. If the FEC in the second FEC / Label mapping already exists in the first FEC / Label mapping, the first FEC / Label mapping is updated based on the second FEC / Label mapping. If the FEC in the second FEC / Label mapping does not exist in the first FEC / Label mapping, the second FEC / Label mapping is added to the first FEC / Label mapping, and the first FEC / Label mapping is transparently transmitted to the online target execution body;

[0037] If the Label Withdraw Message message sent by the neighbor device is monitored, the neighbor class is obtained by querying the srcIp, dstIp, and routeId in the LabelWithdraw Message message, all first FEC / Label mappings of this neighbor are obtained according to the neighbor query cache dictionary, and the second FEC / Label mapping in the LabelWithdraw Message message is obtained cyclically. If the FEC in the second FEC / Label mapping already exists in the first FEC / Label mapping, the second FEC / Label mapping in the first FEC / Label mapping is deleted, and the first FEC / Label mapping is transparently transmitted to the online target execution body;

[0038] If a Label Release Message, a Label Request Message or a Label Abort Request Message sent by the neighboring device is monitored, it is directly discarded.

[0039] Preferably, the acquiring of the tag management information and synchronizing the tag between the target execution body and the neighbor device based on the tag management information includes:

[0040] If a Label Mapping Message message sent by any of the target executable bodies is monitored, and FEC / Label mapping information has not been sent to any of the target executable bodies, the neighbor class is obtained by querying according to srcIp, dstIp, and routeId in the Label Mapping Message message, all FEC / Label mappings of the neighbor device are obtained by querying the cache dictionary according to the neighbor, and a new Label Mapping Message message is constructed according to all the FEC / Label mappings and sent to any of the target executable bodies;

[0041] If a Label Mapping Message sent by any executor is monitored and the FEC / Label mapping information has been sent to any executor, the Label Mapping Message is directly discarded;

[0042] If a Label Withdraw Message sent by any executable body is monitored, a Label Release Message corresponding to the Label Withdraw Message is created and sent to the any executable body;

[0043] If a Label Request Message and a Label AbortRequest Message sent by any executor is monitored, they are forwarded to the neighbor device.

[0044] A tag synchronization system, applied to a target mimic device, comprising:

[0045] A Hello message management module is used to obtain and save the LDP Hello message sent by the neighboring device connected to the target mimicking device; distribute the LDP Hello message to all online target executors of the target executor, so that the target executor discovers and maintains the neighboring device based on the LDP Hello message;

[0046] A TCP link state management module, used to obtain a TCP link state management message, and manage the TCP link between the target execution body and the neighbor device based on the TCP link state management message;

[0047] An LDP session establishment and maintenance management module, used to obtain an LDP session management message, and manage the LDP session between the target execution body and the neighbor device based on the LDP session management message;

[0048] A neighbor address cache distribution management module, used to obtain a neighbor address management message, and manage the neighbor address information in the target executable body based on the neighbor address management message;

[0049] The FEC label cache distribution management module is used to obtain label management information and synchronize the labels between the target execution body and the neighbor device based on the label management information, so as to synchronize the labels between the target execution bodies.

[0050] A tag synchronization device, applied to a target mimic device, comprising:

[0051] Memory for storing computer programs;

[0052] A processor is used to implement the steps of any of the above-mentioned tag synchronization methods when executing the computer program.

[0053] A computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of any of the above-mentioned tag synchronization methods are implemented.

[0054] The present application provides a label synchronization method, which is applied to a target mimic device, obtains and saves the LDP Hello message sent by a neighbor device connected to the target mimic device; distributes the LDP Hello message to all online target executors, so that the target executor discovers and maintains neighbor devices based on the LDP Hello message; obtains a TCP link state management message, and manages the TCP link between the target executor and the neighbor device based on the TCP link state management message; obtains an LDP session management message, and manages the LDP session between the target executor and the neighbor device based on the LDP session management message; obtains a neighbor address management message, and manages the neighbor address information in the target executor based on the neighbor address management message; obtains label management information, and synchronizes the label between the target executor and the neighbor device based on the label management information. In the present application, the target mimic device can manage the LDP interaction process between the online target executor and the neighbor device based on the corresponding message, synchronize the label between the target executor and the neighbor device, so that the labels in all online target executors in the target mimic device are consistent. The label synchronization system, device and computer-readable storage medium provided by the present application also solve the corresponding technical problems. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0056] Figure 1 This is a schematic diagram of the interaction of the LDP protocol;

[0057] Figure 2 A flowchart of a tag synchronization method provided in an embodiment of the present application;

[0058] Figure 3 A first schematic diagram of managing a TCP link between a target execution body and a neighbor device based on a TCP link state management message;

[0059] Figure 4 A second schematic diagram of managing a TCP link between a target execution body and a neighboring device based on a TCP link state management message;

[0060] Figure 5 A first schematic diagram of managing an LDP session between a target execution entity and a neighboring device based on an LDP session management message;

[0061] Figure 6 A second schematic diagram of managing an LDP session between a target execution entity and a neighbor device based on an LDP session management message;

[0062] Figure 7 A third schematic diagram of managing an LDP session between a target execution entity and a neighboring device based on an LDP session management message;

[0063] Figure 8 A fourth schematic diagram of managing an LDP session between a target execution entity and a neighboring device based on an LDP session management message;

[0064] Fig. 9 A schematic diagram of a double-layer hash table storage for address information;

[0065] Fig.10 A schematic diagram of a double-layer hash table storage for mapping information;

[0066] Fig.11 A first schematic diagram of synchronizing tags between a target execution body and a neighbor device based on tag management information;

[0067] Fig.12 A second schematic diagram of synchronizing tags between a target execution body and a neighbor device based on tag management information;

[0068] Fig.13A structural diagram of a tag synchronization system provided in an embodiment of the present application;

[0069] Fig.14 A structural diagram of a tag synchronization device provided in an embodiment of the present application;

[0070] Fig.15 Another structural schematic diagram of a tag synchronization device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0071] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0072] In order to facilitate the understanding of the present application, the LDP protocol involved in the present application is now explained.

[0073] LDP is a control and signaling protocol in the MPLS (Multi-Protocol Label Switching) system, responsible for the classification of FEC (Forwarding Equivalent Class), the allocation of Labels, and the establishment and maintenance of LSP (Label Switch Path). In an MPLS network, network devices map a label to each internal route by running the LDP protocol, and then notify all neighbors of the label information. In this way, network devices establish a label forwarding table and eventually form LSP. When the network topology changes, LDP will respond to this change in real time and dynamically establish LSP.

[0074] Among them, the messages of the LDP protocol can be divided into four categories: Discovery, Session, Advertisement and Notification. Among them, Discovery Message is used to announce and maintain the existence of LSR (Label Switch Router) in the network; Session Message is used to establish, maintain and terminate sessions between LDP peers; Advertisement Message is used to create, change and delete FEC label mappings; Notification Message is used to provide advisory messages and error notifications. The specific message types are shown in Table 1. In order to ensure the reliable transmission of LDP messages, except for Discovery messages that use UDP (User Datagram Protocol) for transmission, other messages are transmitted using TCP (Transmission Control Protocol).

[0075] Table 1 LDP protocol message types

[0076]

[0077] The interaction process of the LDP protocol can be described as follows Figure 1As shown in the figure, it can be divided into three parts: discovery mechanism, session establishment, and LSP establishment. The discovery mechanism refers to: LSR periodically multicasts Hello messages, and the LDP peers in the same network segment complete neighbor discovery after receiving the Hello messages; LSR will decide based on the routerId carried in the Hello message, and the party with the larger routerId will be the active party to initiate the LDP session; at the same time, the periodically sent Hello messages are also used to maintain neighbors. If the Hello hold timer times out and no new Hello message is received, the Hello adjacency relationship will be deleted. After the adjacency relationship is deleted, the local LSR will send a Notification message to end the LDP session. Among them, session establishment means: the party with a larger routerId will initiate a TCP connection as the active party, and the party with a smaller routerId will start TCP connection listening; after completing the TCP connection through the TCP three-way handshake, the party with a larger routerId will actively send an Initialization message to notify its own configuration parameters, and the party with a smaller routerId will reply to the Initialization message to notify the local configuration after receiving the Initialization message from the other party, and will also reply to the Keepalive message; after receiving the Initialization+keepalive message, the active party completes parameter negotiation and starts sending keepalive messages; the keepalive messages periodically sent by the LSR are also used to maintain the session. If the session hold timer (Keepalive hold timer) times out and still no Keepalive message is received, the TCP connection is closed, and the local LSR will send a Notification message to end the LDP session. Among them, LSP establishment means: after the LDP session is established, LDP sends label request and label mapping messages to notify the binding relationship between FEC and labels between LDP peers, thereby establishing LSP.

[0078] See also Figure 2 , Figure 2 A flowchart of a tag synchronization method provided in an embodiment of the present application.

[0079] A tag synchronization method provided in an embodiment of the present application, applied to a target mimicking device, may include the following steps:

[0080] Step S101: Obtain and save an LDP Hello message sent by a neighboring device connected to the target mimicking device.

[0081] Step S102: distribute LDP Hello messages to all online target executors, so that the target executors discover and maintain neighbor devices based on the LDP Hello messages.

[0082] In actual applications, the target mimic device can first obtain and save the LDP Hello message sent by the neighboring device connected to the target mimic device, and then distribute the LDP Hello message to all its online target executors, such as transparently processing the LDP Hello message and distributing it to all online executors, so that the target executor can discover and maintain neighboring devices based on the LDP Hello message. In this way, all online executors in the target mimic device can discover and maintain neighboring devices.

[0083] It should be noted that when an executor in the target mimic device comes online, for example, when an executor that has been offline comes back online, the executor becomes the target executor. At this time, the target mimic device can distribute LDO Hello messages to the executor so that the executor can discover and maintain neighbor devices based on LDP Hello messages. In addition, it should be noted that the LDPHello message is the only message in the LDP protocol that is transmitted via UDP (User Datagram Protocol). The LDP Hello message is used to discover and maintain LDP neighbors. During this process, the target mimic device can also actively send LDP Hello messages to neighbor devices. Specifically, the target mimic device can send the LDP Hello message sent by the main executor to the neighbor device, and can not process the LDP Hello message sent by the slave executor.

[0084] Step S103: Obtain a TCP link state management message, and manage the TCP link between the target execution body and the neighbor device based on the TCP link state management message.

[0085] In actual applications, the target mimic device can also obtain TCP link state management messages, and manage the TCP link between the target executor and the neighboring device based on the TCP link state management messages. In this process, the target mimic device can save the obtained TCP link state management messages, and when there is a new executor online, it can send the saved TCP link state management message to the executor, so that the new executor online synchronizes the TCP link state with the neighboring device.

[0086] It should be noted that the type of TCP link state management message can be determined according to actual needs. For example, the TCP link state management message can include a TCP link generation message, which is used to instruct the executor to establish a TCP link with a neighboring device. In addition, according to the LDP protocol rules, the party with a larger LDP routeId actively initiates a TCP connection. Considering that there are multiple executors in the target mimic device, and each executor needs to establish a TCP link with a neighboring device, in order to facilitate the distinction of TCP link establishment information between each executor and the neighboring device, the direction field can also be set in the corresponding TCP link information to identify the TCP connection direction, and whether the target mimic device is the active party, etc.

[0087] In a specific application scenario, a TCP link state management message may include a link establishment or teardown message (TCP SYN / SYN+ACK / ACK FIN / FIN+ACK); at this time, the target mimic device obtains the TCP link state management message, and manages the TCP link between the target executor and the neighboring device based on the TCP link state management message. If a TCP link state management message sent by the neighboring device is monitored, the TCP link state management message can be cached to obtain the TCP link state between the main executor in the target executor and the neighboring device, and the TCP link between the slave executor in the target executor and the neighboring device is managed based on the TCP link state and the TCP link state management message, so that the TCP link state between all executors and the neighboring devices is consistent. For example, if the TCP link state between the main executor and the neighboring device is linked, the slave executor and the neighboring device can be controlled to establish a TCP link based on the link establishment message. The processing flow is as follows: Figure 3 As shown in the figure, the schematic diagram of processing the TCP link message sent by the neighboring device is as follows Figure 3 As shown, the sniff corresponding interface 646 port represents the corresponding receiving port on the target mimic device, and the target execution body in the target mimic device can be subdivided into a main execution body and a slave execution body, wherein the main execution body refers to the execution body in the target mimic device used to directly interact with the neighboring device for data, and the slave execution body refers to the execution body that interacts with the neighboring device for data through the main execution body; if the TCP link state management message sent by the main execution body in the target mimic device is monitored, the TCP link between the target execution body and the neighboring device can be managed based on the TCP link state management message. For example, if the main execution body sends a teardown message, the TCP links between all execution bodies and neighboring devices are removed based on the teardown message, and the processing flow is as follows Figure 4As shown; if a TCP link state management message sent by any slave execution body is monitored, it is determined whether the link establishment between the neighboring device and the main execution body is completed. If so, the TCP link between any slave execution body and the neighboring device is managed based on the TCP link state management message. For example, the TCP link state management message sent by any slave execution body can be stored for subsequent interaction with any slave execution body. Construct TCP SYN, SYN+ACK, ACK, FIN, FIN+ACK and other messages; if the neighboring device and the main execution body have not completed the link establishment, the TCP link state management message sent by any slave execution body can be discarded, etc. The processing flow is as follows Figure 4 As shown, the schematic diagram of processing the TCP connection message sent by the execution body is as follows Figure 4 shown.

[0088] Step S104: Obtain an LDP session management message, and manage the LDP session between the target execution entity and the neighbor device based on the LDP session management message.

[0089] In actual applications, the target mimic device can also obtain LDP session management messages, and manage the LDP session between the target executor and the neighboring device based on the LDP session management messages. For example, when the LDP session management message is an LDP session message (including Initialization messages and keepalive messages), if the target mimic device receives an LDPsession message sent by a neighboring device, it can cache the LDP session message and copy and distribute it to all online executors, etc. It should be noted that, similar to the TCP link establishment method, in the LDP protocol, the party with a larger routerId actively initiates the session, that is, actively sends the Initialization message. Therefore, when determining the sending status of the LDP session message, the TCP connection direction can be judged through the direction field to decide whether to actively send the Initialization message, etc.

[0090] In a specific application scenario, the message types in the LDP session management message may include an Initialization message and a keepalive message; accordingly, in the process of the target mimicking device obtaining the LDP session management message and managing the LDP session between the target executor and the neighboring device based on the LDP session management message, if the target mimicking device is the passive party in establishing the LDP session, after monitoring the Initialization message and / or keepalive message sent by the neighboring device, the Initialization message and / or keepalive message is cached, and the Initialization message and / or keepalive message is sent to the target executor that completes the TCP link establishment. The processing flow is as follows: Figure 5 As shown in the figure, when the target device is the passive party, the process of processing the LDP session message sent by the neighboring device is as follows Figure 5 As shown; if the target mimic device is the passive party to establish the LDP session, after monitoring the SYN+ACK message generated by any executor in the target executor during the TCP link establishment process, the corresponding ACK message is sent to the executor, and the Initialization message of the cached neighbor device is sent to the executor. The processing flow is as follows Figure 6 As shown; if the target mimic device is the passive party to establish the LDP session, after listening to the Initialization+keepalive message sent by any executor, it sends the corresponding ACK message to any executor and sends the cached keepalive message of the neighboring device to any executor. The processing flow is as follows Figure 6 As shown in FIG. 1 , that is, when the target device is the passive party, the process of processing the LDP session message sent by the executor is as follows Figure 6 shown.

[0091] Correspondingly, if the target mimic device is the active party to establish the LDP session, after listening to the Initialization+keepalive message sent by the neighboring device, it caches the Initialization+keepalive message and sends the Initialization+keepalive message to the target execution body that completes the TCP link establishment. The processing flow is as follows: Figure 7 As shown in the figure, when the target device is the active party, the process of processing the LDP session message sent by the neighboring device is as follows Figure 7 As shown; if the target mimic device is the active party to establish the LDP session, after monitoring the Initialization message sent by any executor in the target executor, it sends the corresponding ACK message to any executor, and sends the cached Initialization+keepalive message of the neighboring device to any executor. The processing flow is as follows Figure 8 As shown; if the target mimic device is the active party to establish the LDP session, after monitoring the keepalive message sent by any executor, it sends the corresponding ACK message to any executor. The processing flow is as follows Figure 8 As shown, when the target device is the active party, the process of processing the LDP session message sent by the executor is as follows Figure 8 shown.

[0092] Step S105: Obtain a neighbor address management message, and manage the neighbor address information in the target executable body based on the neighbor address management message.

[0093] In actual applications, the target mimic device can also obtain neighbor address management messages and manage neighbor address information in the target executor based on the neighbor address management messages. For example, the address information of the neighbor device is cached, copied and distributed to each online executor, and the LDP Address message sent by each executor is processed at the same time.

[0094] It should be noted that the LDP protocol stipulates that after the session is established, the two parties will exchange interface addresses. This process has two types of messages: Address Message and Address Withdraw Message. Address Message is used to announce the interface address, and Address Withdraw Message is used to revoke the interface address. Since the address announcement message involves operations such as announcement and revocation, it is not possible to simply cache the latest Address Message, but it is necessary to cache the correct neighbor address. For this reason, this application designs a two-layer hash table to store address information. The key of the first-layer dictionary is the neighbor class, which is used to identify a neighbor. The key of the second-layer dictionary is the address. See the data structure diagram. Fig. 9 , where the neighbor class contains three fields, namely the original address srcIp, the destination address dstIp, and the device's routeId. Among them, srcIp refers to the address of the message sender, dstIp refers to the address of the message receiver, and routeId refers to the device ID of the message sender. When the target mimic device receives the Address Message message from the neighbor device, it first obtains the neighbor class through the srcIp, dstIp, and routeId in the AddressMessage message, and adds all the Addresses in the message to the hash table; when receiving the Address Withdraw Message message from the neighbor device, it queries all cached Addresses through the neighbor class, and deletes the cache if it is the same as the withdrawn address in the message. In this way, the address information cached in the target mimic device can be guaranteed to be consistent with the address information of the neighbor device.

[0095] In a specific application scenario, when the target mimic device obtains a neighbor address management message and manages the neighbor address information in the target executive body based on the neighbor address management message, if the target mimic device monitors the AddressMessage message sent by the neighbor device, the neighbor class is obtained based on the srcIp, dstIp, and routeId in the Address Message message, and all Addresses in the Address Message message are added to the address hash table corresponding to the neighbor class; if the target mimic device monitors the Address Withdraw Message message sent by the neighbor device, all cached Addresses are queried based on the neighbor class, and all Addresses that are the same as the Address in the Address Message message are deleted from the address hash table corresponding to the neighbor class; if the target mimic device monitors the neighbor address management message sent by the target executive body that successfully establishes the LDP session, the target mimic device creates an Address Message message based on the address information cached locally and sends it to the target executive body.

[0096] Step S106: Acquire tag management information, and synchronize tags between the target execution body and neighbor devices based on the tag management information.

[0097] In actual applications, the target mimic device can also obtain tag management information and synchronize tags between the target executor and neighboring devices based on the tag management information, so as to synchronize tags between target executors. For example, the tag message sent by the neighboring device is cached and copied and distributed to each online executor.

[0098] It should be noted that LDP has five types of label messages: Label Mapping Message is used to announce FEC / label mapping information, Label Withdraw Message is used to withdraw FEC / label mapping information, Label Release Message is used to release labels, Label Request Message is used to request FEC label mapping, and Label Abort Request Message is used to terminate the unfinished Label Request Message. And similar to the address information announcement, the LDP protocol has Label Mapping Message to announce FEC / label mapping information and Label Withdraw Message to withdraw FEC / label mapping information. Since there are operations such as label announcement and label withdrawal, and they may be relatively frequent, all label messages cannot be cached directly, but the correct FEC / label mapping information needs to be cached. For this reason, this application also uses a double-layer hash table to save FEC / label mapping information. See the data structure diagram. Fig.10 . The key of the first-layer dictionary is the neighbor class. The definition of the neighbor class is the same as above. It is used to identify a neighbor device. Its corresponding value is also a dictionary, which saves all FEC / Label mappings of this neighbor device; the key of the second-layer dictionary is FEC, and the value is the corresponding Label. When receiving the Label Mapping Message from the neighbor device, first get the neighbor class through srcIp, dstIp, and routeId, and add all FEC / Label mappings in the message to the hash table; when receiving the Label Withdraw Message from the neighbor device, query all cached FEC / Label mappings through the neighbor class, and delete the cache if it is the same as the label withdrawn in the message. This ensures that the cached label information is consistent with the label information of the neighbor device.

[0099] In a specific application scenario, the target mimic device obtains label management information, and in the process of synchronizing the label between the target executor and the neighbor device based on the label management information, if the Label MappingMessage message sent by the neighbor device is monitored, the neighbor class is queried based on the srcIp, dstIp, and routeId in the Label Mapping Message message, and all first FEC / Label mappings of this neighbor mimic device are obtained according to the neighbor query cache dictionary, and the second FEC / Label mapping in the Label Mapping Message message is cyclically obtained (the Label MappingMessage message includes several FEC / Label mappings). If the FEC in the second FEC / Label mapping already exists in the first FEC / Label mapping, the first FEC / Label mapping is updated based on the second FEC / Label mapping. If the FEC in the second FEC / Label mapping does not exist in the first FEC / Label mapping, the second FEC / Label mapping is added to the first FEC / Label mapping, and then the first FEC / Label mapping is transparently transmitted to the online target executor, thereby synchronizing the label between the target executor and the neighbor device. The processing flow is as follows: Fig.11 As shown, the transparent transmission in this application refers to transparent transmission, which means that no matter what the business content of the transmission is, it is only responsible for transmitting the transmission content from the source address to the destination address without making any changes to the business data content; if the Label Withdraw Message message sent by the neighbor device is monitored, the neighbor class is obtained through the srcIp, dstIp, and routeId in the LabelWithdraw Message message, and the cache dictionary is queried according to the neighbor to obtain all the first FEC / Label mappings of this neighbor, and the second FEC / Label mapping in the Label WithdrawMessage message is obtained cyclically. If the FEC in the second FEC / Label mapping already exists in the first FEC / Label mapping, the Label mapping of the FEC in the cache is deleted, and then the first FEC / Label mapping is transparently transmitted to the online target executor, thereby synchronizing the label between the target executor and the neighbor device. The processing flow is as follows Fig.11 As shown; if the Label Release Message, Label Request Message or Label AbortRequest Message sent by the neighboring device is monitored, it will be discarded directly. The processing flow is as follows Fig.11 As shown in the figure, the process of processing label management information sent by neighboring devices is as follows Fig.11 shown.

[0100] In a specific application scenario, the target mimic device obtains label management information and synchronizes the labels between the target executor and the neighbor device based on the label management information. If the Label Mapping Message message sent by any executor in the target executor is monitored and the FEC / Label mapping information has not been sent to any executor, the neighbor class is obtained according to the srcIp, dstIp, and routeId in the Label Mapping Message message, and the cache dictionary is queried according to the neighbor to obtain all FEC / Label mappings of this neighbor device. A new Label Mapping Message message is constructed according to all the obtained FEC / Label mappings and sent to any executor, thereby synchronizing the labels between the target executor and the neighbor device. The processing flow is as follows: Fig.12 As shown; if a Label MappingMessage message sent by any executor is monitored and FEC / Label mapping information has been sent to any executor, the LabelMapping Message message is directly discarded without processing. The processing flow is as follows Fig.12 As shown; if the LabelWithdraw Message message sent by any executor is monitored, a Label ReleaseMessage message corresponding to the Label Withdraw Message message is created and sent to the executor to simulate the process of neighboring devices releasing labels, thereby synchronizing the labels between the target executor and the neighboring devices. The processing flow is as follows Fig.12 As shown; if the Label RequestMessage and Label Abort Request Message sent by any executor are monitored, they are forwarded to the neighboring device. The processing flow is as follows Fig.12 As shown, the process of processing the tag management information sent by the execution body is as follows Fig.12 shown.

[0101] A label synchronization method provided in the present application is applied to a target mimicry device, obtains and saves an LDP Hello message sent by a neighboring device connected to the target mimicry device; distributes the LDP Hello message to all online target executors of the target executor, so that the target executor discovers and maintains neighboring devices based on the LDP Hello message; obtains a TCP link state management message, and manages the TCP link between the target executor and the neighboring device based on the TCP link state management message; obtains an LDP session management message, and manages the LDP session between the target executor and the neighboring device based on the LDP session management message; obtains a neighbor address management message, and manages the neighbor address information in the target executor based on the neighbor address management message; obtains label management information, and synchronizes the label between the target executor and the neighboring device based on the label management information. In the present application, the target mimicry device can manage the LDP interaction process between the online target executor and the neighboring device based on the corresponding message, so that the LDP protocol information between all target executors and the neighboring devices is consistent, and can synchronize the label between the target executor and the neighboring device, so that the labels in all online target executors in the target mimicry device are consistent.

[0102] See also Fig.13 , Fig.13 A structural diagram of a tag synchronization system provided in an embodiment of the present application.

[0103] A tag synchronization system provided in an embodiment of the present application is applied to a target mimic device and may include:

[0104] The Hello message management module 101 is used to obtain and save the LDP Hello message sent by the neighboring device connected to the target mimicking device; distribute the LDP Hello message to all online target executors of the target executor so that the target executor discovers and maintains the neighboring device based on the LDP Hello message;

[0105] A TCP link state management module 102, used to obtain a TCP link state management message, and manage the TCP link between the target execution body and the neighbor device based on the TCP link state management message;

[0106] An LDP session establishment and maintenance management module 103, used to obtain an LDP session management message, and manage the LDP session between the target execution body and the neighbor device based on the LDP session management message;

[0107] A neighbor address cache distribution management module 104, used to obtain a neighbor address management message and manage the neighbor address information in the target executable body based on the neighbor address management message;

[0108] The FEC label cache distribution management module 105 is used to obtain label management information and synchronize labels between the target execution body and the neighboring device based on the label management information.

[0109] A label synchronization system provided in an embodiment of the present application is applied to a target mimicking device, wherein a TCP link state management message includes a link establishment or link teardown message;

[0110] The TCP link state management module is specifically used for: if a TCP link state management message sent by a neighboring device is monitored, the TCP link state management message is cached; the TCP link state between the main execution body and the neighboring device in the target execution body is obtained, and the TCP link between the slave execution body and the neighboring device in the target execution body is managed based on the TCP link state and the TCP link state management message; if a TCP link state management message sent by the main execution body is monitored, the TCP link between the target execution body and the neighboring device is managed based on the TCP link state management message; if a TCP link state management message sent by any slave execution body is monitored, it is determined whether the link between the neighboring device and the main execution body is established. If so, the TCP link between any slave execution body and the neighboring device is managed based on the TCP link state management message; if not, the TCP link state management message is discarded.

[0111] A label synchronization system provided in an embodiment of the present application is applied to a target mimic device, and the message types in the LDP session management message include an Initialization message and a keepalive message;

[0112] The LDP session establishment and maintenance management module is specifically used for: when the target mimicking device is the passive party in establishing the LDP session: if the Initialization message and / or keepalive message sent by the neighboring device is monitored, the Initialization message and / or keepalive message is cached, and the Initialization message and / or keepalive message is sent to the target executor that completes the TCP link establishment; if the SYN+ACK message sent by any executor in the target executor is monitored, a corresponding ACK message is sent to the any executor, and the cached Initialization message of the neighboring device is sent to the any executor; if the Initialization+keepalive message sent by any executor is monitored, a corresponding ACK message is sent to the any executor, and the cached keepalive message of the neighboring device is sent to the any executor.

[0113] A label synchronization system provided in an embodiment of the present application is applied to a target mimic device, and the message types in the LDP session management message include an Initialization message and a keepalive message;

[0114] The LDP session establishment and maintenance management module is specifically used for: when the target mimicking device is the active party in establishing the LDP session: if the Initialization+keepalive message sent by the neighboring device is monitored, the Initialization+keepalive message is cached, and the Initialization+keepalive message is sent to the target executor that completes the TCP link establishment; if the Initialization message sent by any executor in the target executor is monitored, a corresponding ACK message is sent to the any executor, and the cached Initialization+keepalive message of the neighboring device is sent to the any executor; if the keepalive message sent by any executor is monitored, a corresponding ACK message is sent to the any executor.

[0115] A label synchronization system provided by an embodiment of the present application is applied to a target mimicking device, and the neighbor address cache distribution management module is specifically used to: if an Address Message message sent by a neighbor device is monitored, then the neighbor class is obtained based on the srcIp, dstIp, and routeId in the AddressMessage message, and all Addresses in the Address Message message are added to the address hash table corresponding to the neighbor class; if an AddressWithdraw Message message sent by a neighbor device is monitored, then all cached Addresses are queried based on the neighbor class, and in the address hash table corresponding to the neighbor class, all Addresses that are the same as the Address in the Address Message message are deleted; if a neighbor address management message sent by a target executor that successfully establishes an LDP session is monitored, then an Address Message message is created based on the address information locally cached by the target mimicking device and sent to the target executor.

[0116] A label synchronization system provided by an embodiment of the present application is applied to a target mimicking device, and an FEC label cache distribution management module is specifically used for: if a Label Mapping Message message sent by a neighbor device is monitored, then the neighbor class is queried based on the srcIp, dstIp, and routeId in the LabelMapping Message message, all first FEC / Label mappings of this neighbor device are obtained according to the neighbor query cache dictionary, and the second FEC / Label mapping in the Label MappingMessage message is obtained cyclically. If the FEC in the second FEC / Label mapping already exists in the first FEC / Label mapping, the first FEC / Label mapping is updated based on the second FEC / Label mapping. If the FEC in the second FEC / Label mapping does not exist in the first FEC / Label mapping, the second FEC / Label mapping is added to the first FEC / Label mapping, and the first FEC / Label mapping is transparently transmitted to the online target executor; if a LabelWithdraw Message message sent by a neighbor device is monitored, the Label Withdraw The srcIp, dstIp, and routeId in the Message are queried to obtain the neighbor class, and all the first FEC / Label mappings of this neighbor are obtained according to the neighbor query cache dictionary. The second FEC / Label mapping in the Label Withdraw Message is obtained in a loop. If the FEC in the second FEC / Label mapping already exists in the first FEC / Label mapping, the second FEC / Label mapping in the first FEC / Label mapping is deleted, and the first FEC / Label mapping is transparently transmitted to the online target executor; if the Label Release Message, Label Request Message, or Label Abort RequestMessage sent by the neighbor device is monitored, it is directly discarded.

[0117] A label synchronization system provided by an embodiment of the present application is applied to a target mimicking device, wherein the FEC label cache distribution management module is specifically used for, if a Label Mapping Message message sent by any executor in the target executor is monitored and FEC / Label mapping information has not been sent to any executor, then the neighbor class is obtained according to the srcIp, dstIp, and routeId in the Label Mapping Message message, all FEC / Label mappings of the neighbor device are obtained according to the neighbor query cache dictionary, and a new Label Mapping Message message is constructed according to all FEC / Label mappings and sent to any executor; if a Label Mapping Message message sent by any executor is monitored and FEC / Label mapping information has been sent to any executor, the Label Mapping Message message is directly discarded; if a Label Withdraw Message message sent by any executor is monitored, a Label Release Message message corresponding to the Label Withdraw Message message is created and sent to any executor; if a Label Request Message message and a Label Abort Request message sent by any executor are monitored Message message is forwarded to the neighboring device.

[0118] The present application also provides a tag synchronization device and a computer-readable storage medium, both of which have the corresponding effects of a tag synchronization method provided in an embodiment of the present application. Fig.14 , Fig.14 A structural diagram of a tag synchronization device provided in an embodiment of the present application.

[0119] A tag synchronization device provided in an embodiment of the present application includes a memory 201 and a processor 202. The memory 201 stores a computer program. When the processor 202 executes the computer program, the steps of the tag synchronization method described in any of the above embodiments are implemented.

[0120] See also Fig.15, another tag synchronization device provided in the embodiment of the present application may also include: an input port 203 connected to the processor 202, used to transmit commands input from the outside to the processor 202; a display unit 204 connected to the processor 202, used to display the processing results of the processor 202 to the outside; a communication module 205 connected to the processor 202, used to realize the communication between the tag synchronization device and the outside. The display unit 204 can be a display panel, a laser scanning display, etc.; the communication mode adopted by the communication module 205 includes but is not limited to mobile high-definition link technology (HML), universal serial bus (USB), high-definition multimedia interface (HDMI), wireless connection: wireless fidelity technology (WiFi), Bluetooth communication technology, low-power Bluetooth communication technology, and communication technology based on IEEE802.11s.

[0121] An embodiment of the present application provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the steps of the tag synchronization method described in any of the above embodiments are implemented.

[0122] The computer-readable storage medium involved in the present application includes random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the technical field.

[0123] For the description of the relevant parts of the tag synchronization system, device and computer-readable storage medium provided in the embodiments of the present application, please refer to the detailed description of the corresponding parts in the tag synchronization method provided in the embodiments of the present application, which will not be repeated here. In addition, the parts of the above technical solutions provided in the embodiments of the present application that are consistent with the corresponding technical solutions in the prior art are not described in detail to avoid excessive elaboration.

[0124] It should also be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0125] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A tag synchronization method, characterized in that: Applied to target mimic devices, including: Obtain and save an LDP Hello message sent by a neighboring device connected to the target mimic device; Distribute the LDP Hello message to all online target executors of the target executor, so that the target executor discovers and maintains the neighbor device based on the LDP Hello message; Obtaining a TCP link state management message, and managing the TCP link between the target execution body and the neighbor device based on the TCP link state management message; Obtaining an LDP session management message, and managing an LDP session between the target execution entity and the neighbor device based on the LDP session management message; Obtaining a neighbor address management message, and managing the neighbor address information in the target executable body based on the neighbor address management message; The tag management information is acquired, and the tags between the target execution body and the neighbor device are synchronized based on the tag management information, so that the tags between the target execution bodies are synchronized.

2. The method according to claim 1, characterized in that The TCP link state management message includes a link establishment or link teardown message; The obtaining of the TCP link state management message, and managing the TCP link between the target execution body and the neighbor device based on the TCP link state management message, includes: If the TCP link state management message sent by the neighboring device is monitored, the TCP link state management message is cached; the TCP link state between the main execution body in the target execution body and the neighboring device is obtained, and the TCP link between the slave execution body in the target execution body and the neighboring device is managed based on the TCP link state and the TCP link state management message; If the TCP link state management message sent by the main execution body is monitored, the TCP link between the target execution body and the neighbor device is managed based on the TCP link state management message; If the TCP link state management message sent by any of the slave execution bodies is monitored, it is determined whether the link establishment between the neighboring device and the main execution body is completed. If so, the TCP link between any of the slave execution bodies and the neighboring device is managed based on the TCP link state management message; if not, the TCP link state management message is discarded.

3. The method according to claim 1, characterized in that The message types in the LDP session management message include Initialization message and keepalive message; The obtaining of the LDP session management message, and managing the LDP session between the target execution body and the neighbor device based on the LDP session management message, includes: When the target mimic device is the passive party establishing the LDP session: If the Initialization message and / or the keepalive message sent by the neighboring device is monitored, the Initialization message and / or the keepalive message is cached, and the Initialization message and / or the keepalive message is sent to the target execution body that completes the TCP link establishment; If a SYN+ACK message sent by any of the target execution bodies is monitored, a corresponding ACK message is sent to the any execution body, and the cached Initialization message of the neighbor device is sent to the any execution body; If the Initialization+keepalive message sent by any of the execution bodies is monitored, a corresponding ACK message is sent to the any of the execution bodies, and the cached keepalive message of the neighbor device is sent to the any of the execution bodies.

4. The method according to claim 1, characterized in that The message types in the LDP session management message include Initialization message and keepalive message; The obtaining of the LDP session management message, and managing the LDP session between the target execution body and the neighbor device based on the LDP session management message, includes: When the target mimic device is the active party in establishing the LDP session: If an Initialization+keepalive message sent by the neighboring device is monitored, the Initialization+keepalive message is cached, and the Initialization+keepalive message is sent to the target execution body that completes the TCP link establishment; If the Initialization message sent by any of the target execution bodies is monitored, a corresponding ACK message is sent to the any execution body, and the cached Initialization+keepalive message of the neighboring device is sent to the any execution body; If the keepalive message sent by any of the execution bodies is monitored, a corresponding ACK message is sent to the any of the execution bodies.

5. The method according to claim 1, characterized in that: The obtaining of the neighbor address management message and managing the neighbor address information in the target executable body based on the neighbor address management message includes: If an Address Message message sent by the neighbor device is monitored, the neighbor class is obtained based on the srcIp, dstIp, and routeId in the Address Message message, and all Addresses in the Address Message message are added to the address hash table corresponding to the neighbor class; If an Address Withdraw Message message sent by the neighbor device is monitored, all cached Addresses are queried based on the neighbor class, and all Addresses that are the same as the Address in the Address Message message are deleted from the address hash table corresponding to the neighbor class; If the neighbor address management message sent by the target executor that successfully establishes the LDP session is monitored, an Address Message message is created based on the address information locally cached by the target mimic device and sent to the target executor.

6. The method according to claim 1, characterized in that The acquiring of the tag management information and synchronizing the tag between the target execution body and the neighbor device based on the tag management information includes: If the Label Mapping Message message sent by the neighbor device is monitored, the neighbor class is queried based on the srcIp, dstIp, and routeId in the LabelMapping Message message, all first FEC / Label mappings of the neighbor device are obtained according to the neighbor query cache dictionary, and the second FEC / Label mapping in the Label MappingMessage message is cyclically obtained. If the FEC in the second FEC / Label mapping already exists in the first FEC / Label mapping, the first FEC / Label mapping is updated based on the second FEC / Label mapping. If the FEC in the second FEC / Label mapping does not exist in the first FEC / Label mapping, the second FEC / Label mapping is added to the first FEC / Label mapping, and the first FEC / Label mapping is transparently transmitted to the online target execution body; If the Label Withdraw Message message sent by the neighbor device is monitored, the neighbor class is obtained by querying the srcIp, dstIp, and routeId in the LabelWithdraw Message message, all first FEC / Label mappings of this neighbor are obtained according to the neighbor query cache dictionary, and the second FEC / Label mapping in the LabelWithdraw Message message is obtained cyclically. If the FEC in the second FEC / Label mapping already exists in the first FEC / Label mapping, the second FEC / Label mapping in the first FEC / Label mapping is deleted, and the first FEC / Label mapping is transparently transmitted to the online target execution body; If a Label Release Message, a Label Request Message or a Label Abort Request Message sent by the neighboring device is monitored, it is directly discarded.

7. The method according to claim 1, characterized in that The acquiring of the tag management information and synchronizing the tag between the target execution body and the neighbor device based on the tag management information includes: If a Label Mapping Message message sent by any of the target executable bodies is monitored, and FEC / Label mapping information has not been sent to any of the target executable bodies, the neighbor class is queried according to srcIp, dstIp, and routeId in the Label Mapping Message message, all FEC / Label mappings of the neighbor device are obtained according to the neighbor query cache dictionary, and a new Label MappingMessage message is constructed according to all the FEC / Label mappings and sent to any of the target executable bodies; If a Label Mapping Message sent by any executor is monitored and the FEC / Label mapping information has been sent to any executor, the Label Mapping Message is directly discarded; If a Label Withdraw Message message sent by any executable body is monitored, a Label Release Message message corresponding to the Label Withdraw Message message is created and sent to the any executable body; If a Label Request Message and a Label Abort Request Message sent by any executor is monitored, they are forwarded to the neighbor device.

8. A label synchronization system, characterized in that: Applied to target mimic devices, including: A Hello message management module is used to obtain and save LDP Hello messages sent by neighboring devices connected to the target mimicking device; distribute the LDP Hello messages to all online target executors of the target executors, so that the target executors discover and maintain the neighboring devices based on the LDP Hello messages; A TCP link state management module, used to obtain a TCP link state management message, and manage the TCP link between the target execution body and the neighbor device based on the TCP link state management message; An LDP session establishment and maintenance management module, used to obtain an LDP session management message, and manage the LDP session between the target execution body and the neighbor device based on the LDP session management message; A neighbor address cache distribution management module, used to obtain a neighbor address management message, and manage the neighbor address information in the target executable body based on the neighbor address management message; The FEC label cache distribution management module is used to obtain label management information and synchronize the labels between the target execution body and the neighbor device based on the label management information, so as to synchronize the labels between the target execution bodies.

9. A tag synchronization device, characterized in that: Applied to target mimic devices, including: Memory for storing computer programs; A processor, configured to implement the steps of the tag synchronization method according to any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the tag synchronization method according to any one of claims 1 to 7 are implemented.

Images