KR100333735B1 - Method For The Accommodation Of The PNNI Routing Protocol In An ATM Switching System - Google Patents

Abstract

1. TECHNICAL FIELD OF THE INVENTION

The present invention relates to a method for accepting private network interface routing in an asynchronous transfer switching system.

2. Technical problem to be solved by the invention

An object of the present invention is to provide a method for accommodating a private network interface in an asynchronous transfer switching system.

3. Summary of the Solution of the Invention

The present invention provides a method for accepting a private network interface routing in an asynchronous transmission system switching system, comprising: extracting a setting link of a routing channel from a shape database; Confirming the existence of the initial link information in the shape database, and generating an initial link and recognizing the link number; Determining a type of the relay line matching module (TIM) of the interface module and assigning a port number to the link if the private network interface (PNNI) type is present; And a fourth step of allocating the link, synchronizing the database between the two nodes, and performing the abbreviated addressing process for the reach address.

4. Important uses of the invention

The present invention is used for private network acceptance in an asynchronous transfer switching system.

Description

Method for Accepting Private Network Interface Routing in Asynchronous Transfer Switching System {Method For The Accommodation Of The PNNI Routing Protocol In An ATM Switching System}

The present invention relates to a method for accepting a private network network (PNNI) routing in an asynchronous transfer switching system, and to a computer readable recording medium having recorded thereon a program for realizing the same. .

In general, to connect between two local networks in a public network, a private line of a public network or a direct physical link between private networks is used.

However, this method has difficulty in managing topology and exchanging information group of PNNI by considering two regions as different domains. There is also a limitation of local PNNI nodes and links or reachable address information.

In the public network, private network protocols are also adopted, and the characteristics of PNNI, namely, topology aggregation, quality of service (hereinafter referred to as "QoS") transmission, source-based routing, and internal / external Exchange of PNNI domains between public regions using interior / exterior reachable addressing, and PNNI network topology data by accepting PNNI end systems at public network nodes. It must be maintained dynamically so that PNNI network service can be performed smoothly in the public network and it is easy to manage hierarchical management.

In other words, with the advancement of Asynchronous Transfer Mode (ATM) technology, ATM network has become the foundation of communication network's backbone network. service is being deployed in a flexible and scalable structure to accommodate.

For this complex service, many exchange system companies including Cisco provide various protocols as public node ATM switching systems as nodes of connectivity network.

However, in the prior art as described above, there are many difficulties in accommodating various service networks in a public network, and due to the diversity of actual protocols, mapping between protocols or hardware interworking units, switches, and virtual path identifiers / virtual channels. There are additional problems, such as identifier resource utilization.

An object of the present invention is to provide a method for efficiently accepting PNNI routing in a public ATM network and a computer readable recording medium recording a program for realizing the same. .

1 is an exemplary configuration diagram of a public network asynchronous transmission system switching system that accommodates a private network interface routing protocol to which the present invention is applied.

2 is a diagram illustrating a private network interface routing function according to an embodiment of the present invention, which receives a relay line matching module link, synchronizes database synchronization between two nodes, and performs an abbreviated addressing process for an arrival address embedded in an address of a public network. Example flow chart.

3A or 3B is a flowchart illustrating an embodiment of performing a hello channel through a registered routing channel and registering a routing channel for performing a private network interface routing protocol according to the present invention.

4 is a flowchart illustrating an embodiment of receiving a hello packet from a neighbor node and performing database synchronization with a partner node according to the present invention.

Figure 5a or 5b is an embodiment flow diagram for the generation of a shortened address from the arrival address and the interworking with the number translation block in accordance with the present invention.

