Method and apparatus for establishing a synchronization session of a ddc network

Abstract

The application relates to the communication technical field, discloses a kind of DDC network's synchronous session establishment method and device. Among them, DDC network includes M NCP equipment, the method can be applied to the first NCP equipment in M NCP equipment, the method includes: the first NCP equipment determines M device ID according to pre-configured device ID range;M device ID includes the device ID of the first NCP equipment and the device ID of other M-1 devices;According to the device ID of the first NCP equipment, the port number of the first NCP equipment is generated, and the port number of M-1 NCP equipment is generated according to the device ID of M-1 NCP equipment;M-1 ARP message is sent, M-1 ARP message corresponds to M-1 NCP equipment one by one, and the first ARP message in M-1 ARP message is used to establish the synchronous session between the second NCP equipment and the first NCP equipment. In this way, without interconnecting through the network between NCP and NCF, the synchronous session between the first NCP equipment and the second NCP equipment can be established by sending ARP message by the first NCP equipment, so as to facilitate to reduce the complexity of configuration.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method and apparatus for establishing a synchronous session in a DDC network. Background Technology

[0002] Distributed disaggregate chassis (DDC) is a network device system based on application-specific integrated circuit (ASIC) chips. It is based on the original rack network equipment (such as switches or routers), making the management board, fabric card and line card into physically independent devices, removing the original rack switch chassis, and then connecting them with cables to form a logical rack switch.

[0003] The DDC network uses Network Cloud Fabric (NCF) devices to replace the original Fabric cards and Network Cloud Packet Forwarders (NCPs) to replace the original line cards. Currently, different NCP devices in the DDC network can forward packets through NCF devices to achieve information synchronization between different NCP devices, but this method results in high configuration complexity for NCP devices.

[0004] Therefore, there is an urgent need for a way to establish synchronous sessions between NCP devices to simplify the configuration complexity of NCP devices. Summary of the Invention

[0005] This invention provides a method and apparatus for establishing a synchronous session in a DDC network, which solves the problem of high configuration complexity of NCP devices in the prior art.

[0006] In a first aspect, embodiments of the present invention provide a method for establishing a synchronous session in a DDC network, wherein the DDC network includes M NCP devices, and the method is applied to the first NCP device among the M NCP devices. The method includes: determining M device IDs based on a pre-configured range of device identifiers; the M device IDs include the device ID of the first NCP device and the device IDs of M-1 NCP devices other than the first NCP device, where M is an integer greater than 1; generating the port number of the first NCP device based on the device ID of the first NCP device, and generating the port numbers of the M-1 NCP devices based on the device IDs of the M-1 NCP devices; sending M-1 Address Resolution Protocol (ARP) packets, each of the M-1 ARP packets corresponding one-to-one with one of the M-1 NCP devices, each of the M-1 ARP packets including a first ARP packet, the first ARP packet including a destination port number, the destination port number being the port number of the second NCP device among the M-1 NCP devices corresponding to the first ARP packet; wherein, the first ARP packet is used to establish a synchronization session between the second NCP device and the first NCP device.

[0007] Using the above method, the first NCP device obtains its source port number and the peer NCP device's port number from a pre-configured device ID range, which serve as the destination port number. This allows the first and second NCP devices to send and receive ARP packets based on the source and destination port numbers, reducing the number of NCP configuration steps and enabling synchronization sessions between them to be established using ARP packets without requiring interconnection between the NCP and NCF networks. Optionally, the pre-configured device ID range can be quite large, allowing newly added NCP devices to be added to the DDC network without modifying existing NCP devices, simplifying deployment complexity and improving usability.

[0008] Optionally, the first ARP packet may further include a source IP address, a destination IP address, a source Media Access Control (MAC) address, a destination MAC address, and a source port number. The source IP address and destination IP address are the IP addresses corresponding to the ports of the first NCP device, the source MAC address is the MAC address of the first NCP device, the destination MAC address is a broadcast MAC address, and the source port number is the port number of the first NCP device.

[0009] Optionally, the first ARP message may further include a TLV field, wherein the TLV field includes the Autonomous System (AS) number of the Border Gateway Routing Protocol (BGP) corresponding to the first NCP device.

