KR100265075B1 - How to Configure a Logical Backbone Link - Google Patents

Abstract

A method of configuring a logical backbone link is described. The method comprises the steps of establishing a logical backbone link between two or more networks of the same system and networks of other systems, and a logical backbone if two or more networks of the same system and a network of other systems are desired. It comprises the steps of sending and receiving routing information, signaling data, user traffic, network management data and the like using a link.

Description

How to Configure a Logical Backbone Link

The present invention relates to a method for constructing a logical backbone link. In particular, when two or more asynchronous transfer mode networks including the same system are connected through different asynchronous transfer mode networks, it is as if one network is connected. It is about how to configure a logical backbone link to work like this.

In general, a backbone in one network carries routing information, signaling data, user traffic, network management data, and the like. It acts as a medium to see from the point of view.

Hereinafter, a description will be given with reference to FIG. 1 to which the prior art is attached.

Conventionally, when two asynchronous transmission mode networks 20a and 20b of the same system are connected to each other with an asynchronous transmission mode network 30 of different systems in the middle for geographical reasons or for some reason, the physical backbone link as shown in FIG. Linked via (Physical Backbone Link).

However, when a network is connected through a physical backbone link as described above, routing related information, signaling data, user traffic, and network management information cannot be directly exchanged, and thus cannot be viewed as the same network.

Therefore, the two networks are treated as completely independent networks, managing each network separately, and having their respective network management systems (NMSs) 10a and 10b.

As described above, when two or more asynchronous transmission mode networks of the same system are connected through different asynchronous transmission mode networks and the conventional physical backbone link, one network management system for each network is required. There is a problem that costs as much.

In addition, there is a problem that can not use the network resources efficiently because it must be treated as a completely different separate network.

Accordingly, the present invention was devised to solve the above problems, and establishes a virtual path (VP) connection through an asynchronous transmission mode network composed of different systems, through which at least two networks are separated by routing information. It is an object of the present invention to provide a method for constructing a logical backbone link that manages and handles signaling, data, and user traffic as if it is a single directly connected network.

The above and other objects and novel features of the present invention will become more apparent from the following detailed description of the invention and the accompanying drawings.

1 is a connection diagram of two identical asynchronous transmission mode networks and another asynchronous transmission mode network according to the present invention.

2 is a connection diagram of two identical asynchronous transmission mode networks and another asynchronous transmission mode network according to the present invention.

3 is a diagram showing a configuration example of a logical backbone link according to the present invention;

4 is a process diagram for configuring a logical backbone link in accordance with the present invention.

<Description of the symbols for the main parts of the drawings>

10a, 10b, 100: network management system

20a, 20b, 110a, 110b: Asynchronous transfer mode network consisting of the same system

30, 120: Asynchronous transmission mode network composed of a system different from the 20a, 20b, 110a, 110b

200: logical backbone link

210: Configuration task

220: call control task

230: routing task

240: Administrative tasks

250: signaling task

In order to achieve the above object, a preferred embodiment of the logical backbone link configuration method according to the present invention,

Establishing a logical backbone link between two or more networks of the same system and networks of other systems; And

When two or more networks composed of the same system and a network composed of other systems are to be connected, routing and routing information, signaling data, user traffic, and network management data are transmitted and received using the logical backbone link.

In this embodiment, the component of the logical backbone link provides a path through a virtual path connection of another network, a logical backbone link that allocates a virtual path identifier, and whether the connected backbone link is a physical backbone link or a logical backbone link. A task that establishes awareness, in the case of a logical backbone link, a configuration task that assigns the corresponding virtual path identifier, manages call settings when all calls are connected, and virtualizes the persistent virtual path for calls that connect through the logical backbone link. Call control tasks that assign path identifiers, routing tasks that send and receive routing-related information, determine routing settings when calls are required, administrative tasks that send and receive network management information, and branch data to required tasks, and physical Maintain backbone links like backbone links, It is preferably composed of a signaling task that is responsible for delivering signaling data.

Configuring a logical backbone link by configuring a permanent virtual path connection to another network, assigning a virtual path identifier, and informing the configuration task of the systems to be connected via the logical backbone link by informing the corresponding port and virtual path identifier. It is preferable to include.

It is preferable that the signaling task having learned from the configuration task that the corresponding port is set as a logical backbone link comprises configuring a signaling stack on the corresponding port, and configuring a signaling channel with an assigned virtual path identifier and a virtual channel identifier. .

