JP3269477B2 - Multi-protocol management network configuration method - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a multi-protocol management network configuration method for managing an access network in a communication network composed of different transmission networks, such as a carrier lightwave transmission network and an access network.

[0002]

2. Description of the Related Art Conventionally, carrier-based management networks have been sufficiently studied and constructed in view of the magnitude of damage caused by network abnormalities, whereas access network management has recently been required. It is. Due to the explosion of Internet users and the increase in capacity and the purpose of use, it has become necessary to increase the reliability of access networks.

[0003]

However, in the prior art, laying a management network covering an extended and distributed access network solely for access network management requires a great deal of cost, which is not practical. There was a problem.

[0004] The present invention has been made in view of the above-mentioned circumstances, and is capable of sharing an existing management network of a lightwave transmission network, performing remote management of an access network, and improving reliability. An object of the present invention is to provide a protocol-based management network configuration method.

[0005]

According to the first aspect of the present invention, there is provided a network in which a plurality of access communication networks are distributed and connected to a carrier transmission network. An access communication frame as a link for a management message communication between the access communication nodes, wherein the access communication nodes of the plurality of access communication networks and the carrier communication nodes of the carrier transmission network are connected by a data communication channel. To connect a management network between the plurality of access communication networks at an IP level, and to provide a management message communication band prepared in advance for management of a carrier transmission network, and a network management service-carrier communication. Using the network for management messages between nodes, the network management service And wherein the configuring the management network for managing the access network.

Further, according to the invention described in claim 2, according to claim 1,
In the multi-protocol management network configuration method described above, the network management service and the access communication node each include SNMP and UDP / IP, which are original access network management protocol stacks,
A network layer protocol, a transport protocol, and OSI-TP4 are provided.
The DP / IP packet is encapsulated and transferred as OSI-TP4 data.

[0007] According to the third aspect of the present invention, the first aspect of the present invention.
In the multi-protocol management network configuration method according to the above, the access communication node transmits the packet received from the data communication channel to an IP on OSI-based network.
Identify whether the packet is a TP4 packet or a standard IP packet and pass it to the OSI stack,
It is characterized in that it is determined whether or not to pass it to the IP stack.

In the present invention, an edge node connecting the plurality of access communication networks and the carrier transmission network is connected to a carrier transmission device by a data communication channel, and a management message communication link is provided between the edge nodes. The management network between the plurality of access communication networks is connected at the IP level by allocating an access communication frame as a communication network, and a management message communication band prepared in advance for the management of a carrier transmission network; A management network for managing the plurality of access networks from a network management service is configured using a management message network between a service and a carrier transmission apparatus. Therefore, it becomes possible for the access communication node to share the management message communication band for the carrier communication node and perform remote management from the network management system.

[0009]

Embodiments of the present invention will be described below with reference to the drawings. A. Configuration of Embodiment FIG. 1 is a block diagram showing a configuration of a communication network to which a management network according to an embodiment of the present invention is applied. In the figure, access communication networks 105, 106, and 107 have edge nodes 108, 109, and 110 installed to accommodate access data frames, for example, ATM cells and IP frames, in a lightwave transmission network. In this embodiment,
The access-system communication frames 117, 118, and 119 are allocated as management message communication bands, and the edge node 1
IP connection between 08, 109 and 110 is performed. Carrier-based lightwave transmission devices (NE2) 102, (NE3) 103,
(NE4) 104 is an edge node 108, 1 for accommodating the access data frame in the lightwave transmission network.
09, 110 and DCC (Data Communication Channel)
They are connected by 111, 112, 114 (optical fibers) and constitute a contact point between the lightwave transmission network and the access network.

[0010] The lightwave transmission network has an OSI protocol stack in the NE, and uses DCC or SDH (Sy) using an arbitrary wavelength for management message communication between the NEs.
nDC-113 in the overhead (Nchronous Digital Hierarchy)
OSI (Open System) is used for communication of management messages between NEs.
tems Interconnection: has an OSI management network using a router network (DCN with IS-IS / ES-IS). Therefore, the access networks 105, 106, 107 including the edge nodes constitute an IP network connected to each other, and the edge nodes 108, 109, 1
Only 10 use the OSI network to provide NMS (Network Manage
ment Service: network management service) 100.

