KR100248420B1 - Vpci data management method - Google Patents

Abstract

It is an object of the present invention to create a fixed VPCI to handle calls with VPIs representing the VPI between the ATM terminal and the cross connector and the VPI values of the VPI between the cross connector and the ATM VC exchange and to modify them as needed. In addition, the present invention provides a fixed VPCI data management method in an ATM VC exchange that manages fixed VPCI data that can be deleted and output. Means for achieving the object of the present invention is a first step of processing a fixed VPCI generation command consisting of interface module number, link number, VPCI, VPI, and a fixed VPCI delete command consisting of interface module number, VPCI A second step, a third step of processing a fixed VPCI change command composed of an interface module number, a VPCI and change information, a VPI, and a fourth step of processing a fixed VPCI information output command consisting of an interface module number and a VPCI; Is done.

Description

A method of managing fixed virtual path connection identifier (BPCI) data in an ATM virtual channel exchange

The present invention relates to a fixed VPCI data management method in an ATM VC switch. In particular, the present invention relates to a VCI between an ATM terminal and a cross connector and a VPCI representing both VPI values of a VPI between a cross connector and an ATM VC switch. The present invention relates to a fixed VPCI data management method in an ATM VC exchange that manages fixed VPCI data that can be created, modified, deleted, and printed as needed.

ATM Virtual Channel (VC) switches do not have one terminal connected to a link that is physically connected to the switch, such as a voice switch or an N-ISDN switch, but multiple links on one link to increase the multiplexing effect of traffic on the call. There is a need for a structure in which a plurality of calls can be processed by connecting a plurality of terminals.

The structure requires that an ATM terminal is connected directly to a device called a cross connector rather than directly connected to an ATM VC switch, and the cross connector is connected to a subscriber matching device of the ATM VC switch. ATM VC exchange could not support this structure.

This structure is necessary because one subscriber rarely uses up to 155Mbps of bandwidth at a time, and practically, the bandwidth used by each subscriber is not very large. This is because connecting to a VC switch can use bandwidth more efficiently.

However, a device called a cross connector is similar to that of a VP (Virtual Path) exchange, so there is no signaling function for call processing, and only a VP is exchanged. Therefore, the VPI (Virtual Path Identifier) defined between the ATM terminal and the cross connector and the VPI defined between the cross connector and the ATM VC exchange are fixed so that the VP exchange is correctly performed at the cross connector, and signaling data and user data transmitted from the ATM terminal are fixed. Is passed through the VPI between the ATM terminal and the cross connector to the VPI defined between the cross connector and the ATM VC exchange, so that signaling data and user data can be received and processed at the ATM VC exchange. The fixed VPCI must be determined by the ATM VC exchange so that it can handle the call with

Thus, there is an absolute need for the ability to manage fixed VPCI data that can create, modify, delete, and output fixed VPCIs as needed. In addition, even if an ATM terminal is directly connected to a physical link without being connected to a cross-connector, the ability to manage fixedly available VPCI data is also required to support the case in which signaling data and user data can be transmitted only through a specific VPI. Was done.

It is an object of the present invention to provide fixed VPCI data in an ATM VC exchange that manages fixed VPCI data that can be created, modified, deleted, and output as required to generate fixed VPCIs for call processing with VPCIs representing both VPI values. To provide a management method.

Means for achieving the object of the present invention is a first step of processing a fixed VPCI generation command consisting of interface module number, link number, VPCI, VPI, and a fixed VPCI delete command consisting of interface module number, VPCI A second step, a third step of processing a fixed VPCI change command composed of an interface module number, a VPCI and change information, a VPI, and a fourth step of processing a fixed VPCI information output command consisting of an interface module number and a VPCI; Is done.

1 is a block diagram of an ATM VC exchange system.

FIG. 2 is a diagram illustrating the configuration of related blocks and message flows for performing a fixed VPCI data management function implemented on an ATM VC switch. FIG.

3 through 9 are general flow diagrams for fixed VPCI data management functions in an ATM VC exchange.

(Explanation of symbols for main parts of drawing)

100: operator terminal 200: ACS