It is preferable that the signaling channel uses channel 5 designated as a signaling channel in the ATM forum.

Once the logical backbone link configuration is complete, it is preferable that the routing tasks further include routing information to and from each other.

If a call is required, the routing task of the system from which the call originated preferably further comprises establishing an entire path to the end system.

The entire path to the end system is preferably set according to service quality, traffic load condition, connection priority, and the like.

Preferably, the call control task further includes assigning a virtual path identifier and a virtual channel identifier on the logical backbone link when the corresponding call is to be connected through a logical backbone link.

The virtual path identifier is assigned to a virtual path identifier of a logical backbone link, and the virtual channel identifier preferably assigns a virtual channel identifier value not used in the virtual path identifier.

The present invention implements and uses another intermediate asynchronous transmission mode network as a logical backbone link when two or more networks composed of the same system are connected with an asynchronous transmission mode network composed of other systems in the middle.

In this way, two or more networks can directly exchange routing information, management data, and the like with each other, so that they can be managed and handled like a single network.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

FIG. 2 is a diagram illustrating a configuration in which two networks of the same system are connected to each other through a logical backbone link.

As shown in FIG. 2, if two networks 110a and 110b use a logical backbone link when connected through different asynchronous transmission mode networks 120, routing information, management data, and the like may be exchanged with one network. Two networks can operate as if it is a single network, it is possible to manage two networks with one network management system (100).

The logical backbone link having the above function is composed of the following components, which are illustrated in FIG.

The logical backbone link 200 provides its path through a virtual path connection of another asynchronous transmission mode network and assigns a virtual path identifier (VPI).

The configuration task 210 is a task for setting whether the connected backbone link is a physical backbone link or a logical backbone link, and allocates a corresponding virtual path identifier in the case of the logical backbone link.

The Call Control Task (CCT) 220 is a task that manages call setup when all calls are connected. The Call Control Task (CCT) 220 manages the call setup through the logical backbone link of the corresponding permanent virtual path (PVP). Assign a virtual path identifier.

Routing task (RT) 230 is a task for sending and receiving routing-related information, and serves to determine the route (Route) when a call is requested.

The management task (MT) 240 exchanges network management information and branches data to necessary tasks.

The signaling task (ST) 250 maintains a backbone link like a physical backbone link and is responsible for transferring signaling data between connected systems.

The present invention composed of the above components operates as follows.

In order to configure two logical backbone links as shown in FIG. 2 to manage two or more networks as if they are one network, a permanent virtual path connection (PVP) is first configured to another asynchronous transmission mode network and a virtual path identifier is assigned.

In addition, a port and a virtual path identifier for a configuration task of systems to be connected through a logical backbone link are informed to configure a logical backbone.

When the signaling task learns that the corresponding port is set as a logical backbone link from the configuration task, the signaling task configures a signaling stack on the corresponding port, and configures a signaling channel with an assigned virtual path identifier and virtual channel identifier of 5.

This is because the channel designated signaling in the ATM forum is 5. And, the signaling stack of the logical backbone link is no different from the physical backbone link except that it uses the assigned virtual path identifier when configuring the signaling channel.

After the logical backbone link configuration is completed, the routing tasks exchange routing information with each other to see the network conditions as if they were on the same network.

When a call is requested, the routing task of the system where the call originates establishes the entire path to the end system according to the quality of service (QOS), traffic load status, connection priority, and the like.

When the corresponding call is to be connected through the logical backbone link, the call control task allocates a virtual path identifier and a virtual channel identifier (VCI) on the logical backbone link.

At this time, the virtual path identifier is assigned to the virtual path identifier of the logical backbone link, and the virtual channel identifier assigns a virtual channel identifier value not used in the virtual path identifier.

The operation process will be described in detail with reference to FIG. 4.

To configure a logical backbone link, you first configure a permanent virtual path connection (PVP) on another network and assign a virtual path identifier.

The management task 240 informs the configuration task 210 of a virtual path identifier value connected through a different network from a port number for configuring a logical backbone link at its node (s1).

The configuration task 210 enables the signaling task 250 to configure the signaling task 250 associated with the Network Node Interface (NNI) on that port and maintain the signaling link.

The signaling task 250 required to configure the logical backbone link configures a signaling stack on the corresponding port and maintains the signaling link according to the protocol.

In this case, when the signaling stack connected to the opposite port and the protocol match each other and transmit data, the routing task 230 informs the routing task 230 (s2).

