Information synchronization method and device

Abstract

Provided is an information synchronization method, comprising: a first communication device sending a first FlexE OH frame to a second communication device through a first FlexE interface, the first FlexE OH frame being used for announcing first information, the first information being used for indicating the capability of the first FlexE interface, the capability of the first FlexE interface at least comprising a time slot granularity supported by the first FlexE interface. The second communication device may send a second FlexE OH frame to the first communication device over a second FlexE interface, the second FlexE OH frame to advertise second information, the second information to indicate a capability of the second FlexE interface, the capability of the second FlexE interface, which may at least include a slot granularity supported by the second FlexE interface. According to the scheme, the efficiency of synchronizing the capability of the FlexE interface can be effectively improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of communication, and in particular to an information synchronization method and device. BACKGROUND

[0002] With the development of network technology, there is a contradiction between the growth of Ethernet interface rate and the growth of service traffic bandwidth. For example, the network interface rate grows from 10 gigabit Ethernet (GB) to 40 GE and 100 GE, etc. While the network traffic bandwidth grows from 100 GE to 400 GE or even terabit Ethernet (TE), etc.

[0003] In order to solve the above contradiction, the optical internetworking forum (OIF) flexible Ethernet (FlexE) standard technology creates an adaptation layer between the media access control (MAC) layer and the physical coding sublayer (PCS), that is, the FLexE shim layer. Through the FLexE shim layer, FLexE channelization can be realized, and greater transmission performance of the device can be realized. Among them, the FLexE channelization can be understood as that multiple low-rate MAC data streams can share one or multiple physical layers (PHY).

[0004] If two communication devices need to communicate by using the FlexE standard technology, the communication devices need to synchronize the FlexE related capabilities. At present, the efficiency of synchronizing the foregoing capabilities between the communication devices is relatively low. Therefore, there is an urgent need for a solution to solve the above problem. SUMMARY

[0005] The present application provides an information synchronization method and device, which can efficiently synchronize the capabilities of the FlexE interface between the communication devices.

[0006] In a first aspect, the present application provides a method for synchronizing information, which can be applied to a first communication device, the first communication device comprising a first FlexE interface. The first communication device sends a first FlexE overhead (OH) frame to a second communication device through the first FlexE interface, the first FlexE OH frame being used to announce first information, the first information being used to indicate a capability of the first FlexE interface, wherein the capability of the first FlexE interface at least comprises a time slot granularity supported by the first FlexE interface. The second communication device comprises a second FlexE interface. The second communication device can send a second FlexE OH frame to the first communication device through the second FlexE interface, the second FlexE OH frame being used to announce second information, the second information being used to indicate a capability of the second FlexE interface, the capability of the second FlexE interface at least comprising a time slot granularity supported by the second FlexE interface. That is, the first communication device can determine the capability of the second FlexE interface by receiving the second FlexE OH frame. As can be seen, the first communication device and the second communication device can announce the capability of their FlexE interfaces to the opposite end through the manner of sending FlexE OH frames to each other, so as to realize the synchronization of the capability of the FlexE interfaces. Through the manner of sending FlexE OH frames to synchronize the capability of the FlexE interfaces, the present application does not need to rely on a layer 3 (L3) protocol, and thus, the synchronization of the capability of the FlexE interfaces can be realized without waiting for the traffic flow between the first communication device and the second communication device, so as to effectively improve the efficiency of synchronizing the capability of the FlexE interfaces.

[0007] In a possible implementation, the first information comprises first indication information, the first indication information being used to indicate the time slot granularity supported by the first FlexE interface. As a specific example, the time slot granularity supported by the first FlexE interface can be indicated according to a chip version corresponding to the first FlexE interface, and thus, the first indication information can be used to indicate the chip version corresponding to the first FlexE interface, and the time slot granularity supported by the first FlexE interface can be indicated by indicating the chip version corresponding to the first FlexE interface.

[0008] In a possible implementation, the capability of the first FlexE interface further includes a PHY rate supported by the first FlexE interface, and / or a PHY add / drop capability supported by the first FlexE interface. That is, the first communication device can announce the slot granularity supported by the first FlexE interface, and the PHY rate supported by the first FlexE interface, and / or the PHY add / drop capability supported by the first FlexE interface, to the second communication device by sending the first FlexE OH frame to the second communication device.

[0009] In a possible implementation, the capability of the second FlexE interface further includes a PHY rate supported by the second FlexE interface, and / or a PHY add / drop capability supported by the second FlexE interface. The second communication device can announce the slot granularity supported by the second FlexE interface, and the PHY rate supported by the second FlexE interface, and / or the PHY add / drop capability supported by the second FlexE interface, to the first communication device by sending the second FlexE OH frame to the first communication device.

[0010] In a possible implementation, the first information includes second indication information, and the second indication information indicates a PHY rate supported by the first FlexE interface. As a specific example, the PHY rate supported by the first FlexE interface can be indicated in consideration of an OIF FlexE protocol version supported by the first FlexE interface, and therefore, the second indication information can be used to indicate the at least one OIF FlexE protocol version supported by the first FlexE interface, and the PHY rate supported by the first FlexE interface is indicated in a manner of indicating the at least one OIF FlexE protocol version supported by the first FlexE interface.

[0011] In a possible implementation, the second information includes third indication information, and the third indication information indicates a PHY rate supported by the second FlexE interface. As a specific example, the PHY rate supported by the second FlexE interface can be indicated in consideration of an OIF FlexE protocol version supported by the second FlexE interface, and therefore, the third indication information can be used to indicate the at least one OIF FlexE protocol version supported by the second FlexE interface, and the PHY rate supported by the second FlexE interface is indicated in a manner of indicating the at least one OIF FlexE protocol version supported by the second FlexE interface.

[0012] In a possible implementation, the first FlexE OH frame comprises a field (referred to as a dedicated field) dedicated to announcing the first information. The dedicated field can be located in a reserved field of the first FlexE OH frame, for example. In this scenario, since the dedicated field is dedicated to announcing the first information, no vendor can use the dedicated field to transmit other custom information. Therefore, the information carried by the dedicated field is not the aforementioned custom information. Thus, in an example, the first communication device can send a first FlexE OH frame to the second communication device to announce the first information to the second communication device, thereby effectively improving the announcement efficiency of the first information and saving the performance overhead of announcing the first information.

[0013] In a possible implementation, the second FlexE OH frame comprises a field (referred to as a dedicated field) dedicated to announcing the second information. The dedicated field can be located in a reserved field of the second FlexE OH frame, for example. In this scenario, since the dedicated field is dedicated to announcing the second information, no vendor can use the dedicated field to transmit custom information. Therefore, the information carried by the dedicated field is not the aforementioned custom information. Thus, in an example, the second communication device can send a second FlexE OH frame to the first communication device to announce the second information to the first communication device, thereby effectively improving the announcement efficiency of the second information and saving the performance overhead of announcing the second information.

[0014] In a possible implementation, considering the available fields (e.g. reserved fields) in the FlexE OH frame, each vendor can use them flexibly as needed. In order to avoid the field used for announcing the first information being used by other vendors for other purposes, the first communication device can send M consecutive FlexE OH frames to the second communication device in a fixed order. M is an integer greater than or equal to 2. For the M consecutive FlexE OH frames, the code type used for announcing the first information in each FlexE OH frame is different. Since the code types used for announcing the first information in the multiple FlexE OH frames are different, the second communication device can check the aforementioned multiple code types used for announcing the first information to determine whether the FlexE OH frame received by the second communication device announces the first information. The M consecutive FlexE OH frames include a first FlexE OH frame. In an example, the first FlexE OH frame can be any one of the aforementioned M consecutive FlexE OH frames. Correspondingly, the first communication device can receive the M consecutive FlexE OH frames sent by the second communication device in a fixed order, and the M consecutive FlexE OH frames sent by the second communication device include the second FlexE OH frame, the code type used for announcing the second information in each FlexE OH frame is different, and M is a positive integer greater than or equal to 2.

[0015] In a possible implementation, in a case where the first information includes first indication information and second indication information, the value of M can be 4. That is, in a case where the first information includes first indication information and second indication information, the code type used for announcing the first information can include four code types.

[0016] In a possible implementation, the first information further includes state indication information, which is used to indicate that information synchronization is successful. The so-called information synchronization success can be understood as that the first communication device successfully announces the first information to the second communication device, and the first communication device also successfully locks the second information announced by the second communication device. In the aforementioned scenario where the first communication device announces the first information to the second communication device through multiple code types, the first information can include, for example, a state indication field, and the value of the state indication field is used to indicate whether the information synchronization is successful.

[0017] In a possible implementation, the first communication device can use a certain code type to notify the second communication device of the first information. In order to avoid the field used for notifying the first information being used by other manufacturers for other purposes, the first communication device can use multiple code types to respectively notify the second communication device of the first information, so that the second communication device can exclude the first information being custom information of other manufacturers based on the first information notified by the first communication device through the multiple code types, and thus correctly lock the first information. In this scenario, the first communication device can adjust the code type used for notifying the first information through the state of the local state machine. In a specific example, if the first communication device receives multiple FlexE OH frames sent by the second communication device, the multiple FlexE OH frames include the second FlexE OH frame, and the code types included in the multiple FlexE OH frames received by the first communication device are all the first code type, the first communication device can adjust the local state machine, for example, jump the state of the state machine from the current state to the next state. Further, according to the state of the adjusted local state machine, the code type used for notifying the first information is adjusted, so as to continue notifying the second communication device of the first information by using other code types different from the first code type.