[0010] Thus, when establishing a synchronization session using EBGP neighbors, the AS number can be obtained from the TLV field of the first ARP message.

[0011] Optionally, sending M-1 ARP messages includes: sequentially sending the M-1 ARP messages according to a preset time interval.

[0012] In this way, the first NCP device can periodically send ARP messages to M-1 other NCP devices besides the first NCP device.

[0013] Optionally, the port number of the first NCP device is generated based on the device ID and port number of the first NCP device; wherein the port numbers of the M-1 NCP devices are the same as the port number of the first NCP device.

[0014] Secondly, embodiments of the present invention provide a method for establishing a synchronization session in a DDC network, the DDC network including M NCP devices, and the method is applied to a first NCP device among the M NCP devices. The method includes: determining M device IDs based on a pre-configured device ID range; the M device IDs include the device ID of the first NCP device and the device IDs of M-1 other NCP devices among the M NCP devices, where M is an integer greater than 1; generating an IP address corresponding to the port of the second NCP device based on the device ID of the second NCP device among the M-1 NCP devices and the prefix portion of a pre-configured IP address; and establishing a synchronization session between the first NCP device and the second NCP device based on the IP address corresponding to the port of the second NCP device.

[0015] By using the above method, since the M NCP devices are pre-configured with the same MAC address and their ports use addresses in the same network segment, the first and second NCP devices do not need to generate ARP entries by sending a first ARP packet. The first NCP device automatically generates ARP entries based on the pre-configured information and establishes a synchronization session between the second and first NCP devices through the IP address corresponding to the port of the second NCP device in the ARP entry. This simplifies the complexity of NCP device configuration and improves the ease of establishing synchronization sessions between NCP devices.

[0016] Optionally, the port number of the first NCP device is generated based on the device ID and port number of the first NCP device; wherein the port numbers of the M-1 NCP devices are the same as the port number of the first NCP device.

[0017] Thirdly, embodiments of the present invention provide a synchronization session establishment apparatus for a DDC network, wherein the DDC network includes M NCP devices, and the apparatus is a first NCP device among the M NCP devices or a chip in the NCP device. The apparatus includes: a determining module, configured to determine M device IDs based on a pre-configured device identifier ID range; the M device IDs include the device ID of the first NCP device and the device IDs of M-1 NCP devices other than the first NCP device among the M NCP devices; generating the port number of the first NCP device based on the device ID of the first NCP device, and a root... The module generates port numbers for the M-1 NCP devices based on their device IDs; the transceiver module sends M-1 Address Resolution Protocol (ARP) packets, each ARP packet corresponding to one of the M-1 NCP devices, and each ARP packet includes a first ARP packet, which includes a destination port number, which is the port number of the second NCP device among the M-1 NCP devices that corresponds to the first ARP packet; the processing module establishes a synchronization session between the second NCP device and the first NCP device based on the first ARP packet.

[0018] Fourthly, embodiments of the present invention provide a synchronization session establishment apparatus for a DDC network, wherein the DDC network includes M NCP devices, and the apparatus is a first NCP device among the M NCP devices or a chip in the NCP device. The apparatus includes: a determining module, configured to determine M device IDs according to a pre-configured device ID range; the M device IDs include the device ID of the first NCP device and the device IDs of M-1 NCP devices other than the first NCP device among the M NCP devices; generating an IP address corresponding to the port of the second NCP device according to the device ID of the second NCP device among the M-1 NCP devices and the prefix portion of a pre-configured IP address; and a processing module, configured to establish a synchronization session between the first NCP device and the second NCP device according to the IP address corresponding to the port of the second NCP device.

[0019] Fifthly, embodiments of the present invention provide a communication device, comprising: a memory for storing a computer program; and a processor for executing the method described in the first or second aspect according to the obtained program when executing the computer program stored in the memory.

[0020] In a sixth aspect, embodiments of the present invention provide a computer-readable storage medium storing a computer program, which, when read and executed by a computer, causes the methods described in the first or second aspect above to be performed.

