KR100362578B1 - Method for tracing call on the way to serviced intelligent network in exchange system - Google Patents

Abstract

The present invention relates to an intelligent network tracking method including an event tracking between a call tracking for a detection point and a distributed function plane (DFP) interface in an exchange system, wherein an SSF in a CTPM of a CCF is requested when an intelligent network tracking is requested from a maintenance terminal. The process of transmitting the intelligent network trace request signal to the call trace package of the SSF, and receiving the intelligent network trace request signal from the SSF trace trace package, registers whether it is a trace point or an event trace for the detection point and registers the intelligent network trace trace. Comparing an object with the intelligent network tracking condition, transmitting the tracking result for the intelligent network tracking request to the CTPM, and receiving the tracking result for the intelligent network tracking request from the CTPM. The process of outputting to the maintenance terminal to notify the operator.

Description

Intelligent network call tracking method in exchange system {METHOD FOR TRACING CALL ON THE WAY TO SERVICED INTELLIGENT NETWORK IN EXCHANGE SYSTEM}

The present invention relates to an intelligent network call tracking method in an exchange system, and more particularly, to a call processing method when a hook flash occurs during an intelligent network call processing in an exchange.

In general, the intelligent network of the exchange system changes the communication service from the voice service to the voice data image, the uniform service is changed to the individualization-oriented service, and the communication service is changed from the mass small product to the small quantity. It combines voice and signaling system into a separate communication network by tying it to one common line signal method.It installs a separate large computer and database on the existing communication network and concentrates the intelligent network service processing functions here to provide various communication services. It is an advanced communication network that can be efficiently implemented and operated. These intelligent network services are increasing in service type and function due to the diverse needs of users and network operators and the development of No.7 common channel signaling technology.

Meanwhile, ITU-T defines an intelligent network capability set (IN CS), which is the target of standardization activity and is targeted at a specific evolutionary stage, and standardizes it. Name it IN CS-1, IN CS-2, IN CS-3, ...

The characteristics of IN CS-1 recommended as the first-level intelligent network capability include intelligent network conceptual model (INCM), basic call state model (BCSM), and intelligent network application for the implementation of service-independent network. The concept of IN Application Protocol (INAP) has been established, and the characteristics of IN CS-2 recommended by the two-stage intelligent network capability extends the IN CS-1 to the target network as well as the fixed network. Therefore, the provision of partial mobile service and multimedia service is also considered.

However, for the intelligent network service, an SSP (Service Switching Point) and SCP (Service Control Point) that perform intelligent network service call processing are required. Among them, SSP means that the existing local exchange can perform the intelligent network service. The SSP decides whether to perform intelligent network service when it meets various detection points (DP) defined in BCSM (Basic State Machine ITU-Q1214) during basic call processing. It will perform the service. Here, if the subscriber uses the hook flash while in a general call or during a call using the intelligent network service (in the case of MidCall detection point), it is investigated whether the corresponding detection pointer satisfies the conditions for performing the intelligent network service. Intelligent network service is performed through the interface.

However, this call tracking function was required because there was no function to track the call during intelligent network call processing in the exchange system.

Accordingly, an object of the present invention is to provide a method for tracking a call in an intelligent network service in an exchange system to solve the above problem.

In order to achieve the above object, the present invention provides an intelligent network call tracking method including an event tracking between a call tracking for a detection point and a distributed function plane (DFP) interface in an exchange system, and the intelligent network call tracking request may be required from a maintenance terminal. The process of transmitting the intelligent network trace request signal from the CTPM of the city CCF to the SSF trace package, and receiving the intelligent network trace request signal from the SSF trace package and identifying whether it is a trace or event trace for the detection point. Registering and comparing the intelligent network tracking object with the intelligent network tracking condition to transmit the tracking result for the intelligent network tracking request to the CTPM, and receiving the tracking result for the intelligent network tracking request from the CTPM. Reporting the call tracking result to the maintenance terminal to notify an operator Characterized by a made of an.

1 is a diagram illustrating a simplified structure of an intelligent network in an exchange system according to an embodiment of the present invention.

2 is a view showing a role between the call tracking package, the call processing package and the objects of the call tracking package in the SSF module according to an embodiment of the present invention.

3 is a diagram illustrating a tracking interface class diagram for each object according to an embodiment of the present invention.

4 is a diagram illustrating a tracking message class diagram for each object according to an embodiment of the present invention.

5 is a diagram illustrating a call tracking and event tracking class diagram for each object according to an embodiment of the present invention.

Figure 6a, 6b is an output example format diagram for the intelligent network call tracking result step 0,1,2,3 of the present invention

7 is a flowchart illustrating a call tracking request registration procedure control according to an embodiment of the present invention.

8 is a control flowchart for call tracking according to an embodiment of the present invention.