[0018] In a second aspect, an embodiment of the present application provides an information synchronization device applied to a first communication device, the device comprising: a sending unit and a receiving unit. The sending unit is configured to send a first FlexE overhead (OH) frame to a second communication device through a first FlexE interface, the first FlexE OH frame being used for notifying first information, the first information being used for indicating a capability of the first FlexE interface, and the capability of the first FlexE interface comprising a time slot granularity supported by the first FlexE interface. The receiving unit is configured to receive a second FlexE OH frame sent by the second communication device through a second FlexE interface, the second FlexE OH frame being used for notifying second information, the second information being used for indicating a capability of the second FlexE interface, and the capability of the second FlexE interface comprising a time slot granularity supported by the second FlexE interface.

[0019] In a possible implementation, the first information comprises first indication information, the first indication information being used for indicating a chip version corresponding to the first FlexE interface, and the chip version being used for indicating the time slot granularity supported by the first FlexE interface.

[0020] In a possible implementation, the capability of the first FlexE interface further includes a PHY rate supported by the first FlexE interface, and / or a PHY add / drop capability supported by the first FlexE interface; and the capability of the second FlexE interface further includes a PHY rate supported by the second FlexE interface, and / or a PHY add / drop capability supported by the second FlexE interface.

[0021] In a possible implementation, the first information includes second indication information, the second indication information indicating at least one Optical Internetworking Forum (OIF) FlexE protocol version supported by the first FlexE interface, the at least one OIF FlexE protocol version supported by the first FlexE interface being used to indicate a PHY rate supported by the first FlexE interface; and the second information includes third indication information, the third indication information indicating at least one OIF FlexE protocol version supported by the second FlexE interface, the at least one OIF FlexE protocol version supported by the second FlexE interface being used to indicate a PHY rate supported by the second FlexE interface.

[0022] In a possible implementation, the first FlexE overhead (OH) frame includes a field specially used to announce the first information, and the second FlexE OH frame includes a field specially used to announce the second information.

[0023] In a possible implementation, the sending unit is configured to: send, to the second communication device, M consecutive FlexE OH frames in a fixed order, the M consecutive FlexE OH frames sent by the sending unit including the first FlexE OH frame, a code type used to announce the first information being different in each FlexE OH frame, and M being a positive integer greater than or equal to 2; and the receiving unit is configured to: receive M consecutive FlexE OH frames sent by the second communication device in a fixed order, the M consecutive FlexE OH frames received by the receiving unit including the second FlexE OH frame, a code type used to announce the second information being different in each FlexE OH frame, and M being a positive integer greater than or equal to 2.

[0024] In a possible implementation, M is equal to 4.

[0025] In a possible implementation, the first information includes state indication information, the state indication information being used to indicate that information synchronization is successful.

[0026] In a possible implementation, the apparatus further includes a processing unit; the receiving unit is configured to receive a plurality of FlexE OH frames, the plurality of FlexE OH frames including the second FlexE OH frame, and a code type used for announcing the second information in the second FlexE OH frame is a first code type; and the processing unit is configured to adjust a local state machine in response to the plurality of FlexE OH frames all including the first code type, and adjust the code type used for announcing the first information according to a state of the local state machine.

[0027] In a third aspect, an embodiment of the present application provides a communication apparatus, including a processor and a memory;

[0028] The memory is configured to store instructions, and the processor is configured to execute the instructions to enable the communication apparatus to perform the method in the first aspect and any one of the implementations of the first aspect.

[0029] In a fourth aspect, an embodiment of the present application provides a communication apparatus, including a communication interface and a processor connected to the communication interface, the communication interface is configured to perform the transceiving operation in the method in the first aspect and any one of the implementations of the first aspect, and the processor is configured to perform other operations in the method in the first aspect and any one of the implementations of the first aspect except the transceiving operation.

[0030] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium, including instructions or a computer program, when the instructions or the computer program are executed on a processor, the method in the first aspect and any one of the implementations of the first aspect is implemented.

[0031] In a sixth aspect, an embodiment of the present application provides a computer program product, including a computer program product, when the computer program product is executed on a processor, the method in the first aspect and any one of the implementations of the first aspect is implemented. BRIEF DESCRIPTION OF DRAWINGS

[0032] Figure 1a An architecture diagram of a FlexE technology corresponding to a sending end;

[0033] Figure 1b An architecture diagram of a FlexE technology corresponding to a receiving end;

[0034] Figure 2 An exemplary application scenario diagram provided by an embodiment of the present application;

[0035] Figure 3 A flow diagram of an information synchronization method provided by an embodiment of the present application;

[0036] Figure 4 A diagram of an information synchronization method provided by an embodiment of the present application;

[0037] Figure 5 A state machine diagram provided for an embodiment of the present application;

[0038] Figure 6 A schematic diagram of another information synchronization method provided for an embodiment of the present application;

[0039] Figure 7 A structural schematic diagram of an information synchronization apparatus provided for an embodiment of the present application;

[0040] Figure 8 A structural schematic diagram of a communication apparatus provided for an embodiment of the present application;

[0041] Figure 9 A structural schematic diagram of a communication device provided for an embodiment of the present application. DETAILED DESCRIPTION

[0042] The present application provides an information synchronization method and apparatus, which can improve the efficiency of the capability of synchronizing FlexE interfaces between communication apparatuses.

[0043] At present, the OIF FlexE standard defines a 50G / 100G / 200G / 400G interface framework, and different rates of FlexE clients are allocated N time slots in a time slot cycle period, and the time slot bandwidth of each time slot is different. As of now, there are certain differences in the supported PHY rates or time slot granularity of the OIF FlexE standard defined in different versions. For example:

[0044] The supported PHY rate of OIF-FLEXE-01.0 (hereinafter referred to as V1.0) only includes 100G, and the time slot granularity supported by V1.0 is 5G granularity.

[0045] The supported PHY rate of OIF-FLEXE-02.0 (hereinafter referred to as V2.0) includes 100G, 200G and 400G, and the time slot granularity supported by V2.0 includes 5G and 25G granularity.

[0046] The supported PHY rate of OIF-FLEXE-02.11 (hereinafter referred to as V2.1) includes 50G, 100G, 200G and 400G, and the time slot granularity supported by V2.1 includes 5G and 25G granularity.

[0047] Before introducing the scheme provided by the embodiments of the present application, the related technologies of FlexE are introduced first. FlexE group: each FlexE group is carried by one or more PHYs. Each PHY is independent in physics. The number of each PHY can be identified by a number between 1 and 254, and 0 and 255 are reserved numbers. The number of a PHY can correspond to an interface on a network device. The same PHY needs to be identified by the same number between adjacent two network devices. The number of each PHY does not have to be continuous. One PHY can be used to carry at least one client, and one client can be transmitted on at least one PHY. FlexE can support mapping and transmission of any multiple different FlexE clients on any group of PHYs, thereby realizing functions such as PHY bundling, channelization and sub-rate.

[0048] FlexE interface: a logical interface bound by one or more physical interfaces. The FlexE interface is used to transmit FlexE clients, and each FlexE interface can be divided into multiple time slots in the time domain.

[0049] FlexE client: corresponding to various user interfaces or bandwidths of a network. The FlexE client represents a client data stream that is transmitted on a FlexE group by specifying a time slot (one time slot or multiple time slots). A FlexE group can carry multiple FlexE clients, and one FlexE client can correspond to one to multiple user service data streams (also referred to as MAC clients). The FlexE client can be flexibly configured according to bandwidth requirements, and supports various rates of Ethernet media access control (MAC) data streams (such as 10G, 40G, n*25G data streams, or even non-standard rate data streams). For example, the data stream can be transmitted to the FlexE shim layer by means of 64B / 66B encoding. Each client sent by the same FlexE group is adapted according to the allocated time slot rate. Wherein: 64 / 66B means that the data block includes 66 bits, the first two bits of which are synchronization bits, and the last 64 bits are data bits. In the physical coding sublayer (PCS), the 64 / 66B encoded data can be extracted by the first two synchronization bits.

[0050] FlexE shim: an adaptation layer inserted between MAC layer and PCS, is the core architecture of FlexE technology based on time slot distribution mechanism. For the sending end, the main role of FlexE shim is to encapsulate data into pre-divided time slots. Then, according to the FlexE time slot table, the divided time slots are mapped to the PHY in the FlexE group for transmission. Each time slot is mapped to a PHY in the FlexE group. Taking 100GE PHY as an example, FlexE Shim layer can divide each 100GE PHY carrying FlexE Group into 20 slot data bearing channels, and each slot corresponds to a bandwidth of 5Gbps. After sending 1023*20Slot 64 / 66B data, a FlexE overhead (OH) is inserted, so as to inform the receiving end how to parse the received data.

[0051] For a better understanding of the present application, Figure 1a and Figure 1b may be referred to, Figure 1a which is a schematic diagram of the architecture of FlexE technology corresponding to the sending end. Figure 1b which is a schematic diagram of the architecture of FlexE technology corresponding to the receiving end. Figure 1a and Figure 1b correspond to the 100G interface framework shown in OIF-FLEXE V2.0.

