KR100617816B1 - Method for object oriented design of call control function entity in intelligent network - Google Patents

Abstract

The present invention relates to an intelligent network (IN), and in particular, an object-oriented design in consideration of minimizing performance and memory usage for a call control function block that performs basic call control and access control for an intelligent network service. Object model using the (Object Oriented Design) method. In order to solve this problem, the present invention has a basic call state model that has attributes that store all variable values necessary for call processing by creating an instance of a class for each call in an intelligent network, and has only methods of simply passing call processing events. An object-oriented design method of a call control function block object model comprising a call processing point and a detection point using attributes of the basic call state model as a storage state of call state model state and information required for call processing. When passing events to each call processing point or detection point in the state model, passing its own object pointer, defining only virtual methods in the basic call state model state, and performing default error handling; Create multiple instances of multiple arc states by creating only one instance at a point or detection point. It is a process that takes care of instances of, and directly accesses private as well as public at each call processing point or detection point by making relation between the basic call state models and call processing point / detection point as friends. It is characterized by.

Intelligent network, object model, object-oriented method

Description

OBJECT ORIENTED DESIGN OF CALL CONTROL FUNCTION ENTITY IN INTELLIGENT NETWORK}             

1 is a state transition diagram of a basic call state model component in accordance with the present invention.

2 is a diagram illustrating an outgoing basic call state model according to the present invention.

3 is a diagram illustrating an incoming basic call state model according to the present invention.

4 is a diagram illustrating an object model of a call control function block according to the present invention.

The present invention relates to an intelligent network (IN), and in particular, an object-oriented design in consideration of minimizing performance and memory usage for a call control function block that performs basic call control and access control for an intelligent network service. Object model using the (Object Oriented Design) method.

In the conventional intelligent network, the existing call control block has a problem that it takes a lot of effort and time to introduce the service because the service control block and the call control block are designed integrally and the call control block must be modified to introduce a new service. .

Accordingly, an object of the present invention is to adopt a structure that separates the service control part and the call control part proposed in the International Telecommunication Union-Telecommunication standardization section (ITU-T) recommendation, so that call control is introduced when a new service is introduced. An object-oriented design method of a call control function block that minimizes performance and memory usage when designing a call control function (CCF) by introducing an object-oriented design technique without affecting the block.

In order to achieve the above object, the present invention provides a basic call state model having attributes for storing all variable values necessary for call processing by creating an instance of a class for each call in an intelligent network, and having only methods of simply passing call processing events. In the object-oriented design method of a call control function block object model consisting of a call processing point and a detection point using the basic call state model state and the attributes of the basic call state model as a storage for information required for call processing, In the case of passing events to each call processing point or detection point in the basic call state model, passing the object pointer together with it, defining the virtual methods in the basic call state model state, and performing default error handling; Create multiple instances of only one instance by creating only one instance at the call processing or discovery point The process of taking care of the instances of the model, the process of directly accessing the private as well as public at each call processing point or detection point by using the relation between the basic call state models and call processing point / detection point as friends. Characterized in that made.

Hereinafter, with reference to the accompanying drawings, preferred embodiments of the present invention will be described in detail. First of all, in adding reference numerals to the components of each drawing, it should be noted that the same components have the same reference numerals as much as possible even if they are displayed on different drawings. In addition, in the following description, numerous specific details, such as specific process flows, are set forth in order to provide a more thorough understanding of the present invention. It will be apparent to those skilled in the art that the present invention may be practiced without these specific details. Detailed descriptions of well-known functions and configurations that are determined to unnecessarily obscure the subject matter of the present invention will be omitted.

The configuration of the call control function (CCF) to be modeled in the present invention is a basic call state model (BCSM), which is a high-level finite state machine representing the call control function as shown in FIG. ) Consists of a number of point in call (PIC) points (110, 130), detection points (DP) (100, 120), transitions, and events. . 1 is a state transition diagram of a basic call state model component in accordance with the present invention.

The call processing points 110 and 130 refer to basic call / connection states that are required for intelligent network service logic instances to control a service. The call processing points 110 and 130 process actual events. 120 serves as a point in time to report to the intelligent network service logic during basic call and connection processing and as an entry point for moving to the call processing point. The result generated after the processing at the call processing point is transmitted to the detection point and reported to the intelligent network service logic instance. The intelligent network service logic instructs the reported result to perform a specific processing or to move to a specific call processing point to implement a service state transition from the detection point to the call processing point, or from the call processing point to the detection point Indicates.

By performing the basic call processing procedure through the components, by detecting the point of time that the service control is required, it can be used regardless of the service type by reporting to the intelligent network service logic.

In the ITU-T intelligent network, the originating part and the called part of the call are functionally divided and defined into an originating basic call state model (Origination BCSM) and an incoming basic call state model (Termination BCSM). Each model applied to the present invention will be described by introducing an object-oriented design technique of a call control function block through FIGS. 2 and 3 to be described later.

In FIG. 2 and FIG. 3, an English capital letter “O” is prefixed to each call processing point and a detection point to indicate origination, and an English capital letter before each call processing point and a detection point to indicate an incoming call. Note the addition of the letter "T".

2 is a diagram illustrating an outgoing basic call state model according to the present invention;

The originating basic call state model represents the basic call state model associated with the originating party. Description of each call processing point of the origin basic call state model is as follows.

O_Null 201: After switching the idle state, the subscriber line or the relay line state to the idle state, the line is monitored and when the call is received from the originating subscriber, detection point 1 (Origination Attempt) is reached. No active calls currently

Authorize_Origination_Attempt 203: Upon receipt of a call from the originating subscriber, monitors the identity / capability of the call and the type of originating resource. When the qualification / capability is verified, detection point 2 (Origination_Attempt Authorized) is reached, and when the verification of the qualification / capability of the call fails or the caller gives up the call, an exception is processed.

Collect_Information (205): In the case where the calling party requests the call and the calling qualification / capability is successful, the initial information (service code, prefix, dialed adress digits) is collected from the calling party and the end point of information collection is determined according to the number plan. . At this time, when the initial information is completely collected from the calling party, detection point 3 (Collected Information) is reached, and when the initial information is not collected completely or the information is not collected by the exchange resource, an error occurs in the collected information. If so, and if the caller gives up, the exception is thrown.

Analyze_Information (207): When initial information is collected from the calling party, the input information is analyzed according to a number plan to determine a routing address and call type. When the routing address and call type are determined, detection point 4 (Analyzed Information) is reached, and when the calling subscriber gives up the call or when the inputted information cannot be analyzed according to the numbering plan, an exception is processed.

Select_Route 209: When the routing address is determined, a route list is selected to select a route, and a directory number such as a local resource is translated into a line number in the exchange. If the route is selected, Authorize_Call_Setup (211) is reached. If the route selection fails or the call is abandoned, an exception is handled.

Authorize_Call_Setup (211), Send_Call (213): The calling credentials for a particular call are verified. At this time, verification of outgoing credentials depends on the type of outgoing line. When verification of the outgoing call is completed, the call is forwarded to the incoming basic call state model. Upon receiving notification of the ring transmission from the incoming basic call state model, detection point 8 (O_term_Seized) is reached. If an additional service request is received from the originating basic call state model, detection point 7 (O_Mid_Call) is reached. If the call is abandoned during the call from the call state model, an exception is thrown.

O_Alerting 215: When the ring basic tone is notified from the incoming basic call state model, the ringer sends a ringback tone to the calling party and waits for a signal from the called party. If an additional service request is received from the originating basic call state model, it reaches discovery point 9 (O_Mid_Call); if it receives a call response from the incoming basic call state model, it reaches detection point 12 (O_Answer); In the case of busy and unanswered calls from the state model, an exception is thrown.

O_Active (217), O_Suspended (219): When a call response is received from the incoming basic call state model, it establishes an inter-origin connection and collects statistics / billing data and monitors the call. If an additional service request is received from the originating basic call state model, detection point 13 (O_Mid_Call) is reached, and if the calling party disconnects the call, detection point 16 (O Disconnect) is reached. If the connection between caller and caller fails, an exception is thrown.

 O_Execption (221): When an exception occurs at all call processing points of the originating basic call state model, processing of exceptions such as resource idle and the like is terminated.

3 is a diagram illustrating an incoming basic call state model according to the present invention;

T_Null 301: After switching the idle state, the subscriber line or the relay line state to the idle state, the line is monitored, and when receiving a call from the originating basic call state model, the detection point 21 (Termination Attempt) reach up to. No active calls currently