9 is a control flow diagram for event tracking according to an embodiment of the present invention.

10 is a flowchart illustrating a call tracking release procedure control according to an embodiment of the present invention.

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

1 is a diagram illustrating a simplified structure of an intelligent network in an exchange system according to an embodiment of the present invention.

The Call Control Function (CCF) 100 is a function for providing call / service processing and control, manipulating or releasing a call / service instance requested by a Call Control Agent Function (CCAF), and the SSF 200. Provides the ability to associate or associate a CCAF entity included in a particular call or service instance, and detects and sends a trigger event to the SSF 200. Service Switching Function (SSF) 200 is a service switching function connected to the CCF 100, and provides functions for interaction between the CCF 100 and the SCF 300, and recognizes the service control trigger In order to interact with the SCF 300, the logic of the CCF 100 is extended, the signaling method between the CCF 100 and the SCF 300 is managed, and the additional service request is processed under the control of the SCF 100. Modify the call / service function of the CCF (100) necessary for the purpose. Service Control Function (SCF) 300 directs intelligent network call control in the processing of supplementary services or user requests, holds intelligent network service logic programs, accesses additional logic or handles intelligent network call / service instances. To interact with other entities. Specialized Resource Function (SRF) 400 provides special resources required for the execution of services such as voice recognition, voice synthesis, etc., and interoperates with SCF 300 and CCF 100 / SSF 200. And logic and processing for transmitting and receiving information from and converting user information. Call Trace Path Set_up Managment (CTPM) 101 manages call tracking and path setup. Call Trace Path Set-up (CTPS) 102 establishes call traces and paths.

2 is a view showing the role between the call tracking package, the call processing package and the objects of the call tracking package in the SSF module according to an embodiment of the present invention.

The tracking interface object receives call tracking and event tracking request / confirmation / release signal from CCF 100 to create / search / destroy call tracking object in case of tracking and create / search / destroy event tracking object in case of event tracking. do. In order to create / search / destroy call tracking and event tracking objects, key attributes are required in these objects, which are Port Job Numbers. The port execution number is generated by the CCF 100 and included in the TrcInRQ signal and transmitted to the tracking interface of the call tracking package. The port number is generated when MMC terminal and call tracking and event tracking are performed. It must be unique in the system.

The call handling package searches for call tracking objects and event tracking objects at the time of sending and receiving a specific event during call processing, and generates a tracking message object when the corresponding condition is satisfied. The tracking message object transmits call tracking results to the CCF 100 at various levels through the tracking interface object.

Activation of call tracking function in SSP module deteriorates system performance by giving call processing speed for one call and overall system, but it does not affect call processing speed and system load and performance when deactivated. . Therefore, call tracking packages should be as simple as possible.

3 is a diagram illustrating a tracking interface class diagram for each object according to an embodiment of the present invention.

It is shown in Unified Modeling Modeling Language (UML) notation. The Interface_, the interface for call tracking, exists as CCF 100 and defined as OTC_List <T1> Telmplate Class type so that callTraces_ and eventTraces_ can manage objects as Linked List so that operators can manage call trace requests. It is. The other attributes are to match the interface of the call trace message with the CTPM 101 of the CCF 100.

There is a registerCallback () method for receiving a call trace signal from CCF 101, and there are handle methods {handleTrcInRQ (), handleStopTrcInRQ () ..} for each signal. TraceEvent () and checkTracing () methods are overloaded for CallEvent and TCinvoke, respectively, to check call trace requirements in CallHandling Package. Other methods are for manipulating trace result messages.

4 is a diagram illustrating a tracking message class diagram for each object according to an embodiment of the present invention.

The trace message class is the superclass of the classes for call processing output. Thus, only the most common elements of the message output exist. The child classes of trace messages are TrcShortRP, TrcLongRP, and TrcDetailRP according to the trace output format, and the upper trace message class diagram shows only the relationship of the class to TrcShortRP.

Excute () method of TrcShortRP is overloaded for CallEvent and TCinvoke. Classes that call trace value (ISCTrcInShoertRP_M) to iscTrcInshortRP_ class of CCF (101) with executeCommon () method may vary according to the family register output stage.

For example, in case of TrcLongRP class, ISC_TrcInLongRP_M signal value of ISC_TrcInLongRP_M is transmitted. In the case of ISC_TrcInLongRP_M, there is an attribute that hex dumps the contents of the message and stores the value.

5 is a diagram illustrating a call tracking and event tracking class diagram for each object according to an embodiment of the present invention.