[0052] As shown in Figure 1a , FlexE client a to FlexE client z come from MAC layer, and the rate of FlexE client is adapted to the rate of PHY through idle code stream addition and deletion. After the idle code stream addition and deletion, the FlexE client (i.e. 66B data block) is mapped to calender slot, and then FlexE OH frame is inserted. The data stream after inserting FlexE OH frame is distributed to one or more 100G PHY for transmission.

[0053] As shown in Figure 1b , FlexE shim extracts FlexE OH from each 100G FlexE instance. According to Flexe OH, the data of each FlexE client is extracted from calender slot, and further through idle code stream addition and deletion operation, the adaptation of PHY rate to MAC rate is realized, so as to obtain the data of each FlexE client to send to MAC layer.

[0054] For the structure of the FlexE OH frame, refer to the relevant description of FlexE in OIF, which is not described in detail here.

[0055] For the 200G interface framework and the 400G interface framework, the basic principle is basically the same as that of the 100G interface framework, and refer to the relevant description of OIF-FLEXE-02.0 or OIF-FLEXE-02.1, which is not repeated here. The two communication devices communicate with each other by using the FlexE standard technology, and need to synchronize the capabilities of the FlexE interface, so as to configure the FlexE interface according to the actual service scenario and the capabilities of the FlexE interface.

[0056] At present, the communication devices can synchronize the capabilities of the FlexE interface through the Link Layer Discovery Protocol (LLDP). The LLDP protocol is a three-layer protocol, and if the LLDP protocol is used to synchronize the capabilities of the FlexE interface, the service flow between the two communication devices needs to be waited for. Specifically, the LLDP channel between the two communication devices needs to be waited for to be opened after the initialization of the service port of the two communication devices is completed. The initialization of the service port takes a long time, so that the efficiency of synchronizing the above-mentioned capabilities between the communication devices is relatively low.

[0057] Moreover, after the capability synchronization is completed, the FlexE communication between the communication devices is established, and the above-mentioned service port needs to be destroyed, so as to further reconfigure the FlexE interface based on the capabilities of the FlexE interface, and the operation process is complex.

[0058] Therefore, the embodiments of the present application provide a method and device for synchronizing information, which can effectively improve the efficiency of synchronizing the capabilities of the FlexE interface.

[0059] Next, the scheme provided by the embodiments of the present application will be introduced in combination with the drawings.

[0060] Referring to Figure 2 , the figure is a schematic diagram of an exemplary application scenario provided by the embodiments of the present application. As Figure 2 shown, the communication device 1 includes a FlexE interface 1, the communication device 2 includes a FlexE interface 2, and the FlexE interface 1 and the FlexE interface 2 communicate with each other through the FlexE technology, wherein the FlexE interface 1 is a logical interface on the communication device 1, and the FlexE interface 2 is a logical interface on the communication device 2.

[0061] Referring to Figure 3 , the figure is a flowchart of a method for synchronizing information provided by the embodiments of the present application.

[0062] Figure 3The method 100 shown includes S101-S102.

[0063] Before introducing the method provided by the embodiments of the present application, it needs to be explained that the communication device (for example, the communication device 1, the communication device 2, the first communication device and the second communication device) mentioned in the embodiments of the present application can be a switch, a router and the like network equipment, or a part of components on the network equipment, for example, a single board, a line card on the network equipment, or a functional module on the network equipment, or a chip for implementing the method of the present application, which is not limited in the embodiments of the present application. The communication devices can be directly connected through an Ethernet cable or an optical cable, for example, but are not limited to.

[0064] S101: The first communication device sends a first FlexE OH frame to the second communication device through a first FlexE interface, the first FlexE OH frame is used to announce first information, and the first information is used to indicate the capability of the first FlexE interface, and the capability of the first FlexE interface includes the time slot granularity supported by the first FlexE interface.

[0065] In one example, the first communication device can correspond to the communication device 1 shown in the figure, for example. Figure 2 The second communication device can correspond to the communication device 2 shown in the figure. Figure 2 The first FlexE interface can correspond to the FlexE interface 1 shown in the figure. Figure 2 Correspondingly, the second communication device includes a second FlexE interface, and the second FlexE interface can correspond to the FlexE interface 2 shown in the figure. Figure 2

[0066] In the embodiments of the present application, the first communication device can send the first FlexE OH frame to the second communication device through the first FlexE interface to announce the first information to the second communication device. In one example, the first information is included in the first FlexE OH frame to achieve the purpose of announcing the first information to the second communication device. In another example, the first FlexE OH frame includes information capable of indicating the first information, and the second communication device can obtain the first information after receiving the aforementioned information indicating the first information.

[0067] The first information is used to indicate the capability of the first FlexE interface. Wherein, the capability of the first FlexE interface can be understood as the capability of the first FlexE interface related to the FlexE technology. In different scenarios, the capability of the first FlexE interface can have different expression ways, for example, in some scenarios, the capability of the first FlexE interface can be the FlexE version information supported by the first FlexE interface. ​

[0068] In one example, the first information can be the capability of the first FlexE interface itself. In yet another example, the first information can not be the capability of the first FlexE interface itself, but information capable of indicating the capability of the first FlexE interface, based on which the second communication device can determine the capability of the first FlexE interface.

[0069] Embodiments of the present application do not specifically limit the capability of the first FlexE interface, which can include at least one capability related to FlexE technology. In one specific example, the capability of the first FlexE interface can include the time slot granularity supported by the first FlexE interface.

[0070] In one example, the first information can include one or more time slot granularities supported by the first FlexE interface.

[0071] In yet another example, the first information can include first indication information used to indicate one or more time slot granularities supported by the first FlexE interface. As one specific example, the first indication information can include indication bits corresponding to various time slot granularities respectively, and the indication bits corresponding to one or more time slot granularities supported by the first FlexE interface are set. As yet another specific example, considering the chip version corresponding to the first FlexE interface, the time slot granularities supported by the first FlexE interface can be indicated, and therefore, the first indication information can be used to indicate the chip version corresponding to the first FlexE interface. For example, the first indication information can be the identification of the chip version corresponding to the first FlexE interface. As another example, the first indication information can be information (e.g. a certain number) capable of indicating the chip version corresponding to the first FlexE interface. The chip version corresponding to the first FlexE interface mentioned here can be the network processor (NP) version corresponding to the first communication device or the central processing unit (CPU) version corresponding to the first communication device.

[0072] In one example, the capability of the first FlexE interface can also include the PHY rate supported by the first FlexE interface.

[0073] In one specific example, the first information can include one or more PHY rates supported by the first FlexE interface.

[0074] In yet another specific example, the first information can include second indication information, which is used to indicate one or more PHY rates supported by the first FlexE interface. As an example, the second indication information can include indication bits corresponding to various PHY rates respectively, and indication bits corresponding to one or more PHY rates supported by the first FlexE interface are set. As yet another example, considering OIF FlexE protocol versions supported by the first FlexE interface, PHY rates supported by the first FlexE interface can be indicated, thus the second indication information can be used to indicate one or more OIF FlexE protocol versions supported by the first FlexE interface. For example, the second indication information can include identities of one or more OIF FlexE protocol versions supported by the first FlexE interface. As another example, the second indication information can be information (e.g. number) capable of indicating one or more OIF FlexE protocol versions supported by the first FlexE interface. In one specific example, if the second indication information indicates that the OIF FlexE protocol version supported by the first FlexE interface includes V1.0, it means that the second indication information indicates that the PHY rate supported by the first FlexE interface includes 100G. In yet another specific example, if the second indication information indicates that the OIF FlexE protocol version supported by the first FlexE interface includes V2.0, it means that the second indication information indicates that the PHY rate supported by the first FlexE interface includes 100G, 200G and 400G. In another specific example, if the second indication information indicates that the OIF FlexE protocol version supported by the first FlexE interface includes V2.1, it means that the second indication information indicates that the PHY rate supported by the first FlexE interface includes 50G, 100G, 200G and 400G.

[0075] In one example, since the OIF FlexE protocol version is also able to indicate the slot granularity, when the second indication information is used to indicate at least one OIF FlexE protocol version supported by the first FlexE interface, the second indication information is also able to indicate one or more slot granularities supported by the first FlexE interface. In one specific example, if the second indication information indicates that the OIF FlexE protocol version supported by the first FlexE interface includes V1.0, it means that the second indication information indicates that the slot granularity supported by the first FlexE interface includes 5G granularity. In another specific example, if the second indication information indicates that the OIF FlexE protocol version supported by the first FlexE interface includes V2.0 and / or V2.0, it means that the second indication information indicates that the slot granularity supported by the first FlexE interface includes 5G granularity and 25G granularity. In this scenario, the slot granularity indicated by the chip version corresponding to the first FlexE interface (corresponding to the first indication information) can be a subset of the slot granularity indicated by the second indication information.

[0076] For example:

[0077] If the OIF FlexE protocol version supported by the first FlexE interface includes V1.0, the slot granularity indicated by the second indication information includes 5G granularity. Correspondingly, the slot granularity indicated by the chip version corresponding to the first FlexE interface is also 5G granularity.

