KR19980077844A - Network Management Method of Common Line Signaling Switching System - Google Patents

Abstract

end. FIELD OF THE INVENTION The present invention relates to an exchange system using a common line signaling method.

I. The technical problem to be solved by the invention: to accurately detect the abnormality of the local subsystem and the remote subsystem to enable more efficient management of the entire network.

All. Summary of Solution of the Invention: When an event generated in the case of no response for a predetermined time after a predetermined operation occurs in the ASE is received, the state of the sub-system is inquired to S7SMG, the N0.7 network management block. In this case, if the sub system is allowed, the local subsystem is a problem. However, if the sub-system is practically available, it will enact an operation of the network management MAP to inform the sub-system that it will live with the unused exchange or HLR.

la. Important uses of the invention: The network can be managed reliably and the operator can react immediately in case of abnormalities.

Description

Network Management Method of Common Line Signaling Switching System

The present invention relates to a switching system using a common line signaling method, and more particularly, to a method for more efficiently managing an entire network by accurately detecting an abnormality of a local subsystem and a remote subsystem.

Common Channel Signaling (CCS), which is widely used in exchange systems these days, is a signaling method that separates signaling information from traffic by using NO.7 signal. This common line signaling method provides the transmission speed that is easy to provide a large amount of information, has the characteristics of easy network management and control, and can provide better service to the operator, It provides many advantages, such as enabling fast call control and increasing network efficiency.

The common line signaling protocol layer is composed of four levels. The first level (Level 1) of the protocol is a layer defining the physical and electrical characteristics of the signal data link and an access method, and mainly uses a 64 Kbps digital link signal. The second level (Level 2) is a layer that defines the functions and processes involved in transmitting a message with high reliability through each signal data link in the first level, in the form of a signal unit that can vary the signal message. It is transmitted through the signal link. Level 3 is a layer that defines the transmission function and process of signal message through each signal link. It guarantees reliable message delivery through alternative link or alternative path in case of failure of signal link or signal transmission point. And reconfiguration of the message path. The fourth level (Level 4) is composed of different user parts, and is a layer that defines signaling functions and processes applicable only to users of a predetermined type.

Meanwhile, as described above, the third level layer of the common line signaling protocol performs a network management function. When an operation for performing the network management function is generated and transmitted to the other network, an operation according to the transferred operation is performed. However, if there is no response even after the designated time elapses after the operation occurs, there is a problem that network management cannot be performed correctly. More specifically, when there is no response to the operation for network management, it is not possible to know exactly whether there is no response due to an error of the operation generating subsystem or that there is no response due to an error of the remote subsystem.

Accordingly, an object of the present invention is to provide a method for enabling more accurate network management in an exchange system using common line signaling.

Another object of the present invention is to provide a method of handling when there is no response to an operation for network management in a switching system using a common line signaling method.

It is still another object of the present invention to provide a method for accurately detecting an error cause of a system when there is no response for an operation for network management in an exchange system using a common line signaling method.

The present invention for achieving these objectives relates to the L_Cancel primitive, which is an event handled when there is no response to a given generated operation. When such an event is received by the ASE, the S7SMG, the N0.7 network management block, is queried for the status of the power subsystem. If the power subsystem is allowed, the local subsystem is allowed to go to the allowed state because it is a problem with the local subsystem. Perform the procedure. However, if the sub-system is practically available, it will enact an operation of the network management MAP to inform the sub-system that it will live with the unused exchange or HLR. The network management MAP reports and retries the operator so that the sub-systems survive. By performing this procedure, the network can remain stable and the operator can respond immediately if there is a problem.

1 is a view schematically showing a connection configuration of a common line signaling system to which the present invention is applied;

FIG. 2 shows the structure of a local table structured in the LRP / ASS-T / ASS-M shown in FIG.

3 is a diagram showing a protocol for network management operation according to the present invention performed when the other network is available.

4 is a diagram illustrating a protocol for network management operation according to the present invention performed by the calling party when the other party network is in an unavailable state.

5 is a diagram illustrating a protocol for network management operation according to the present invention performed at the called party when the other network is in an unavailable state.