[0021] In a seventh aspect, embodiments of the present invention provide a computer program product that, when read and executed by a computer, causes the methods described in the first or second aspect above to be performed. Attached Figure Description

[0022] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0023] Figure 1 This is a schematic diagram of the system architecture of the DDC system provided in an embodiment of the present invention;

[0024] Figure 2 The flowchart corresponds to the synchronization session establishment method of a DDC network provided in Embodiment 1 of the present invention;

[0025] Figure 3 A schematic diagram of an ARP message provided in an embodiment of the present invention;

[0026] Figure 4 A schematic diagram of a TLV field provided in an embodiment of the present invention;

[0027] Figure 5 The flowchart corresponds to the synchronization session establishment method of a DDC network provided in Embodiment 2 of the present invention;

[0028] Figure 6 A schematic diagram of a synchronization session establishment device for a DDC network provided in an embodiment of the present invention;

[0029] Figure 7 A schematic diagram of a synchronization session establishment device for a DDC network provided in an embodiment of the present invention;

[0030] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0031] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are merely some embodiments of this invention, and not all embodiments. Based on the embodiments of this invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this invention. In the embodiments of this invention, "multiple" refers to two or more. Terms such as "first," "second," etc., are used only for descriptive purposes and should not be construed as indicating or implying relative importance, nor as indicating or implying order.

[0032] In a DDC network, to synchronize table entries among various NCPs, one approach is to have the network cloud controller (NCC) centrally configure the forwarding of table entries to each NCP device. However, if the NCC device malfunctions, causing the NCC to lose connection with the NCPs and / or NCFs, the DDC network will become uncontrollable, affecting the normal operation of the NCPs and / or NCFs within the network.

[0033] To address the risk of system failure due to the disconnection of the NCC from the NCP and / or NCF, an alternative approach has been introduced: removing the NCC device while retaining the NCP and NCF devices. For example... Figure 1 As shown, the DDC network includes N NCF devices and M NCP devices, where M and N are both integers greater than 1. Full connections are established between the M NCP devices and the N NCF devices. An NCP device is connected to N NCF devices in the DDC network, and similarly, an NCF device is connected to M NCP devices in the DDC network. Thus, different NCP devices can forward messages through NCF devices to facilitate information synchronization between different NCP devices.

[0034] When using the network between NCP devices and NCF devices to establish a synchronization session between NCP devices, it is necessary to configure the port numbers and address resolution protocol (ARP) entries of the other M-1 NCP devices on each NCP device. Thus, the number of configuration times for the M NCP devices is M*(M-1), which makes the configuration complexity of this method relatively high.

[0035] Based on this, embodiments of the present invention provide a method for establishing a synchronization session in a DDC network. This method does not require interconnection between the NCP and NCF networks. A synchronization session between the first NCP device and the second NCP device can be established by sending an ARP message through the first NCP device, thereby reducing the complexity of configuration.

[0036] The methods provided in the embodiments of this application will be described in detail below with reference to Embodiment 1 and Embodiment 2.

[0037] Example 1

[0038] In Embodiment 1, the first NCP device sends multiple ARP packets to facilitate the establishment of a synchronization session between the second NCP device and the first NCP device by other NCP devices (such as the second NCP device). The first NCP device is any one of the M NCP devices included in the DDC network.

[0039] Figure 2 The flowchart corresponding to the synchronization session establishment method of a DDC network provided in Embodiment 1 of the present invention is as follows: Figure 2 As shown, the method includes the following steps:

[0040] Step 201: The first NCP device determines M device IDs based on the pre-configured device ID range.

[0041] Here, the M device IDs include the device ID of the first NCP device and the device IDs of the M-1 NCP devices other than the first NCP device.

[0042] For example, the device ID of the first NCP device can be pre-configured as 'a' and the device ID range can be 'a' to 'b', and the IP address corresponding to the port of the first NCP device can be pre-configured as 'IPA'. The pre-configured device ID range can be greater than or equal to the number of NCP devices in the current DDC network. When the pre-configured device ID range is greater than the number of NCP devices in the current DDC network, the existing NCP configuration does not need to be modified when new NCP devices are added to the DDC network. For example, if there are 3 NCP devices in the current DDC network, and the pre-configured device ID range is 1 to 4, then the first NCP can determine 4 device IDs based on the pre-configured device ID range, namely 1, 2, 3, and 4.