[0078] If the OIF FlexE protocol version supported by the first FlexE interface includes V2.0, the slot granularity indicated by the second indication information includes 5G and 25G granularities. Correspondingly, the chip corresponding to the first FlexE interface supports part or all of the slot granularities supported by the V2.1 version. That is, the slot granularity indicated by the chip version corresponding to the first FlexE interface is 5G granularity and / or 25G granularity. In other words, the chip corresponding to the first FlexE interface can only support 5G slot granularity or 25G slot granularity, or can support both 5G slot granularity and 25G slot granularity. For example, when the chip corresponding to the first FlexE interface supports 5G slot granularity but does not support 25G slot granularity, the slot granularity indicated by the chip version corresponding to the first FlexE interface is 5G granularity. For another example, when the chip corresponding to the first FlexE interface supports 25G slot granularity but does not support 5G slot granularity, the slot granularity indicated by the chip version corresponding to the first FlexE interface is 25G granularity. For another example, when the chip corresponding to the first FlexE interface supports both 5G slot granularity and 25G slot granularity, the slot granularity indicated by the chip version corresponding to the first FlexE interface is 5G granularity and 25G granularity.

[0079] In a specific example, the first information can comprise fourth indication information indicating the PHY add / drop capability supported by the first FlexE interface. The fourth indication information can be used to indicate the PHY add / drop capability supported by the first FlexE interface. For example, the fourth indication information can comprise first sub-information and second sub-information. The first sub-information can be used to indicate the PHY add capability supported by the first FlexE interface. The second sub-information can be used to indicate the PHY drop capability supported by the first FlexE interface.

[0080] In a specific example, the first information can comprise fourth indication information indicating the PHY add / drop capability supported by the first FlexE interface. The fourth indication information can be used to indicate the PHY add / drop capability supported by the first FlexE interface. For example, the fourth indication information can comprise first sub-information and second sub-information. The first sub-information can be used to indicate the PHY add capability supported by the first FlexE interface. The second sub-information can be used to indicate the PHY drop capability supported by the first FlexE interface.

[0081] In another specific example, the PHY add / drop capability supported by the first FlexE interface can be determined according to the chip version corresponding to the first FlexE interface. Therefore, the fourth indication information can also be the first indication information used to indicate the chip version corresponding to the first FlexE interface. In this scenario, the first indication information can be used to indicate not only the slot granularity supported by the first FlexE interface, but also the PHY add / drop capability supported by the first FlexE interface.

[0082] The embodiments of the present application do not specifically limit the carrying position of the information for announcing the first information in the first FlexE OH frame. In one example, the available field in the FlexE OH frame, such as the reserved field, can be utilized to carry the information for announcing the first information. As a specific example, the current FlexE OH frame can be extended, and a certain available field in the FlexE OH frame is determined as a dedicated field for announcing the first information, for example, P bits in the reserved field in the FlexE OH frame are determined as the dedicated field for announcing the first information. In this scenario, the first FlexE OH frame can include the field (i.e., the dedicated field) dedicated for announcing the first information, which is used to announce the first information. As another specific example, part or all of the reserved field in the FlexE OH frame can also be utilized to announce the first information, in which case the part or all of the reserved field is not the field dedicated for announcing the first information, and different manufacturers can flexibly use the part or all of the reserved field according to their own needs.

[0083] S102: The first communication device receives a second FlexE OH frame sent by the second communication device through a second FlexE interface, the second FlexE OH frame is used to announce second information, and the second information is used to indicate the capability of the second FlexE interface, including the time slot granularity supported by the second FlexE interface.

[0084] In the embodiments of the present application, the second communication device can send a second FlexE OH frame to the first communication device through a second FlexE interface to announce second information to the first communication device. In other words, the first communication device can receive the second FlexE OH frame sent by the second communication device to obtain the second information. In one example, the second information can be included in the second FlexE OH frame to achieve the purpose of announcing the second information to the first communication device. In another example, the second FlexE OH frame can include information capable of indicating the second information, and the first communication device can obtain the second information after receiving the information indicating the second information.

[0085] The second information is used to indicate the capability of the second FlexE interface. The capability of the second FlexE interface can be understood as the capability related to the FlexE technology possessed by the second FlexE interface. In different scenarios, the capability of the second FlexE interface can have different expressions, for example, in some scenarios, the capability of the second FlexE interface can be the FlexE version information supported by the second FlexE interface.

[0086] In the embodiments of the present application, the second information is used to indicate the capability of the second FlexE interface. As to the capability of the second FlexE interface, reference can be made to the foregoing description of the capability of the first FlexE interface, which will not be repeated here. Correspondingly, as to the specific indication manner of the second information indicating the capability of the second FlexE interface, reference can also be made to the foregoing description of the first information indicating the capability of the first FlexE interface, which will not be repeated here.

[0087] As can be known from the foregoing description, by using the scheme provided in the embodiments of the present application, the first communication device and the second communication device can advertise the capability of their FlexE interfaces to the opposite end through the manner of transmitting FlexE OH frames to each other, thereby realizing the synchronization of the capability of the FlexE interfaces. By synchronizing the capability of the FlexE interfaces through the manner of transmitting FlexE OH frames, the LLDP protocol does not need to be relied on, and thus the synchronization of the capability of the FlexE interfaces can be realized without waiting for the traffic flow between the first communication device and the second communication device, thereby effectively improving the efficiency of synchronizing the capability of the FlexE interfaces.

[0088] Moreover, the present scheme does not use the LLDP protocol to synchronize the capability of the FlexE interfaces, and thus the initialization of the service port does not need to be completed, and correspondingly, the service port used to punch through the LLDP channel between the first communication device and the second communication device does not need to be further destroyed after the synchronization of the capability of the FlexE interfaces. The present scheme uses the FlexE OH frame to synchronize the capability of the FlexE interfaces, and after the synchronization of the capability of the FlexE interfaces, the configuration of the FlexE interfaces can be further performed based on the capability of the FlexE interfaces after the synchronization, thereby simplifying the operation process.

[0089] The information used to advertise the capability of the FlexE interface is uniformly encoded, for example, the IP version (for example, the version of the OIF protocol) and / or the product version (for example, the chip version, which can indicate the differentiated capability supported by the chip) of the chip are uniformly encoded, and are mutually advertised between devices through the FlexE OH frame. When the device is subjected to flashover or automatic protection switching (APS), based on the method of the prior art, it usually takes more than 1s to complete the synchronization of the interface capability, while based on the method provided in the present application, the information of the opposite end can be quickly identified in less than 1ms, the rapid connection is supported, and the range of service damage is effectively reduced. For example, when the opposite end is quickly identified to support the dynamic addition and deletion of PHY, the PHY is quickly deleted after the fault is sensed, thereby ensuring the service continuity.

[0090] In one example, the first communication device can send a first FlexE OH frame to the second communication device to announce the first information to the second communication device. For example, in the scenario that the first FlexE OH frame comprises the field dedicated to announce the first information, since the dedicated field is used to announce the first information, the dedicated field cannot be used by the vendors to transmit the custom information. Therefore, the information carried by the dedicated field is not the custom information, and thus in one example, the first communication device can send a first FlexE OH frame to the second communication device to announce the first information to the second communication device, so as to effectively improve the announcement efficiency of the first information and save the performance overhead of announcing the first information. Correspondingly, the second communication device can also send a second FlexE OH frame to the first communication device to announce the second information to the first communication device. For example, in the scenario that the second FlexE OH frame comprises the field dedicated to announce the second information, the second communication device can send a second FlexE OH frame to the first communication device to announce the second information to the first communication device.

[0091] In yet another example, considering that the vendors can flexibly use the available fields (e.g., the reserved field) in the FlexE OH frame as needed, in order to avoid the field used to announce the first information being used by other vendors for other purposes, the first communication device can send M consecutive FlexE OH frames to the second communication device in a fixed order. M is an integer greater than or equal to 2. In the embodiments of the present application, for the M consecutive FlexE OH frames, the code type used to announce the first information in each FlexE OH frame is different. Since the code types used to announce the first information in the multiple FlexE OH frames are different, the second communication device can check the multiple code types used to announce the first information to determine whether the FlexE OH frame received by the second communication device announces the first information. The M consecutive FlexE OH frames comprise a first FlexE OH frame. In one example, the first FlexE OH frame can be any one of the M consecutive FlexE OH frames.

[0092] The code type used to announce the first information is not limited in the embodiments of the present application.

[0093] In one specific example, in the case that the first information comprises the first indication information, the value of M can be 2. In this scenario, the code types for announcing the first information can comprise code type X and code type Y. Wherein, both code type X and code type Y comprise a field 1 for announcing the first indication information, wherein the value of the field 1 in code type X can be used to indicate the first indication information, and the value of the field 1 in code type Y can be used to indicate the first indication information after processing. For example, the value of the field 1 in code type Y can be used to indicate the first indication information after inversion.

[0094] In another specific example, in the case that the first information comprises the first indication information and the second indication information, the value of M can be 4. In this scenario, the code types for announcing the first information can comprise code type a, code type b, code type c and code type d. Wherein: code type a, code type b, code type c and code type d all comprise a field 1 for announcing the first indication information and a field 2 for announcing the second indication information. As a specific example, in code type a: the value of the field 1 can be used to indicate the first indication information, and the value of the field 2 can be used to indicate the second indication information; in code type b: the value of the field 1 can be used to indicate the first indication information, and the value of the field 2 can be used to indicate the second indication information after processing (e.g. inversion); in code type c: the value of the field 1 can be used to indicate the first indication information, and the value of the field 2 can be used to indicate the second indication information after processing (e.g. inversion); in code type d: the value of the field 1 can be used to indicate the first indication information, and the value of the field 2 can be used to indicate the second indication information after processing (e.g. inversion).