6 to 8 are views showing the processing flow for the network management operation according to the present invention.

DETAILED DESCRIPTION A detailed description of preferred embodiments of the present invention will now be described with reference to the accompanying drawings. First of all, in adding reference numerals to the components of each drawing, it should be noted that the same reference numerals are used as much as possible even if displayed on different drawings. In addition, in the following description of the present invention, if it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted. In addition, the terms to be described below are terms defined in consideration of functions in the present invention, which may vary according to the intention or custom of the user or chip designer, and the definitions should be made based on the contents throughout the present specification.

1 is a view schematically showing a configuration of a common line signaling system to which the present invention is applied, and this configuration shows a connection configuration in terms of performing a function related to the third level of the common line signaling protocol. to be. That is, FIG. 1 is a diagram illustrating a connection configuration of a common line signaling system for performing network management related functions.

Referring to FIG. 1, the exchange system includes an OMP 10, an LRP / ASS-T / ASS-M 20, an ASS-7 30, and a lower-level processor PP (Peripheral) serving as a high-level processor MP (Main Processor). It consists of SMHP 40, which serves as a processor. Operation Maintenance Processor (OMP) 10 performs functions such as system operation, maintenance, billing and statistics. The OMP 10 includes an SMG-AP 12, an Application Service Element (SMGF-ASE) 14, and a Transaction Capability Application Part (SMGG-TCAP) 16. LRP / ASS-T / ASS-M 20 is a subsystem that provides services by matching relay lines and general subscribers, and provides access switching subsystem for accessors (ASS-T) and access switching subsystem for mobile subscribers (ASS-M). It is a block that performs a function as a registration processor, LRP (Location Registraion Processor), and consists of application programs 22, ASE's (Application Service Elements) 24, and TCAP (Transaction Capability Application Part) 26 to perform these functions. ASS-7 (Access Switching Subsystem NO.7 Signaling) 30 performs all functions related to MTP (Message Transfer Part) and SCCP (Signaling Connection Control Part) in NO.7 Signaling Processing System. Signaling NO.7 Signaling Connection Control Part Management-Access Switching Processor) Signaling Message Handling Processor (SMHP) 40 performs a SCCP function after performing signaling message handling functions such as discrimination, distribution, and routing among the functions of the message transfer part (MTP). . The SMHP 40 includes S7SRC (Signaling System No.7 SCCP Routing Control Handling Block) / S7SDH (Signaling System NO.7 SCCP Data Handling Block) 42 and S7MH (Signalling NO.7 Message Handling Block) 44.

FIG. 2 is a view showing the structure of a local table operating for network management operation according to the present invention. The local table is structured in LRP / ASS-T / ASS-M 20 shown in FIG. .

Referring to FIG. 2, the local table consists of an RLOE block 20A and an ASLC library 20B. The process of operating the local table is largely divided into three processes. The first process is to initialize the library, the second process is to operate the library, and the third process is to use the library network. During library initialization, RLOE block 20A inserts both 'SPC_NO', 'SP_ST' (signal point state ⇒ INSERVICE), and 'SS_ST' (subsystem state ⇒ INSERVICE) into ASLC library 20B based on 'PFX_NO'. The procedure call used at this time is pd_networkinit indicated by reference numeral '1'. If there is a state change of a subsystem or a change of a signal point in a library operation process, an event is received from SMG_AP 12 of OMP 10 shown in FIG. 1 and a library operation procedure call is performed by this message. The procedure call used here is pd_networkadm, denoted by the reference character '2'. After all operations have occurred, the library detects 'PFX_NO' of the routing data received at the destination address and returns TRUE if the transfer checking point (subsystem, DPC status) is not in service (INSERVICE). . The procedure call used for detecting 'PFX_NO' in the above is pd_networkuse indicated by the reference numeral '3'. In the case of return true, the operation continues, whereas in case of return false, a report of cancellation is sent to SMG-AP 12.

