CN103209122A - Information interaction method of routing management module and protocol subsystem - Google Patents
Information interaction method of routing management module and protocol subsystem Download PDFInfo
- Publication number
- CN103209122A CN103209122A CN2012103395386A CN201210339538A CN103209122A CN 103209122 A CN103209122 A CN 103209122A CN 2012103395386 A CN2012103395386 A CN 2012103395386A CN 201210339538 A CN201210339538 A CN 201210339538A CN 103209122 A CN103209122 A CN 103209122A
- Authority
- CN
- China
- Prior art keywords
- routing
- command
- zsys
- subsystem
- module
- 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.)
- Granted
Links
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
An information interaction method of a routing management module and a protocol subsystem comprises the following steps of (1) establishing a routing deleting interface function and a routing adding interface function of the protocol subsystem, registering various service interfaces of the protocol subsystem and starting a guarding monitoring program of the protocol subsystem; (2) filling routing information which need to be deleted or added; (3) setting a routing deleting command and a routing adding command; (4) performing a public service interface of the routing information; (5) building a command massage and sending a routing command message to a ZSYS (Z System) module; and 6) receiving the routing command message which is sent from the protocol subsystem through the ZSYS module, determining a type of the routing command message, performing a routing deletion function of a gateway system when the routing command message is the routing deleting command, performing a routing update or adding function of the gateway system when the routing command message is the routing adding command and redistributing a command task to a backend of the guarding monitoring program of the protocol subsystem when the routing command message is a routing redistributing command through the ZSYS module.
Description
Technical field
The present invention relates to the gateway technique field, the information interacting method of a kind of routing management module and agreement subsystem is provided.
Background technology
At present, in VPN (virtual private network), use the MPLS-VPN architecture more and more, and the satellite communication gateway equipment of support MPLS-VPN function, very rare, in electric power system, ground network makes up and also adopts the MPLS-VPN pattern to make up the ground VPN (virtual private network) usually, yet the satellite communication system in emergency communication is based on the network configuration of pure IP mode, this pattern makes the MPLS-VPN message directly not transmit in satellite network, and the form that can only encapsulate by the gre tunneling message of GRE-MPLS-VPN is carried out the transmission agency of MPLS, although the correlation function with top can be met from the ground router of costliness, but, in relevant therewith satellite communication, because the complexity of ductility and space environment during satellite transmission high, make the bandwidth availability ratio deficiency of satellite communication link, therefore, the realization of functions such as the control protocol conversion of more excellent space link can be used for improving the utilance of spacing wireless channel, and equipment such as ground router seem helpless.
Summary of the invention
The objective of the invention is to exist not enough at existing equipment and technology, comprising apparatus expensive, safeguard shortcomings such as inconvenience, there is not a kind of design of electric power gateway device to take into account ground network access and these two kinds of demands of space transmission network efficient fully, the technical scheme of related documents and materials is comparatively general, the not concrete practical design method that proposes, the invention describes the design of routing management module in the gateway function, the exchange method that it relates to correlation subsystem provides the information interacting method of a kind of routing management module and agreement subsystem.
The present invention is to achieve these goals by the following technical solutions:
The information interacting method of a kind of routing management module and agreement subsystem is characterized in that may further comprise the steps:
11), route delete interface function, the route that makes up the agreement subsystem added all kinds of service interfaces of interface function, log-in protocol subsystem and started the oracle listener of guarding of agreement subsystem;
12), fill the routing iinformation that needs deletion or add;
13), route delete command and route is set adds order is set;
14), carry out the common services interface of routing iinformation;
15), make up command messages, send routing command message to the ZSYS module that is used for the management agreement subsystem;
16), the ZSYS module is received the routing command message that the agreement subsystem sends, judge the routing command type of message, when being the deletion routing command, routing command message carries out the route delete function of gateway system, carry out the routing update of gateway system or add function when adding routing command, during for route distribution command again the ZSYS module again the distribution command task guard the oracle listener rear end in the subsystem.
17), the agreement subsystem reads the command messages from the ZSYS module, when when adding routing command, the route of the subsystem that carries on an agreement is added function, during for the deletion routing command, the route delete function of the subsystem that carries on an agreement.
In the such scheme, described ZSYS module establishment step for the management agreement subsystem:
21) create the monitoring socket, monitor the TCP connection request then;
22) listen to the connection request of client after, add socket binding Service events, to add the bound socket mission thread, in the bound socket task of zsys_accept, add socket task binding task event again, to continue this service;
23) in the bound socket mission thread course of work, by setting newly-increased client instance socket unblock attribute, make the client instance asynchronous working, create client instance at last, and add zsys client instance managing listings to;
24) after the monitoring socket listened to the service request of client, the ZSYS module received the command messages that the agreement subsystem sends; After the message verification, according to command type, select corresponding registered function service function, carry out and response;
25) event type drives
When event is when listening to the event that produces behind the connection request of protocols having submodule, drive the work of ZSYS module according to step 22;
When event is when reading the event that produces after the service request of agreement submodule, the routing command message that receiving step 16 described agreement subsystems send drives the work of ZSYS module according to this module establishment step 4.
The present invention has following beneficial effect:
In the routing module class of this gateway, each agreement demons not with the direct communication of (SuSE) Linux OS kernel, but by send command request to the ZSYS module, be responsible for communicating by letter with the Linux kernel by the ZSYS demons.The ZSYS module is served distribution and is distributed to corresponding agreement subsystem (client) with other as the routing iinformation that service end will obtain from kernel.Each agreement subsystem has the routing table of oneself.The ZSYS module is responsible for the routing table update of linux kernel, and to the again distribution of route information at the different agreement subsystem, for the structure of MPLS data message then by realize in the linux system kernel that mpls protocol drives and with this protocol registration to the linux system kernel, abandoned the method for message at application layer structure MPLS, this design has improved the operating efficiency of gateway system in the big data quantity scene.
In gateway designs, for supporting various protocols, adopt the sub-module design and use this exchange method, be conducive to independently carrying out of function design, be conducive to unit testing and system maintenance.
Description of drawings
Fig. 1 sets up subsystem service schematic diagram for ZSYS module of the present invention;
Fig. 2 is the routing iinformation interaction diagrams of ZSYS module of the present invention and Routing Protocol subsystem;
Fig. 3 is the explanation of universal information head formal definition;
Fig. 4 is the explanation of equivalence class message interchange format;
The explanation of Fig. 5 deferent segment message interchange format:
Fig. 6 imports the explanation of segment information DIF;
The explanation of Fig. 7 Label space message format;
Fig. 8 Routing Information Exchange format description.
Embodiment
Below the present invention is described further:
The invention provides the information interacting method of a kind of routing management module and agreement subsystem, it is characterized in that may further comprise the steps:
11), route delete interface function, the route that makes up the agreement subsystem added all kinds of service interfaces of interface function, log-in protocol subsystem and started the oracle listener of guarding of agreement subsystem;
12), fill the routing iinformation that needs deletion or add;
13), route delete command and route is set adds order is set;
14), carry out the common services interface of routing iinformation;
15), make up command messages, send routing command message to the ZSYS module that is used for the management agreement subsystem;
16), the ZSYS module is received the routing command message that the agreement subsystem sends, judge the routing command type of message, when being the deletion routing command, routing command message carries out the route delete function of gateway system, carry out the routing update of gateway system or add function when adding routing command, during for route distribution command again the ZSYS module again the distribution command task guard the oracle listener rear end in the subsystem.
17), the agreement subsystem reads the command messages from the ZSYS module, when when adding routing command, the route of the subsystem that carries on an agreement is added function, during for the deletion routing command, the route delete function of the subsystem that carries on an agreement.
In the such scheme, described ZSYS module establishment step for the management agreement subsystem:
21) create the monitoring socket, monitor the TCP connection request then;
22) listen to the connection request of client after, add socket binding Service events, to add the bound socket mission thread, in the bound socket task of zsys_accept, add socket task binding task event again, to continue this service;
23) in the bound socket mission thread course of work, by setting newly-increased client instance socket unblock attribute, make the client instance asynchronous working, create client instance at last, and add zsys client instance managing listings to;
24) after the monitoring socket listened to the service request of client, the ZSYS module received the command messages that the agreement subsystem sends; After the message verification, according to command type, select corresponding registered function service function, carry out and response;
25) event type drives
When event is when listening to the event that produces behind the connection request of protocols having submodule, drive the work of ZSYS module according to step 22;
When event is when reading the event that produces after the service request of agreement submodule, the routing command message that receiving step 16 described agreement subsystems send drives the work of ZSYS module according to this module establishment step 4.
In Fig. 1, in the routing module class of this gateway, each agreement demons not with the direct communication of (SuSE) Linux OS kernel, but by send command request to ZSYS, be responsible for communicating by letter with the Linux kernel by the ZSYS demons.ZSYS serves distribution and is distributed to corresponding agreement subsystem (client) with other as the routing iinformation that service end will obtain from kernel. and each agreement subsystem has the routing table of oneself.ZSYS is responsible for the routing table update of linux kernel, and to the again distribution of route information at the different agreement subsystem, for the structure of MPLS data message then by realize in the linux system kernel that mpls protocol drives and with this protocol registration to the linux system kernel, abandoned the method for message at application layer structure MPLS, this design, improved the operating efficiency of gateway system in the big data quantity scene, design for the MPLS kernel module, gateway system compiles into operating system with MPLS bottom functional module with the form of static module, MPLS kernel processes module is when dividing into groups to transmit or handle, need be mutual with the ldpd agreement subsystem of user's attitude, its reciprocal process is embodied in the maintenance to MPLS function important data structures, as: label stack, ILM, NHLFE, LABELSPACE etc., its communication mode is Generic Netlink socket communication, actually finish communication and then finish by the ZSYS module, meanwhile, the ZSYS module also is responsible for the management of system journal, the vtyCmd management, system break, anomalous signals catches, the management of agreement subsystem routing iinformation, the response of agreement subsystem message request, linux kernel routing update management, user command Message Processing or distribution etc., also be responsible for to the LDP protocol module OSPF/BGP Routing Protocol modules configured and to the management of gateway database.ZSYS sets up agreement subsystem sockets services end by zsys_serv in the system initialization process, its structural representation, as shown in Figure 2:
The ZSYS module after socket is monitored in establishment, is added socket binding Service events in the zsys_serv function, to add bound socket reading task thread, in the bound socket task of zsys_accept, add socket task binding task event again, to continue this service.By setting newly-increased client instance socket unblock attribute, make the client instance asynchronous working.Create client instance at last, and add zsys client instance managing listings to.Work as client instance, when reading the message of agreement subsystem by the reading task thread, the alignment processing function is zsys_client_read, every client instance of ZSYS module creation, receive the command messages that the agreement subsystem sends by the zsys_client_read function, after the message verification, according to command type, as: add route ID (ZSYS_ROUTER_ID) order, select the alignment processing function.The interaction models of ZSYS module and each Routing Protocol module is C/S model, wherein subsystem: ospfd, and bgpd, ldpd are the client end, and zsysd is the server end, the mutual schematic diagram of the routing iinformation of subsystem and zsysd, shown in Fig. 2-7:
In Fig. 3, each subsystem example, be example with the ospf protocol, OSPFD is by function ospf_add_discard, ospf_delete_discard adds respectively, the acquired routing iinformation of deletion ospfd uses public function zapi_ipv4_route structure and sends command messages to ZSYS module instance process in the process.ZSYS module instance process service end receives and responds each command request, for example ought receive command type is that ZSYS_REDISTRIBUTE_ADD (adds again, distribute route) time, be routed to subsystem by the allocation of zsys_redistribute function, as ospfd.
Wherein the message format for communications of ZSYS system and each agreement subsystem is defined as follows:
(1) common message format head
Fig. 4 universal information head format description:
Length: the message total bytes contains message header 6 bytes;
Marker: message identifier value: 255;
Version: version number: 1;
Command: command type, as ZSYS_ROUTE_ID, ZSYS_INTERFACE_ADD.
(2) equivalence class information interaction form
The explanation of Fig. 5 equivalence class message interchange format:
Type: the type of sign equivalence class, as: ZSYS_MPLS_FEC_IPV4;
Owner: the owner of this message, as ZSYS_ROUTE_LDP;
PrefixLen: equivalence class prefix length;
PrefixAddr: equivalence class prefix addresses;
OutSegmentIndex: equivalence class index.
(3) deferent segment information interaction form
The explanation of Fig. 6 deferent segment message interchange format:
Type: tag types, as: ZSYS_MPLS_LABEL_GEN;
Owner: the owner of this message, as ZSYS_ROUTE_LDP;
GenericLabel: universal tag value;
IfName: belonging network interface name;
IPFamily:ip same clan type is supported ipv4 at present;
PrefixIPV4: prefix addresses;
Index: the call number of self-defined OutSegment;
Req: deferent segment request number.
(4) the mutual form of input segment information
Fig. 7 imports the segment information DIF:
Owner: the owner of this message
Labelspace: Label space;
Protocol: protocol type, as ipv4 family;
Pop: acquiescence is made as 1 temporarily
Type: the type of label;
GenericLabel: universal tag value.
(5) Label space message format
The explanation of Fig. 8 Label space message format:
Owner: message owner;
Labelspace: Label space;
InterfaceName: interface name.
(6) route messages DIF
The Routing Information Exchange format description:
Type: the type of message: ZSYS_ROUTE_OSPF;
Flags: be defaulted as 0;
Message: route messages attribute bit field, as ZAPI_MESSAGE_ATTR_NEXTHOP;
PerfixLen: prefix figure place;
PerfixAddr: prefix IP address;
NextHopCount: next jumps number;
NextHopFlag: next jumps type bit domain identifier, as ZSYS_NEXTHOP_IFINDEX:
NextHop_Addr/IfIndex: next jumps the corresponding ip address of type identification or network interface index;
Distance: optional far-end value;
MetricCost: optional cost value.
Above message format is defined as the intermodule communication message of the routing function of invention gateway.
Tradition route software is used as a process, this process provides all Routing Protocol functions, and this method adopts a kind of different design, namely it as a common maintaining routing list of service routine collection, services set is divided into ad hoc routing protocol finger daemon and system kernel management finger daemon.The ad hoc routing protocol finger daemon is responsible for the mutual of corresponding Routing Protocol, as Routing Protocol ospf.System kernel management finger daemon is responsible for to the management of ad hoc routing protocol and to the management of system kernel.The present invention provides the information interacting method of a kind of routing management module (system kernel management demons) with agreement subsystem (ad hoc routing protocol demons).Its each subsystem example adds respectively by function, deletes acquired routing iinformation, uses public function zapi_ipv4_route structure in the process and sends command messages to ZSYS module instance process.ZSYS module instance service routine receives and responds each command request, for example ought receive command type is that ZSYS_REDISTRIBUTE_ADD (adds again, distribute route) time, be routed to subsystem by the allocation of zsys_redistribute function, as the demons of ospf Routing Protocol---ospfd.
Claims (2)
1. the information interacting method of a routing management module and agreement subsystem is characterized in that may further comprise the steps:
11), route delete interface function, the route that makes up the agreement subsystem added all kinds of service interfaces of interface function, log-in protocol subsystem and started the oracle listener of guarding of agreement subsystem;
12), fill the routing iinformation that needs deletion or add;
13), route delete command and route is set adds order is set;
14), carry out the common services interface of routing iinformation;
15), make up command messages, send routing command message to the ZSYS module that is used for the management agreement subsystem;
16), the ZSYS module is received the routing command message that the agreement subsystem sends, judge the routing command type of message, when being the deletion routing command, routing command message carries out the route delete function of gateway system, carry out the routing update of gateway system or add function when adding routing command, during for route distribution command again the ZSYS module again the distribution command task guard the oracle listener rear end in the subsystem;
17), the agreement subsystem reads the command messages from the ZSYS module, when when adding routing command, the route of the subsystem that carries on an agreement is added function, during for the deletion routing command, the route delete function of the subsystem that carries on an agreement.
2. the information interacting method of a kind of routing management module according to claim 1 and agreement subsystem is characterized in that: described ZSYS module establishment step for the management agreement subsystem:
21) create the monitoring socket, monitor the TCP connection request then;
22) listen to the connection request of client after, add socket binding Service events, to add the bound socket mission thread, in the bound socket task of zsys_accept, add socket task binding task event again, to continue this service;
23) in the bound socket mission thread course of work, by setting newly-increased client instance socket unblock attribute, make the client instance asynchronous working, create client instance at last, and add ZSYS client instance managing listings to;
24) after the monitoring socket listened to the service request of client, the ZSYS module received the command messages that the agreement subsystem sends; After the message verification, according to command type, select corresponding registered function service function, carry out and response;
25) event type drives
When event is when listening to the event that produces behind the connection request of protocols having submodule, drive the work of ZSYS module according to step 22;
When event is when reading the event that produces after the service request of agreement submodule, the routing command message that receiving step 16 described agreement subsystems send drives the work of ZSYS module according to this module establishment step 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210339538.6A CN103209122B (en) | 2012-09-14 | 2012-09-14 | A kind of routing management module and the information interacting method of protocol subsystem |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210339538.6A CN103209122B (en) | 2012-09-14 | 2012-09-14 | A kind of routing management module and the information interacting method of protocol subsystem |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103209122A true CN103209122A (en) | 2013-07-17 |
| CN103209122B CN103209122B (en) | 2016-08-03 |
Family
ID=48756211
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210339538.6A Active CN103209122B (en) | 2012-09-14 | 2012-09-14 | A kind of routing management module and the information interacting method of protocol subsystem |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103209122B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110784527A (en) * | 2019-10-18 | 2020-02-11 | 三体云智能科技有限公司 | Information management system and method |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2001067678A1 (en) * | 2000-03-10 | 2001-09-13 | Shenzhen Liming Network Systems Co., Ltd. | An information switch |
| CN101217479A (en) * | 2008-01-09 | 2008-07-09 | 中兴通讯股份有限公司 | Network route management method |
| CN102497023A (en) * | 2011-11-29 | 2012-06-13 | 纵横资通能源股份有限公司 | Intelligent micro-grid control system and intelligent power consumption management method |
-
2012
- 2012-09-14 CN CN201210339538.6A patent/CN103209122B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2001067678A1 (en) * | 2000-03-10 | 2001-09-13 | Shenzhen Liming Network Systems Co., Ltd. | An information switch |
| CN101217479A (en) * | 2008-01-09 | 2008-07-09 | 中兴通讯股份有限公司 | Network route management method |
| CN102497023A (en) * | 2011-11-29 | 2012-06-13 | 纵横资通能源股份有限公司 | Intelligent micro-grid control system and intelligent power consumption management method |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110784527A (en) * | 2019-10-18 | 2020-02-11 | 三体云智能科技有限公司 | Information management system and method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103209122B (en) | 2016-08-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105515978B (en) | Realize the method and device of distributed routing, physical host access | |
| CN103312605B (en) | A kind of gateway device identity setting method and management gateway equipment | |
| CN102801599B (en) | A kind of communication means and system | |
| CN102845123B (en) | Virtual private cloud connection method and tunnel proxy server | |
| CN104040964B (en) | Method, device and data center network across service area communication | |
| US10454880B2 (en) | IP packet processing method and apparatus, and network system | |
| EP2262185A1 (en) | Method and system for forwarding data among private networks | |
| WO2013007158A1 (en) | Method for virtual private cloud to access network, network side device and data centre device | |
| CN101951325A (en) | Network terminal configuration system based on automatic discovery and configuration method thereof | |
| CN113132170B (en) | Data management method and system, association subsystem and computer readable medium | |
| WO2016070633A1 (en) | Network log generation method and device | |
| CN103414885A (en) | Communication method of network audio-video monitoring system | |
| JP2019519146A (en) | Routing establishment, packet transmission | |
| CN104539539A (en) | Multi-service-board data forwarding method for AC device | |
| CN110851238A (en) | Implementation method of openstack fully-distributed dhcp service | |
| JP4202286B2 (en) | VPN connection control method and system | |
| CN102571394A (en) | Simple network management protocol (SNMP) network managing method and system | |
| CN106533984B (en) | A kind of cut-in method and device of social resources | |
| CN103209122A (en) | Information interaction method of routing management module and protocol subsystem | |
| CN116566830A (en) | Network configuration method, device, system, edge equipment and storage medium | |
| CN103141072A (en) | Ip address obtaining method and network access device | |
| CN105591871A (en) | Method and device for configuration of auto discovery virtual private network (ADVPN) spoke | |
| CN101316239A (en) | Method for controlling access and forwarding in virtual special LAN service network | |
| CN115333819A (en) | Remote network access system and communication method | |
| CN101170502B (en) | A method and system for realizing mutual access between stacking members |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |