KR0150532B1 - Execution method of intelligent service logic using fsm - Google Patents

Abstract

The present invention relates to a method of performing an intelligent network service logic using a finite state machine. In the method of performing an intelligent network service logic using a finite state machine applied to a service logic execution environment of an intelligent network system, an information flow is inputted to a message queue. A first step (100 to 102) of reading the received information flow from the message queue and confirming whether the input information flow is an information flow requesting a new call; If the information flow requesting a new call in the first step (100 to 102), a service logic instance (SLI) is created, and the information about the new call (call request difference, requested service name, Inserts the state number q _o ), performs the action defined in the entry S [q ₀ , λ], transitions to the new state q _j , and enters if the input information flow IF _i is not an information flow requesting a new call. Retrieve the call table 60 entry corresponding to the call identifier loaded on the information flow IF _i and extract the state number q _j , perform the actions defined in the entry S [q _j , IF _i ], and return to state q _j . A second step (103 to 111) of grasping the state of the transitioned state q _j after the transition; And if the state q _j transitioned in the second steps 103 to 111 is a normal state, perform the action defined in the entry S [q _j , λ], transition to state q _j , and transition to If q _j is in the Wait state, the current state number is stored by updating the call table 60, and the transitioned state q _j is the final state and the behavior defined in the S [q _j , λ] entry is stored. Simulate the service logic in a test bed using a finite state machine with the same functionality as the intelligent network platform, including performing a third step 112-118 to delete entries for the current call in the call table 60, By displaying the simulation process on the screen, the user can observe the service operation.

Description

Implementation Method of Intelligent Service Logic Using Finite State Machine

1 is a functional block diagram of a service development environment prototype to which the present invention is applied.

2 is a functional block diagram of a service logic execution environment to which the present invention is applied.

3 is a conceptual diagram of a finite state machine used in the present invention.

4 is a table showing a service logic instance created by the service logic instance generator to which the present invention is applied.

5 is a driver diagram illustrating a service logic execution environment to which the present invention is applied.

6 is an overall flowchart according to an embodiment of the present invention.

The present invention relates to a method of performing intelligent network service logic using a finite state machine.

The development of communication services requires a high degree of expertise, and the service structure is complex and difficult, requiring a lot of time and effort. In addition, due to the development of the telecommunications industry, the service providers have no choice of designing and providing services that customers want one by one, but gradually the network operators or customers define services using the service creation environment (SCE). It is evolving. The service development environment describes a service by combining standardized parts that abstractly expresses the capabilities of the network. The service development environment automatically generates service software that can be executed on an intelligent network platform using an automation tool. Specifically, in service development environments, a high-level service description language that does not require a visual programming environment or advanced programming skills (for service architects or customers) to easily describe concepts for new services. Service Description Language). Service logic created using the service development environment must go through the verification process before being introduced into the network.

Accordingly, the present invention simulates service logic in a test bed using a finite state machine having the same function as an intelligent network platform, and displays a simulation process on a screen to allow a user to observe service operation. The purpose is to provide a method of performing service logic.

The present invention for achieving the above object is an intelligent network service logic execution method using a finite state machine applied to the service logic execution environment of the intelligent network system, when the information flow is input to the message queue reads the input information flow from the message queue A first step of confirming whether the input information flow IF _i is an information flow requesting a new call; If the information flow requesting a new call in the first step, a service logic instance (SLI) is created, and information about the new call (required call identification, requested service name, status number q _o ) is inserted into the call table. , performing the actions defined in the S [q _0, λ] entry and transitions to a new state q _j, and input information to flow IF _i a new call for which silryeoon to the or an input information flow IF _i information flow request call Retrieves the state number q _j by searching the call table entry corresponding to the identifier, performs the action defined in the entry S [q ₀ , IF _i ], transitions to the new state q _j , and then transitions to the state q _j Identifying a second step; If the state q _j transits from the second phase state normally _{(Normal), S [q j} , λ] , perform the acts defined in the entry, transition and is a transition state q _j standby state q _j (Wait ) State, updates and saves the current state number in the call table; if the transition state q _j is final, performs the action defined in S [q _j , λ] entry; And a third step of deleting an entry.

Hereinafter, with reference to the accompanying drawings will be described an embodiment of the present invention;

1 is a functional block diagram of a service development environment prototype to which the present invention is applied, in which 1 is an overall service logic editor, 2 is a distributed service logic converter, 3 is an extractor, 4 is a test bed, 5 is an information flow indicator, 6 shows the functional design relationship indicators, respectively.

The user describes the Global Service Logic (GSL) by combining a Service Independent builiding Blick (SIB) that abstractly expresses network capabilities using the General Service Logic Editor 1, which is a visual programming environment. The GSL of the general service logic editor 1 is converted into a distributed service logic (DSL) representing a message flow of functional entities constituting the intelligent network platform through the distributed service logic converter 2. The Distributed Service Logic Translator (DSL) 2 is composed of an Information Folw (IF) and a Functional Entity Action (FEA) between functional entities constituting the intelligent network platform. An information flow (IF) is represented by an information element (IE) which is data constituting the sending functional entity, the receiving functional entity, and the information flow IF. The functional entity operation (FEA) refers to a basic operation for performing a function required for an intelligent network platform. The extractor 3 extracts special resource information, trigger information, service logic, and data template from the distributed service logic converter (DSL) 2 to form the test bed 4 and the SRF 4-1 and SSF ( 4-2), SCF 4-3 and SDF 4-4. The service logic downloaded to the SCF 4-3 is performed in a Service Logic Execution Environment (SLEE) in the SCF 4-3. The information flow between the functional entities of the intelligent network platform is output through the information flow indicator 5 and the functional entity relationship indicator 6, and the user observes whether the service defined by the user operates as desired.