[0095] The embodiments of the present application do not specifically limit the order of the four code types in the four consecutive FlexE OH frames sent by the first communication device in the foregoing cycle. For example, the order of the four code types in the four consecutive FlexE OH frames sent by the first communication device in the foregoing cycle can be: code type a→code type b→code type c→code type d, i.e., the first communication device can continuously send four FlexE OH frames to the second communication device, the first FlexE OH frame of the four FlexE OH frames comprises code type a, the second FlexE OH frame of the four FlexE OH frames comprises code type b, the third FlexE OH frame of the four FlexE OH frames comprises code type c, and the last FlexE OH frame of the four FlexE OH frames comprises code type d.

[0096] For the specific implementation of the first communication device cyclically sending M consecutive FlexE OH frames to the second communication device in a fixed order, reference can be made to the description part of “Implementation Mode 1” below.

[0097] Correspondingly, to avoid the field used for announcing the second information being used by other vendors for other purposes, the second communication device can cyclically send M consecutive FlexE OH frames to the first communication device in a fixed order. M is an integer greater than or equal to 2. The specific implementation of the second communication device cyclically sending M consecutive FlexE OH frames to the first communication device in a fixed order can refer to the foregoing specific description of the first communication device cyclically sending M consecutive FlexE OH frames to the second communication device in a fixed order, which will not be repeated here.

[0098] In a possible implementation, S101, when specifically implemented, the first communication device can use a certain code type to announce the first information to the second communication device. As described above, considering the available fields (such as the reserved field) in the FlexE OH frame, each vendor can use them flexibly as needed. To avoid the field used for announcing the first information being used by other vendors for other purposes, the first communication device can use multiple code types to respectively announce the first information to the second communication device, so that the second communication device can exclude the first information being custom information of other vendors based on the first information announced by the first communication device through the multiple code types, thereby correctly locking the first information. In this scenario, the first communication device can adjust the code type used for announcing the first information through the state of a local state machine. When the state machine is in a certain state, the first communication device can continuously send the code type corresponding to the state to the second communication device to announce the first information to the second communication device. In one specific example, the code type used for announcing the first information in the foregoing first FlexE OH frame can be a first code type. That is, the first communication device can continuously send multiple FlexE OH frames to the second communication device, and the code type used for announcing the first information in the multiple FlexE OH frames is the first code type. The first code type mentioned here can be any one of the six code types a to d, code type X, and code type Y.

[0099] Similarly, the second communication device can also use multiple code types to announce the second information to the first communication device, so that the first communication device can exclude the second information as custom information of other manufacturers based on the second information announced by the second communication device through the multiple code types, so as to correctly lock the second information. In this scenario, the second communication device can adjust the code type used to announce the second information through the state of the local state machine. When the state machine is in a certain state, the second communication device can continuously send the code type corresponding to the state to the first communication device to announce the second information to the first communication device. In a specific example, the code type used to announce the second information in the foregoing second FlexE OH frame can be a first code type. That is, the second communication device can continuously send multiple FlexE OH frames to the first communication device, and the code type used to announce the second information in the multiple FlexE OH frames is the first code type.

[0100] In a specific example, if the first communication device receives multiple FlexE OH frames sent by the second communication device, the multiple FlexE OH frames include the second FlexE OH frame, and the code types included in the multiple FlexE OH frames received by the first communication device are all the first code type, the first communication device can adjust the local state machine, for example, jump the state of the state machine from the current state to the next state. Further, according to the state of the adjusted local state machine, the code type used to announce the first information is adjusted to continue to announce the first information to the second communication device using a code type different from the first code type.

[0101] Similarly, if the second communication device receives multiple FlexE OH frames sent by the first communication device, the multiple FlexE OH frames include the first FlexE OH frame, and the code types included in the multiple FlexE OH frames received by the second communication device are all the first code type, the second communication device can adjust the local state machine, for example, jump the state of the state machine from the current state to the next state. Further, according to the state of the adjusted local state machine, the code type used to announce the second information is adjusted to continue to announce the second information to the first communication device using a code type different from the first code type.

[0102] In one example, the first information further comprises state indication information, which is used to indicate that the information synchronization is successful. The information synchronization successful can be understood as that the first communication device successfully announces the first information to the second communication device, and the first communication device also successfully locks the second information announced by the second communication device. In the scenario that the first communication device announces the first information to the second communication device through multiple code types, the first information can comprise a state indication field, for example, the value of the state indication field is used to indicate whether the information synchronization is successful. In one specific example, if the first communication device receives the second information announced by the multiple second communication devices through the last code type, the state indication field in the first information announced by the first communication device to the second communication device through the last code type can be used to carry the state indication information indicating that the information synchronization is successful. Correspondingly, the first communication device does not comprise the state indication information in the first information announced to the second communication device through other code types except the last code type. Alternatively, if the first communication device does not receive the second information announced by the multiple second communication devices through the last code type, the first communication device also does not comprise the state indication information in the first information announced to the second communication device through the last code type.

[0103] Similarly, the second information further comprises state indication information, which is used to indicate that the information synchronization is successful. The information synchronization successful mentioned herein can be understood as that the second communication device successfully announces the second information to the first communication device, and the second communication device also successfully locks the first information announced by the first communication device. In the scenario that the second communication device announces the second information to the first communication device through multiple code types, the second information can comprise a state indication field, for example, the value of the state indication field is used to indicate whether the information synchronization is successful. In one specific example, if the second communication device receives the first information announced by the multiple first communication devices through the last code type, the state indication field in the second information announced by the second communication device to the first communication device through the last code type can be used to carry the state indication information indicating that the information synchronization is successful. Correspondingly, the second communication device does not comprise the state indication information in the second information announced to the first communication device through other code types except the last code type. Alternatively, if the second communication device does not receive the first information announced by the multiple first communication devices through the last code type, the second communication device also does not comprise the state indication information in the second information announced to the first communication device through the last code type.

[0104] The above describes the scheme provided by the embodiments of the present application, and next, several possible implementation manners for implementing the method 100 are described in combination with the drawings.

[0105] Implementation manner 1

[0106] See Figure 4 The figure is a schematic diagram of an information synchronization method provided in an embodiment of this application.

[0107] like Figure 4 As shown, communication device 1 can continuously send four FlexE OH frames to communication device 2. FlexE OH frame 1 is the first FlexE OH frame among these four FlexE OH frames, FlexE OH frame 2 is the second FlexE OH frame among these four FlexE OH frames, FlexE OH frame 3 is the third FlexE OH frame among these four FlexE OH frames, and FlexE OH frame 4 is the fourth FlexE OH frame among these four FlexE OH frames. The first FlexE OH frame mentioned in the above embodiment can be any one of FlexE OH frame 1, FlexE OH frame 2, FlexE OH frame 3, or FlexE OH frame 4.

[0108] Communication device 2 can continuously send four FlexE OH frames to communication device 1. FlexE OH frame 1' is the first FlexE OH frame among these four FlexE OH frames, FlexE OH frame 2' is the second FlexE OH frame among these four FlexE OH frames, FlexE OH frame 3' is the third FlexE OH frame among these four FlexE OH frames, and FlexE OH frame 4' is the fourth FlexE OH frame among these four FlexE OH frames. The second FlexE OH frame mentioned in the above embodiment can be any one of FlexE OH frame 1', FlexE OH frame 2', FlexE OH frame 3', or FlexE OH frame 4'.

[0109] In this embodiment, communication device 1 can correspond to the first communication device in the above embodiments, and communication device 2 can correspond to the second communication device in the above embodiments.

[0110] like Figure 4 As shown:

[0111] FlexE OH frame 1 includes code pattern a, which comprises two fields. The value of one field indicates the chip version (chip version 1) supported by the first FlexE interface, corresponding to the first indication information in the above embodiment. The value of the other field indicates the OIF FlexE protocol version (OIF FlexE version 1) supported by the first FlexE interface, corresponding to the second indication information in the above embodiment.

[0112] The code type b included in the FlexE OH frame 2 includes two fields, one of which indicates the chip version supported by the first FlexE interface. The value of the other field indicates the OIF FlexE protocol version supported by the first FlexE interface after being inverted.

[0113] The code type c included in the FlexE OH frame 3 includes two fields, one of which indicates the chip version supported by the first FlexE interface after being inverted. The value of the other field indicates the OIF FlexE protocol version supported by the first FlexE interface.

[0114] The code type d included in the FlexE OH frame 4 includes two fields, one of which indicates the chip version supported by the first FlexE interface after being inverted. The value of the other field indicates the OIF FlexE protocol version supported by the first FlexE interface after being inverted.

[0115] Figure 4 The four FlexE OH frames shown as the FlexE OH frame 1 to the FlexE OH frame 4 can be a group, and the communication device 1 can send multiple groups to the communication device 2 in a cycle. Figure 4 The FlexE OH frame shown.