[0043] Optionally, other possible information can also be pre-configured on the first NCP device, such as a time interval, so that the first NCP device can send APR messages according to the time interval, as described below.

[0044] For example, the device ID of the first NCP device is 1, and the device ID range is 1 to 4. The IP address (IPA) corresponding to the port of the first NCP device is 1.1.1.1 / 32, and the above time interval is 60 seconds. For example, the configuration information of the first NCP device is as follows:

[0045] ddc device-id 1

[0046] ddc ncp device-range 1 4

[0047] interface cpu 0

[0048] IP address 1.1.1.1 255.255.255.255

[0049] arp bind ddc remote-cpu

[0050] arp gratuitous-send enable

[0051] arpgratuitous-sendinterval 60 1

[0052] Step 202: The first NCP device generates the port number of the first NCP device based on the device ID of the first NCP device, and generates the port number of the M-1 NCP devices based on the device IDs of the M-1 NCP devices.

[0053] Here, the port number of the first NCP device is generated based on its device ID and port number. Taking the first NCP device as an example, the other M-1 NCP devices can be referenced. The port number of the first NCP device includes its device ID and port number, which each occupy 2 bytes. The high byte stores the device ID, and the low byte stores the port number. The port numbers of the M-1 NCP devices are the same as those of the first NCP device, and these port numbers can be uniformly set to 0. In this case, the port number of the first NCP device is 0x10, the port number of the second NCP device is 0x20, and so on, until the port number of the Mth NCP device is 0xM0.

[0054] Step 203: The first NCP device sends M-1 ARP packets, and each of the M-1 ARP packets corresponds to one of the M-1 NCP devices.

[0055] Here, the first NCP device sends M-1 ARP packets to M-1 other NCP devices, including the first ARP packet. For example, the first NCP device can send M-1 ARP packets sequentially at a preset time interval (i.e., the pre-configured time interval mentioned above). For instance, if the preset time interval is 60 seconds, the first NCP device will send the first ARP packet, then the second ARP packet after a 60-second interval, and so on.

[0056] Taking the first ARP packet as an example (other ARP packets can be referenced accordingly), such as Figure 3 As shown, the first ARP packet also includes a source IP address, a destination IP address, a source Media Access Control (MAC) address, a destination MAC address, a source port number, and a destination port number. The source IP address and destination IP address are the IP addresses corresponding to the ports of the first NCP device; the source MAC address is the MAC address of the first NCP device; the destination MAC address is the broadcast MAC address; the source port number is the port number of the first NCP device; and the destination port number is the port number of the second NCP device among M-1 NCP devices that corresponds to the first ARP packet.

[0057] Optionally, the above method further includes:

[0058] Step 204: The second NCP device receives the first ARP message and establishes a synchronization session between the second NCP device and the first NCP device based on the first ARP message.

[0059] For example, after receiving the first ARP packet sent by the first NCP device, the second NCP device can process the first ARP packet to generate a corresponding first ARP entry. Specifically, the second NCP device finds the interface 1 of the first NCP device on the second NCP device based on the source port number (i.e., the port number of the first NCP device) carried in the first ARP packet. Interface 1 is the source interface of the first ARP packet. The second NCP device generates a first ARP entry based on the IP address, MAC address, and interface 1 of the port of the first NCP device carried in the first ARP packet. See Table 1 for an example of a first ARP entry.

[0060] Table 1: Example of the first ARP entry

[0061] IP address interface MAC address 1.1.1.1 Interface 1 NCP1 MAC address

[0062] Furthermore, the second NCP device uses the IP address in the first ARP entry as the border gateway routing protocol (BGP) neighbor address to establish a synchronization session between the first NCP device and the second NCP device. There are several ways to establish the synchronization session, such as implementation method 1 and implementation method 2.