In order to achieve the above object, the present invention provides a method for accommodating private network interface routing in an asynchronous transmission system switching system, comprising: extracting a configuration link of a routing channel for performing a private network interface (PNNI) routing protocol from a shape database; Stage 1; A second step of confirming the existence of the initial link information in the shape database, generating an initial link and recognizing the link number if the link does not exist, and recognizing the link number immediately if the link exists; Determining a type of the relay line matching module (TIM) of the interface module and assigning a port number to the link if the private network interface (PNNI) type is present; And a fourth step of allocating a link, synchronizing a database between two nodes, and performing a condensed addressing process for the arrival address.

In addition, the present invention, in order to accommodate private network interface routing in the asynchronous transmission system switching system, in the configuration database to establish a link of the routing channel for performing a private network interface (PNNI) routing protocol in the switching system having a large capacity processor A first function of extracting; A second function of confirming the existence of initial link information in the shape database, creating an initial link and recognizing a link number if a link does not exist, and recognizing a link number immediately if a link exists; A third function of determining the type of the relay line matching module (TIM) of the interface module and assigning a port number to the link if the private network interface (PNNI) type is present; And a computer readable recording medium having recorded thereon a program for realizing a fourth function of allocating a link, synchronizing a database between two nodes, and performing a condensed addressing process for a destination address.

