KR100317121B1 - Method of PNNI node management in ATM switching system - Google Patents

Abstract

The present invention relates to a private network-network interface (PNNI) node management method in an ATM switching system.

The present invention comprises a first step of constructing a database for managing PNNI nodes in a running ATM switching system comprising a node information database, a number analysis database, and a reachable address database; A second step of configuring node information to configure a node, registering the node information in a node information database, and instructing a routing protocol to be reflected in a network topology; And removing the node information from the node information database for removing any node in the PNNI network and instructing the routing protocol to be performed to be reflected in the network topology.

According to the present invention, when a new node is configured or a node is removed during system operation, the system administrators can construct and remove the node through a simple command without building new software, thereby dynamically constructing topology information about the network. Operators can easily manage node and PNNI network related data.

Description

{Method of PNNI node management in ATM switching system}

The present invention relates to a PNNI node management method in an ATM switching system.

In PNNI node management, newly defined node information according to configuration of node for PNNI function or addition of node ID of existing node during system initialization and operation, and node information removed when any node removal occurs during PNNI network operation, PNNI node management is a function that dynamically reflects PNNI network topology information through Routing Protocol. PNNI node management is more efficient when a new node is configured or removed during system operation. There is a need for a method, but there is currently no method for managing a PNNI node and a PNNI network.

The present invention devised by the necessity as described above allows system operators to configure and remove nodes through simple commands without dynamically producing new software in the event of fluctuations in nodes during system operation. Its purpose is to provide a method for managing PNNI nodes that enables the construction of topology information to efficiently manage data related to nodes and PNNI networks.

1 is a subsystem diagram of an ATM switching system required for implementing the present invention.

2 is an overall flowchart of a PNNI node management method according to the present invention;

Figure 3a to 3c is a database configuration implemented in the present invention

4A through 4D are flowcharts illustrating a PNNI node configuration according to the present invention.

5A-5D are flowcharts of PNNI node removal in accordance with the present invention.

In order to achieve the above object, the present invention provides a method for managing a PNNI node in an ATM switching system including an ATM local switching subsystem (ALS) and an ATM central switching subsystem (ACS). A first step of constructing a database for managing a PNNI node into a node information database, a number analysis database, and a reachable address database; A second step of configuring node information to configure a node, registering the node information in a node information database, and instructing a routing protocol to be reflected in a network topology; And removing the node information from the node information database for removing any node in the PNNI network and instructing the routing protocol to be reflected in the network topology.

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

1 is a configuration diagram of an ATM switching system to which the present invention is applied, which is distributed in units of ATM Local Switching Subsystem (ALS) and interconnected by an ATM Central Switching Subsystem (ACS). Form.

In this case, the transport network includes an access switch network module (ASNM) in the local switching subsystem, an interconnection switch network module (ISNM) in the central switching subsystem, a switch network and a central switching subsystem in the local switching subsystem. It consists of link interface modules (LIMs) between the switch networks and interface modules (IMs) for subscriber / relay lines.

In addition, the control network includes various software for performing various call / connection control, signaling protocol processing, subscriber network link resource management, network node matching link resource management, internal switch link resource management, station number translation, link and subscriber service profile data processing, and the like. Call and Connection Control Processor (CCCP), which handles call / connection control functions including modules, and system operation and maintenance functions, call number translation, route control, route and number data processing. It consists of an Operation and Maintenance Processor (OMP), which handles the operation maintenance control functions including several software modules, and inter-processor communication is performed through a switch network.

PNNI node management according to an embodiment of the present invention in such an ATM switching system, as shown in Figure 2, to configure the database to effectively manage the PNNI node and performs the corresponding function whenever a node configuration or node deletion occurs This is done by performing procedures.

3A to 3C show a node information database 100, a number resolution database 110, and a reachable address database 120 implemented in the present invention, respectively.

The node information database 100 has a sequential structure of the number of nodes that can be accommodated in the system. The node number becomes a key to access the corresponding tuple 108. The node No 101, the node Id 102, and the Peer Group Id (103), ATM End System Address (AESA, 104), Level Id (105), Leader Priority (106), Nodal flag (107), and the like.