[0116] The code type a included in the FlexE OH frame 1' includes two fields, one of which indicates the chip version (chip version 2) supported by the second FlexE interface, corresponding to the fifth indication information in the above embodiment. The value of the other field indicates the OIF FlexE protocol version (OIF FlexE version 2) supported by the second FlexE interface, corresponding to the third indication information in the above embodiment.

[0117] The code type b included in the FlexE OH frame 2 includes two fields, one of which indicates the chip version supported by the second FlexE interface. The value of the other field indicates the OIF FlexE protocol version supported by the second FlexE interface after being inverted.

[0118] The code type c included in the FlexE OH frame 3 includes two fields, one of which indicates the chip version supported by the second FlexE interface after being inverted. The value of the other field indicates the OIF FlexE protocol version supported by the second FlexE interface.

[0119] The code type d included in the FlexE OH frame 4 includes two fields, one of which indicates the chip version supported by the second FlexE interface after the value is inverted. The other field indicates the OIF FlexE protocol version supported by the second FlexE interface after the value is inverted.

[0120] Figure 4 The four FlexE OH frames shown as the FlexE OH frame 1' to the FlexE OH frame 4' can be a group, and the communication device 2 can send multiple groups to the communication device 1 in a cycle Figure 4 The FlexE OH frame shown.

[0121] It should be noted that the chip version 1 and the chip version 2 can be the same or different, and the embodiments of the present application do not make specific limitations. The OIF FlexE version 1 and the OIF FlexE version 2 can be the same or different, and the embodiments of the present application do not make specific limitations.

[0122] Implementation 2:

[0123] Referring to Figure 5 , which is a schematic diagram of a state machine provided by an embodiment of the present application. The local state machine maintained by the first communication device and the local state machine maintained by the second communication device can be as shown in Figure 5 .

[0124] The following describes the information synchronization process performed by the first communication device from the perspective of the first communication device, and the information synchronization process performed by the second communication device is basically the same as the process performed by the first communication device, the difference being that the first information announced by the first communication device is the first information, and the second information announced by the second communication device is the second information.

[0125] As shown in Figure 5 , for the first communication device, the initial state of the local state machine is the idle (IDLE) state.

[0126] When the first communication device detects that the physical layer link between the first communication device and the second communication device is locked, the local state machine jumps from the IDLE state to the first state. The physical layer link mentioned here can be a physical coding sublayer (PCS) lock. In one example, the first state can also be referred to as a physical layer link lock (PHY_LINKUP) state, and the PHY_LINKUP state indicates that the physical layer link between the first communication device and the second communication device is locked, and the information synchronization can be started.

[0127] The first communication device continuously sends FlexE OH frames to the second communication device in the first state of the local state machine, and each FlexE OH frame adopts the code type 1 to announce the first information to the second communication device. As shown in Figure 5 The code type 1 includes three parts (which can also be understood as three fields), the value of the first part is used to indicate the OIF FlexE protocol version supported by the first FlexE interface, the value of the second part is used to indicate the chip version supported by the first FlexE interface. The third part is used to indicate whether the information synchronization is successful. In the code type 1, the third part is an optional part. When the code type 1 includes the third part, the value of the third part in the code type 1 is used to indicate that the information synchronization has not been successful.

[0128] If the first communication device continuously receives the second information announced by the plurality of second communication devices through the code type 1 when the local state machine is in the first state, the local state machine jumps from the first state to a second state. In an example, the second state can also be referred to as a message receiving (MSG_RCV) state, and the MSG_RCV state is an intermediate link for the first communication device and the second communication device to mutually announce information. The first communication device continuously sends FlexE OH frames to the second communication device in the second state of the local state machine, and each FlexE OH frame adopts the code type 2 to announce the first information to the second communication device. As shown in Figure 5 The code type 2 includes three parts, the value of the first part is used to indicate the OIF FlexE protocol version supported by the first FlexE interface, and the value of the second part is used to indicate the chip version supported by the first FlexE interface after being inverted. The third part is used to indicate whether the information synchronization is successful. In the code type 2, the third part is an optional part. When the code type 2 includes the third part, the value of the third part in the code type 2 is used to indicate that the information synchronization has not been successful.

[0129] If the first communication device continuously receives the second information announced by the plurality of second communication devices through the code type 2 when the local state machine is in the second state, the local state machine jumps from the second state to a third state. In an example, the third state can also be referred to as a message change (MSG_CHG) state, and the MSG_CHG state is an intermediate link for the first communication device and the second communication device to mutually announce information.

[0130] The first communication device continuously sends FlexE OH frames to the second communication device in the third state of the local state machine, and each FlexE OH frame adopts the code type 3 to announce the first information to the second communication device. As shown in Figure 5As shown, the code type 3 includes three parts, the value of the first part is used to indicate the OIF FlexE protocol version supported by the first FlexE interface after being negated, the value of the second part is used to indicate the chip version supported by the first FlexE interface. The third part is used to indicate whether the information synchronization is successful. In the code type 3, the third part is an optional part. When the local state machine is in the third state, the value of the third part in the code type 3 is used to indicate that the information synchronization has not been successful.

[0131] If the first communication device continuously receives the second information announced by the plurality of second communication devices through the code type 3 when the local state machine is in the third state, the local state machine jumps from the third state to a fourth state. In an example, the fourth state can also be referred to as a device locking (LOCK_DV) state. The LOCK_DV state indicates that the first communication device successfully locks the second information announced by the opposite end device (corresponding to the second communication device), and the state indicates that the information synchronization is successful.

[0132] The first communication device continuously sends the FlexE OH frame to the second communication device when the local state machine is in the fourth state, and the code type 3 is used to announce the first information to the second communication device in each FlexE OH frame. When the local state machine is in the fourth state, the value of the third part in the code type 3 is used to indicate that the information synchronization is successful. That is, when the local state machine is in the fourth state, the first communication device has successfully announced the first information to the second communication device, and the first communication device has successfully locked the second information announced by the second communication device.

[0133] If the first communication device determines that the physical layer link between the first communication device and the second communication device is interrupted when the local state machine is in the fourth state, the local state machine jumps from the fourth state to a fifth state. In an example, the fourth state can also be referred to as a filtering (FILTER) state, which is used to determine whether the link interruption is temporary, and the subsequent information synchronization process is determined according to the determination result.

[0134] The first communication device continuously sends the FlexE OH frame to the second communication device when the local state machine is in the fifth state, and the code type 2 is used to announce the first information to the second communication device in each FlexE OH frame, and the time of the physical layer link interruption is timed.

[0135] If the timer used for timing is timed out, it indicates that the physical layer link interruption time is relatively long, at this time, the state of the first FlexE interface and the second FlexE interface can be changed, at this time, the state machine jumps from the fifth state to an idle state.

[0136] If the timer does not expire, it means that the physical layer link interruption time is short, at this time, the information synchronization process can be further performed, specifically, if the first communication device does not receive the second information announced by the second communication device using the code type 2, the state machine jumps from the fifth state to the first state. If the first communication device continuously receives the second information announced by the second communication device through the code type 2, the local state machine jumps from the fifth state to the sixth state. In an example, the sixth state can also be referred to as a FILTER_RCV state. FILTER_RCV is a link after a short interruption. A link is a link after a short interruption.

[0137] The first communication device continuously sends FlexE OH frames to the second communication device in the sixth state of the local state machine, and each FlexE OH frame uses code type 3 to announce the first information to the second communication device. When the local state machine is in the sixth state, the value of the third part in the code type 3 is used to indicate that the information synchronization has not been successful.

[0138] If the first communication device continuously receives the second information announced by the second communication device through the code type 3 when the local state machine is in the sixth state, the local state machine jumps from the sixth state to the fourth state.

[0139] If the first communication device does not receive the second information announced by the second communication device through the code type 3 when the local state machine is in the sixth state, the local state machine jumps from the sixth state to the seventh state. In an example, the seventh state can also be referred to as an UNKNOWN_DV state. UNKNOWN_DV is a link after a short interruption. A link is a link after a short interruption.

[0140] The first communication device continuously sends FlexE OH frames to the second communication device in the seventh state of the local state machine, and each FlexE OH frame uses code type 1 to announce the first information to the second communication device.

[0141] In addition, when the local state machine is in the seventh state, if the second information announced by the second communication device through the code type 1 is continuously received, the local state machine jumps from the seventh state to the first state. If the second information announced by the second communication device through the code type 1 is not received, the local state machine stays in the seventh state.

[0142] In addition, when the local state machine is in any one of the states other than the fourth state and the fifth state, if it is determined that the physical layer link between the first communication device and the second communication device is interrupted, the local state machine jumps from the current state to the IDLE state.

[0143] In Embodiment 2, the first FlexE OH frame mentioned in the above embodiments can be one of the FlexE OH frames sent by the first communication device to the second communication device in any one state.

[0144] Implementation manner 3:

[0145] Referring to Figure 6 , the figure is a schematic diagram of another information synchronization method provided by the embodiments of the present application.

[0146] As Figure 6 indicated, the communication device 1 can send a first FlexE OH frame to the communication device 2, and the first FlexE OH frame uses code type 1 to announce first information.

[0147] The communication device 2 can send a second FlexE OH frame to the communication device 1, and the second FlexE OH frame uses code type 1 to announce second information.

[0148] Among them, the communication device 1 can correspond to the first communication device in the above embodiments, and the communication device 2 can correspond to the second communication device in the above embodiments.

[0149] As Figure 6 indicated:

