CN115333949B - Method for realizing topology discovery service model based on narrowband network - Google Patents
Method for realizing topology discovery service model based on narrowband network Download PDFInfo
- Publication number
- CN115333949B CN115333949B CN202210909457.9A CN202210909457A CN115333949B CN 115333949 B CN115333949 B CN 115333949B CN 202210909457 A CN202210909457 A CN 202210909457A CN 115333949 B CN115333949 B CN 115333949B
- Authority
- CN
- China
- Prior art keywords
- byte
- information
- neighbor
- node
- sdn
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 19
- IVJYMCMDQOZJPK-UHFFFAOYSA-N FCSS Chemical compound FCSS IVJYMCMDQOZJPK-UHFFFAOYSA-N 0.000 claims abstract description 43
- 230000002457 bidirectional effect Effects 0.000 claims abstract description 38
- 230000001360 synchronised effect Effects 0.000 claims abstract description 30
- 230000006854 communication Effects 0.000 claims abstract description 24
- 238000004891 communication Methods 0.000 claims abstract description 23
- 102100036409 Activated CDC42 kinase 1 Human genes 0.000 claims description 12
- 101000928956 Homo sapiens Activated CDC42 kinase 1 Proteins 0.000 claims description 12
- 230000003993 interaction Effects 0.000 claims description 7
- 238000007906 compression Methods 0.000 claims description 5
- 230000006835 compression Effects 0.000 claims description 5
- 238000004364 calculation method Methods 0.000 abstract description 3
- 230000005540 biological transmission Effects 0.000 description 30
- 230000007175 bidirectional communication Effects 0.000 description 7
- 230000009286 beneficial effect Effects 0.000 description 6
- 230000007547 defect Effects 0.000 description 3
- 238000010276 construction Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000004927 fusion Effects 0.000 description 2
- 230000008447 perception Effects 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 238000013144 data compression Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/14—Network analysis or design
- H04L41/145—Network analysis or design involving simulating, designing, planning or modelling of a network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
Abstract
The invention discloses a method for realizing a topology discovery service model based on a narrowband network, which belongs to the technical field of narrowband network communication and comprises the following steps: constructing an FCSS protocol; simplifying and encoding each piece of equipment information and corresponding port information in the software defined network SDN, and storing the equipment information and the corresponding port information into a database of each piece of equipment; based on the FCSS protocol, respectively establishing bidirectional neighbor point-to-point communication between the main software defined network device and a plurality of neighbor software defined network devices; data synchronous exchange and bidirectional active pushing are carried out; converting the newly added neighbor information into link information, and synchronizing the link information to the SDN by using the FCSS protocol; the method and the device for achieving the topology discovery service model based on the narrow-band network solve the problem that the calculation of the full-network topology is difficult to be carried out efficiently under the narrow-band condition.
Description
Technical Field
The invention belongs to the technical field of narrowband network communication, and particularly relates to a method for realizing a topology discovery service model based on a narrowband network.
Background
The narrowband network refers to a network transmission mode performed in a wired or wireless access scene with very low network bandwidth; the network access mode with the network access speed of 64kbs and lower than the network access speed is generally called a narrowband, and compared with a broadband narrowband, the network access mode has the defects of low access speed and low transmission rate, and many Internet applications cannot be performed in a narrowband environment;
when the topology discovery service model is used for interconnection and interworking of equipment, connection conditions of the equipment and neighbor equipment can be independently and controllably discovered, the topology information of the whole network can be obtained by synchronizing the neighbor information of the whole network equipment, and the equipment can obtain the shortest path information of any equipment by selecting a proper shortest path algorithm, such as Dijkstra algorithm, for path calculation;
in the current common topology protocols, the following two schemes are generally adopted:
(1) The device neighbor protocol based on LLDP (Link Layer Discovery Protocol) and controller acquisition is a data link layer protocol, and the principle is that neighbor information can be obtained by periodically sending self interface information and extracting remote information after the opposite end is received; the protocol has the defects that only neighbors can be perceived, the topology information of the whole network is not available, the protocol is triggered periodically, the occupied bandwidth is related according to frequency, and the bandwidth can be occupied continuously and periodically under the narrow-band condition; meanwhile, the controller can acquire neighbor information of all devices, so that a large amount of messages appear in the bandwidth, and the bandwidth is more and more obvious along with the increase of the network scale, so that the feasibility of the scheme is insufficient for the whole network topology perception of the narrowband network;
(3) Based on an OSPF perception full network topology scheme, an OSPF protocol is adopted to acquire node information of a full network routing switch, the scheme only works in a three-layer interface mode, topology information under a two-layer interface cannot be acquired, and the condition that the protocol occupies bandwidth is higher than that of a narrow band, so that the method is similarly insufficient in feasibility under the condition of a narrow band network.
Disclosure of Invention
Aiming at the defects in the prior art, the method for realizing the topology discovery service model based on the narrowband network solves the problem that the calculation of the whole network topology is difficult to be performed efficiently under the narrowband condition.
In order to achieve the aim of the invention, the invention adopts the following technical scheme:
the invention provides a method for realizing a topology discovery service model based on a narrowband network, which comprises the following steps:
s1, constructing an FCSS protocol;
s2, simplifying and encoding each piece of equipment information and corresponding port information in the software defined network SDN, and storing the equipment information and the corresponding port information into a database of each piece of equipment;
s3, based on the FCSS protocol, respectively establishing bidirectional neighbor point-to-point communication between the main software defined network device SDN-A and A plurality of neighbor software defined network devices SDN-B;
s4, based on bidirectional neighbor point-to-point communication, carrying out data synchronous exchange and bidirectional active pushing;
s5, based on data synchronous exchange and bidirectional active pushing, converting newly added neighbor information into link information, and synchronizing the link information to the SDN by using an FCSS protocol;
s6, obtaining topology information of the whole network according to the equipment information and the link information, and calculating to obtain path information among all the equipment in the software defined network by using Dijkstra algorithm to complete the realization of the topology discovery service model based on the narrowband network.
The beneficial effects of the invention are as follows: the method for realizing the topology discovery service model based on the narrowband network realizes the establishment of bidirectional neighbor point-to-point communication for each device in the SDN, bidirectional differential synchronous transmission of database information, bidirectional port load balancing, compression coding, expandable protocol coding and fusion of the traditional protocols, improves the narrowband utilization rate, realizes the acquisition of the whole network topology through a single node of the device, and does not need a controller to perform training to acquire all device information, thereby reducing the bandwidth occupancy rate.
Further, the step S1 includes the steps of:
s11, constructing an FCSS head;
s12, defining FCSS protocol version, message type, FLAG and data interaction format.
The beneficial effects of adopting the further scheme are as follows: the construction method of the FCSS protocol is provided, and a foundation is provided for realizing the synchronization of software-defined network data based on the FCSS protocol.
Further, the step S11 includes the steps of:
s111, defining the FCSS header as 32 bytes, and dividing the FCSS header into a first 16-byte segment and a second 16-byte segment;
s112, dividing the first 16 byte section into a first 4 byte section, a second 4 byte section, a third 4 byte section and a fourth 4 byte section in sequence;
s113, dividing the second 16 byte section into a fifth 4 byte section, a sixth 4 byte section, a seventh 4 byte section and an eighth 4 byte section in sequence;
s114, using the first 4 byte segment to represent the protocol version, using the second 4 byte segment to represent the message type, using the third 4 byte segment to represent FLAG, using the fourth 4 byte segment, the fifth 4 byte segment and the sixth 4 byte segment to represent the message length with header length, and using the seventh 4 byte segment and the eighth 4 byte segment to represent the CRC message checksum.
The beneficial effects of adopting the further scheme are as follows: the FCSS header construction method provides a foundation for realizing software-defined network data synchronization based on FCSS protocol
Further, the step S12 includes the steps of:
s121, defining a protocol version as a No. 0 version;
s122, respectively defining 0x01 to represent HELLO and heartbeat messages, 0x02 to represent equipment and link information interaction, 0x03 to represent equipment configuration synchronous exchange, 0x04 to represent ACK synchronous response and 0x05 to represent FINISH synchronous completion;
s123, defining 0001 to represent GZIP compression coding;
s124, defining the FCSS data exchange format as 32 bytes, and dividing the FCSS data exchange format into a third 16-byte segment and a fourth 16-byte segment;
s125, dividing the third 16 byte section into a ninth 4 byte section, a tenth 4 byte section, an eleventh 4 byte section and a twelfth 4 byte section in sequence, and dividing the fourth 16 byte section into a thirteenth 4 byte section, a fourteenth 4 byte section, a fifteenth 4 byte section and a sixteenth 4 byte section in sequence;
s126, representing a device ID with a ninth 4-byte, a tenth 4-byte, an eleventh 4-byte, a twelfth 4-byte, a thirteenth 4-byte, and a fourteenth 4-byte, and representing a traffic type with a fifteenth 4-byte and a sixteenth 4-byte;
s127, the service ID is represented by a ninth 4-byte, a tenth 4-byte, an eleventh 4-byte, and a twelfth 4-byte, and the transmitted data is represented by a thirteenth 4-byte, a fourteenth 4-byte, a fifteenth 4-byte, and a sixteenth 4-byte.
The beneficial effects of adopting the further scheme are as follows: providing relevant definitions of FCSS protocol version, message type, FLAG and data interaction format provides a basis for implementing software defined network data synchronization based on FCSS protocol.
Further, the step S3 includes the following steps:
the step S3 includes the steps of:
s31, starting an FCSS protocol, transmitting A first HELLO message to A plurality of neighbor software-defined network devices SDN-B by using A main software-defined network device SDN-A, and simultaneously, transmitting A second HELLO message to the main software-defined network device SDN-A by using each neighbor software-defined network device SDN-B;
s32, respectively receiving A first HELLO message by utilizing each neighbor software defined network device SDN-B, and receiving A second HELLO message by utilizing the main software defined network device SDN-A, and completing the establishment of bidirectional neighbor point-to-point communication between the main software defined network device SDN-A and each neighbor software defined network device SDN-B.
The beneficial effects of adopting the further scheme are as follows: the method for establishing the bidirectional neighbor point-to-point communication between the main software defined network device SDN-A and each neighbor software defined network device SDN-B provides A basis for datA synchronous exchange and bidirectional active push based on the bidirectional neighbor point-to-point communication.
Further, the step S4 includes the steps of:
s41, based on bidirectional neighbor point-to-point communication, identifying neighbor active and standby conditions according to the MAC address of the main software defined network device SND-A by utilizing each neighbor software defined network device SDN-B respectively;
s42, data synchronous exchange and bidirectional active pushing are carried out according to neighbor active and standby conditions.
Further, the step S42 includes the steps of:
s421, according to neighbor active/standby conditions, setting A master software defined network device SDN-A as A master node, setting A port of the master software defined network device SDN-A as A master port, setting all neighbor software defined network devices SDN-B as slave nodes, and setting ports of the neighbor software defined network devices SDN-B as slave ports;
s422, sending a third HELLO message comprising the CRC information of the database of the master node to each slave node by using the master node, and respectively sending a fourth HELLO message comprising the CRC information of the database of the corresponding slave node to the master node by using each slave node;
s423, receiving a fourth HELLO message through the main port, and receiving a third HELLO message through the slave port;
s424, judging whether the database CRC of the main node is consistent with the database CRC in the fourth HELLO message, if so, entering a step S425, otherwise, entering a step S426;
s425, respectively using the master node and the slave node to correspondingly send FINISH to the slave node and the master node, and proceeding to step S429;
s426, judging whether the slave node has new data, if so, entering a step S428, otherwise, entering a step S427;
s427, sequentially sending master node database information to the slave nodes by using the master nodes, replying a slave node acknowledgement character ACK to the master nodes after the slave nodes FINISH receiving the master node database information by using the slave nodes, correspondingly sending FINISH to the slave nodes and the master nodes by using the master nodes and the slave nodes respectively, and proceeding to step S429;
s428, sequentially sending master node database information to slave nodes by using the master node, replying a slave node acknowledgement character ACK to the master node after the slave node finishes receiving the master node database information by using the slave node, sending FINISH to the slave node by using the master node, sequentially sending data items which need to be added by the slave node to the master node, replying a master node acknowledgement character ACK1 to the slave node after receiving the data items which need to be added by the slave node by using the master node at the master port, correspondingly sending FINISH to the slave node and the master node by using the master node and the slave node respectively, and proceeding to step S429;
s429, data synchronous exchange between the master node and each slave node is completed, and bidirectional active pushing is performed.
The beneficial effects of adopting the further scheme are as follows: based on the bidirectional neighbor point-to-point communication, database information of each node is synchronized, data synchronous exchange and bidirectional active pushing are carried out, and a foundation is provided for obtaining the topology information of the whole network based on equipment information and link information.
Drawings
Fig. 1 is a flowchart of steps of a method for implementing a topology discovery service model based on a narrowband network in an embodiment of the invention.
Fig. 2 is a default topology diagram of the full network topology synchronization in an embodiment of the present invention.
Fig. 3 is a schematic diagram of SPTN-1 sequentially synchronizing its own link information to a neighboring node based on FCSS in an embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention is provided to facilitate understanding of the present invention by those skilled in the art, but it should be understood that the present invention is not limited to the scope of the embodiments, and all the inventions which make use of the inventive concept are protected by the spirit and scope of the present invention as defined and defined in the appended claims to those skilled in the art.
Dijkstra algorithm: the dijkstra algorithm is a typical single-source shortest path algorithm for calculating the shortest path from one node to all other nodes;
OSPF protocol: the open shortest path first routing protocol is a link state routing protocol for an internet protocol, IP, network.
As shown in fig. 1, in one embodiment of the present invention, the present invention provides a method for implementing a topology discovery service model based on a narrowband network, including the following steps:
s1, constructing an FCSS protocol;
the step S1 includes the steps of:
s11, constructing an FCSS head;
the step S11 includes the steps of:
s111, defining the FCSS header as 32 bytes, and dividing the FCSS header into a first 16-byte segment and a second 16-byte segment;
s112, dividing the first 16 byte section into a first 4 byte section, a second 4 byte section, a third 4 byte section and a fourth 4 byte section in sequence;
s113, dividing the second 16 byte section into a fifth 4 byte section, a sixth 4 byte section, a seventh 4 byte section and an eighth 4 byte section in sequence;
s114, using the first 4 byte segment to represent the protocol version, using the second 4 byte segment to represent the message type, using the third 4 byte segment to represent FLAG, using the fourth 4 byte segment, the fifth 4 byte segment and the sixth 4 byte segment to represent the message length with header length, and using the seventh 4 byte segment and the eighth 4 byte segment to represent the CRC message checksum, as shown in table 1:
TABLE 1
S12, defining FCSS protocol version, message type, FLAG and data interaction format;
the step S12 includes the steps of:
s121, defining a protocol version as a No. 0 version;
s122, respectively defining 0x01 to represent HELLO and heartbeat messages, 0x02 to represent equipment and link information interaction, 0x03 to represent equipment configuration synchronous exchange, 0x04 to represent ACK synchronous response and 0x05 to represent FINISH synchronous completion;
s123, defining 0001 to represent GZIP compression coding;
s124, defining the FCSS data exchange format as 32 bytes, and dividing the FCSS data exchange format into a third 16-byte segment and a fourth 16-byte segment;
s125, dividing the third 16 byte section into a ninth 4 byte section, a tenth 4 byte section, an eleventh 4 byte section and a twelfth 4 byte section in sequence, and dividing the fourth 16 byte section into a thirteenth 4 byte section, a fourteenth 4 byte section, a fifteenth 4 byte section and a sixteenth 4 byte section in sequence;
s126, representing a device ID with a ninth 4-byte, a tenth 4-byte, an eleventh 4-byte, a twelfth 4-byte, a thirteenth 4-byte, and a fourteenth 4-byte, and representing a traffic type with a fifteenth 4-byte and a sixteenth 4-byte;
s127, the service ID is represented by a ninth 4-byte, a tenth 4-byte, an eleventh 4-byte, and a twelfth 4-byte, and the transmitted data is represented by a thirteenth 4-byte, a fourteenth 4-byte, a fifteenth 4-byte, and a sixteenth 4-byte, as shown in table 2:
TABLE 2
The DeviceID is used for indicating which device the data item belongs to, the service type is used for identifying the service (belonging to a part of KEY), the KEY is used for indicating the ID of the service, and the data is used for indicating the transmitted data;
s2, simplifying and encoding each piece of equipment information and corresponding port information in the software defined network SDN, and storing the equipment information and the corresponding port information into a database of each piece of equipment;
s3, based on the FCSS protocol, respectively establishing bidirectional neighbor point-to-point communication between the main software defined network device SDN-A and A plurality of neighbor software defined network devices SDN-B;
the step S3 includes the steps of:
s31, starting an FCSS protocol, transmitting A first HELLO message to A plurality of neighbor software-defined network devices SDN-B by using A main software-defined network device SDN-A, and simultaneously, transmitting A second HELLO message to the main software-defined network device SDN-A by using each neighbor software-defined network device SDN-B;
s32, respectively receiving A first HELLO message by utilizing each neighbor software defined network device SDN-B, and receiving A second HELLO message by utilizing the main software defined network device SDN-A, so as to complete the establishment of bidirectional neighbor point-to-point communication between the main software defined network device SDN-A and each neighbor software defined network device SDN-B;
s4, based on bidirectional neighbor point-to-point communication, carrying out data synchronous exchange and bidirectional active pushing;
the step S4 includes the steps of:
s41, based on bidirectional neighbor point-to-point communication, identifying neighbor active and standby conditions according to the MAC address of the main software defined network device SND-A by utilizing each neighbor software defined network device SDN-B respectively;
s42, carrying out data synchronous exchange and bidirectional active pushing according to neighbor active and standby conditions;
the step S42 includes the steps of:
s421, according to neighbor active/standby conditions, setting A master software defined network device SDN-A as A master node, setting A port of the master software defined network device SDN-A as A master port, setting all neighbor software defined network devices SDN-B as slave nodes, and setting ports of the neighbor software defined network devices SDN-B as slave ports;
s422, sending a third HELLO message comprising the CRC information of the database of the master node to each slave node by using the master node, and respectively sending a fourth HELLO message comprising the CRC information of the database of the corresponding slave node to the master node by using each slave node;
s423, receiving a fourth HELLO message through the main port, and receiving a third HELLO message through the slave port;
s424, judging whether the database CRC of the main node is consistent with the database CRC in the fourth HELLO message, if so, entering a step S425, otherwise, entering a step S426;
s425, respectively using the master node and the slave node to correspondingly send FINISH to the slave node and the master node, and proceeding to step S429;
s426, judging whether the slave node has new data, if so, entering a step S428, otherwise, entering a step S427;
s427, sequentially sending master node database information to the slave nodes by using the master nodes, replying a slave node acknowledgement character ACK to the master nodes after the slave nodes FINISH receiving the master node database information by using the slave nodes, correspondingly sending FINISH to the slave nodes and the master nodes by using the master nodes and the slave nodes respectively, and proceeding to step S429;
s428, sequentially sending master node database information to slave nodes by using the master node, replying a slave node acknowledgement character ACK to the master node after the slave node finishes receiving the master node database information by using the slave node, sending FINISH to the slave node by using the master node, sequentially sending data items which need to be added by the slave node to the master node, replying a master node acknowledgement character ACK1 to the slave node after receiving the data items which need to be added by the slave node by using the master node at the master port, correspondingly sending FINISH to the slave node and the master node by using the master node and the slave node respectively, and proceeding to step S429;
s429, completing data synchronous exchange between the master node and each slave node, and performing bidirectional active pushing;
s5, based on data synchronous exchange and bidirectional active pushing, converting newly added neighbor information into link information, and synchronizing the link information to the SDN by using an FCSS protocol;
s6, obtaining topology information of the whole network according to the equipment information and the link information, and calculating to obtain path information among all the equipment in the software defined network by using Dijkstra algorithm to complete the realization of the topology discovery service model based on the narrowband network.
The method for realizing the topology discovery service model based on the narrowband network realizes the establishment of bidirectional neighbor point-to-point communication for each device in the SDN, bidirectional differential synchronous transmission of database information, bidirectional port load balancing, compression coding, expandable protocol coding and fusion of the traditional protocol, improves the narrowband utilization rate, realizes the acquisition of the whole network topology through a single node of the device, and does not need a controller to perform training to acquire all device information, thereby reducing the bandwidth occupancy rate;
when a plurality of ports are linear, the method of load balancing is utilized to synchronize database information on a plurality of lines during communication among neighbor nodes; in the flow communication process, a data compression coding technology is adopted to compress data; the scheme can expand protocol coding, integrate traditional protocols and improve narrowband utilization rate:
for narrowband characteristics, the scheme supports protocol expansion for replacing ARP/LLDP/STP, but is not limited to the protocol content;
aiming at ARP protocol, when the technology establishes neighbors, the opposite terminal ARP table information is recovered through the MAC address in the protocol message and the IP address in the database, and the source ARP detection message is reduced;
aiming at LLDP protocol, when establishing neighbor point-to-point bidirectional communication based on FCSS protocol of the scheme, the LLDP table information of the opposite end is restored through port number in protocol message;
for STP protocol, the protocol has whole network path information, so loop can be calculated directly.
As shown in FIG. 2, in one practical example of the present invention, the full network default topology includes a first packet transport network device SPTN-1, a second packet transport network device SPTN-2, a third packet transport network device SPTN-3, a fourth packet transport network device SPTN-4, a fifth packet transport network device SPTN-5, a sixth packet transport network device SPTN-6, a seventh packet transport network device SPTN-7, and an eighth packet transport network device SPTN-8;
the first packet transmission network device SPTN-1 is respectively connected with the second packet transmission network device SPTN-2 and the fourth packet transmission network device SPTN-4 in a two-way communication manner; the second packet transmission network device SPTN-2 is in bidirectional communication connection with the third packet transmission network device SPTN-3; the third packet transmission network device SPTN-3 is respectively connected with the fourth packet transmission network device SPTN-4 and the fifth packet transmission network device SPTN-5 in a bidirectional communication manner; the fourth packet transmission network device SPTN-4 is in bidirectional communication connection with the sixth packet transmission network device SPTN-6; the fifth packet transmission network device SPTN-5 is respectively connected with the sixth packet transmission network device SPTN-6 and the seventh packet transmission network device SPTN-7 in a bidirectional communication manner; the sixth packet transmission network device SPTN-6 is in bidirectional communication connection with the eighth packet transmission network device SPTN-8; the seventh packet transmission network device SPTN-7 is in bidirectional communication connection with the eighth packet transmission network device SPTN-8;
as shown in fig. 3, the neighbor node attaches to its own database according to the received device information, and then sequentially synchronizes to its neighbor node; if the data are repeatedly added by the neighbor nodes, the database recognizes that the data exist, no event is triggered, and the data are not required to be repeatedly synchronized;
the first packet transmission network device SPTN-1 synchronizes itself to the fourth packet transmission network device SPTN-4, the third packet transmission network device SPTN-3 also synchronizes the first packet transmission network device SPTN-1 data to the fourth packet transmission network device SPTN-4, the fourth packet transmission network device SPTN-4 actively recognizes that the database has no update operation, the fourth packet transmission network device SPTN-4 does not need to trigger FCSS synchronization, if the fourth packet transmission network device SPTN-4 actively recognizes that the database has newly added neighbor information, the fourth packet transmission network device SPTN-4 triggers FCSS to update link information to the whole network based on bidirectional neighbor point-to-point communication; with SPTN-1 as the viewing angle, the synchronization process is briefly described as follows:
SPTN-1 obtains link information according to self neighbor information, SPTN-4/SPTN-2, and stores the link information in a self database;
SPTN-1 and SPTN-4/SPTN-2 synchronous databases respectively, after SPTN-4 receives a synchronous message, identifying link information of lines SPTN-1, SPTN-4 and SPTN-1, SPTN-2, and storing the link information into a local database;
SPTN-4 continues to synchronize to other neighbors in the manner of SPTN-1;
when the SPTN-4 receives the link information sent by the SPTN-3, the link information of the SPTN-1 is already existed at the moment, the information is merged into the database at the moment, if no change exists, the synchronization is not needed to other neighbors, and the synchronization loop is terminated;
Claims (4)
1. the method for realizing the topology discovery service model based on the narrowband network is characterized by comprising the following steps:
s1, constructing an FCSS protocol;
the step S1 includes the steps of:
s11, constructing an FCSS head;
the step S11 includes the steps of:
s111, defining the FCSS header as 32 bytes, and dividing the FCSS header into a first 16-byte segment and a second 16-byte segment;
s112, dividing the first 16 byte section into a first 4 byte section, a second 4 byte section, a third 4 byte section and a fourth 4 byte section in sequence;
s113, dividing the second 16 byte section into a fifth 4 byte section, a sixth 4 byte section, a seventh 4 byte section and an eighth 4 byte section in sequence;
s114, using the first 4 byte section to represent a protocol version, using the second 4 byte section to represent a message type, using the third 4 byte section to represent FLAG, using the fourth 4 byte section, the fifth 4 byte section and the sixth 4 byte section to represent a message length containing a header length, and using the seventh 4 byte section and the eighth 4 byte section to represent a CRC message checksum;
s12, defining FCSS protocol version, message type, FLAG and data interaction format;
the step S12 includes the steps of:
s121, defining a protocol version as a No. 0 version;
s122, respectively defining 0x01 to represent HELLO and heartbeat messages, 0x02 to represent equipment and link information interaction, 0x03 to represent equipment configuration synchronous exchange, 0x04 to represent ACK synchronous response and 0x05 to represent FINISH synchronous completion;
s123, defining 0001 to represent GZIP compression coding;
s124, defining the FCSS data exchange format as 32 bytes, and dividing the FCSS data exchange format into a third 16-byte segment and a fourth 16-byte segment;
s125, dividing the third 16 byte section into a ninth 4 byte section, a tenth 4 byte section, an eleventh 4 byte section and a twelfth 4 byte section in sequence, and dividing the fourth 16 byte section into a thirteenth 4 byte section, a fourteenth 4 byte section, a fifteenth 4 byte section and a sixteenth 4 byte section in sequence;
s126, representing a device ID with a ninth 4-byte, a tenth 4-byte, an eleventh 4-byte, a twelfth 4-byte, a thirteenth 4-byte, and a fourteenth 4-byte, and representing a traffic type with a fifteenth 4-byte and a sixteenth 4-byte;
s127, representing the traffic ID with a ninth 4-byte, a tenth 4-byte, an eleventh 4-byte, and a twelfth 4-byte, and representing the transmitted data with a thirteenth 4-byte, a fourteenth 4-byte, a fifteenth 4-byte, and a sixteenth 4-byte;
s2, simplifying and encoding each piece of equipment information and corresponding port information in the software defined network SDN, and storing the equipment information and the corresponding port information into a database of each piece of equipment;
s3, based on the FCSS protocol, respectively establishing bidirectional neighbor point-to-point communication between the main software defined network device SDN-A and A plurality of neighbor software defined network devices SDN-B;
s4, based on bidirectional neighbor point-to-point communication, carrying out data synchronous exchange and bidirectional active pushing;
s5, based on data synchronous exchange and bidirectional active pushing, converting newly added neighbor information into link information, and synchronizing the link information to the SDN by using an FCSS protocol;
s6, obtaining topology information of the whole network according to the equipment information and the link information, and calculating to obtain path information among all the equipment in the software defined network by using Dijkstra algorithm to complete the realization of the topology discovery service model based on the narrowband network.
2. The method for implementing a topology discovery service model based on a narrowband network according to claim 1, wherein said step S3 comprises the steps of:
s31, starting an FCSS protocol, transmitting A first HELLO message to A plurality of neighbor software-defined network devices SDN-B by using A main software-defined network device SDN-A, and simultaneously, transmitting A second HELLO message to the main software-defined network device SDN-A by using each neighbor software-defined network device SDN-B;
s32, respectively receiving A first HELLO message by utilizing each neighbor software defined network device SDN-B, and receiving A second HELLO message by utilizing the main software defined network device SDN-A, and completing the establishment of bidirectional neighbor point-to-point communication between the main software defined network device SDN-A and each neighbor software defined network device SDN-B.
3. The method for implementing a topology discovery service model based on a narrowband network according to claim 2, wherein said step S4 comprises the steps of:
s41, based on bidirectional neighbor point-to-point communication, identifying neighbor active and standby conditions according to the MAC address of the main software defined network device SND-A by utilizing each neighbor software defined network device SDN-B respectively;
s42, data synchronous exchange and bidirectional active pushing are carried out according to neighbor active and standby conditions.
4. The method for implementing a topology discovery service model based on a narrowband network according to claim 3, wherein said step S42 comprises the steps of:
s421, according to neighbor active/standby conditions, setting A master software defined network device SDN-A as A master node, setting A port of the master software defined network device SDN-A as A master port, setting all neighbor software defined network devices SDN-B as slave nodes, and setting ports of the neighbor software defined network devices SDN-B as slave ports;
s422, sending a third HELLO message comprising the CRC information of the database of the master node to each slave node by using the master node, and respectively sending a fourth HELLO message comprising the CRC information of the database of the corresponding slave node to the master node by using each slave node;
s423, receiving a fourth HELLO message through the main port, and receiving a third HELLO message through the slave port;
s424, judging whether the database CRC of the main node is consistent with the database CRC in the fourth HELLO message, if so, entering a step S425, otherwise, entering a step S426;
s425, respectively using the master node and the slave node to correspondingly send FINISH to the slave node and the master node, and proceeding to step S429;
s426, judging whether the slave node has new data, if so, entering a step S428, otherwise, entering a step S427;
s427, sequentially sending master node database information to the slave nodes by using the master nodes, replying a slave node acknowledgement character ACK to the master nodes after the slave nodes FINISH receiving the master node database information by using the slave nodes, correspondingly sending FINISH to the slave nodes and the master nodes by using the master nodes and the slave nodes respectively, and proceeding to step S429;
s428, sequentially sending master node database information to slave nodes by using the master node, replying a slave node acknowledgement character ACK to the master node after the slave node finishes receiving the master node database information by using the slave node, sending FINISH to the slave node by using the master node, sequentially sending data items which need to be added by the slave node to the master node, replying a master node acknowledgement character ACK1 to the slave node after receiving the data items which need to be added by the slave node by using the master node at the master port, correspondingly sending FINISH to the slave node and the master node by using the master node and the slave node respectively, and proceeding to step S429;
s429, data synchronous exchange between the master node and each slave node is completed, and bidirectional active pushing is performed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210909457.9A CN115333949B (en) | 2022-07-29 | 2022-07-29 | Method for realizing topology discovery service model based on narrowband network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210909457.9A CN115333949B (en) | 2022-07-29 | 2022-07-29 | Method for realizing topology discovery service model based on narrowband network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115333949A CN115333949A (en) | 2022-11-11 |
| CN115333949B true CN115333949B (en) | 2023-10-27 |
Family
ID=83920324
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210909457.9A Active CN115333949B (en) | 2022-07-29 | 2022-07-29 | Method for realizing topology discovery service model based on narrowband network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115333949B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009076848A1 (en) * | 2007-12-04 | 2009-06-25 | Huawei Technologies Co., Ltd. | A method and device of automatic topology discovery and resource management in the pbb network |
| WO2017142516A1 (en) * | 2016-02-16 | 2017-08-24 | Hewlett Packard Enterprise Development Lp | Software defined networking for hybrid networks |
| CN108696595A (en) * | 2018-05-28 | 2018-10-23 | 郑州云海信息技术有限公司 | Distributed type assemblies method of data synchronization, master node, slave node, system and medium |
| CN109510769A (en) * | 2018-10-10 | 2019-03-22 | 中国电子科技集团公司第七研究所 | A kind of fusion route system being suitable for width combination network and its method |
| CN111356202A (en) * | 2020-03-09 | 2020-06-30 | 大唐联诚信息系统技术有限公司 | Low-overhead hybrid routing protocol method for narrowband ad hoc network |
| CN113612646A (en) * | 2021-08-30 | 2021-11-05 | 复旦大学 | Neighborhood network topology visualization method based on neighbor discovery |
| CN113890848A (en) * | 2021-09-10 | 2022-01-04 | 西安电子科技大学 | Topology discovery system and method for layered domain-division SDN multi-controller architecture |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9749214B2 (en) * | 2014-02-26 | 2017-08-29 | Futurewei Technologies, Inc. | Software defined networking (SDN) specific topology information discovery |
-
2022
- 2022-07-29 CN CN202210909457.9A patent/CN115333949B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009076848A1 (en) * | 2007-12-04 | 2009-06-25 | Huawei Technologies Co., Ltd. | A method and device of automatic topology discovery and resource management in the pbb network |
| WO2017142516A1 (en) * | 2016-02-16 | 2017-08-24 | Hewlett Packard Enterprise Development Lp | Software defined networking for hybrid networks |
| CN108696595A (en) * | 2018-05-28 | 2018-10-23 | 郑州云海信息技术有限公司 | Distributed type assemblies method of data synchronization, master node, slave node, system and medium |
| CN109510769A (en) * | 2018-10-10 | 2019-03-22 | 中国电子科技集团公司第七研究所 | A kind of fusion route system being suitable for width combination network and its method |
| CN111356202A (en) * | 2020-03-09 | 2020-06-30 | 大唐联诚信息系统技术有限公司 | Low-overhead hybrid routing protocol method for narrowband ad hoc network |
| CN113612646A (en) * | 2021-08-30 | 2021-11-05 | 复旦大学 | Neighborhood network topology visualization method based on neighbor discovery |
| CN113890848A (en) * | 2021-09-10 | 2022-01-04 | 西安电子科技大学 | Topology discovery system and method for layered domain-division SDN multi-controller architecture |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115333949A (en) | 2022-11-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101599909B (en) | Method and device for forwarding flow rate | |
| US9077558B2 (en) | Client/bridge failure recovery method and system | |
| CN108418896A (en) | Method and apparatus for being integrated into bluetooth equipment in neighbours' sensing network | |
| CN101409666B (en) | Ring network, ring network topology discovering method and node | |
| CN104539325A (en) | Networking interconnection method and system based on low-power-consumption Bluetooth piconets | |
| CN101764751A (en) | Method, system and equipment for forwarding roaming messages for wireless user terminal travelling across VLAN | |
| CN107820262B (en) | Parameter configuration method, device and system | |
| CN102355741A (en) | Remote control system and method thereof, and central office access equipment | |
| CN100364289C (en) | Method for implementing layer-2 equipment interconnection in resilient packet ring (RPR) based network | |
| CN102065508B (en) | Wireless bridge forwarding equipment and method | |
| WO2009036792A1 (en) | Compressed source routing | |
| CN115333949B (en) | Method for realizing topology discovery service model based on narrowband network | |
| JP2006148822A (en) | Atm communication support system, data transmission supporting apparatus, data transmitting method, and computer program | |
| US8767736B2 (en) | Communication device, communication method, and recording medium for recording communication program | |
| CN104811378A (en) | Route isolation and synchronization method | |
| CN101106506A (en) | Network information exchange method | |
| CN106941450B (en) | Route synchronization method, equipment and communication system | |
| CN103634843A (en) | Data transmission method, wireless network controller, base station and mobile communication system | |
| JP7447263B2 (en) | Network structures and methods for transmitting/receiving packets between network elements within a network | |
| JP2007318791A (en) | System for supporting communication between atm devices, data transmission supporting apparatus, data transmitting method, and computer program | |
| CN106993018A (en) | System and method for managing high network data rate | |
| CN103795557B (en) | Method, device, and system for synchronizing port modes between devices | |
| CN110650510A (en) | Low-power-consumption wide-area multi-hop networking method and system based on software definition | |
| CN115834003B (en) | Definable Ethernet link layer redundancy method and definable Ethernet link layer redundancy device based on compatible real-time synchronization | |
| CN104410723A (en) | LSDB (LinkState Database) synchronization method and system in OSPF (Open Shortest Path First) |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| PE01 | Entry into force of the registration of the contract for pledge of patent right | ||
| PE01 | Entry into force of the registration of the contract for pledge of patent right |
Denomination of invention: A method for implementing topology discovery service model based on narrowband networks Granted publication date: 20231027 Pledgee: Haidian Beijing science and technology enterprise financing Company limited by guarantee Pledgor: Beijing Guoxin Blue Shield Technology Co.,Ltd. Registration number: Y2024110000018 |