The number analysis database 110 is a dual linked list structure in which the digits of each node number are linked to each other, and includes a node number link point field 111, a node number digit field 112, a digit status field 113, and a back link point. Field 114, the next called party link point field 115, and the number information 116, the node number link point and the node number digit become keys to access the corresponding tuple 117.

The reachable address database 120 has a sequential structure as long as the reachable address base is acceptable to the system, and the reachable address becomes a key to access the corresponding tuple 127, and the reachable address prefix 121 and the reachable address prefix length. It consists of information such as 122, Port Id 123, Level Id 124, Node Id 125, and Scope 126.

4A through 4D are flowcharts illustrating a process of configuring a new node according to a node configuration request.

To explain this, first, when receiving a PNNI node configuration request (S201), the input parameters (Level Id, Address Type, Address, Priority, Nodal flag, etc.) are sorted into a type suitable for the system (S202) and the availability of data is examined ( S203).

If all of the input parameters are valid, the result of the investigation (S203) is stored for use in performing the node generation function (S204) and a node sequence number is generated and assigned to manage the generated node (S205).

Thereafter, in order to configure node information necessary for node generation using the input parameters, an address type is first examined and analyzed (S206 and S207), and AFI (Authority and Format Identifier) is defined for each address type. (S208 to S210)

That is, as a result of analyzing the address type in steps S206 and S207, as a result, if the address type is E.164, AFI is 45 (S208), and if the address type is DCC (Data Country Code), the AFI is 39. (S209), in the case of ICD, AFI is defined as 47 (S210).

Next, a 20-octet ATM End System Address (AESA) is constructed using the defined AFI and Address (Prefix, End System Identifier (ESI)) (S211).

Then, after generating node Id of 44 strings, which is the nucleus of the node information, using Level Id and AESA (S212), a Peer Group Id is generated using AESA and Level Id (S213). Peer Group Id consists of Prefixes of Level Id and AESA. Peer Group Id consists of Prefix having the length of Bit of Level ID among AESA Prefix (13 octets).

Next, nodal Flag is configured. nodal Flag consists of an 8-bit string, of which bits 1 to 3 are reserved and bits 4 to 8 are used. If the value of the variable is True by using the input nodal parameter, the bit is set to 1, and if it is false, it is set to 0 to configure a nodal flag of 8 bits (S214).

Once the node information is configured, the configured information should be stored in the node information database. When accommodating one node in a single layer, the node information database is managed with Level Id. To store in the node information database, the corresponding tuple of the node information database is found using Level Id (S215), and the tuple is already in use. If it is already in use, the result message is arranged into a pre-registration (S217), and the execution error message is output and terminated (S218).

If the result of the investigation in step S216 is that the corresponding tuple is not used, the configured node information is stored (S219).

Subsequently, the node address is interworked with the number translation routine to set SVCC Switched Virtual Channel Connection Routing Control Channel (RCC). That is, the node address is registered in the number translation database.

To this end, first find the corresponding tuple of the number translation database using AESA (S220), and examine the state of the number (node, called number) (S221) (S222). If it is already registered with the node address (already), the result message is arranged in the existing registration (S223), and the execution error message is output and terminated (S224).

If the digit status check result in step S222 is registered with the general subscriber number, the result message is summarized into the general subscriber number (S225), and the execution error message is output and terminated (S226).

As a result of the digit status check in step S222, if not defined, the AESA is registered as a node address in the number translation database (S227), and a routing protocol with the power is performed (S228).

Thereafter, the success output message is arranged (S229), and the message is output and terminated (230).

5A through 5D are flowcharts illustrating a process of deleting a registered node according to a node deletion request.

Upon receiving the PNNI node removal request (S231), the input parameters (Level Id, Address Type, AESA) are arranged into a type suitable for the system (S232) and the availability of the data is checked (S233).

If all of the input parameters are valid, the search result (S233) is stored for use in performing the node deletion function (S234).