Authorize_Termination_Attempt (303): Receives an incoming call from the originating basic call state model and verifies the authority for call routing to the called party. Exceptions are received if a call is received from the originating basic call state model and the detection point 22 (Termination_Attempt Authorized) is reached when the entitlement to verify that the call is received by a specific incoming resource is reached and the caller is not able to reach the called party or the caller has abandoned the call. Do the processing.

Select_Facility (305), Present_Call (307): Successful verification of call routing to called party. Select a specific available line and send the ring to the incoming line. When the incoming call signal to the called party is received or the called party responds, the detection point 27 (T_Answer) is reached, and an exception is thrown when all the circuits of the called party are busy and the call abandon notification is received from the calling party. .

T_Alerting (309): In the case where the called party sends an incoming signal such as a ring, it notifies the called basic call state model that the incoming signal has been sent to the called party, continues the call processing for call setup, and responds to the called party. Wait. If the called party answers the call, detection point 27 (T_ANSWER) is reached, and if the called party is unanswered or the calling party is busy and unanswered from the basic call state model, an exception is thrown.

T_Active 311 and T_Suspended (313): When the called party answers, the called party notifies the called party's response, establishes the connection between the called party, and continuously monitors the call. When an additional service request is received from the called party, detection point 28 (T_Mid_Call) is reached, and when the called party disconnects the call, detection point 32 (T Disconnect) is reached. If the connection between caller and caller fails, an exception is thrown.

T_Execption 315: When an exception occurs at all call processing points of the incoming basic call state model, processing of an exception such as resource idle is performed and the processing of the exception is terminated.

4 is a diagram illustrating an object model of a call control function block according to the present invention. The configuration of the model includes a basic call state model (BCSM) 410, a BCSM state 420, a call processing point 430, and a detection point. It is composed of 440, the relation used between each class (Class) is used, such as friend, aggregation, generarization. The basic call state model 410 has attributes that store an instance of the class for each call, storing all the variable values needed for call processing, and have only methods of simply passing call processing events. In this case, when the basic call state model delivers events to each call processing point or detection point, the basic call state model also delivers its object pointer.

The BCSM state 420 has no attributes and defines only virtual methods to allow default error processing. The virtual methods redefine and use methods required at each call processing point or detection point, and use the default error handling methods as they are not overridden.

The call processing point or the detection points have methods for executing call processing without attributes, and generate only one instance to handle several instances of the basic call state model. Use the attributes of the call state model.

By making the relation between the basic call state models and the call processing point / detection point a friend, each call processing point or detection point does not access attributes using public methods of the basic call state model, Allow private access directly. This reduces performance by avoiding PUSH / POP of register values on the stack each time accessing the basic call state models to access basic call state models at the call processing or detection point. performance can be improved. In addition, by creating only one instance of each call processing point and discovery point class to handle multiple instances of the basic call state model class, it has a 1: 1 relationship with the default call state model instance and each call processing point or detection point. N (zero or more): 1 relations reduce the amount of memory used by each call processing or detection point.

On the other hand, in the detailed description of the present invention has been described with reference to specific embodiments, of course, various modifications are possible within 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.

By introducing the object-oriented design technique of the call control function block in the intelligent network, the optimized object model of the basic call state model is developed to minimize the performance and memory usage, thereby improving the system performance and reducing the cost.

Claims (3)

In the intelligent network, each call creates an instance of the class to store all the variable values necessary for call processing, and has a basic call state model, a basic call state model state, and a call that only have methods of simply passing call processing events. In the object-oriented design method of a call control function block object model consisting of a call processing point and a detection point using the attributes of the basic call state model as a storage location for processing, In the basic call state model, when the events are delivered to each call processing point or detection point, the object call is also delivered. Performing default error processing by defining only virtual methods in the basic call state model state; Creating a single instance at the call processing point or the detection point to handle instances of several basic call state models; Call control in an intelligent network comprising direct access to public as well as private at each call processing point or detection point using the relation between the basic call state models and the call processing point / detection point as friends Object-oriented design method of functional blocks. The method of claim 1, The virtual methods redefine and use methods required at each call processing point or detection point, and the undefined ones use the default error processing methods as they are, and the object-oriented design method of a call control function block in an intelligent network. The method of claim 2, And the basic call state model instance has an N: 1 relationship with each call processing point or detection point.

Images