That is, in the present invention, a user of a broadband-to-integrated telecommunication network of a public network having a signaling network (for example, Signaling System No. 7) (hereinafter simply referred to as "signal network") as a method for efficiently accommodating a private network PNNI network in a public network. Unlike the protocol (ISDN User Part (hereinafter referred to as "ISUP") (hereinafter simply referred to as "B-ISUP") protocol, PNNI is routed to a dedicated virtual channel (hereinafter referred to as "VC"). By performing signaling, different types of internetworks and internal networks are constructed.

Accordingly, in the present invention, the PNNI network is serviced from the public network to the transit network, and information exchange between the betting regions PNNI domain through the public network and the PNNI end system are accommodated at the public network node. Efficient acceptance method considering common processing parts, number translation, and resource management throughout public network exchange system to make PNNI network service smoothly in public network by making PNNI network topology data dynamic and to make hierarchical management easily To present.

Also, consider the following three points for efficient PNNI protocol.

First, link recognition to recognize neighboring switch nodes from the PNNI Hello protocol allows the link to be used by the trunk line matching module (TIM), which is the access module of the switching system in the network for implementation independent of B-ISUP of the public network. The configuration type is assigned to each trunk line matching module (TIM) type to induce an independent approach.

In other words, the hardware configuration is a protocol-dependent trunk line matching module (TIM), which facilitates not only resource management but also routing, signaling channel allocation, and data channel allocation, and enables consistent maintenance in terms of system configuration management.

Secondly, if the routing channel is registered according to the above TIM configuration (VPI = n / VCI = 18), this means that signal traffic is a major part of the MTP-3b function of the signaling network for B-ISUP realization of the public network. No signal routes, no signal links, no signal network management, etc., and B-ISUP is used instead of routing tables for hop-by-hop static routing where routing is determined at each node. PNNI requires a topology data table for dynamic source-routing.

Third, the PNNI is an address of an asynchronous transmission end system based on the International Organization for Standardization (hereinafter referred to as "ISO") Network Service Access Point (hereinafter referred to as "NSAP"). ATM End System Address (hereinafter referred to as "AESA") is used.

It consists of a 13-byte prefix, a 6-byte End System Identifier (hereinafter referred to as "ESI"), and a 1-byte selector.

The 13 bytes reflect the PNNI topology, which can be expressed as the bit length of the level indicator representing the layer. B-ISUP, on the other hand, is defined as a public telephone numbering system based on native E.164, recommended by the International Telecommunications Advisory Committee (ITU-T). The complete mapping as a method of acceptance within an exchange of these two numbering systems is meaningless.

In other words, it is difficult to directly convert the address of the PNNI bit string system to the field system of the B-ISUP (CC: country code, TC: trunk code, OFC: office code, SN: subscriber number). Because.

In light of this, independent number allocation based on network design is required for fast implementation and economics. That is, the number translation block in the exchange performs branching of the corresponding number to the B-ISUP and PNNI in the registered number table.

Hereinafter, a preferred embodiment of the present invention will be described in detail with reference to FIGS. 1 to 5.

1 is an exemplary configuration diagram of a public network asynchronous transmission system switching system that accommodates a private network interface routing protocol to which the present invention is applied. Basically, the central switching subsystem (hereinafter referred to as "ACS") 110 is illustrated. And a local exchange switching subsystem (hereinafter referred to as "ALS") 120.

The ACS 110 is composed of a central switch (hereinafter referred to as "CS") 111 and an operation and maintenance processor (hereinafter referred to as "OMP") 112.

ALS 120 is a Subscriber Interface Module (hereinafter referred to as "SIM") 121, a self-routing switch module (Local Switch: referred to as "LS") 122, call connection A control processor (Call Connection Control Processor) (hereinafter referred to as "CCCP") 123, and a trunk line interface matching module (Trunk Interface Module: referred to as "TIM") (124).

The ALS 120 includes a TIM type for PNNI to accommodate the PNNI protocol. Similar to the TIM type of B-ISUP, this TIM is connected to the switch network of ALS through an Inter Module Interface (hereinafter referred to as "IMI"), and a virtual path to the CCCP 123 to perform the PNNI protocol function. Identifier (Virtual Path Identifier: "VPI") / Virtual Channel Identifier ("VCI") Private Network Interface for Channel Matching Asynchronous Transfer Mode Data Adaptation Layer (PNNI ATM Adaptation Layer: "" PAAL ") and an internal channel interface (hereinafter referred to as" ICI ") for internal VPI / VCI conversion.

In the OMP 112 of the ACS 110, CONFiguration data processing (hereinafter referred to as "CONF") to hold initial shape data to accommodate the PNNI routing function and processing input data from an operator, PNNI routing packet type Encoding / decoding packets (Packet Encoding / Decoding: "PED") to encode / decode data according to the above, Hello data processing ("HEL") for processing Hello packets, and public network It consists of NUMBer branching processing (hereinafter referred to as "NUMB") that performs number translation in the ATM switching system.

ACS 110 performs system-wide maintenance and self-routing switching and synchronizer functions using CS, the same switch element as ALS.

ALS 120 is mainly responsible for the call processing function and the call connection is made by the communication between the originating ALS and the destination ALS. A single stage LS 122 is embedded, and is comprised of a SIM 121 and a TIM 124 for private / public network subscriber line matching and private / public network trunk line matching.

2 is a diagram illustrating a private network interface routing function according to an embodiment of the present invention, which receives a relay line matching module link, synchronizes database synchronization between two nodes, and performs an abbreviated addressing process for an arrival address embedded in an address of a public network. Example flow chart.

First, a set link of a routing channel for performing the PNNI routing protocol is extracted from the shape database (201).

The existence of the initial link information is confirmed in the configuration database (202). If the link exists, the following is performed. If the link does not exist, the terminal continuously waits for input from the operator (203).

The operator creates an initial link from the Human-Machine Interface (hereinafter referred to as "HMI") (204), recognizes the ALS, the interface module (IM), and the link number (205) to determine the interface module (IM). The TIM types are compared (206).

If the TIM type is PNNI type, the port is assigned to the link (207) and used as an identifier for routing packet transmission.

When the link is created, the link is registered (208), and if two nodes belong to the same peer group by the Hello protocol, processing for matching the dynamic topology data synchronization 209 is performed. When the information on the arrival address is processed, address summarization of the arrival address is performed (210).

FIG. 3A or FIG. 3B illustrate Routing Connection Control (hereinafter, referred to as "RCC") routing channel registration for performing a private network interface routing protocol according to the present invention, and performs a Hello protocol through a registered routing channel. One embodiment is a flow chart.

First, an executable routing link and a channel are transmitted to the PAAL (301).

The PAAL determines whether the information is channel registration information or release information (302). If the channel registration information is the channel registration information, the PAAL performs VPI / VCI internal conversion (303).

After internal conversion, it is requested that this channel can actually be registered on the TIM board (304). If a response comes from the call library block (305), then the response is retrieved (306). If registration is not possible, retry (307). If possible, the HEL will be notified of the link registration confirmation (308).

The registered link information is stored in an internal data list for later exchange of PNNI Topology State Element (PTSE) information (309). Link information is reported to the PED (310) for the provision of an internal packet data transmission path.

When a service access point identifier (ID) according to the ALS number, the interface module (IM) number, and the link number (hereinafter referred to as "SAP-ID") is allocated (311) and the SAP-ID is allocated from the PED Upon receiving this (312), in the hello processing process, when a link is registered, it means that a path through which a packet can be transmitted is now established, so that the link is finally notified (313) and an initial hello packet is configured. (314).

According to the Finite State Machine (hereinafter referred to as "FSM") of the Hello protocol, the initial down state of the link is changed to Attempt state (315), and the configured packet is transmitted to the PED. (316) It is changed to an internal packet data unit (hereinafter referred to as "PDU") and transmitted to PAAL. (317) PAAL should attempt to match this data with TIM for transmission to the other node. to be.

4 is a flowchart illustrating an embodiment of receiving a hello packet from a neighbor node and performing database synchronization with a partner node according to the present invention.

First, when a Hello packet is received from a neighbor node (relative node) (401), the relative node ID (ID) is extracted from this initial packet (402) and the relative port identifier (ID) is extracted from this packet ( 403) Store this as routing database and local data.

Based on the data received from the counterpart node, the Hello packet of the node is configured, and information including the peer group ID of the node is transmitted again (404). The peer group ID and the peer group priority are extracted from the packet received from the neighbor node (405), and the peer group ID (ID) is compared with the peer group (406).

If it is the same peer group (407), since the actual database synchronization needs to be performed, a data summary packet (hereinafter, referred to as "DSP") is configured (409).

When receiving the DSP from the partner node (410), the partner node requests detailed data of the PNNI Topology State Element (hereinafter referred to as "PTSE") included in the data summary and receives the information. 412). This operation is performed until the summary PTSE information is received so that the database is synchronized between the two nodes (411).

FIG. 5A or FIG. 5B is a flowchart illustrating an embodiment for generating a shortened address from an arrival address and interworking with a number translation block according to the present invention.

First, the reach address is stored in the routing database. Initially, addressable address summarization is performed for the reach address of the own node. After that, due to the exchange of PTSE, the reach address of the partner node begins to be shortened.

For address abbreviation, the destination address is extracted from the routing database (501), and the destination address exists in the database (502), and if it does not exist, the operator waits for input (503).

Inputting the arrival address to my node from the operator (504) obtains my node ID and arrival address by default capability (505) and compares the node ID and arrival address by bit stream. (506) If the node ID is large, a bit or less according to the node ID is truncated at the arrival address (507) and stored in the address abbreviation list for number translation and PTSE information exchange for call processing (508). ).