Subsequently, in order to configure the node Id for deleting the node by using the input parameter, an address type is first analyzed and analyzed (S235 and S236) to define an AFI for each address type (S237 to S239).

That is, as a result of examining and analyzing the address type in steps S235 and S236, as a result, if the address type is E.164, AFI is 45 (S237), if the address type is DCC, AFI is 39 (S2238), and ICD. In this case, AFI is defined as 47 (S239).

Next, a 20-octet AESA is configured using the defined AFI and Address (Prefix, ESI) (S240), and node Id of 44 strings, which is a nucleus of node information, is generated using Level Id and AESA (S241).

When the node Id is generated, the corresponding tuple of the node information database is found by using the node Id to delete the corresponding node information stored in the node information database (S242).

If the tuple is not already used, that is, it does not exist (S243), and if it does not already exist, the result message is sorted into deletion (S244), and the execution error message is output and terminated (S245).

As a result of the investigation in step S242, if the corresponding tuple is used, node information is deleted (S246).

Subsequently, the corresponding tuple of the number analysis database is found by using AESA to delete the node address registered in the number analysis database (S247), and the state (node, called number) of the number is examined (S248) and the digit state is checked. (S249).

If the node address has already been deleted (not assigined), the result message is arranged to be deleted (S250), and the execution error message is output and terminated (S251).

In step S249, if the digit status check result is registered with the general subscriber number, the result message is summarized with the general subscriber number (S252), and a performance error message is output and terminated (S253).

As a result of the digit state check in step S249, if it is registered as a node address, the node address is deleted (S254), and a reachable address using the node address to delete an address registered as a reachable address to the host system. (S255). Using the created reachable address, the corresponding tuple of the reachable address database is found and deleted (S256), and a routing protocol with the power is performed (S257).

After that, the success output message is sorted out (S258), and the message is outputted and terminated (S259).

As described above, the present invention enables system administrators to configure and remove nodes through simple commands without automatically creating new software when new nodes are configured or removed. By constructing the system, operators can easily manage node and PNNI network related data.

The technical spirit of the present invention has been described above with reference to the accompanying drawings, but this is by way of example only and not intended to limit the present invention. In addition, it is obvious that any person skilled in the art can make various modifications and imitations without departing from the scope of the technical idea of the present invention.

Claims (10)

