KR100296972B1 - Storage and Method of Overall Service Logic in Open Service Creation Environment - Google Patents

Abstract

The present invention relates to a storage device and a method of overall service logic in an open service creation environment. The present invention relates to a framework by configuring a service creation structure to have a framework-based service creation environment structure to facilitate the expansion of an open service creation environment. It is easy to insert, delete or change a component without affecting the service.In the framework-based service generation environment structure, information about each SIB existing in a server must be coordinated and stored as one general service logic. Therefore, the independent information of each developed SIB is tied together into one, so that the overall service logic can be stored in one file.

Description

Storage and Method of Overall Service Logic in Open Service Creation Environment

The present invention relates to a storage device and a method of general service logic in an open service generation environment. In particular, when addition, deletion, or change of a new SIB occurs in a service generation environment for intelligent network service generation, addition to SIB components, The present invention relates to a storage device and a storage method of a general service logic for facilitating deletion or modification, and for efficiently storing information distributed to clients and servers.

In general, communication software is implemented in a real-time distributed environment and has a complex structure, which has been developed by skilled professionals for a long time and has difficulty in adding and changing maintenance and functions.

On the other hand, the intelligent network enables the external computer to perform the service processing function among the call processing functions and service processing functions that the exchange has performed previously, and introduces the concept of service creation environment to create and introduce new services quickly and economically. As such, the service creation environment of the intelligent network is a communication software environment that enables a service developer to easily and efficiently develop an intelligent network service without a high level of expertise. This communication software environment is a service component that abstracts network capabilities. It shortens the time required for service development by expressing services by visually combining service components called SIB (Service Independent Building Block).

However, this communication software environment is limited to accommodate changes in network capabilities and service characteristics because it focused on generating intelligent network services within the limits of a specific capability group of intelligent networks, and it is not easy to expand by adding new service parts. not. In addition, as the intelligent network capability 2 and the intelligent network capability 3 have evolved, there is a need to expand the service generation capability by designing the service generation environment itself as an open service system based on a distributed processing environment.

Therefore, in order to store the overall service logic in the existing intelligent network service creation environment, the storage method was decided in consideration of the relationship between the service creation method and the tools constituting the service creation environment. The most commonly used storage method is the graphical user interface. We used the method of storing the service logic data input through the external file.

However, such a conventional storage method includes a storage function inside the service specification function, so when a new SIB is added, deleted, or changed, the program of each tool including the storage function must be programmed directly. Not only does it take time and effort, but it also has the problem of changing the entire programming structure.

Therefore, in the present invention, to solve this problem, by calling the storage operation of the SIB component that is performed independently to store the data of the SIB component in a single file on a SIB object basis, the service creation environment can be easily expanded as well as information. To provide a storage device and method for the overall service logic in an open service creation environment that enables efficient storage of data.

In order to achieve the above object, the present invention configures a service creation structure to have a framework-based service creation environment structure in order to facilitate the expansion of an open service creation environment. In the framework-based service generation environment structure, since the information on each SIB existing in the server must be coordinated and stored as one general service logic, the independent information of each independently developed SIB is required. By tying them together, the aggregate service logic can be stored in a single file.

1 is a block diagram of a general service logic storage device according to an embodiment of the present invention;

2 is a structural diagram of a general service logic storage coordinator;

3 is an operation flowchart of an SIB operation;

4 is a data structure diagram of a general service logic storage coordinator;

5 is a process flow diagram for storing aggregate service logic in accordance with an embodiment of the present invention.

<Explanation of symbols for main parts of drawing>

11: client 12: overall service logic storage coordinator

14: external file 16: server

19: Object Request Broker

Hereinafter, with reference to the accompanying drawings will be described in more detail the storage structure and method of the overall service logic of the present invention.