Now, if there is no response even after a predetermined time has elapsed in the TCAP 26 of FIG. 1 (no response), the L_Cancel primitive is generated. At this time, the occurrence of the L_Cancel primitive is related to each of blocks 12 to 16 of the OMP 10 shown in FIG. 1, and the inquiry about the state management of the subsystem is related to the S7SMG-ASP of ASS-7 30. TCAP 26 generates an L_Cancel primitive and informs ASE 24 of the generated L_Cancel primitive. At this time, Prefix of the unprocessed operation is received and ASE 24 receives the DPC and Subsystem against Prefix to SMG-AP 12 of OMP 10. That is, ASE 24 generates SMG-Lcancel and informs the generated SMG-Lcancel to SMG-AP 12.

SMG-AP 12 then inquires the management status of the peer network to the S7SMG-ASP block of ASS-7 30. At this time, if the other network is available, the Restrart_Tcap signal is thrown to the TCAP 26, the processor of the received signal (SMG_Lcancel), and the TCAP 26 inputs the Restrart_Tcap signal to perform the restart procedure. In this state, that is, the protocol execution procedure corresponding to the case where the other network is available is illustrated in FIG. 3.

Referring to FIG. 3, TCAP 26 of ASS-T 20 generates L_Cancel, and ASE 24 generates SMG-Lcancel in response to the generated L_Cancel. In response to the generated SMG-Lcancel, SMG-AP 12 of OMP 10 generates SMG_StatusSS_SP, and in response, S7SMG of ASS-7 30 generates SMG_StatusSS_SPack. SMG-AP 12 of OMP 10 then generates Restart_Tcap and forwards it to TCAP 26.

On the other hand, when SMG-AP 12 inquires the management status of the other party's network with the S7SMG-ASP block of ASS-730, it generates ActivationSS operation when the other party's network is unavailable. Upon receiving the above operation, the power SMG-AP 12 throws a Restart_Tcap signal to the TCAP of all the processors in which the corresponding subsystem exists, and in response, the TCAP 26 performs the restart procedure. After receiving the ActivationSS result, SMG-AP 12 queries the S7SMG block of the ASS-7 30 for the management status of the other network. At this time, if the other network is normally serviced, Prefix values for DPC are transmitted to various ASSs and LRPs, and if abnormal, retry is performed.

4 and 5 show a procedure of a protocol that is processed when the other network is unavailable when the SMG-AP 12 inquires the management status of the other network with the S7SMG-ASP block of ASS-7 30 as described above. Drawing. 4 shows a procedure of a protocol performed by a calling party when the other network is unavailable, and FIG. 5 shows a procedure of a protocol performed by a receiving party when the other network is unavailable.

Referring to FIG. 4, TCAP 26 of the calling party ASS-T 20 generates L_Cancel, and ASE 24 generates SMG-Lcancel in response to the generated L_Cancel. In response to the generated SMG-Lcancel, SMG-AP 12 of OMP 10 generates SMG_StatusSS_SP, and in response, S7SMG of ASS-7 30 generates SMG_StatusSS_SPack. Then, SMG-AP 12 of OMP 10 generates ActivationSSr and delivers it to SMG-ASE 14, and SMG-ASE 14 generates BEGreq and INVreq in response to SMG-TCAP 16. SMG-TCAP 16 delivers N_UDTr to SMHP 40 in response to the generated BEGreq and INVreq. Subsequently, when N_UDTi is received from SMHP 40, SMG-TCAP 16 generates and delivers ENDind and RESind to SMG-ASE 14. SMG-ASE 14 generates an ActivationSSc in response to the ENDind and the RESind being delivered to the SMG-AP 12. SMG-AP 12 generates SMG_StatusSS_SP in response to the occurrence of the ActivationSSc and delivers it to S7SMG of ASS-7 30. Subsequently, when SMG_StatusSS_SPack is received from S7SMG, SMG-AP 12 sequentially generates Restart_Tcap and A_PFXind and delivers them to TCAP 26 of ASS-T 20.