A method for managing a PNNI node in an ATM switching system distributed in a local switching subsystem (ALS) unit and interconnected by a central switching subsystem (ACS), As a database for managing PNNI nodes, a node information database is configured in a sequential structure by the number of nodes that can be accommodated in the system, a number analysis database is configured in a double linked list structure, and a reachable address database is configured in a sequential structure. process; A second step of configuring node information for node configuration according to a new node configuration request, registering the node information in a node information database, and instructing a routing protocol to be reflected in a network topology; And And removing the node information from the node information database according to a request for removing a node in the PNNI network, and instructing execution of a routing protocol to be reflected in the network topology. The method of claim 1, The second process, When the node configuration request is made, the input parameters (Level Id, Address Type, Address, Priority, Nodal flag, etc.) are sorted into the correct type for the system, and the useful data is stored as the type necessary to perform the node configuration function. A first step of generating and assigning a node sequence number for managing the node afterwards; A second step of configuring new node information and performing registration in the node information database; And And registering a node address in a number translation database and performing a routing protocol. The method of claim 2, The second step, Investigating and analyzing an address type; Defining an AFI (Authority and Format Identifier) according to the address type, and configuring a 20 octet AESA using the defined AFI and Address (Prefix, ESI); Generating a node Id using Level Id and AESA; Creating a Peer Group Id using AESA and Level Id; Configuring a nodal flag by setting the corresponding bit to 1 when the value of the variable is True using the input nodal parameter and setting it to 0 when false; And A method for managing a PNNI node in an ATM switching system, comprising storing the configured node information in a node information database. The method of claim 3, Storing the configured node in a node information database, Finding a corresponding tuple of the node information database using Level Id; Examining whether the tuple is already in use (exists); And In the above step, if the tuple is already in use as a result of the registration of the result message to the pre-registration, and outputs an error message and then terminates, otherwise it comprises the step of registering the configured node information in the node information database ATM How to manage PNNI nodes in a switching system. The method of claim 2, The third step, Checking the digit state by finding the corresponding tuple of the number translation database using the AESA and examining the state of the number (node, called number); As a result of digit status check, if the node address is registered, sorting the result message into pre-registration, outputting an execution error message and ending; Digit status check result, if it is registered with the general subscriber number, outputting the execution error message by terminating the result message into the general subscriber number and ending; If not defined, registering the AESA as a node address in the number translation database; Performing a routing protocol with a power station; And And performing a routing protocol, outputting a message and terminating the success output message to terminate the PNNI node in the ATM switching system. The method of claim 1, The third process, Receiving a request to remove a PNNI node, arranging input parameters (Level Id, Address Type, AESA) into a type suitable for a system, checking whether data is available, and storing all the input parameters if they are valid; A second step of configuring node Id to perform a node information deletion function of the node information database; And And deleting a node address of the number resolution database, deleting a reachable address of the reachable address database, and performing a routing protocol. The method of claim 6, The second step, Investigating and analyzing the address type; Defining an AFI for each address type analyzed and analyzed, and configuring the AESA using the defined AFI and Address (Prefix, ESI); Generating a node Id using Level Id and AESA; And And deleting the node information by finding a corresponding tuple of the node information database using the node Id. The method of claim 7, wherein Deleting node information using the node Id may include: Finding the corresponding tuple of the node information database using the node Id; Examining whether the tuple is not already used, that is, it does not exist; And Investigating in the above step, if the tuple does not already exist, the result message is arranged to be deleted by pre-deleting and outputting the execution error message and ending, and if there exists, the ATM exchange comprising the step of deleting node information. How to manage PNNI nodes on your system. The method of claim 6, The third step, Checking the digit state by finding the corresponding tuple of the number translation database using the AESA and examining the state of the number (node, called number); As a result of digit status checking, if the node address has already been deleted, sorting the result message into a pre-deletion, outputting an execution error message and ending; Digit status check result, if it is registered with the general subscriber number, outputting a result error message by terminating the result message into the general subscriber number and ending; Deleting the node address if it is registered as a node address and creating a reachable address using the node address to delete an address registered as a reachable address to a local system; Finding the corresponding tuple of the reachable address database using the created reachable address, deleting the contents, and performing a routing protocol with the power; And And performing a routing protocol, outputting a message and terminating the success output message to terminate the PNNI node in the ATM switching system. Claims [1] A computer readable recording medium having recorded a program for managing a PNNI node in an ATM switching system distributed in a local switching subsystem (ALS) unit and interconnected by a central switching subsystem (ACS). As a database for managing PNNI nodes, a node information database is configured in a sequential structure by the number of nodes that can be accommodated in the system, a number analysis database is configured in a double linked list structure, and a reachable address database is configured in a sequential structure. process; When the node configuration request is made, the input parameters (Level Id, Address Type, Address, Priority, Nodal flag, etc.) are sorted into the correct type for the system, and the useful data is stored as the type necessary to perform the node configuration function. And generating and assigning a node sequence number to manage the node, configuring new node information to register in the node information database, and registering a node address in the number translation database and performing a routing protocol. And a second step of configuring node information for node configuration according to a new node configuration request, registering the node information in a node information database, and instructing a routing protocol to be reflected in a network topology; And In response to the request to remove the PNNI node, the input parameters (Level Id, Address Type, AESA) are arranged into a type suitable for the system, and the data are checked for usefulness and stored if all the input parameters are valid, and the node Id is stored. Configuring and performing the node information deletion function of the node information database, and deleting the node address of the number resolution database, deleting the reachable address of the reachable address database, and performing a routing protocol. Records an executable program that performs PNNI node management in an ATM switching system, including the third step of removing node information from the node information database according to any node removal request and instructing routing protocols to be reflected in the network topology. Computer-readable recording media.