The general trace class consists of the call trace request requested by the operator and the method and attribute that checks whether the call in progress meets the call trace requirement. This class is a superclass of CallTrcRep and EventTracerEP, and their common data and roles are defined. TraceInterface class stores CallTraceRep in case of TestCallEvent or CallEvent according to call trace request, and EventTraceRep in OTC_List <> in case of TCinvoke (see INAP). When the message transmitted / received during the intelligent network call processing is related to the CCF 100, when the CallTraceRep object is the SCF 300 or the SRF 400, the EventTraceRep object checks whether the call tracking requirement is satisfied. The method of conditional checking is compareCallCriterial () and compareCallCommonCriterial (). The execute () method is responsible for transmitting call trace output to CTPM 101 in a different output format according to traceLevel ().

And intelligent network tracking requirements are shown in Table 1 below.

DP: Detection Point (DP1-DP26), ROUTE: Route, CallingNunber: Calling Number, DialedNumber: Calling Number, Service: Service Name for Intelligent Network Service, INAP: INAP Operator, TriggerType: Request / Notification.

The following describes the signals used when the operator requests, confirms, or releases an intelligent network call trace.

signal Explanation Interface modul Performance impact TrcInRQ Requires network call tracking. CTPM → Call Tracing Less StopTrcInRQ Requires selective release of intelligent network call tracking. CTPM → Call Tracing Less KillInTrc Requires disabling intelligent network tracking. CTPM → Call Tracing Less TrcInRP Send step 0 as a result of the intelligent network call tracking. Call Tracing → CTPCASP (Call) → Call Handling Less TrcInLongRP As a result of intelligent network call tracking, send step 1. Call Tracing → CTPCASP (Call) → Call Handling middle TrcInDetailRP As a result of the intelligent network call tracking, step 2 is transmitted. Call Tracing → CTPCASP (Call) → Call Handling plenty TrcInFullRP As a result of the intelligent network call tracking, send step 3. Call Tracing → CTPCASP (Call) → Call Handling plenty

In Table 2, the output example formats for the intelligent network call tracking result steps 0, 1, 2, and 3 are shown in FIGS. 6A and 6B.

6A is PrimaryDP (CCF → SSF), which is a CallEvent for the intelligent network call trace result step 0,1,2,3 of the present invention.

6B is InitialDP (SSF → SCF) which is a TCinvoke for the intelligent network call tracing result step 0,1,2,3 of the present invention.

The following describes the steps of each call trace output message.

Step 0: Message Name + ASP Number + Service Name + Call Origination Time (SSP Time) + AIP Number + Call Trace Order (BEGIN: Start Call Tracking), CONTINUE (Continue Call Tracking), END (End Call Tracking) + CallState (State_Idle = 1, State_W_aitInfo = 2, State_WaitInst = 3, State_WaitEndUserInteraction = 4, State_WaitEndTempCon = 5, State_WaitAssIst = 6, State_Monitoring = 7, State_WaitGapFilter = 8)

Step 1: Hex Dump of Step 0+ Message

Step 2: Initial interpretation of step 0 + messages (if the message contains submessages, only the values are output without listing the parameter names of the submessages)

Step 3: Complete interpretation of step 0+ messages (up to the name and content of the sub message and the interpretation)

7 is a flowchart illustrating a call tracking request registration procedure control according to an embodiment of the present invention.

When the terminal a makes an intelligent network call tracking request, the CTPM 101 of the CCF 100 sends a tracking request signal (TrcInRQ) to the call tracking package to the SSF 200. Then, the Trace Interface of the SSF 200 transmits the registerCallbacks signal to the CTPM 101 in step 101 when the TrcInRQ signal is received, and the CTPM 101 of the CCF 100 calls the handleTrcInRQ () method (). Register to do it. When the registration is completed, in step 102, the registration request signal (handleTrcInRQ) according to the trace type is sent to the trace interface. The trace interface then registers the CallTrace / EventTrace according to the trace type. Thereafter, in step 103, the trace interface transmits a signal TrcInRQ ACK in response to the tracking request signal TrcInRQ to the CTPM 101. In step 104, the trace interface is created to be inserted into OTC_List according to the call trace type among CallTrace / EventTrace. At this time, it is created to be inserted by referring to the contents of the message in the trace request signal (TrcInRQ). Then, in step 105, the trace interface inserts a CallTrac / EventTrace object into CallTrace_ and EventTrace_. In this case, the port operation ID is the only key value and should not allow duplication.

8 is a control flowchart for call tracking according to an embodiment of the present invention.

When the call handling message is transmitted / received with the CCF 100 during call processing in the call handling package 202, the call handling package 202 calls CheekEvent () and checkEvent () in step 201. Then, in step 202 and 203, the trace interface sends compareCallCriteria signal and compareCallCommonCriteria to CallTrace, and CallTrace compares the ongoing call with the call tracking condition and loops the number of times in OTC_List to check if the condition is satisfied. If the condition is satisfied in step 204, the corresponding object is created according to the output step. Thereafter, the call tracking result is transmitted to the CPPM 101 in step 105.