2 is a functional block diagram of a service logic execution environment to which the present invention is applied.

The service logic generated using the service development environment is stored in the service logic library 10, and events (e.g. specific digit dialing, on-hook) that the user can call the service logic using the testbed's phone When input, the service logic instance generator 20 converts the corresponding service logic into a service logic instance (SLI) 30, which is a finite state machine, and the service logic instance driver 40 converts the service logic instance (SLI). To drive.

3 shows a conceptual diagram of a finite state machine used in the present invention.

Circles in the figure represent states, in which 100 represents the start state and 107 represents the end state. The rectangles represent the actions performed during the state transition process. These actions include sending information flows to functional entities such as SDF (4-4), SSF (4-2), and SEF (4-1) 101, functional entity behavior 102, functional entity behavior results, or SDF. (4-4), there is an act 105 of comparing data of information flows received by the SRF 4-1 and SSF 4-2.

i ₁ (103) and i ₂ (104) are inputs causing a state transition, and represent information flows received from the SDF 4-4, SRF 4-1, and SSF 4-2. λ 106 causes a state transition to occur regardless of the input information flow.

4 shows a service logic instance created by the service logic instance generator to which the present invention is applied.

The generated service logic instance SLI consists of a two-dimensional array S [q _i , j]. q _i denotes a state and j denotes an input information flow. S [q _i , λ] acts on the entry defined regardless of the flow of input information, and S [q _i , IF _i ] waits for the information flow IF _i to enter, then IF _i enters the action defined on the entry. Do The former is called normal and the latter is called wait. The actions defined in the entry include Start, Send Information Flow, Function Entity Action, Condition Transition, Transition to State q _# and End Service.

The start indicates the action of the start of the service logic, the information flow transmission is the action of sending the information flow IF _# , and the function entity action indicates the action of performing the function entity action fea _# .

The conditional transition indicates a transition to state q _# only if the condition C _# is satisfied. State q _# transition is an action of transition to state q _# , and service termination indicates the termination of the corresponding service logic.

5 is a diagram illustrating a driver configuration of a service logic execution environment to which the present invention is applied.

The service logic execution environment driver receives an information flow input to the message queue 80 in the functional entity access manager 50 and performs an action defined in the service logic instance SLI.

The call table 60 records information about the user requesting a call through a telephone connected to the test bed.

The service logic instance driver 40 may drive a service logic instance (SLI) for a plurality of calls through the call table 60.

Information stored in the call table 60 includes a call identifier (call_id), a service identifier (service_id), a state number (state_num), and the like.

6 is a flowchart illustrating a service logic execution according to an embodiment of the present invention.

The service logic instance driver 40 waits for the information flow to be input to the message queue 80, and when the information flow is input (100), the service logic instance driver 40 reads the input information flow from the message queue (101) and inputs the information flow IF _i to a new value. Confirm 102 that it is the information flow requesting the call.

If the check result is an information flow requesting a new call, a service logic instance (SLI) is created (103), and information about the new call (requested call identifier, requested service name, status number q ₀ ) is displayed in the call table 60. Insert (104), perform the action defined in the S [q ₀ , λ] entry (105), and transition to a new state q _j (106).

If the input information flow IF _i is not an information flow requesting a new call, retrieve the call table 60 entry corresponding to the call identifier carried in the input information flow IF _i (107) and extract the state number q _j (108). ), After performing the action defined in the entry S [q _j , IF _i ] (109), transitioning to the new state q _j (110).

If state q _j is a normal state (111), then perform the action defined in the entry S [q _i , λ] (112), transition to state q _j (113), and then state q _j is a normal state Repeat the process of identifying cognition. If it is in the Wait state (114), the current state number is updated by storing the call table 60 (115), and the state is returned to the initial state. In the final state, the action defined in the entry S [q _i , λ] is performed (117), the entry for the current call is deleted from the call table 60 (118), and the state is returned to the initial state.

The present invention operating as described above has the effect of simulating the service logic in the test bed using a finite state machine having the same function as the intelligent network platform, and displaying the simulation process on the screen so that the user can observe the service operation. .

Claims (1)

In the method of performing intelligent network service logic using finite state machine applied to the service logic execution environment of intelligent network system, when the information flow is input to the message queue, the input information flow is read from the message queue and the input information flow IF _i is a new call. A first step (100 to 102) of confirming whether the information flow is a request; If the information flow requesting a new call in the first step (100 to 102), create a service logic instance (SLI), and the information about the new call (requested call identifier, requested service name, status) in the call table 60 Insert the number q _o ), perform the action defined in the entry S [q ₀ , λ], transition to the new state q _j , and enter the information flow if the input flow _i is not an information flow requesting a new call. Retrieve the call number 60 entry corresponding to the call identifier carried in the information flow IF _i to extract the state number q _j , perform the action defined in the entry S [q _j , IF _i ], and return to the new state q _j . A second step (103 to 111) of grasping the state of the transitioned new state q _j after the transition; And if the state q _j transitioned in the second steps 103 to 111 is a normal state, perform the action defined in the entry S [q _j , λ], transition to the new state q _j , and transition to If state q _j is in the Wait state, the current state number is updated and stored in the call table 60. If the transitioned state q _j is in the Final state, the behavior defined in the entry S [q _j , λ] And a third step (112 to 118) of deleting entries for the current call in the call table (60).