1 is a block diagram of a general service logic storage device according to an embodiment of the present invention. Referring to FIG. 1, the general service logic storage device operates in a client 11-server 16 model. (11) The overall service logic storage coordinator 12, which plays a role, requests the SIBs of the server 16 to request / response (17, 18) through the object request broker 19 to obtain client information 13 of the object. After storing in the external file 13 by the general service logic storage coordinator 12 of the client 11, the overall service by storing the server information 15 stored in the server 16 in the external file 13 Allow the logic to be stored as an object in an external file.

2 illustrates a structure of a general service logic storage coordinator operating as a client in the general service logic storage device.

In general, users who use SIB components to store general service logic do not need to know the structure for SIB components to store SIB dependencies. They need to know the interfaces provided by the SIB components, such as attributes and operations. Just call the operation.

Accordingly, referring to FIG. 2, the general service logic storage coordinator includes a communication management block 26 for controlling communication with the SIB component 27 in which the developed SIB is stored, and the SIB component 27 in which a service development environment is developed. The SIB management block 25 which manages SIBs generated by the proxy SIB when inserted into the SIB and communicates with the communication management block 26, and common information storing location information of the object such as an arrow start point and an arrow end point. Communication management with the SIB management block 25 includes the storage block 22 and the information of the common information storage block 22, the number of the SIB, the name of the SIB, and the write operation of the SIB component 27. The SIB component storage block 23, which is called through the block 26, is used to store information held by the connected component, and includes information of the common information storage block 22 for the dialog object. Connection component storage block 24 which stores information about pointer, link name, next SIB name, POR type, POR number, POR type name, POR destination address, and user's event to perform overall service logic storage. When the event is converted into a semantic event, it is determined whether the object list consisting of the linked list belongs to the common information storage block 22, the SIB component storage block 23, or the connected component storage block 24. It consists of a user event processing block 21 for processing to store each.

As such, the information in the overall service logic storage coordinator is stored for each object in the common information storage block 22 and the connected component storage block 24, and the SIB component storage block 23 is a SIB component inserted into the overall service logic storage coordinator. It is a structure that can store the information of the inserted new SIB even if a new SIB is inserted, deleted or changed, without changing the routine for storing the overall service logic.

3 is an operation flowchart of an SIB operation, in which a graphic representation of an SIB operation of ITU-T Q.1223, an international standardization organization, corresponds to a data structure diagram for developing a SIB component and a connection component. Referring to FIG. The operation 31 starts with a logical start 36, ends with a logical end 37, and as input / output SIB data parameters 32, 33, part 1 (CID (Call Instance Data), SSD). (Service Support Data), Service Instance Data (SID),... , Part N (CID, SSD, SID), and process input and output (34, 35) as process name 1 (Point Of Initiation (POI), Point Of Synchronization (POS), Point Of Return (POR), … , Process name N (POI, POS, POR). In this case, the logical end point may have N.

The separation of data parameters and processes input / output to the SIB operation 31 is because N logical end points 35 have information about the next SIB connected at the starting SIB.

4 is a data structure diagram of the overall service logic storage coordinator. Referring to FIG. 4, the data structure of the general service logic storage coordinator includes an arrow object list 410 representing arrow objects, a dialog object 420 and 430, and a SIB. SIB object list 440 representing the objects, when the user selects the SIB from the toolbar, the general service logic storage coordinator is the SIB object 441 and the SIB including the location information, sib number and name of the SIB; Dialog objects 420 and 430 for handling the logical termination of the object 441 are created together to form a linked list.

In this way, the SIB object 441 created in the edit window designates the dialog object 420 of the SIB object as a pointer (s44), and links_name 421 and next_sib_num 422 of the specified dialog object 420. , next_sib_pos (423), POR (424) has a value initialized to the field. At this time, the POR (424) field has as many Links as dial objects, and the data for the POR connected with Basic Call Process (BCP) is type (431), num (432), and name (433). , dest_addr (434).

On the other hand, the connector component is shown as an arrow object 410, when the user connects the start SIB and the next SIB using the arrow, the arrow objects are composed of a linked list, and designates Link [i] of the dialog object as a pointer. s41) and assign a value.