When the logical port is configured as a logical backbone link and becomes active to exchange data with the other port, the routing task 230 transmits its routing information to the other routing task through the signaling task 250. 230).

Then, the routing information data of another node from the other routing task 230 is updated in its own database. This allows you to grasp the situation of other networks as if it were your own network (s3).

In the case of the permanent virtual connection, the call is initiated from the network management system, and transmits the data required for the permanent virtual connection to the call control task 220 through the management task 240 (s4).

Permanent virtual connection is received from the management task 240, and in the case of Switched Vir-tual Connection (SVC) from the user's protocol stack (Protocol Stack), the call control task 220 receives the connection request The routing task 230 asks for route information to the corresponding destination.

In addition, when the port to which the call is to be proceeded is a logical backbone link, the virtual path identifier among the virtual channel connection identifier (VCCI) values to be used through the backbone link is assigned by assigning a virtual path identifier used by the logical backbone link to proceed with the call. (S5, s6).

The management data destined for another node is transmitted to the signaling task 250 through the management task 240, which is transferred to the management task 240 of the node and used to manage the node. This allows you to manage the systems of other networks as if they were nodes of your own network (s7).

While the invention is susceptible to various modifications and alternative forms, the disclosure thereof has been described with reference to specific embodiments only.

It is to be understood, however, that the present invention is not limited to the specific forms referred to in the specification, but rather that the invention is intended to cover all modifications, equivalents, and substitutions falling within the spirit and scope of the invention as defined by the appended claims. It should be understood to include.

In the present application operating as described above, the effects obtained by the representative ones of the disclosed inventions will be briefly described as follows.

When two or more asynchronous transfer mode networks using the same concept backbone are connected through different asynchronous transfer mode networks, and if the logical backbone link described above is used, between each asynchronous transfer mode network using the same concept backbone, It is economical because it can manage routing information, management data, etc. like a system in the same network and manage the whole as one network.

In addition, routing information can be sent and received according to the quality of service, traffic load, and connection priority, so that the call can be routed efficiently so that network resources can be efficiently used.

Claims (10)

Establishing a logical backbone link between two or more networks of the same system and networks of other systems; And In order to connect two or more networks of the same system and a network of other systems, the logical backbone includes a step of exchanging routing information, signaling data, user traffic, network management data, etc. using the logical backbone link. How to configure link. The apparatus of claim 1, wherein the components of the logical backbone link are: A logical backbone link providing the path through a virtual path connection of another network and assigning a virtual path identifier; A configuration task for setting whether the connected backbone link is a physical backbone link or a logical backbone link, and assigning a corresponding virtual path identifier if the backbone link is a logical backbone link; A call control task that manages call setup when all calls are connected, and assigns a virtual path identifier of the permanent virtual path to a call that is connected through a logical backbone link; A routing task for exchanging routing information and determining routing establishment when a call is requested; An administrative task of exchanging network management information and branching data into necessary tasks; And And a signaling task that maintains the backbone link, such as a physical backbone link, and is responsible for transferring signaling data between connected systems. The method of claim 1, wherein the method is Establishing a permanent virtual path connection to another network and assigning a virtual path identifier; And And configuring the logical backbone link by informing the configuration task of systems to be connected via the logical backbone link by informing the corresponding port and virtual path identifier. 4. The method of claim 3, wherein the signaling task having learned from the configuration task that the corresponding port is set as a logical backbone link configures a signaling stack on the corresponding port, and configures a signaling channel with an assigned virtual path identifier and virtual channel identifier. Further comprising, the logical backbone link configuration method. The method of claim 4, wherein the signaling channel uses channel 5 designated as a signaling channel in an ATM forum. 5. The method of claim 4, further comprising, when the logical backbone link configuration is complete, the routing tasks sending and receiving routing information to each other. 7. The method of claim 6, further comprising: if a call is requested, the routing task of the system from which the call originated establishes an entire path to the end system. 8. The method of claim 7, wherein the entire path to the end system is established in accordance with service quality, traffic load conditions, connection priorities, and the like. 8. The method of claim 7, further comprising the step of a call control task assigning a virtual path identifier and a virtual channel identifier on the logical backbone link when the call is to be connected through a logical backbone link. 10. The method of claim 9, wherein the virtual path identifier is assigned to a virtual path identifier of a logical backbone link and the virtual channel identifier assigns a virtual channel identifier value that is not used within the virtual path identifier.