300-1,300-2: ALS 2: OMP

12: HANDF 13-1, 13-2: UDHF

23-1, 23-2: ULRHF 33-1, 33-2: LIBMLF

A subscriber whose ATM terminal is connected to a cross connector must first be registered as a fixed subscriber, distinct from a regular subscriber, at the time of subscriber creation. Once created as a fixed subscriber, for this fixed subscriber a VPCI representing the VPI defined between the ATM terminal and the cross connector and between the cross connector and the ATM VC exchange should be determined. Because cross connector does not have signaling processing related to call processing, only signaling and user data transmitted to VPI defined between ATM terminal and cross connector transfers data to corresponding VPI defined between cross connector and ATM VC exchange. Unlike the general subscriber, the fixed subscriber can only determine the VPI required for the call connection corresponding to the VPCI by the ATM VC exchange.

Thus, there is a need for instructions for managing fixed VPCI data for fixed subscribers. In addition, to support the case where an ATM terminal can transmit signaling and user data only to a specific VPI, an ATM VC exchange needs to manage fixed VPCI data so that a fixed VPCI corresponding to a specific VPI can be used.

Therefore, the ATM VC switch consists of a command to create a fixed VPCI, a command to change the information of the fixed VPCI data as needed, a command to delete the unnecessary VPCI data, and a command to output the information held by the fixed VPCI. Fixed VPCI data management capabilities are needed.

By inventing the data management function for the fixed VPCI in the ATM VC exchange, it allows the structure to increase the traffic multiplexing in the ATM VC exchange, thereby increasing the bandwidth utilization efficiency of the ATM VC exchange, and enabling data transmission using only a specific VPI. It also supports ATM terminals, so that various types of terminals can be connected to increase the portability of the terminals, and provides operators with data management functions for fixed VPCIs, making it easier for operators to operate and maintain fixed VPCIs for fixed subscribers. The objective is to increase the reliability of the exchange by ensuring that the fixed VPCI data is consistent and always operating correctly.

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

1 is a block diagram of an ATM VC exchange system.

This ATM VC switch is composed of ATM Local Switching Subsystem (ALS) 300-1 and 300-2 and ATM Central Switching Subsystem (ACS) 200.

The ALS (300-1), (300-2) is a call and connection control processor (CCCP) (3-1), (3-2) performing a call processing function, subscriber data management function and fixed VPCI data management function And an IM (Interface Module) for performing subscriber matching.

The ACS 200 performs an operator matching function, a number translation data processing function, and an operation and maintenance processor (OMP) that provides an interface between the operator terminal 100 and the ATM VC exchange 2. It is composed of

Looking at the functions of the blocks required for the fixed VPCI data management function, the HANDF 12 analyzes the operator commands input from the operator terminal and checks whether they are entered according to the command format. This function outputs the result of completing the requested function and the input command to the operator terminal.

The UDHFs 13-1 and 13-2 perform the fixed VPCI generation function, the delete function, the change function, and the information output function. The ULRHFs 23-1 and 23-2 contain the fixed VPCI generation request. When the VPI between the cross connector associated with the fixed VPCI and the ATM VC exchange is fixed, change the status to Fixed.If a request for changing the fixed VPCI is received, the VPI before the change is fixed and not in use and the VPI is fixed after the change. Function to change the status of the VPI to fixed when not using the fixed VPCI deletion request.

The ULRHFs 23-1 and 23-2 only change the state whether the corresponding VPI is fixed or not in use, but does not set the bandwidth in advance. When LIBMLF creates, changes, or deletes fixed VPCI data, the LIBMLF checks whether the VPI in the link and the subscriber module associated with the fixed VPCI is normal or abnormal.

FIG. 2 is a diagram illustrating the configuration of related blocks and message flows for performing a fixed VPCI data management function implemented on an ATM VC switch.

When the operator inputs a fixed VPCI generation, deletion, change, or information output command from the operator terminal 100, the HANDF 12 checks whether these commands are input as originally defined, and if there is no error, inputs them together with the corresponding command. Sends the processing request to the UDHF 13-1.

