KR100316187B1 - Method of V5.2 startup process - Google Patents

Abstract

The present invention relates to a V5.2 startup procedure method for promoting system stabilization by preventing the restoration of ISDN calls by adding a procedure for terminating all ISDN calls connected when performing the startup procedure. It solves the inconveniences of subscribers by preventing the transition to the abnormal state that occurs when performing the activation procedure in the state, and is used as a common resource (V5.2 PSTN, V5.2 ISDN) on the V5.2 exchange side. System stabilization is achieved by preventing abnormal bearer channel occupation.

Description

5.2 Method of Startup Procedure

The present invention relates to a method for starting a V5.2, and more particularly, to perform a startup procedure after transitioning an Integrated Service Digital Network (ISDN) call to a busy state on a V5.2 protocol. It relates to a V5.2 start-up procedure method to control the abnormal operation of the ISDN call.

Conventionally, a local exchange (LE) and a subscriber network access device (AN) are connected through a mutual V5.2 interface. Referring to FIG. 1 and FIG. The explanation is as follows.

1 is a V5.2 startup procedure diagram starting with a subscriber network access device in a conventional local exchange, and FIG. 2 is a V5.2 activation procedure diagram starting with a local exchange in a conventional subscriber network access device. Therefore, it will be described based on the procedure of FIG. 1.

In response to a V5.2 start request from within, the local exchange (LE) sends a Set Asynchronous Balance Mode Extended (SABME) to the subscriber network access unit (AN) (10). The AN sends an Unnumbered Acknowledge (UA) message to the local exchange LE (11).

Accordingly, the local exchange LE sends a reset subscriber number command message (RESET SN COM) to the subscriber station (AN) (12), and the subscriber station (AN) sends a reset subscriber number confirmation message (RESET SN ACK). ) Is sent to the local exchange (LE) (13).

Subsequently, when the local exchange LE sends a command control message (COMMON CTRL) requesting various interface IDs to the subscriber station (AN) (14), the command switch message (COMMON) is transmitted from the subscriber station (AN). A command control acknowledgment message (COMMON CTRL ACK) indicating that the CTRL is received is sent to the local exchange (LE) (15). It also sends various interface IDs 16 to the local exchange (LE) side. Accordingly, the local exchange (LE) sends a command control confirmation message (COMMON CTRL ACK) to the subscriber station access point (AN) indicating that the various interface IDs have been received (17), and performs a link identification procedure for startup. A link control message (LINK CONTROL) requesting (FE_IDReq; Link Identification Request) is sent to the subscriber station access point (AN) (18).

Upon receiving this, the subscriber station access point (AN) sends a link control acknowledgment message (LINK CONTROL ACK) to the local exchange (LE) (19). At the same time, if the link state is normal, the link control for the link identification procedure request acknowledgment (FE_IDAck) is performed. Send a message (LINK CONTROL) to the local exchange (LE) (20).

Accordingly, the local exchange (LE) receiving the link control 20 message sends a link control confirmation message to the subscriber network access device (AN) (21), recognizing that the link state is normal, and requesting the release of the link identification procedure ( A link control message requesting FE_IDRel (Link Identification Release Request) is transmitted to the subscriber station access point (AN) (22).

When the subscriber station access device (AN) sends a link control confirmation message indicating that the link exchange message has been received to the local exchange (LE) (23), the local exchange (LE) receives a command control message requesting restart. Sending to the access point (AN) (24), and receiving the subscriber network access point (AN) sends a confirmation of the command control message to the local exchange (LE) (25), the local exchange (LE) issues a restart command The command control message is transmitted to the subscriber station (AN) (26).

Accordingly, by sending an acknowledgment that the subscriber network access unit has received the command control message to the local exchange (LE) (27) and simultaneously sending a command control message representing the restart command to the local exchange (LE). (28) A startup procedure is performed.

In the conventional startup procedure, since there is no specific reference to ISDN call disconnection, an abnormal state occurs in which the interface is in a non-service state but the call is connected at the moment when the activation proceeds. And even if the interface transitions back to the service state after performing the activation procedure, the layer 2 data link resetting procedure is performed for each protocol of the corresponding interface, so the call information of layer 2 is different from the existing layer 3 call information. This causes a problem that the ISDN call of the higher layer 3 is shifted to an unrecovered state.

In other words, if the ISDN call is transferred to the busy state after the V5.2 protocol, the call state is maintained, but there are cases where a call that is not cut is generated when the call is cut. This is because the algorithm that terminates the PSTN call that is connected through the restart procedure when the start-up procedure is applied is applied, but the function is not implemented because there is no specific recommendation for the ISDN call.

Accordingly, the present invention has been made in view of the above-mentioned conventional circumstances, and the method of starting the V5.2 procedure for stabilizing the system by preventing the restoration of the ISDN call by adding a procedure for terminating all ISDN calls connected when the start procedure is performed. The purpose is to provide.

According to a preferred embodiment of the present invention, the V5.2 startup procedure method comprises: storing a child process ID generated for each interface and port number when an ISDN call is generated in the ISDN call processing software module;

Transmitting a call disconnection request from the system manager to the ISDN call processing software module when receiving a data link configuration confirmation notification of Layer 2 for each protocol when the local exchange is activated;

The system manager transmits a command control message requesting different interface IDs to the subscriber network access device and proceeds with the activation procedure as the ISDN call processing software module transmits the release completion to the subscriber network access device. .

V5.2 activation procedure method according to another embodiment of the present invention, the ISDN call processing software module for storing the ID of the child process generated for each interface and port number when the ISDN call occurs;

When starting from the subscriber network access device, after performing the data link setting of Layer 2 for each protocol requested by the subscriber network access device, and sending the command control requesting the different interface ID to the local exchange, it calls the ISDN call processing software module. Sending a cutting request;

The ISDN call processing software module transmits the release completion to the subscriber network access device.

1 is a V5.2 startup procedure diagram starting from a conventional local exchange;

2 is a V5.2 startup procedure starting from a conventional subscriber network access device,

3 is a V5.2 startup procedure started at a local exchange according to an embodiment of the present invention;

4 is a V5.2 startup procedure starting from a subscriber network access device according to an embodiment of the present invention;

5 is a call information storage diagram of the integrated information communication network call processing software module according to an embodiment of the present invention.

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

3 is a V5.2 startup procedure diagram starting at a local exchange according to an embodiment of the present invention.

The ISDN call processing software module stores the child process ID generated by the corresponding interface and the port number when the ISDN call occurs and enters the active state (30).

In the busy state, when the local exchange LE is activated, it receives a data link setting confirmation notification of Layer 2 of each protocol (31). At this time, the system manager SM transmits a Call Disc RQ message to the ISDN call processing software module (32). The ISDN call processing software module then sends the Call Disc RQ message to each child process managed for each interface.

Accordingly, each child process receiving this transmits a Release Complete message to the subscriber network access device (AN) (33, 34), and the system manager SM controls the command to the subscriber network access device (AN). (Request Variant and Interface ID) message is sent and the start procedure is carried out (35). The subsequent procedure is the same as the procedure of the prior recommendation of FIG.

4 is a V5.2 startup procedure diagram starting from a subscriber network access device according to an embodiment of the present invention.

The ISDN call processing software module stores a child process ID generated for each interface and port number when an ISDN call occurs and enters a busy state (40).

In the busy state, when the subscriber network access device (AN) is activated, after setting the data link of the layer 2 for each protocol requested by the subscriber network access device (AN) (41), the local exchange ( When the LE receives a Request Variant and Interface ID message (42), the system manager SM transmits a Call Disc RQ message to the ISDN call processing software module (43). The ISDN call processing software module then sends the Call Disc RQ message to the child process being managed for each interface.

Each child process transmits a Release Complete message to the subscriber network access device (AN) (45, 46), and the system manager (SM) commands control to the subscriber network access device (Variant and Interface ID). ) Transmits the message (47) and proceeds with the startup procedure. The subsequent procedure is the same as that of the prior recommendation of FIG.

In the above, when the call is disconnected at the local exchange (LE) (Fig. 3), the call is immediately after the data link setup of the layer 2 is completed (31), and the call is started at the subscriber network access device (AN). In this case (FIG. 4), this is immediately after receiving the command control (Request Variant and Interface ID) message (47).

For example, if an ISDN call is generated between the call 51 from the subscriber network access device (AN) or the call 52 from the network, the ISDN call processing software module is shown in FIG. The interface ID and port number are obtained (53), and unlike the general PSTN call, the ISDN call generates two or more child processes, so the generated child process is started (54) to generate the corresponding interface and port number. The stored child process ID is stored (55) and then active (56). At this time, the stored child process ID is stored in a linked list structure.

According to the present invention as described above, in addition to the procedure of terminating all ISDN calls that are connected when performing the activation procedure to prevent the recovery of the ISDN call to solve the inconvenience of the subscriber, and in terms of V5.2 exchange System stabilization is achieved by preventing abnormal bearer channel occupied by common resources (V5.2 PSTN, V5.2 ISDN).

In terms of service, abnormal charging and statistics are prevented.

In addition, this invention is not limited only to the above-mentioned embodiment, It can implement by modifying and modifying within the range which does not deviate from the summary of this invention.

Claims (4)

Claims [1] A method for processing ISDN call processing requests from a local exchange or subscriber network access device under control of a system manager. If the ISDN call processing is required, storing the child process ID generated for each interface and port number when the ISDN call occurs in the ISDN call processing software module; Transmitting a call disconnection request from the system manager to the ISDN call processing software module when receiving a data link configuration confirmation notification of Layer 2 for each protocol when the local exchange is activated; When the ISDN call processing software module transmits a release completion to a subscriber network access device, the system manager transmits a command control message requesting a different interface ID to the subscriber network access device and proceeds with a start-up procedure. V5.2 starting procedure method characterized in that. The method of claim 1, The child process ID stored in the process of storing the child process ID is stored in a linked list structure V5.2 start method. Claims [1] A method for processing ISDN call processing requests from a local exchange or subscriber network access device under control of a system manager. Storing a child process ID generated for each interface and port number when an ISDN call occurs in the ISDN call processing software module; When starting from the subscriber network access device, after performing the data link setting of Layer 2 for each protocol requested by the subscriber network access device, and sending the command control requesting the different interface ID to the local exchange, it calls the ISDN call processing software module. Sending a cutting request; And a process of proceeding with a start-up procedure as the release complete signal is transmitted from the ISDN call processing software module to the subscriber network access device. The method of claim 3, wherein The child process ID stored in the process of storing the child process ID is stored in a linked list structure V5.2 start method.