[0063] Implementation Method 1: The second NCP device uses the IP address in the first ARP entry as the BGP neighbor address to generate an Internal Border Gateway Protocol (IBGP) neighbor as a synchronization session. Furthermore, the second NCP device can find the first NCP device as a neighbor using the IP address in the first ARP entry (such as the IP address 1.1.1.1 corresponding to the port of the first NCP device). The parameters of the IBGP neighbor can be configured using BGP peer-group.

[0064] For example, a configuration example of the second NCP device:

[0065] router bgp 100

[0066] neighbor ncp peer-goup

[0067] neighbor ncp remote-as 100

[0068] neighbor ncp update-source cpu 0

[0069] neighbor ncp dynamic-peer arp ddc-remote-cpu

[0070] Implementation Method 2: For situations where the Autonomous System (AS) numbers of the M NCP devices in a DDC network are different, an External Border Gateway Protocol (EBGP) neighbor is used as the synchronization session. The IP address in the first ARP entry is used as the BGP neighbor address to generate an EBGP neighbor for the synchronization session. When using EBGP neighbors as the synchronization session, the first ARP packet sent from the first NCP device to the second NCP device includes a tag-length-value (TLV) field, which can carry multiple different types of TLV fields, such as... Figure 4 As shown, the TLV field includes TLV type, TLV length, and TLV content.

[0071] In this case, assuming that the BGP AS number needs to be carried, the TLV type can be set to 1. The TLV length indicates the length of the TLV content in bytes. For example, if the BGP AS number is 4 bytes, the TLV length field is set to 4. The TLV content field is used to carry different content according to the different types of TLV. For example, if the BGP AS number is carried, the TLV content field stores the BGP AS number corresponding to the first NCP device.

[0072] The second NCP device can find the first NCP device as a neighbor by using the IP address in the first ARP entry (such as the IP address 1.1.1.1 corresponding to the port of the first NCP device) and the BGP AS number in the TLV content field of the TLV field in the first ARP packet (such as the BGP AS number 101 of the first NCP device).

[0073] For example, a configuration example of the second NCP device:

[0074] router bgp 101

[0075] neighbor ncp peer-goup

[0076] neighbor ncp update-source cpu 0

[0077] neighbor ncp dynamic-peer arp ddc-remote-cpu

[0078] It is understandable that the above example uses the second NCP device. After the other M-1 MCP devices receive the ARP message from the first NCP device, they can also establish synchronization with the first NCP device. For details, please refer to the description of the second NCP device.

[0079] Using the above method, since the first NCP device obtains its source port number and the destination port number of the peer NCP device through a pre-configured device ID range, it is not necessary to interconnect through the network between the NCP and NCF. A synchronization session between the first and second NCP devices can be established simply by the first NCP device sending an ARP packet. Compared to the previous method of "different NCP devices forwarding packets through an NCF device to achieve information synchronization between different NCP devices," configuring the device ID range on each of the M NCP devices only requires M configuration operations, thus reducing the complexity of NCP device configuration.

[0080] Example 2

[0081] In Embodiment 2, the first NCP device directly generates an ARP entry based on the pre-configured information. Through the IP address corresponding to the port of the second NCP device in the ARP entry, a synchronization session is established between the second NCP device and the first NCP device. Embodiment 2 will be described in detail below.

[0082] Figure 5 The flowchart corresponding to the synchronization session establishment method of a DDC network provided in Embodiment 2 of the present invention is as follows: Figure 5 As shown, the method includes the following steps:

[0083] Step 501: The first NCP device determines M device IDs based on the pre-configured device ID range.

[0084] Here, the M device IDs include the device ID of the first NCP device and the device IDs of the M-1 NCP devices other than the first NCP device.

[0085] For example, the device ID of the first NCP device can be pre-configured as a and the device ID range can be a to b. The prefix part of the IP address of the first NCP device can also be pre-configured as IPB, so that the M NCP devices in the DDC network use the same network segment address. In addition, the MAC address of the first NCP device needs to be pre-configured as IPC. The same MAC address IPC is pre-configured on the M-1 NCP devices other than the first NCP device in the DDC network.

[0086] For example, the device ID of the first NCP device is 1, the device ID range is 1 to 4, the prefix part of the IP address of the first NCP device is 100.1.1.0 / 24, and the MAC address can be 1234.1234.1234.1234.