When the UDHF block 13-1 receives the fixed VPCI generation request, the UDHF block 13-1 first checks whether there is an error in the information values input for the fixed VPCI generation. If there is no error, it checks whether the interface module to generate the fixed VPCI is a subscriber interface module or a trunk interface module. If it is a subscriber interface module, it searches whether the existing VPCI exists in the fixed VPCI relation, and if not, the ULRHF 23-1. The VPI corresponding to the fixed VPCI is required to be fixed.

The ULRHF 23-1 checks its own VPI management table to see if the required VPI can be used in a fixed manner, changes the VPI to be used in a fixed manner, and notifies the UDHF 13-1 of the result. If the requested VPI can be used as a fixed type, it is requested whether the VPI corresponding to the fixed VPCI can be generated in the interface module number and link number inputted to the LIBMLF 33-1.

The LIBMLF 33-1 generates the VPI inputted to the interface module number and link number requested by the UDHF 13-1 through the switch system configuration information, and delivers the result to the UDHF 13-1. If the result received from the LIBMLF 33-1 is that the corresponding VPI can be generated in the interface module number and the link number, the UDHF 13-1 is connected to the fixed VPCI relation managed by the UDHF 13-1. Stores interface module number, link number, VPCI, and VPI information.

When this process is normally completed, the UDHF 13-1 transmits the fixed VPCI generation completion result to the HANDF 12, and the HANDF 12 outputs the fixed VPCI generation completion result to the operator terminal.

Next, when the UDHF 13-1 receives the fixed VPCI deletion request, it checks whether the interface module number with the VPCI to be deleted is a subscriber interface module or a trunk interface module. When the fixed VPCI relation is searched by using the interface interface number and the VPCI as a key, and the corresponding VPCI exists, the ULRHF requests the ULRHF to delete the VPI corresponding to the VPCI so as not to use the fixed VCI. Change your own VPI table to disabled for fixed use. The result is transmitted to the UDHF 13-1.

The UDHF 13-1 then asks the LIBMLF 33-1 to delete the VPI generated at the interface module number and link number, which is the information received with the fixed VPCI delete request, and the LIBMLF is associated with the corresponding interface module number. The VPI existing in the link number is deleted and the result is transmitted to the UDHF 13-1. The UDHF 13-1 then deletes the fixed VPCI information from the fixed VPCI relation. When this process is normally completed, the UDHF 13-1 transmits the fixed VPCI deletion completion result to the HANDF 12, and the HANDF 12 outputs the fixed VPCI deletion completion result to the operator terminal.

Next, when the UDHF 13-1 receives the change request of the fixed VPCI information for changing the VPI information, the fixed VPCI information to be changed in the fixed VPCI relation is entered using the interface module number and the VPCI as the information received together with the change request. If it exists, it checks whether the interface module number, information received with the fixed VPCI change request if it is a subscriber interface module or a trunk interface module, and if it is a subscriber interface module, uses the VPI before the change as a ULRHF (23-1). If not required, the ULRHF 23-1 changes its own VPI table by disabling the use of the VPI as a fixed type, and transmits the result to the UDHF 13-1.

Then, the UDHF 13-1 requests the ULRHF 23-1 to use the fixed VPI after the change, and the ULRHF 23-1 changes its own VPI table to use the fixed VPI after the change. The result is then passed to the UDHF 13-1. The UDHF 13-1 then asks the LIBMLF 33-1 to delete the pre-change VPI created in the interface module number and link number, and the LIBMLF 33-1 in the corresponding interface module number and link number. Delete the existing VPI before the change and transfer the result to the UDHF 13-1.

The UDHF 13-1 then asks the LIBMLF 33-1 to create a post-change VPI in its interface module number and link number, which is the information received with the fixed VPCI change request, and the LIBMLF 33-1 After changing the interface module number and link number, VPI is generated and the result is transmitted to UDHF 13-1.

The UDHF 13-1 then deletes the fixed VPCI information before the change from the fixed VPCI relation and adds the new fixed VPCI information with the VPI after the change to the fixed VPCI relation. When this process is normally completed, the UDHF 13-1 transmits the fixed VPCI change completion result to the HANDF 12, and the HANDF 12 outputs the fixed VPCI change completion result to the operator terminal.

Next, when the UDHF 13-1 receives the fixed VPCI information output request, the UDHF 13-1 checks whether the interface module number having the fixed VPCI information to be output is a subscriber interface module or a trunk interface module. The fixed VPCI relation is searched using the interface module number and the VPCI, which are the received information, and if the fixed VPCI information is present, the HANDF (12) displays the information and the search result of the fixed VPCI composed of the interface module number, link number, VPCI, and VPI. The HANDF 12 outputs the fixed VPCI information output completion result to the operator terminal.

3 through 9 are overall flow diagrams for the fixed VPCI data management function in an ATM VC exchange.

When the HANDF 12 receives the fixed VPCI data management command consisting of the fixed VPCI generation, deletion, change, and information output commands from the operator terminal 100 (S1), the HANDF 12 checks whether these commands are input according to the form. (S2) If there is an error (S3), output the error result to the operator terminal (S4). If there is no error (S3), request processing of fixed VPCI generation, deletion, change, information output command to UDHF 13-1. Transmit (S5).

When the UDHF 13-1 receives the fixed VPCI generation instruction processing request (S6), as shown in Figs. 4A and 4B, the UDHF 13-1 checks whether there is an error in the received information and if there is an error ( S7) The HANDF 12 transmits the error result to the HANDF (S8) and receives the error result (S9). The HANDF 12 outputs the error result to the operator terminal 100 (S10).

If there is no error (S7), it compares with the fixed VPCI generation command whether the interface module number which is the received information is the subscriber module or not (S11) and transmits the error result to the HANDF 12 (S8) and sends the error result. The received HANDF 12 outputs an error result to the operator terminal 100 (S10). If the subscriber module is present (S11), the HANDF 12 searches for the existence of the fixed VPCI that requires generation in the fixed VPCI relation (S12). ) And transmits the error result to the HANDF 12 (S8) and receives the error result (S9), the HANDF 12 outputs the error result to the operator terminal 100 (S10), if not present (S12) ULRHF ( 23-1), the VPI corresponding to the fixed VPCI requested to be generated is requested to be used as the fixed type (S13).

Receiving the fixed usage request of the VPI requesting the creation (S14), the ULRHF 23-1 searches for this VPI in its own VPI table and changes it to fixed (S15) to use the required VPI as fixed (S15). It transmits to (13-1) (S16). Receiving a fixed usage request result of the requested VPI (S17), the UDHF 13-1 transmits an error result to the HANDF if the requested VPI is not available (S18) and transmits an error result (S8). The received (S9) HANDF 12 outputs the error result to the operator terminal 100 (S10), and if available (S18), the interface module number (IM) and the link number, which are information received with the fixed VPCI generation command. It requires the LIBMLF 33-1 to generate the VPI fixedly at LINK (S19).

Receiving a fixed generation request of the VPI (S20), the LIBMLF 33-1 generates a fixed VPI required for the corresponding interface module number and link number through the switch system configuration information (S21), and outputs the result of the UDHF (13). -1) (S22). The UDHF 13-1, having received the fixed generation request result of the requested VPI (S23), transmits an error result to the HANDF 12 (S8) if the VPI for which the result is required cannot be fixedly generated (S24). Upon receiving the error result (S9), the HANDF 12 outputs the error result to the operator terminal 100 (S10), and if it can be generated (S24), the UDHF 13-1 is connected to the fixed VPCI relation managed by itself. The fixed VPCI information including the interface module number, link number, VPCI, and VPI is added (S25). The fixed VPCI generation result is transmitted to the HANDF 12 (S26), and the fixed VPCI generation result is received (S27). The HANDF 12 outputs the result to the operator terminal 100 (S28).

As shown in Fig. 3, when the UDHF 13-1 next receives the fixed VPCI delete command processing request (S29), as shown in Figs. 6A and 6B, the fixed VPCI delete command is shown. HANDF 12 receives an error result (S9) and transmits an error result to the HANDF 12 (S30). If the error result is output to the operator terminal 100 (S10), and if the subscriber module (S30), if there is a fixed VPCI requesting deletion from the fixed VPCI relation exists and does not exist (S31), the error result is sent to the HANDF 12. After transmitting (S8) and receiving an error result (S9), the HANDF 12 outputs an error result to the operator terminal 100 (S10), and if present (S31), a fixed type requesting deletion to the ULRHF 23-1. It is required not to use the VPI corresponding to the VPCI fixedly (S32). Receiving the fixed unused request of the VPI requesting deletion (S33), the ULRHF (23-1) searches for this VPI in its own VPI table so that the requested VPI is not used as fixed and changes its use to fixed. In operation S34, the result is transmitted to the UDHF 13-1 (S35).

Receiving the fixed unused request result of the requested VPI (S36), the UDHF 13-1 deletes the VPI from the fixed type in the interface module number (IM) and link number (LINK), which are received with the fixed VPCI delete command. Ask LIBMLF if possible (S37). Receiving the fixed deletion request of the VPI (S38), the LIBMLF 33-1 deletes the VPI required for the corresponding interface module number and link number from the fixed type through the switch system configuration information (S39), and the result is UDHF (13). -1) (S40).

Receiving the result of the fixed deletion request of the requested VPI (S41), the UDHF 13-1 deletes the fixed VPCI information from the fixed VPCI relation (S42). The HANDF transmits the fixed VPCI deletion result to the HANDF (S43), and receives the fixed VPCI deletion result (S44). The HANDF outputs the result to the operator terminal (S45).

As shown in FIG. 3, when the UDHF 13-1 receives the fixed VPCI change command processing request (S46), the UDHF 13-1 compares whether the interface module number which is the received information with the fixed VPCI change command is a subscriber module or not. If it is not the subscriber module (S47), and transmits the error result to the HANDF 12 (S8) and receives the error result (S9) HANDF 12 outputs the error result to the operator terminal (S10), ( As shown in a) and (b), if the subscriber module (S47) detects whether there is a fixed VPCI requesting a change in the fixed VPCI relation, and if it does not exist (S48), transmits an error result to the HANDF 12 ( S8) Upon receiving the error result (S9), the HANDF 12 outputs the error result to the operator terminal (S10) and, if present (S48), fixes the VPI before the change of the fixed VPCI requesting the change to the ULRHF 13-1. It is required not to be used as (S49).

Receiving the fixed unused request of the pre-change VPI requiring deletion (S50), the ULRHF 23-1 searches for this VPI in its own VPI table so that the requested pre-change VPI is not fixed. It changes to no use (S51) and transmits the result to the UDHF 13-1 (S52). The UDHF 13-1 receiving the fixed non-use request result of the VPI before the change (S53) requests the VPI to be used fixed after the change to the ULRHF 23-1 (S54).

After receiving the fixed use request of the VPI after the change (S55), the ULRHF 23-1 searches for this VPI in its own VPI table to use the fixed VPI after the change, and changes the fixed use to the fixed use (S56). The data is transmitted to the UDHF 13-1 (S57). Receiving the fixed usage request result of the VPI after the change (S58), the UDHF 13-1 sends the VPI before the change to the interface module number (IM) and the link number (LINK), which are information received with the fixed VPCI change command. Ask LIBMLF to be deleted (S59).

Upon receiving the fixed deletion request of the VPI before the change (S60), the LIBMLF 33-1 deletes the change VPI required for the corresponding interface module number and the link number from the fixed type through the switch system configuration information (S61), and as a result, Is transmitted to the UDHF 13-1 (S62).

As shown in (a) and (b) of FIG. 8, the UDHF 13-1 receiving the fixed deletion request result of the VPI before the change (S63) may generate the LIBMLF 33-1 so that the VPI is fixedly generated after the change. (S64). Receiving the fixed generation request of the VPI after the change (S65), the LIBMLF 33-1 generates the modified VPI required for the corresponding interface module number and link number in the fixed form through the switch system configuration information (S66), and as a result, Is transmitted to the UDHF 13-1 (S67).

Receiving the fixed generation request result of the VPI after the change (S68), the UDHF 13-1 deletes the fixed VPCI information before the change in the fixed VPCI relation (S69) and adds the fixed VPCI information after the change (S70). The fixed VPCI change result is transmitted to the HANDF 12 (S71), and the fixed VPCI change result is received (S72). The HANDF 12 outputs the result to the operator terminal 100 (S73).

As shown in FIG. 3, when the UDHF 13-1 receives the fixed VPCI information output command processing request (S74), as shown in FIG. 9, the information received together with the fixed VPCI information output command is shown. If it is not the subscriber module (S75) and transmits the error result to the HANDF 12 (S8) and receives the error result (S9), the HANDF 12 sends the error result to the operator terminal. Outputs (S10), if it is a subscriber module (S75), detects whether there is a fixed VPCI requesting information output from the fixed VPCI relation, and if it does not exist (S76), transmits an error result to the HANDF 12 (S8); The received (S9) HANDF 12 outputs an error result to the operator terminal (S10), and if present (S76), the UDHF 13-1 extracts the corresponding fixed VPCI information from the fixed VPCI relation (S77). Transfer the VPCI information output to HANDF 12 And (S78). Receiving the fixed VPCI information output result (S79), the HANDF 12 outputs the result to the operator terminal (S80).

The present invention has the following effects.

First, it allowed the ATM VC switch to increase the traffic multiplexing called cross-connector, thereby increasing the bandwidth utilization efficiency of the ATM VC switch.

Second, ATM terminals that can transmit data using only certain VPIs are also supported, which enables various types of terminals to be connected, thus enhancing portability of terminals.

Third, the fixed VPCI data management function is provided to the operator, making it easier to operate and maintain the fixed VPCI data for the fixed subscribers.

Fourth, by providing the fixed VPCI data management function, the consistency of the fixed VPCI data is maintained so that the exchange always operates correctly, thereby increasing the reliability of the exchange.

Claims (6)

A first step of processing a fixed VPCI generation command consisting of an interface module number, a link number, a VPCI, and a VPI; A second step of processing a fixed VPCI delete command consisting of an interface module number and a VPCI; A third step of processing an interface module number, a VPCI and a link number which is change information, and a VPI-configured fixed VPCI change command; And a fourth step of processing a fixed VPCI information output command composed of an interface module number and a VPCI. The method of claim 1, The interface module in the first step includes a subscriber interface module and a trunk interface module, and the fixed VPCI data management method in the ATM VC switch, characterized in that the processing to generate a fixed VPCI only in the subscriber interface module. The method of claim 1, In the first step, upon receiving a fixed VPCI generation command processing request, HANDF checks whether there is an error in the received information, and if there is no error, compares whether the interface module number, which is the received information with the fixed VPCI generation command, is a subscriber module or not. A first step of requesting generation in the fixed VPCI relation and searching for the existence of the fixed VPCI if it is a subscriber module; If the VPCI does not exist as a result of the search, the VPI corresponding to the fixed VPCI requesting the generation using the ULRHF is requested to be used in a fixed manner, and then the VPI required for the ULRHF receiving the fixed use request of the VPI requesting the generation is fixed. A second step of retrieving the VPI from its own VPI table, changing it to a fixed type, and transmitting the result to the UDHF; If the UDHF 13-1 receives the fixed usage request result of the requested VPI, and the result is available in the fixed VPI, the interface module number (IM), which is information received with the fixed VPCI generation instruction, A third step of requesting LIBMLF to generate a VPI fixedly at a link number LINK; The LIBMLF receiving the fixed generation request of the VPI generates the fixed VPI required for the interface module number and the link number through the exchange system configuration information, sends the result to the UDHF, and then requests the fixed generation of the requested VPI. A fourth step of adding fixed VPCI information to the fixed VPCI relation managed by the UDHF if the UDHF that has received the result can generate a fixed VPI; And a fifth process of transmitting the fixed VPCI generation result to the HANDF and outputting the result to the operator terminal (100) by the HANDF receiving the fixed VPCI generation result. The method of claim 1, When the UDHF receives the fixed VPCI delete command processing request, the second step compares whether the interface module number, which is information received with the fixed VPCI delete command, is a subscriber module, and if the subscriber module is a fixed type, requesting deletion from the fixed VPCI relation. Searching for the existence of the VPCI and, if present, requesting that the VPI corresponding to the fixed VPCI requested to be deleted by the ULRHF not be used as a fixed type; The ULRHF receives a fixed unused request from the VPI requesting deletion, retrieves this VPI from its own VPI table, and changes the use of the fixed to unused so that the requested VPI is not used as a fixed, and sends the result to the UDHF. After transmission, the UDHF receiving the fixed unused request result of the requested VPI asks LIBMLF to delete the VPI from fixed on the interface module number (IM) and link number (LINK), which is the information received with the fixed VPCI delete command. A second process of doing; Receiving, by the LIBMLF, a fixed deletion request of the VPI, deleting the VPI required for the corresponding interface module number and the link number from the switch system configuration information in a fixed manner, and transmitting the result to the UDHF; The UDHF receiving the fixed deletion request result of the requested VPI deletes the corresponding fixed VPCI information from the fixed VPCI relation, sends the fixed VPCI deletion result to the HANDF, and receives the fixed VPCI deletion result to the operator terminal. The fixed VPCI data management method of the ATM VC switch, characterized in that comprises a fourth process for outputting. The method of claim 1, When the UDHF receives the fixed VPCI change command processing request, the third step compares whether the interface module number, which is information received with the fixed VPCI change command, is a subscriber module, and if it is a subscriber module, requesting a change in the fixed VPCI relation. Searching for the existence of the fixed VPCI and, if present, requesting not to use the fixed VPI of the fixed VPCI that has been changed to ULRHF as fixed; The ULRHF, which receives a fixed unused request for a VPI that requires deletion, searches for this VPI in its own VPI table to change the usage of the fixed to disabled so that the requested unchanged VPI is not used as a fixed one. Transmitting the UDHF to the UDHF and requesting that the UDHF receiving the fixed non-use request result of the VPI before the change to the ULRHF be used as the fixed VPI; The ULRHF receives the fixed usage request of the VPI after the change, retrieves this VPI from its own VPI table, changes it to fixed usage, and sends the result to the UDHF so that the requested VPI is used as the fixed type. The third step of the UDHF receiving the fixed use request result of requesting LIBMLF to delete the VPI from the fixed type in the interface module number (IM) and the link number (LINK), which are information received with the fixed VPCI change command, and ; After receiving the fixed deletion request of the VPI before change, the LIBMLF 33-1 deletes the change VPI required for the corresponding interface module number and link number from the fixed type through the exchange system configuration information and transmits the result to the UDHF. A fourth step of requesting LIBMLF to generate a fixed VPI after the change by the UDHF receiving the fixed deletion request result of the VPI before the change; After receiving the fixed creation request of the VPI after the change, LIBMLF generates the post-change VPI required for the corresponding interface module number and link number in the fixed form through the exchange system configuration information, and transmits the result to the UDHF, and then changes the VPI. A fifth step of the UDHF receiving the fixed generation request result of deleting the pre-modified fixed VPCI information from the fixed VPCI relation and adding the fixed VPCI information after the change; The fixed VPCI data management in the ATM VC exchange comprising the sixth step of transmitting the fixed VPCI change result to the HANDF and outputting the result to the operator terminal 100 (S73). Way. The method of claim 1, When the UDHF receives the fixed VPCI information output command processing request, the fourth step compares whether the interface module number, which is information received with the fixed VPCI information output command, is a subscriber module, and outputs information in the fixed VPCI relation if it is a subscriber module. A first step of searching for whether there is a fixed VPCI that requires? If the VPCI exists, the UDHF extracts the fixed VPCI information from the fixed VPCI relation, transmits the fixed VPCI information output result to the HANDF, and then receives the fixed VPCI information output result from the HANDF to the operator terminal. The fixed VPCI data management method of the ATM VC switch, characterized in that the second process to output.

Images