The abbreviated address generates a PTSE header for the exchange of PTSE information to neighbor nodes (509), searches the periodic abbreviated address database (510), and reports the dynamic database arrival address to the number translation block (511).

After receiving a response from the number translation block that the registration has been successfully performed (512), there must be continuous exchange of PTSE information for maintaining the dynamic arrival address for maintaining the dynamic arrival address (513).

The present invention described above is capable of various substitutions, modifications, and changes without departing from the spirit of the present invention for those skilled in the art to which the present invention pertains, and the above-described embodiments and accompanying It is not limited to the drawing.

As described above, the present invention not only efficiently accommodates the service of the PNNI from the public network to the transit network by considering common processing parts, number translations, resource management, etc. throughout the public network switching system, but also the PNNI at the public network node. By accommodating the end system, the PNNI network topology data is dynamically maintained, so that the PNNI network service can be performed smoothly in the public network and the hierarchical management can be easily performed.

Claims (6)

A method for accepting private network interface routing in an asynchronous transmission switching system, Extracting, from a shape database, a configuration link of a routing channel for performing a private network interface (PNNI) routing protocol; A second step of confirming the existence of the initial link information in the shape database, generating an initial link and recognizing the link number if the link does not exist, and recognizing the link number immediately if the link exists; Determining a type of the relay line matching module (TIM) of the interface module and assigning a port number to the link if the private network interface (PNNI) type is present; And Fourth step of assigning links, synchronizing database between two nodes, and performing abbreviated addressing process for reach addresses A method for accommodating private network interface routing in an asynchronous transfer switching system including a. The method of claim 1, The fourth step, A fifth step of registering the link when the link is created; A sixth step of synchronizing dynamic topology data when two nodes belong to the same peer group; And Step 7 of performing address shortening of the destination address when the information on the destination address is processed. A method for accommodating private network interface routing in an asynchronous transfer switching system including a. The method of claim 2, The fifth step, An eighth step of determining whether the information about the executable routing link and the channel is channel registration information; if the channel registration information is the channel registration information, performing the virtual path identifier / virtual channel identifier (VPI / VCI) internal conversion; ; A ninth step of judging whether the channel can actually be registered on the TIM board after internal conversion, retrying if registration is impossible, and confirming link registration if registration is possible; A tenth step of storing the registered link information in an internal data list and allocating a service access point identifier-ID according to the link number; And Construct an initial hello packet, change the initial down state of the link to Attempt state according to the finite state device (FSM) of the hello protocol (315), and with the relay line matching module (TIM). 11th step to try matching A method for accommodating private network interface routing in an asynchronous transfer switching system including a. The method of claim 3, wherein The sixth step, A twelfth step of extracting and storing a partner node ID and a partner port ID from the initial packet when the hello packet is received from the partner node; It constructs Hello packet of my node based on the data received from the other node and sends back information including peer group ID of its own node, and determines whether peer group ID is the same peer group from the packet received from neighbor node. A thirteenth step; A fourteenth step of forming a data summary packet (DSP) if the peer group is the same as the determination result of the thirteenth step; And Receiving a data summary packet (DSP) from a counterpart node, receiving a detailed data of a private network interface topology status element (PTSE) included in the data summary from a counterpart node to synchronize the database between the two nodes; A method for accommodating private network interface routing in an asynchronous transfer switching system including a. The method according to any one of claims 2 to 4, The seventh step, Extracting a destination address from the routing database for address reduction and determining whether my node ID is greater than the destination address; As a result of the determination of the sixteenth step, if the node ID is large, cutting a bit or less according to the node ID from the arrival address and storing it in the address abbreviation list; An eighteenth step of generating a private network interface topology status element (PTSE) header, searching the periodic abbreviated address database and reporting the dynamic database arrival address to the number translation block; And A nineteenth step of receiving a response from the number translation block that the registration is successful and maintaining the dynamic destination address A method for accommodating private network interface routing in an asynchronous transfer switching system including a. In order to accommodate private network interface routing in an asynchronous transmission switching system, a switching system having a large processor, A first function of extracting, from a shape database, a configuration link of a routing channel for performing a private network interface (PNNI) routing protocol; A second function of confirming the existence of initial link information in the shape database, creating an initial link and recognizing a link number if a link does not exist, and recognizing a link number immediately if a link exists; A third function of determining the type of the relay line matching module (TIM) of the interface module and assigning a port number to the link if the private network interface (PNNI) type is present; And A computer-readable recording medium having recorded a program for realizing a fourth function of allocating a link, synchronizing a database between two nodes, and performing a short addressing process on a destination address.