[0087] Step 502: Generate the IP address corresponding to the port of the second NCP device based on the device ID of the second NCP device among the M-1 NCP devices and the prefix part of the pre-configured IP address.

[0088] Here, the port number of the first NCP device is generated based on the device ID and port number of the first NCP device. Taking the first NCP device as an example, the other M-1 NCP devices can refer to this. The port number of the first NCP device includes the device ID and port number of the first NCP device. The port numbers of the M-1 NCP devices are the same as the port number of the first NCP device. The port number can be uniformly set to 0. At this time, the port number of the first NCP device is 0x10, the port number of the second NCP device is 0x20, and so on. The port number of the Mth NCP device is 0xM0.

[0089] Based on the device ID of the first NCP device and the prefix of its pre-configured IP address, generate the IP address corresponding to the port of the first NCP device. For example, if the device ID of the first NCP device is 1 and the prefix of its IP address is 100.1.1.0 / 24, then the IP address corresponding to the port of the first NCP device is 100.1.1.1. Based on the device ID of the second NCP device and the prefix of its pre-configured IP address, generate the IP address corresponding to the port of the second NCP device. For example, if the device ID of the second NCP device is 2 and the prefix of the first NCP device's IP address is 100.1.1.0 / 24, then the IP address corresponding to the port of the first NCP device is 100.1.1.2.

[0090] On the first NCP device, an ARP entry can be generated based on the device ID range, the device's port number, the IP address corresponding to the port, and the MAC address. Specifically, the first NCP device finds the corresponding interface 2 of the second NCP device on the first NCP device based on the port number of the second NCP device. The first NCP device obtains the IP address 1.1.1.2 corresponding to the port of the second NCP device based on the device ID of the second NCP device and the prefix of the preset IP address. The first NCP device generates an ARP entry based on the IP address corresponding to the port of the second NCP device, the corresponding interface 2 of the second NCP device on the first NCP device, and the pre-configured MAC address. See Table 2 for an example of an ARP entry generated by the first NCP device.

[0091] Table 2: Examples of ARP entries generated by the first NCP device

[0092] IP address interface MAC address 100.1.1.2 Interface 2 1234.1234.1234.1234 100.1.1.3 Interface 3 1234.1234.1234.1234 100.1.1.4 Interface 4 1234.1234.1234.1234

[0093] Step 503: Establish a synchronization session between the first NCP device and the second NCP device based on the IP address corresponding to the port of the second NCP device.

[0094] In this embodiment of the invention, the IP address in the ARP entry is used as the BGP neighbor address to generate an IBGP neighbor as a synchronization session. The first NCP device can find the second NCP device as a neighbor through the IP address corresponding to the port of the second NCP device in the ARP entry (such as the IP address 100.1.1.2 corresponding to the port of the second NCP device). The parameters of the IBGP neighbor can be configured using BGP peer-group.

[0095] For example, the configuration example of the first NCP device:

[0096] router bgp 100

[0097] neighbor ncp peer-goup

[0098] neighbor ncp remote-as 100

[0099] neighbor ncp update-source cpu 0

[0100] neighbor ncp dynamic-peer arp ddc-remote-cpu

[0101] Using the above method, since the M NCP devices are pre-configured with the same MAC address and their ports share the same network segment, there is no need for the first and second NCP devices to generate ARP entries by sending a first ARP packet. The first NCP device directly generates ARP entries based on the pre-configured information and establishes a synchronization session between the second and first NCP devices using the IP address corresponding to the port of the second NCP device in the ARP entry. This simplifies the complexity of NCP device configuration.

[0102] Based on the same concept, embodiments of the present invention also provide a synchronization session establishment apparatus for a DDC network, wherein the DDC network includes M NCP devices, and the apparatus is the first NCP device among the M NCP devices or a chip in the NCP device. Figure 6 A schematic diagram of a synchronization session establishment apparatus for a DDC network provided in an embodiment of the present invention is shown below. Figure 6 As shown, the device includes:

[0103] The determination module 601 is used to determine M device IDs according to a pre-configured range of device identifiers; the M device IDs include the device ID of the first NCP device and the device IDs of M-1 NCP devices other than the first NCP device; the port number of the first NCP device is generated according to the device ID of the first NCP device, and the port number of M-1 NCP devices is generated according to the device IDs of the M-1 NCP devices.

[0104] The transceiver module 602 is used to send M-1 ARP packets, wherein each M-1 ARP packet corresponds to one of M-1 NCP devices. Each M-1 ARP packet includes a first ARP packet, which includes a destination port number. The destination port number is the port number of the second NCP device that corresponds to the first ARP packet among the M-1 NCP devices.

[0105] The processing module 603 is used to establish a synchronization session between the second NCP device and the first NCP device based on the first ARP message.

[0106] Optionally, the first ARP packet in the transceiver module 602 may also include a source IP address, a destination IP address, a source media access control address (MAC address), a destination MAC address, and a source port number; the source IP address and destination IP address are the IP addresses corresponding to the ports of the first NCP device, the source MAC address is the MAC address of the first NCP device, the destination MAC address is the broadcast MAC address, and the source port number is the port number of the first NCP device.

[0107] Optionally, the first ARP message in the transceiver module 602 may also include a TLV field, which includes the Autonomous System (AS) number of the BGP corresponding to the first NCP device.

[0108] Optionally, the transceiver module 602 is also used to send M-1 ARP messages sequentially according to a preset time interval.

[0109] Optionally, the determining module 601 is further configured to generate the port number of the first NCP device based on the device ID of the first NCP device and the port number of the first NCP device; wherein the port numbers of the M-1 NCP devices are the same as the port number of the first NCP device.

[0110] Based on the same concept, embodiments of the present invention also provide a synchronization session establishment apparatus for a DDC network, wherein the DDC network includes M NCP devices, and the apparatus is the first NCP device among the M NCP devices or a chip in the NCP device. Figure 7 A schematic diagram of a synchronization session establishment apparatus for a DDC network provided in an embodiment of the present invention is shown below. Figure 7 As shown, the device includes:

[0111] The determination module 701 is used to determine M device IDs based on a pre-configured range of device IDs; the M device IDs include the device ID of the first NCP device and the device IDs of M-1 NCP devices other than the first NCP device among the M NCP devices; and generate the IP address corresponding to the port of the second NCP device based on the device ID of the second NCP device among the M-1 NCP devices and the prefix part of the pre-configured IP address.

[0112] The processing module 702 is used to establish a synchronization session between the first NCP device and the second NCP device based on the IP address corresponding to the port of the second NCP device.

[0113] Optionally, the determining module 701 is further configured to generate the port number of the first NCP device based on the device ID of the first NCP device and the port number of the first NCP device; wherein the port numbers of the M-1 NCP devices are the same as the port number of the first NCP device.

[0114] Figure 8 This is a schematic diagram of the structure of a device 8000 provided in an embodiment of the present invention. This device is used to implement the functions of the first communication device in the above embodiment. Figure 8 As shown, the device 8000 includes at least one processor 801 and a memory 802 connected to the at least one processor 801. In this embodiment, the specific connection medium between the processor 801 and the memory 802 is not limited. Figure 8 Taking the connection between processor 801 and memory 802 via a bus as an example, the bus can be divided into address bus, data bus, control bus, etc. In this embodiment of the invention, memory 802 stores instructions that can be executed by at least one processor 801. By executing the instructions stored in memory 802, at least one processor 801 can implement the steps of the above-mentioned synchronous session establishment method for DDC network.

[0115] The processor 801 is the control center of the computer device, capable of connecting various parts of the computer device via various interfaces and lines. It performs resource configuration by running or executing instructions stored in the memory 802 and accessing data stored in the memory 802. Optionally, the processor 801 may include one or more processing units. The processor 801 may integrate an application processor and a modem processor. The application processor primarily handles the operating system, user interface, and applications, while the modem processor primarily handles wireless communication. It is understood that the modem processor may not be integrated into the processor 801. In some embodiments, the processor 801 and the memory 802 may be implemented on the same chip; in other embodiments, they may be implemented on separate chips.

[0116] The processor 801 can be a general-purpose processor, such as a central processing unit (CPU), digital signal processor, application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.