[0150] The first FlexE OH frame includes code type 1, and the code type 1 includes five fields. The first field is a magic head field, and the value of the magic head field can carry a preset numerical value, for example. The value of the second field indicates that the first FlexE interface supports OIF FlexE protocol version 1 (OIF FlexE version 1), which corresponds to the second indication information in the above embodiments. The value of the third field indicates OIF FlexE version 1 after being inverted. The fourth field indicates that the first FlexE interface supports chip version 1 (chip version 1), which corresponds to the first indication information in the above embodiments. The fifth field indicates the chip version 1 after being inverted.

[0151] The code type 1 included in the second FlexE OH frame includes five fields, the first field is a magic head field, a value of the magic head field can carry a preset value for example. A value of the second field indicates an OIF FlexE protocol version (OIF FlexE version 2) supported by the second FlexE interface, corresponding to the third indication information in the above embodiment. A value of the third field indicates the OIF FlexE version 2 after being inverted. The fourth field indicates a chip version (chip version 2) supported by the second FlexE interface, corresponding to the fifth indication information in the above embodiment. The fifth field indicates the chip version 2 after being inverted.

[0152] In one example, the communication apparatus 1 can continuously send a plurality of FlexE OH frames to the communication apparatus 2, each FlexE OH frame is used to announce the first information to the second communication apparatus by using the code type 1 as shown in FIG. 4. Figure 6

[0153] Correspondingly, the communication apparatus 2 can continuously send a plurality of FlexE OH frames to the communication apparatus 1, each FlexE OH frame is used to announce the second information to the first communication apparatus by using the code type 1 as shown in FIG. 5. Figure 6

[0154] In another example, after the communication apparatus 1 continuously receives a plurality of second information announced by the communication apparatus 2 through the code type 1, the communication apparatus 1 can also announce the first information to the communication apparatus 2 by using a code type 2. The code type 2 can be a code type obtained by exchanging positions of at least two fields in the code type 1 for example. For example, the structure of the code type 2 can be as shown in FIG. 6. Figure 6 Figure 6 The structure of the code type 2 is not repeated here.

[0155] Similarly, after the communication apparatus 2 continuously receives a plurality of first information announced by the communication apparatus 1 through the code type 1, the communication apparatus 2 can also announce the second information to the communication apparatus 1 by using the code type 2. The code type 2 can be a code type obtained by exchanging positions of at least two fields in the code type 1 for example, which is not repeated here.

[0156] Based on the information synchronization method provided in the above embodiments, the embodiments of the present application further provide an information synchronization apparatus for executing the information synchronization method 100 executed by the first communication apparatus provided in the above method embodiments. Next, the information synchronization apparatus is introduced in combination with the accompanying drawings.

[0157] Referring to Figure 7 , the figure is a structural schematic diagram of an information synchronization apparatus provided in the embodiments of the present application. Figure 7 ​​​The information synchronization apparatus 700 shown includes a sending unit 701 and a receiving unit 702. The sending unit 701 is configured to implement the sending operations in the information synchronization method 100 described above and / or various possible implementation manners of the implementation method 100. The receiving unit 702 is configured to implement the receiving operations in the information synchronization method 100 described above and / or various possible implementation manners of the implementation method 100. In one implementation, the information synchronization apparatus 700 can further include a processing unit 703, which is configured to implement other operations in addition to the sending and receiving operations in the information synchronization method 100 described above and / or various possible implementation manners of the implementation method 100. In one implementation, part or all of the operations performed by the sending unit 701, the receiving unit 702, and the processing unit 703 can be implemented by different circuits respectively. For example, a first circuit implements part or all of the operations performed by the sending unit 701, a second circuit implements part or all of the operations performed by the receiving unit 702, and a third circuit implements part or all of the operations performed by the processing unit 703.

[0158] For example,

[0159] The sending unit 701 is configured to send, to a second communication apparatus, a first FlexE overhead (OH) frame through a first flexible Ethernet (FlexE) interface, where the first FlexE OH frame is used to announce first information, and the first information is used to indicate a capability of the first FlexE interface, and the capability of the first FlexE interface includes a time slot granularity supported by the first FlexE interface.

[0160] The receiving unit 702 is configured to receive a second FlexE OH frame sent by the second communication apparatus through a second FlexE interface, where the second FlexE OH frame is used to announce second information, and the second information is used to indicate a capability of the second FlexE interface, and the capability of the second FlexE interface includes a time slot granularity supported by the second FlexE interface.

[0161] In one possible implementation manner, the first information includes first indication information, and the first indication information is used to indicate a chip version corresponding to the first FlexE interface, and the chip version is used to indicate the time slot granularity supported by the first FlexE interface.

[0162] In a possible implementation, the capability of the first FlexE interface further includes a PHY rate supported by the first FlexE interface, and / or a PHY add / drop capability supported by the first FlexE interface; and the capability of the second FlexE interface further includes a PHY rate supported by the second FlexE interface, and / or a PHY add / drop capability supported by the second FlexE interface.

[0163] In a possible implementation, the first information includes second indication information, the second indication information indicating at least one Optical Internetworking Forum (OIF) FlexE protocol version supported by the first FlexE interface, the at least one OIF FlexE protocol version supported by the first FlexE interface being used to indicate a PHY rate supported by the first FlexE interface; and the second information includes third indication information, the third indication information indicating at least one OIF FlexE protocol version supported by the second FlexE interface, the at least one OIF FlexE protocol version supported by the second FlexE interface being used to indicate a PHY rate supported by the second FlexE interface.

[0164] In a possible implementation, the first FlexE overhead (OH) frame includes a field dedicated to announcing the first information, and the second FlexE OH frame includes a field dedicated to announcing the second information.

[0165] In a possible implementation, the sending unit 701 is configured to: send, to the second communication apparatus, M consecutive FlexE OH frames in a fixed order, the M consecutive FlexE OH frames sent by the sending unit 701 including the first FlexE OH frame, a code type used to announce the first information being different in each FlexE OH frame, and M being a positive integer greater than or equal to 2; and the receiving unit 702 is configured to: receive M consecutive FlexE OH frames sent by the second communication apparatus in a fixed order, the M consecutive FlexE OH frames received by the receiving unit 702 including the second FlexE OH frame, a code type used to announce the second information being different in each FlexE OH frame, and M being a positive integer greater than or equal to 2.

[0166] In a possible implementation, M is equal to 4.

[0167] In a possible implementation, the first information includes state indication information, the state indication information being used to indicate that information synchronization is successful.

[0168] In one possible implementation, the apparatus further includes the processing unit 703; the receiving unit 702 is configured to: receive a plurality of FlexE OH frames, the plurality of FlexE OH frames including a second FlexE OH frame, wherein the code pattern used to announce the second information in the second FlexE OH frame is a first code pattern; the processing unit is configured to: adjust a local state machine in response to the plurality of FlexE OH frames all including the first code pattern; and adjust the code pattern used to announce the first information according to the state of the local state machine.

[0169] For details on the specific implementation of each unit of the information synchronization device 700, please refer to the description of the various possible implementations of method 100 and / or specific implementation of method 100 above, which will not be repeated here.

[0170] In addition, this application also provides a communication device 800, see [link to relevant documentation]. Figure 8 As shown, Figure 8 This is a schematic diagram of a communication device provided in an embodiment of this application. The communication device 800 includes a communication interface 801 and a processor 802 connected to the communication interface 801. The communication device 800 can be used to execute the method 100 in the above embodiments.

[0171] When the communication device 800 executes method 100, the communication interface 801 performs the receiving and / or transmitting operations in method 100. The processor 802 performs other operations in method 100 besides the receiving and / or transmitting operations. For example, the processor 802 generates a first FlexE OH frame, which announces first information indicating the capabilities of the first FlexE interface, including the time slot granularity supported by the first FlexE interface. The communication interface 801 then transmits the first FlexE OH frame to a second communication device via the first FlexE interface.

[0172] In addition, this application also provides a communication device 900, see [link to relevant documentation]. Figure 9 As shown, Figure 9 This is a schematic diagram of a communication device provided in an embodiment of this application. The communication device 900 can be used to execute the method 100 in the above embodiments.

[0173] like Figure 9 As shown, the communication device 900 may include a processor 910, a communication interface 920, and a memory 930 coupled to the processor 910.

[0174] The processor mentioned in the present application can be one or more processors. When the processor is multiple, the types of the processors can be the same or different. The processor can be, for example, a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP. The processor can also be one or more processing circuits. The processor can also be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0175] The memory 930 mentioned in the present application can include a volatile memory such as a random-access memory (RAM); the memory can also include a non-volatile memory such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD), or a solid-state drive (SSD); the memory 930 can also include a combination of the above-mentioned types of memories. The memory 930 can refer to one memory or can include multiple memories. In an embodiment, the memory 930 stores computer-readable instructions including a plurality of software modules, such as a sending module 931, a processing module 932, and a receiving module 933. The processor 910 executes each software module and performs corresponding operations according to the instructions of each software module. In the present embodiment, the operation performed by a software module actually refers to the operation performed by the processor 910 according to the instructions of the software module.