In this way, when the editing of the overall service logic is completed and the user presses the save button in the file menu of the edit window, first, the arrow object lists 411 to 414 are called one by one to save the arrow object 410. To store the SIB objects 440 displayed on the screen, first store information, location information, sib number, and sib name of the general service logic storage coordinator, and then read () the SIB component 450. The storage is performed by calling the storage () operation (s45 to s47). In this way, the SIB component server 450 stores the stored information on the SIB component 450, so that a service developer adds, deletes, or changes a new SIB to process internal operations of read () and save () operations of the corresponding SIB component. Just implement the routine.

FIG. 5 is a flowchart illustrating a process of storing overall service logic according to an embodiment of the present invention, and when a user selects a storage menu for editing on a screen, a procedure of storing the overall service logic created so far is shown. Referring to FIG. 1, when a user selects a save menu using a mouse (S501), a dialog for recording a file name to be displayed is displayed, and the user records a file name to be stored. Then, open the external file to be saved with the file name entered by the user (s502) and make the object list of the overall service logic drawn so far, and search the object list (s503) one by one until the object list is not NULL (blank). Record the information of the object.

At this time, if NULL is encountered in the object list, only the information on the object in the object list is stored up to now and the file is closed (s510), and then terminated or waiting for the user's next selection (s511). If not NULL, the object is compared (s504), and if the SIB object stores the information of the overall service logic storage coordinator (s505) and delivers the storage message to the proxy SIB (s507) and then waits (s508). Then, the SIB component waits, receives a storage message of the general service logic storage coordinator, stores information in the same file used by the general service logic storage coordinator (s509), and retrieves the next object list.

On the other hand, if the searched object s504 is a connector object, information stored by the connector object is stored (s506), and the object list is searched to search for the next object.

As described above, the present invention calls for the storage operation of the SIB component to store the data of the SIB component in a single file on a SIB object basis so that the service creation environment can be easily expanded and the information can be efficiently stored. There is.

Claims (3)

A general service logic storage coordinator that controls the data of the SIB component to be stored in one file by SIB object unit, A server for storing the SIB component information; An object request broker configured to perform SIB information request and response between the general service logic storage coordinator and a server; And storing the client information of the object by the general service logic storage coordinator in an external file, and then storing the information of the server. 2. The system of claim 1, wherein the aggregate service logic storage coordinator is A communication management block for controlling communication with the SIB component in which the developed SIB is stored; A SIB management block which manages SIBs generated by proxy SIBs when the SIB component is developed and inserted into a service development environment, and performs communication with the communication management block; A common information storage block for storing location information of the object, such as the start point of the arrow and the end point of the arrow; A SIB component storage block for calling the SIB number, the name of the SIB, and the write operation of the SIB component including the information of the common information storage block through the SIB management block and the communication management block; It is used to store the information held by the connection component. It contains information on the common object storage block, including the pointer to the dialog object, the link name, the next SIB name, the POR type, the POR number, the POR type name, and the POR destination address. A connection component storage block for storing When an event of a user for performing overall service logic storage is input, the event is converted into a semantic event, and object lists composed of linked lists belong to any one of the common information storage block, SIB component storage block, or connected component storage block. Storage of the overall service logic in the open service creation environment, characterized in that the user event processing block for processing to determine the storage to store for each object. A first process of creating a linked list by generating a SIB object for processing the SIB object and a dialog object for processing the logical termination of the SIB when a user's request for generating the overall service logic is input; A second step of designating a dialog object owned by the SIB object generated in the first step as a pointer and initializing a field of the dialog object; A third step of connecting the SIBs by an arrow object when a user selects a start SIB and a next SIB to generate the overall service logic; A fourth process of constructing a linked list of information of SIBs connected by the arrow object; When the user's request for storing the generated overall service logic is input, an open service generation environment comprising a linked process comprising a fifth process of calling arrow objects connecting SIBs one by one and storing them in an SIB component. To store global service logic