[0117] Memory 802, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules. Memory 802 may include at least one type of storage medium, such as flash memory, hard disk, multimedia card, card-type memory, random access memory (RAM), static random access memory (SRAM), programmable read-only memory (PROM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic storage, magnetic disk, optical disk, etc. Memory 802 can be any other medium capable of carrying or storing desired program code in the form of instructions or data structures that can be accessed by a computer, but is not limited thereto. In the embodiments of this application, memory 802 can also be a circuit or any other device capable of implementing storage functions for storing program instructions and / or data.

[0118] Based on the same technical concept, embodiments of the present invention provide a computer-readable storage medium storing a computer program, wherein the computer program is executed by a processor to perform the above-described method for establishing a synchronous session in a DDC network.

[0119] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0120] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0121] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0122] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0123] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A method for establishing a synchronous session in a distributed rack-mount (DDC) network, characterized in that, The DDC network includes M network cloud packet forwarding NCP devices. The method is applied to the first NCP device among the M NCP devices. The method includes: Based on the pre-configured device identifier ID range, M device IDs are determined; the M device IDs include the device ID of the first NCP device and the device IDs of M-1 NCP devices other than the first NCP device, where M is an integer greater than 1; The port number of the first NCP device is generated based on the device ID of the first NCP device, and the port number of the M-1 NCP devices is generated based on the device IDs of the M-1 NCP devices; Send M-1 Address Resolution Protocol (ARP) packets, each of which corresponds one-to-one with one of the M-1 NCP devices. Each M-1 ARP packet includes a first ARP packet, which includes a destination port number. The destination port number is the port number of the second NCP device among the M-1 NCP devices that corresponds to the first ARP packet. The first ARP message is used to establish a synchronization session between the second NCP device and the first NCP device.

2. The method as described in claim 1, characterized in that, The first ARP packet also includes the source IP address, destination IP address, source Media Access Control (MAC) address, destination MAC address, and source port number; Wherein, the source IP address and destination IP address are the IP addresses corresponding to the ports of the first NCP device, the source MAC address is the MAC address of the first NCP device, the destination MAC address is the broadcast MAC address, and the source port number is the port number of the first NCP device.

3. The method as described in claim 1, characterized in that, The first ARP message also includes a Type Length Value (TLV) field, which includes the Autonomous System (AS) number of the Border Gateway Routing Protocol (BGP) corresponding to the first NCP device.

4. The method as described in claim 1, characterized in that, Sending M-1 ARP messages includes: According to the preset time interval, M-1 ARP messages are sent sequentially.

5. The method according to any one of claims 1-4, characterized in that, The port number of the first NCP device is generated based on the device ID of the first NCP device, including: The port number of the first NCP device is generated based on the device ID and port number of the first NCP device. The port numbers of the M-1 NCP devices are the same as the port number of the first NCP device.

6. A synchronization session establishment device for a DDC network, characterized in that, The distributed split rack (DDC) network includes M network cloud packet forwarding (NCP) devices. The device is either the first NCP device among the M NCP devices or a chip within the NCP device. The device includes: The determination module is used to determine M device IDs based on a pre-configured range of device identifier IDs; the M device IDs include the device ID of the first NCP device and the device IDs of M-1 NCP devices other than the first NCP device; the module generates the port number of the first NCP device based on the device ID of the first NCP device, and generates the port number of the M-1 NCP devices based on the device IDs of the M-1 NCP devices, where M is an integer greater than 1; The transceiver module is used to send M-1 Address Resolution Protocol (ARP) packets, each of which corresponds one-to-one with one of the M-1 NCP devices. Each M-1 ARP packet includes a first ARP packet, which includes a destination port number. The destination port number is the port number of the second NCP device among the M-1 NCP devices that corresponds to the first ARP packet. The processing module is used to establish a synchronization session between the second NCP device and the first NCP device based on the first ARP message.

7. A communication device, characterized in that, include: Memory, used to store computer programs; A processor, when executing a computer program stored in the memory, implements the method steps of any one of claims 1-5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the method steps of any one of claims 1-5.

Images