In this embodiment, when a plurality of access networks are dispersedly connected to a carrier transmission network in the above-described manner, the access system is used as a management message communication link between the edge nodes 108, 109, and 110. The communication frames 117, 118, and 119 are allocated to connect the management networks between the access networks 105, 106, and 107 at the IP level, and the connection between the edge nodes 108, 109, and 110 and the lightwave transmission devices 102, 103, and 104 includes SD.
DCC assigned to overhead of H optical signal
111, 112, and 114 are used. Furthermore, a management message communication band 113 prepared in advance for the management of the lightwave transmission network and a management message network (hereinafter referred to as DCN: Data Communication N) between the NMS and the lightwave transmission device.
etwork) to configure a management network for managing the access network from the NMS 100.

FIGS. 2 and 3 show a management protocol configuration between the NMS 100 and the edge nodes 108, 109, and 110, and an SNMP (Simple Network Man) of the present invention.
agement Protocol) over UDP / IP on
It is a conceptual diagram for explaining OSI-TP4. NMS
100 and the edge nodes 108, 109, 110
SNM, the original access network management protocol stack
In addition to P and UDP / IP, network layer protocols such as CLNP (ISO8473) and IS-IS (ISO 1058)
9), ES-IS (ISO 9542) and OSI-TP4 (X.224 / ISO8073 Transport
t Layer Protocol Class 4) and the OSI-TP4 connection with the IP Virtual Link (hereinafter referred to as IP
TP4 connection control unit 202 for encapsulating and transferring a UDP / IP packet as
203.

Further, the NMS 100 includes an OSI LA
LLC T defined as N link control protocols
Equipped with ype-1 (ISO 8802-2). Edge node 1
In 08, 109 and 110, since connection with other edge nodes using DCC is also required, it is determined whether the packet received from the DCC is an IP on OSI-TP4 packet or a standard IP packet, and the OSI
A frame processing unit 201 is provided for determining whether to pass the packet to the stack or the UDP / IP stack.

The edge node 109 and the NMS 1 shown in FIG.
The IPVL 115 between 00 and 00 is the OSI TP shown in FIG.
4 connections 200. As shown in FIG.
IP Subnetwork to which NMS and edge node belong
ork is configured on the OSI TP4 connection. FIG. 2 shows a DCC-Ether as an OSI router.
The protocol used by the optical transmission device 103 for performing OSI packet routing between the nets has been described. In this case, the IPVL does not use the DCC 113 of the lightwave transmission network.

The edge node 110 and the NMS 1 shown in FIG.
00, the IPVL 116 is the OSI TP shown in FIG.
It corresponds to four connections 300. IPVL in this case
Also use the DCC 113 of the lightwave transmission network. In FIG.
In this case, the protocol used by the lightwave transmission devices 104 and 101 serving as passing points as OSI routers is shown.
Also, the TP4 connection control unit 202 of the NMS 100
Then, as shown in FIG. 4, an NSAP address table of an edge node is provided as IPVL information. NMS10
0 uses the TP4 connection control unit 202 to communicate between the OSI TP and the edge node registered in the table.
Four connections must be established at all times.

B. Next, the operation of the present embodiment will be described with reference to the drawings.
The edge nodes 108, 109 and 110 communicate with UDP in the access network to which the edge nodes belong and between other edge nodes.
In order to send / receive a / IP packet and send / receive a UDP / IP on OSI-TP4 packet for management message communication with the NMS 100, the LAPD packet received from the DCC must be identified and distributed to the OSI stack and the UDP / IP stack. No. FIG. 5 shows a frame format of a UDP / IP packet, and FIG. 6 shows a UDP / IP packet.
3 shows a frame format of an on OSI-TP4 packet. LAPD He for UDP / IP packets
In the SAPI of the ader, an ID that clearly indicates that the packet is a UDP / IP packet is set, and the UDP / IP on O
In the case of the SI-TP4 packet, "62" is set in the SAPI. The frame processing unit 201 performs distribution according to the SAPI.

The TP4 connection processing unit 202 of the NMS 100 always establishes an OSI TP4 connection with the edge node registered in the table shown in FIG. TP4 Conn for Edge Node
Requests TP4 to send an action request. TP4 on the edge node side is TP4 Con
Upon receiving the connection request, TP4
The Connection Confirm is returned, and the TP4 connection processing unit 203 sends the TP4 Co
Notify connection indication.

As a result, the establishment of IPVL is recognized between the two TP4 connection processing units, and the SuTP in the IP network is recognized.
TP shown in FIG. 6 using IP data as b-network
It is accommodated in the 4User Data area and transmitted. The lightwave transmission network is completely unaware that the packet to be routed is an IP packet encapsulated TP4 DT-TPDU. Even when the TP4 Connection is aborted due to a network failure or the booting of the edge node, the TP4 connection processing unit 202 continues the TP4 connection processing.
4 Request re-establishment of Connection and maintain the establishment at all times.

FIG. 7 is a conceptual diagram for explaining an example of an operation representing a change in an access route when the IPVL 116 is disconnected 701 due to a failure in the management system control package of the NE 4104. When the IPVL 116 is disconnected, I
A detour at the P level occurs, and the access network 107
DCC 11 using VL700 and access communication frame
7 is accessed from the NMS 100.

In the above-described embodiment, the UDP / I
P packets are encapsulated into OSITP-4 data, but the data to be encapsulated is TCP
The present invention is also included in the present invention since it can be realized by exactly the same method even if it is replaced with / IP packet or simply ARP or ICMP.

[0021]

As described above, according to the present invention,
The advantage is obtained that the access communication node can share the management message communication band for the carrier communication node and perform remote management from the network management system. Also, there is an advantage that Ops of the access network and the transmission network can be combined. In addition, the access network management protocol is generally SNMP over UDP.
The advantage of using / IP is that the reliability of the management message is low, but the added value of high reliability of the management network can be obtained by using the carrier-oriented connection-oriented communication path. Is obtained. Furthermore, in order to encapsulate the IP packet and accommodate it in the OSI-TP4 connection,
An advantage is obtained that NE management can be performed using an IP address.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a configuration of a communication network to which a management network according to an embodiment of the present invention is applied.

FIG. 2 shows a management protocol configuration between the NMS 100 and the edge node 109, and SNMP over according to the present invention.
FIG. 3 is a conceptual diagram for describing UDP / IP on OSI-TP4.

FIG. 3 shows a management protocol configuration between the NMS 100 and the edge node 110, and SNMP over according to the present invention.
FIG. 3 is a conceptual diagram for describing UDP / IP on OSI-TP4.

FIG. 4 is a conceptual diagram showing a configuration of an NSAP address table of an edge node.

FIG. 5 is a conceptual diagram showing a frame format of a UDP / IP packet.

FIG. 6 is a conceptual diagram showing a frame format of a UDP / IP on OSI-TP4 packet.

FIG. 7 is a conceptual diagram for explaining an operation example showing a change in an access path when a failure occurs in the management system control package of the NE 4104 and the IPVL 116 is disconnected 701.

[Explanation of symbols]

100 NMS (Network Management Service) 102, 103, 104 Lightwave Transmission Device (Carrier Communication Node) 105, 106, 107 Access Network 108, 109, 110 Edge Node (Access Communication Node) 111, 112, 114 DCC 113 Management Message Communication band 116 IPVL 117, 118, 119 Access communication frame

Continuation of the front page (56) References JP-A-11-215085 (JP, A) Atsushi Tanahashi, Implementation of TMN Customer Network Management Agent in ATM Network, IEICE Technical Report, Japan, IEICE, 1997 September 29, Vol. 97 No. 127, p. 25-p. 30 Makoto Yoshida, All About Network Management Toward the 21st Century, Japan, Toppan Corporation, January 25, 1996, p. 90-p.102 (58) Field surveyed (Int. Cl. ⁷ , DB name) H04L 12/42 H04L 12/24 H04L 12/26

Claims (3)

(57) [Claims] 1. A network in which a plurality of access communication networks are dispersedly connected to a carrier transmission network, wherein the access communication nodes of the plurality of access communication networks and the carrier communication of the carrier transmission network. Connecting a management network between the plurality of access communication networks at the IP level by allocating an access communication frame as a management message communication link between the access communication nodes; Using a management message communication band prepared in advance for the management of a carrier transmission network and a network for a management message between a network management service and a carrier communication node; A management network that performs management. Multi-protocol management network configuration method. 2. The network management service and the access communication node respectively include a network layer protocol, a transport protocol, and an OSI-TP4 in addition to SNMP and UDP / IP, which are original access network management protocol stacks. And encapsulates UDP / IP packets as IPVL, and uses OSI-T
2. The method according to claim 1, wherein the data is transferred as P4 data. 3. The access communication node according to claim 1, wherein the packet received from the data communication channel is IP on O
Identify whether the packet is an SI-TP4 packet or a standard IP packet and pass it to the OSI stack,
2. The method according to claim 1, wherein it is determined whether to pass the packet to a DP / IP stack.