Referring to FIG. 5, in response to receiving N_UDTi from SMHP 40, SMG-TCAP 16 of the called party OMP 10 generates BEGind and INVind and transmits them to SMG-ASE 14. The SMG-ASE 14 generates an ActivationSSi in response to receiving the BEGind and the INVind and delivers it to the SMG-AP 12. Then, SMG-AP 12 generates Restart_Tcap in response to the delivered ActivationSSi and delivers it to TCAP 26, and simultaneously generates and sends ActivationSSs to SMG-ASE 14. SMG-ASE 14 sequentially generates ENDreq and RESreq in response to the delivered ActivationSSs and delivers them to SMG-TCAP 16. SMG-TCAP 16 then generates N_UDTr in response to the delivered ENDreq and RESreq and delivers it to SMHP 40.

3 to 5 is a protocol for performing a network management function according to the present invention as described above. That is, when the other network is available, the protocol of the procedure as shown in FIG. 3 is performed, and when the other network is unavailable, the protocol of the procedure as shown in FIGS. 4 and 5 is performed.

6 to 7 correspond to the protocol described with reference to FIGS. 3 to 5, and show a processing flow of the network management operation according to the present invention.

Now, assuming that the L_Cancel primitive is generated in TCAP 26 of FIG. 1, this generated L_Cancel primitive is received in ASE's 24. ASE's 24 then processes the operation according to the flow as shown in FIG. When ASE's 24 receives L_Cancel (step 601 of FIG. 6), ASE's 24 sends SMG_Lcancel message information about DPC and SS (subsystem) to SMG-AP 12 (step 604). After the SMG-AP 12 receives the SMG_Lcancel message (step 701), the SMG-AP 12 sends the SMG_StatusSS_SP message to the S7SMG-ASP of the ASS-7 30 (step 702), and receives the SMG_StatusSS_SPack message in response (703). step). The SMG-AP 12 may know the SS status of the DPC from the received SMG_StatusSS_SPack message. Therefore, after determining the state of the DPC and the state of the SS (steps 704 and 705), the SMG-AP 12 determines whether to activate the remote subsystem or the local subsystem according to the determination result. If either the state of the DPC or the state of the SS is unavailable, the SMG-AP 12 forwards the ActivationSSr to the partner network, which is the remote subsystem (step 708), and receives a response ActivationSSc (step 709). In contrast, if the state of the DPC and the SS are both available, SMG-AP 12 sends Restart_Tcap to its TCAP 26 to activate the local subsystem (step 706). Upon receiving the ActivationSSr (step 801), the SMG-AP 12 of the remote subsystem transmits Restart_Tcap to its TCAP 26 (step 802) to activate its own subsystem, and sends a response ActivationSSc to the calling party (803). step). This activates the remote subsystem.

The operation of network management according to the present invention as shown above is summarized as follows. NO.7 TCAP 26 of FIG. 1 checks network status management if there is no response within a predetermined time even after an operation occurs. In this case, when the local subsystem is not available, the local subsystem is processed to be available. In contrast, when the remote subsystem is not available, the remote subsystem is made available by creating an interface operation between network management systems. Process as much as possible.

As described above, in the present invention, when there is no response to an operation for network management, the present invention determines whether it is an error of the local subsystem or a remote subsystem, and then takes an action accordingly. That is, if the local subsystem that generated the operation is abnormal, the local subsystem is activated in an available state. If the remote subsystem is abnormal, the subsystem is activated in an available state. Accordingly, there is an advantage that it is possible not only to accurately detect the cause of the system fault, but also to enable more accurate network management by activating the subsystem in which the problem occurs in an available state.

Meanwhile, in the detailed description of the present invention, specific embodiments have been described, but various modifications may be made without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined not only by the scope of the following claims, but also by the equivalents of the claims.

Claims (3)

In a network management method of a switching system using a common line signaling method, the network management block includes a network management block, and if the network management block is unresponsive even after a predetermined time has elapsed, the network management block indicates the state of the counterpart subsystem. A network management method characterized by activating a local subsystem or a remote subsystem in an available state according to the result of the query after the inquiry. The network management method according to claim 1, wherein if the result of the inquiry by the network management block determines that the status of the local subsystem is abnormal, the network management method is activated. 3. The method according to claim 1 or 2, wherein if the result of the inquiry by the network management block determines that the state of the remote subsystem is abnormal, the method of activating the remote subsystem becomes available.