[0176] When the communication device 900 is configured to perform the above method 100, the communication interface 920 is configured to perform the receiving and / or transmitting operations in the method 100. The processor 910 is configured to perform the operations in the method 100 other than the receiving and / or transmitting operations. For example, the processor 910 is configured to generate a first FlexE OH frame, the first FlexE OH frame being configured to announce first information, the first information being configured to indicate a capability of the first FlexE interface, the capability of the first FlexE interface including a time slot granularity supported by the first FlexE interface. The communication interface 920 is configured to transmit the first FlexE OH frame to a second communication device through the first FlexE interface.

[0177] The present application also provides a computer readable storage medium, having stored therein instructions or a computer program, which when executed on a processor, can implement any one or more operations of the method (e.g., the method 100) described in the foregoing embodiments.

[0178] The present application also provides a computer program product, comprising a computer program, which when executed on a processor, can implement any one or more operations of the method (e.g., the method 100) described in the foregoing embodiments.

[0179] The terms "first", "second", "third", "fourth" etc. (if any) in the description and claims of the present application and above drawings are used to distinguish similar objects, and do not necessarily have to be used to describe a specific order or sequence. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device that includes a series of steps or units does not have to be limited to only those steps or units clearly listed, but can include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0180] It can be clearly understood by those skilled in the art that, for the convenience and brevity of description, the specific working processes of the above-described system, device and unit can refer to the corresponding processes in the foregoing method embodiments, which will not be described here.

[0181] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other manners. For example, the division of the above-described device embodiments is merely a logical division, and there can be another division manner in actual implementation. For example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections between different units, can be indirect couplings or communication connections through some interfaces, devices or units, and can be in electrical, mechanical or other forms.

[0182] The units described as separated components can or can not be physically separated, and the components displayed as units can or can not be physical units, i.e., can be located in one place, or can be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purposes of the embodiments of the present application.

[0183] In addition, each service unit in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present alone, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software service unit.

[0184] If the integrated unit is realized in the form of a software service unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the present application, the essential part or contribution to the prior art, or all or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium, and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and various program code storage media.

[0185] Those skilled in the art should understand that, in one or more examples described above, the described services of the present application can be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the services can be stored in or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.

[0186] The above detailed description sets forth the purposes, technical solutions, and beneficial effects of the present application. It should be understood that the above is merely a specific implementation of the present application.

[0187] The above examples are merely used to illustrate the technical solutions of the present application, and are not intended to limit the present application; although the present application has been described in detail with reference to the foregoing examples, those skilled in the art should understand that the technical solutions recorded in the foregoing examples can still be modified, or some technical features can be replaced by equivalents; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. An information synchronization method, characterized in that, Applied to a first communication device, the method includes: A first FlexE overhead OH frame is sent to a second communication device through a first FlexE interface. The first FlexE OH frame is used to announce first information, which is used to indicate the capabilities of the first FlexE interface. The capabilities of the first FlexE interface include the time slot granularity supported by the first FlexE interface. The second communication device receives a second FlexE OH frame sent through the second FlexE interface. The second FlexE OH frame is used to announce second information, which is used to indicate the capabilities of the second FlexE interface, including the time slot granularity supported by the second FlexE interface.

2. The method according to claim 1, characterized in that, The first information includes first indication information, which is used to indicate the chip version corresponding to the first FlexE interface, and the chip version is used to indicate the time slot granularity supported by the first FlexE interface.

3. The method according to claim 1 or 2, characterized in that, The capabilities of the first FlexE interface also include: The PHY rate supported by the first FlexE interface, and / or the PHY addition / removal capability supported by the first FlexE interface; The capabilities of the second FlexE interface also include: The PHY rate supported by the second FlexE interface, and / or the PHY addition / removal capability supported by the second FlexE interface.

4. The method according to claim 3, characterized in that, The first information includes second indication information, which indicates at least one Optical Internet Forum (OIF) FlexE protocol version supported by the first FlexE interface. The at least one OIF FlexE protocol version supported by the first FlexE interface is used to indicate the PHY rate supported by the first FlexE interface. The second information includes third indication information, which indicates at least one OIF FlexE protocol version supported by the second FlexE interface, and the at least one OIF FlexE protocol version supported by the second FlexE interface is used to indicate the PHY rate supported by the second FlexE interface.

5. The method according to any one of claims 1-4, characterized in that, The first FlexE overhead OH frame includes a dedicated field for announcing the first information, and the second FlexE overhead OH frame includes a dedicated field for announcing the second information.

6. The method according to any one of claims 1-4, characterized in that, The first communication device sends M consecutive FlexE OH frames to the second communication device in a fixed order. The M consecutive FlexE OH frames sent by the first communication device include the first FlexE OH frame. Each FlexE OH frame has a different code pattern for announcing the first information. M is a positive integer greater than or equal to 2. The first communication device receives M consecutive FlexE OH frames sent cyclically by the second communication device in a fixed order. The M consecutive FlexE OH frames sent by the second communication device include the second FlexE OH frame. Each FlexE OH frame has a different code pattern used to announce the second information, and M is a positive integer greater than or equal to 2.

7. The method according to claim 6, characterized in that, M equals 4.

8. The method according to any one of claims 1-4, characterized in that, The first information includes status indication information, which is used to indicate that the information synchronization was successful.

9. The method according to claim 8, characterized in that, The method further includes: Receive multiple FlexE OH frames, the multiple FlexE OH frames including the second FlexE OH frame, wherein the code pattern used to announce the second information in the second FlexE OH frame is the first code pattern; In response to the fact that all of the plurality of FlexE OH frames include the first code pattern, the local state machine is adjusted; Adjust the code pattern used to announce the first information based on the state of the local state machine.

10. An information synchronization device, characterized in that, Applied to a first communication device, the device comprising: The transmitting unit is configured to transmit a first FlexE overhead OH frame to a second communication device through a first Flexible Ethernet (FlexE) interface. The first FlexE OH frame is used to announce first information, which is used to indicate the capabilities of the first FlexE interface. The capabilities of the first FlexE interface include the time slot granularity supported by the first FlexE interface. The receiving unit is configured to receive a second FlexE OH frame sent by the second communication device through the second FlexE interface. The second FlexE OH frame is used to announce second information, which is used to indicate the capabilities of the second FlexE interface. The capabilities of the second FlexE interface include the time slot granularity supported by the second FlexE interface.

11. The apparatus according to claim 10, characterized in that, The first information includes first indication information, which is used to indicate the chip version corresponding to the first FlexE interface, and the chip version is used to indicate the time slot granularity supported by the first FlexE interface.

12. The apparatus according to claim 10 or 11, characterized in that, The capabilities of the first FlexE interface also include: The PHY rate supported by the first FlexE interface, and / or the PHY addition / removal capability supported by the first FlexE interface; The capabilities of the second FlexE interface also include: The PHY rate supported by the second FlexE interface, and / or the PHY addition / removal capability supported by the second FlexE interface.

13. The apparatus according to claim 12, characterized in that, The first information includes second indication information, which indicates at least one Optical Internet Forum (OIF) FlexE protocol version supported by the first FlexE interface. The at least one OIF FlexE protocol version supported by the first FlexE interface is used to indicate the PHY rate supported by the first FlexE interface. The second information includes third indication information, which indicates at least one OIF FlexE protocol version supported by the second FlexE interface, and the at least one OIF FlexE protocol version supported by the second FlexE interface is used to indicate the PHY rate supported by the second FlexE interface.

14. The apparatus according to any one of claims 10-13, characterized in that, The first FlexE overhead OH frame includes a dedicated field for announcing the first information, and the second FlexE overhead OH frame includes a dedicated field for announcing the second information.

15. The apparatus according to any one of claims 10-13, characterized in that, The transmitting unit is used for: The transmitting unit cyclically sends M consecutive FlexE OH frames in a fixed order to the second communication device. The M consecutive FlexE OH frames sent by the transmitting unit include the first FlexE OH frame. Each FlexE OH frame has a different code pattern used to announce the first information. M is a positive integer greater than or equal to 2. The receiving unit is used for: The receiving unit receives M consecutive FlexE OH frames sent cyclically in a fixed order by the second communication device. The M consecutive FlexE OH frames received by the receiving unit include the second FlexE OH frame. Each FlexE OH frame has a different code pattern used to announce the second information, and M is a positive integer greater than or equal to 2.

16. The apparatus according to claim 15, characterized in that, M equals 4.

17. The apparatus according to any one of claims 10-13, characterized in that, The first information includes status indication information, which is used to indicate that the information synchronization was successful.

18. The apparatus according to claim 17, characterized in that, The device also includes a processing unit; The receiving unit is configured to: receive a plurality of FlexE OH frames, the plurality of FlexE OH frames including the second FlexE OH frame, wherein the code pattern used to announce the second information in the second FlexE OH frame is the first code pattern; The processing unit is configured to: adjust the local state machine in response to the fact that all of the plurality of FlexE OH frames include the first code pattern; and adjust the code pattern used to announce the first information according to the state of the local state machine.

19. An information synchronization device, characterized in that, include: Processor and memory; The memory is used to store instructions; The processor is configured to execute the instructions, causing the communication device to perform the method according to any one of claims 1-9.

20. A computer-readable storage medium, characterized in that, Includes instructions or computer programs that, when executed on a processor, implement the method described in any one of claims 1-9.

21. A computer program product, characterized in that, The computer program product includes instructions or a computer program that, when run on a computer, causes the computer to perform the method described in any one of claims 1-9.

Images