In addition, in step 206 and 207, the trace interface sends compareCallCriteria signal and compareCallCommonCriteria to EventTrace, and CallTrace compares the call progress with the call tracking condition and checks if the condition is satisfied by looping as many times as in OTC_List. If the condition is satisfied in step 208, the corresponding object is created according to the output stage. In step 209, the call tracking result is transmitted to the CPPM 101.

When the call handling message is transmitted / received with the CCF 100 during call processing in the call handling package 202, the call handling package 202 calls EventTrace after the first time. In step 211, the trace interface handles CallTrace or EventTrace separately. Then, in step 212, create the object according to the output stage. In operation 213, the call tracking result is transmitted to the CTPM 101.

In addition, in step 214, the trace interface is divided into CallTrace or EventTrace. Then, in step 215, the object is created according to the output stage. In operation 216, the call tracking result is transmitted to the CTPM 101. In step 217 and step 218, the call tracking condition is compared with the ongoing call tracking condition to check whether the condition is satisfied by looping the number of times in the OTC_List. If the condition is satisfied in step 219, the corresponding object is created according to the output step. Then, in step 220, the call tracking result is transmitted to the CPPM 101.

9 is a control flowchart for event tracking according to an embodiment of the present invention.

When the call handling message is transmitted / received between the SCF 300 and the SRF 400 during call processing in the call handling package 202, the call handling package 202 calls TraceEvent () in step 301. In step 302, the trace interface checks whether the event tracking requirements are met and updates any call tracking requirements (checkCall). Then, in steps 303 and 304, the trace interface sends a compareCallCriteria signal and compareCallCommonCriteria to CallTrace. It compares the call in progress with the call tracking condition and checks if the condition is satisfied by looping the number of times in OTC_List. (CompareCallCriteria, compareCallCommonCriteria) And if the condition is satisfied in step 305, the object is created according to the output step. The trace interface then compares the signal to compareCallCriteria If you send compareCallCommonCriteria to CallTrace, CallTrace compares the call with the tracking conditions in progress and loops the number of times in OTC_List to see if the condition is met (compareCallCriteria, compareCallCommonCriteria) .In step 308, the trace message is sent to the output stage if the condition is met. Then, the corresponding object is created. (New) In step 309, the call tracking result is transmitted to the CPPM 101. (postMessagetoCCF)

10 is a flowchart illustrating a call tracking release procedure control according to an embodiment of the present invention.

When the operator requests the call trace release using the terminal, in step 401, the CTPM 101 requests the port operation ID for the trace interface object of the call trace package (stopTrcInRQ). When Delete signal is sent to EventTrace / CallTrac, the corresponding port operation ID exists in the EventTrace / CallTrac object. In operation 403, the trace interface finds and deletes a corresponding job ID from the OTC_List.

And the classification of the message that can be output as a result of intelligent network call tracking of the present invention and the corresponding message is shown in Table 3 below.

interface message Description of the message Scalability Tracking CCF → SSP (Event1) Depends on network BCSM and billing messages Multilevel expandable necessary CCF → SSP (Event2) INAP Messages about call processing and billing Multilevel expandable necessary CCF → SSP (Event3) INAP Defined in Q.1214, Q1218 Multilevel expandable necessary CCF → SSP (Event4) INAP Defined in Q.1214, Q1218 Multilevel expandable necessary CCF → SSP (Event5) INAP Defined in Q.1214, Q1218 Multilevel expandable necessary CCF → SSP (Event6) INAP Defined in Q.1214, Q1218 Multilevel expandable necessary

As described above, in the present invention, when an intelligent network call is attempted in an exchange system that performs an intelligent network service, the system extracts and tracks a call attempted at a specific detection point or traces a call attempted at a specific event to affect the performance of the system. It has the advantage of intelligent network tracking without giving, and also it can examine the call processing process externally in the development stage of the system. Differently, there is an advantage that can reduce the development cost by shortening the system development stage and test period.

Claims (1)

In an intelligent network call tracking method including an event tracking between a call tracking for a detection point and a distributed function plane (DFP) interface in a switching system, When there is a request for intelligent network tracking from the maintenance terminal, transmitting the request signal for intelligent network tracking from the CTPM of the CCF to the SSF tracking package; After receiving the intelligent network trace request signal from the call trace package of the SSF, it registers whether it is a trace or event trace for a detection point, and registers the intelligent network trace object and the intelligent network trace condition by comparing the intelligent network trace request condition to the intelligent network trace request. Transmitting the call trace result to the CTPM; And receiving the call tracking result for the intelligent network call tracking request from the CTPM, and outputting the call tracking result to the maintenance terminal to notify an operator.