KR100265077B1 - Method and apparatus of generating interactive services which uses short message service - Google Patents

Abstract

Disclosed are a method and apparatus for creating an interactive service using a short service. In the wireless network environment in which the short service is provided, the apparatus for generating a service according to the present invention includes an operation instruction file generator for indicating a service flow by a network operator, an operation instruction file generated by the generator, a runtime engine that actually executes the file, Session managers that exchange runtime engine and user property information; short message service center interfaces used to request short message transmissions to actual short message centers; action instruction file generators, runtime engines, and events generated by the session manager. And an output device for recording and displaying the system status, operation status, etc. of the event processed by the event manager and the event manager for transmitting to the appropriate output device.

Description

Method and apparatus for creating interactive service using short service

The present invention relates to a method and apparatus for creating an interactive service using a short service, and more particularly, to a method and apparatus for easily and conveniently providing and modifying a new service by providing an environment for easily creating and modifying an interactive service. .

Short service is a service that allows a short message to be exchanged through a network between two entities capable of transmitting and receiving letters and numbers. As is well known to those skilled in the art, an entity herein refers to an object capable of transmitting and receiving short messages such as a terminal device, a system, or a program. In general, such short service can be divided into one-way short service and two-way short service.

In the one-way short service, an entity capable of transmitting a short message transmits a letter or number to a corresponding terminal device. The terminal device is a type of service that displays information received on the subscriber display device so that the subscriber can recognize it.

The two-way short service transmits a text or numeric message to a device capable of processing a short message through a terminal device, and the received entity is a service that appropriately processes the short message.

1 is a configuration diagram of a wireless network environment. An application block that will provide a short message service in the wireless network 100 is an entity requesting transmission to a short message service center (SMSC). The actual transmission of the short message to or from the terminal 130 is handled by the SMSC. The flow of the service informs the signal network 110 of the location registration system 120 where the location of the mobile station 130 or the terminal 130 is registered. Thereafter, the short message is transmitted to the terminal through the exchange 150, and finally through the base station and the control station 140. As such, the SMSC provides an interface between the network and the service application block.

For example, a message generated by a service application block requests transmission to a corresponding terminal device through an interface between SMSCs. The transmission to the actual terminal is transmitted by the SMSC to the network according to the called party address, and the transmission result can be reported back to the service application block. When a short message is generated at the terminal, the SMSC determines whether to route the short message to the service application block according to the called party address or transmit the short message to another terminal.

In an environment where a short message service is provided to such a terminal or a mobile station, various types of information provision services are possible, and the forms of the two-way short message services such as weather and news and two-way short message services such as account inquiry and poll are mutually communicated. It may be a brother.

However, a bidirectional service in a network environment in which a conventional short service is provided is not specifically implemented, and is only partially used in the fields of an audio response system (ARS) and a voice mailing service (VMS).

As such, some ARS and VMS fields use a production tool for easily configuring a service to a user, but there is no authoring tool that provides a service in a conversational form to a subscriber in a network environment in which a short service is provided. Therefore, whenever a new type of service is required, a program must be implemented by a programmer, and when an existing service method or flow is changed, there is a problem in that the existing implemented program must be modified every time.

Therefore, the present invention was devised to solve the above problems, and provides an environment in which anyone can easily create and modify a conversation type service so that it is easy to provide and modify a new service. An object of the present invention is to provide a production method and apparatus.

Still other objects and advantages of the present invention will become more apparent from the following detailed description when read in conjunction with the accompanying drawings.

1 is a configuration diagram of a wireless network environment to which the present invention is applied.

2 is a block diagram of an interactive service generating apparatus according to the present invention.

3 is a message processing flow diagram between a session manager and a runtime engine.

4 is a flowchart of an interactive service creation method according to the present invention.

5 is a screen configuration diagram of an initial cell according to the present invention.

6 is a screen configuration diagram of a responsive cell according to the present invention.

7 is a screen configuration diagram of a processing cell according to the present invention.

8 is a screen configuration diagram of an error handling cell according to the present invention.

9 is a screen configuration diagram of a retry processing cell according to the present invention.

10 is a screen configuration diagram of a termination cell according to the present invention.

<Explanation of symbols for the main parts of the drawings>

100: interface network

110: signal network

120: location registration system

130: mobile station

140: base station and control station

150: exchanger

200: operation instruction file generator

210: runtime engine

220: session manager

230: short message service center interface

240: operation instruction file

250: Event Manager

260: output device

In order to achieve the above object, according to the present invention, the preferred embodiment of the interactive service generating apparatus using a short service,

In a wireless network environment in which a short service is provided, an operation instruction file generator for a network operator to instruct a service flow, an operation instruction file generated by the generator, a runtime engine that actually executes the file, and a runtime engine and a user's A session manager for exchanging property information, a short message service center interface used for requesting a short message transmission to a real short message center, the action instruction file generator, a runtime engine, and an event generated by the session manager to an appropriate output device. And an output device for recording and displaying a system state, an operation state, and the like of an event manager to transmit and an event processed by the event manager.

In an embodiment of the present invention, the operation instruction file may include a cell number, a cell name defined by an operator, a type of a cell, a short content input that is a short message to be transmitted to a terminal, a next performed cell number to be performed according to a user response, It is preferable that the cell consists of a plurality of cells consisting of the next cell number and the number of cell executions.

One of the elements constituting the cell is one of the forms of the cell, which requires the response of the user to perform the next processing, the processing of the user's response and automatically moves to the next cell number, and one of the forms of ending. Is preferably,

The session manager preferably further includes a storage device such as a subscriber number, a subscriber station type, a class of service, and a number of retries after allocating necessary storage areas for the subscriber.

To achieve another object of the present invention, a preferred embodiment of the interactive service generation method using the short service according to the present invention,

In a wireless network environment in which a short service is provided, an initialization step of a short service to be provided, a response cell generation step by the initialization process, a process cell generation step according to a user response to the response cell, and the processing cell Requesting transmission to the user for an error, error checking for the user's transmission, creating and terminating an error handling cell if there is an error by the checking process, and ending cell if there is no error by the checking process. It comprises a step of generating and ending.

In another embodiment of the present invention, the initialization step includes a service file name generated by a runtime engine that actually executes the file, and a timeout time by a session manager that exchanges characteristic information of the user with the runtime engine. It is preferable to create an initialization cell containing the contents such as the number of retries.

The session manager preferably transmits a message informing the start of a new user and information on the subscriber terminal type to the runtime engine.

Preferably, the session manager sends an operation information to a runtime engine such as a message indicating that the user is terminated and whether the termination message is a non-response or abnormal termination from a subscriber.

Preferably, the runtime engine sends an end response message to the end message to the session manager.

Preferably, the runtime engine is operable to send a message to the session manager that the next message from the current user is waiting for operation.

Preferably, the session manager operates to initialize the number of retries to zero upon receiving the message.

Preferably, the session manager notifies the runtime engine of the information when a new message arrives from the current user.

The step of generating a responsive cell includes the contents of a service, the number of response digits of a user for a regular service, the processing of a user's response, the contents of a transmission message in case of error, the number of the end cell when a timeout occurs, and the number of the end cell when a retry occurs In this case, it is preferable to create an initialization cell including contents of the ending cell number in case of an error.

The processing cell generation step may include a number of the processed cell, a name of the processed cell, a number of the next cell to be moved after processing, a message content of a cell to be transmitted to the user from the processed cell, and the number of times the processed cell is performed. It is preferable to create a treatment cell including the contents of

The error handling cell may include a number of the error handling cell, a name of the error handling cell, a shape of the error handling cell, a number of a next cell to be moved after processing, a message content of a cell to be transmitted to a user in the error handling cell, and the error. It is preferable to generate an error processing cell including contents such as the number of executions of the processing cell,

The error processing cell generation step may include a retry processing cell generation step including a cell number, a cell name, a cell type, a number of a next cell to be moved after processing, a message content to be sent to a user, and a number of retries. It is preferable to further include,

The terminal cell includes a cell number including the cell number of the terminal cell, the cell name of the terminal cell, the type of the terminal cell, the contents of the message to be sent to the user, the number of times the terminal cell is performed, and the like. It is desirable to produce.

On the other hand, the features and functions of the well-known short message service are not described in detail in order not to obscure the present invention, and the same term is used in English initials or Korean language for convenience of explanation and understanding.

2 is a block diagram of an interactive service generating apparatus according to the present invention. Referring to the configuration of the interactive service generating apparatus according to the present invention with reference to the drawings, the interactive service generating apparatus,

An operation instruction file generator 200 for a network operator to instruct a service flow, an operation instruction file 240 generated by the generator, a runtime engine 210 that actually executes the file, the runtime engine 210 and a user A session manager 220 for exchanging characteristic information of a short message service center interface 230 used to request a short message transmission to an actual short message center, the operation instruction file generator 200, a runtime engine 210, a session An event manager 250 for processing an event generated by the manager 220 and transmitting the event to an appropriate output device, and an output device 260 for recording and displaying the system state, operation status, etc. of the event processed by the event manager. It is composed.

Here, the operation indicator generator is a device for generating an operation instruction file according to the service flow defined by the operator. The action instruction file created by the action indicator generator is sequentially read and executed by the runtime engine when an actual user is connected. This requires a promised exchange of information between the runtime engine and the session manager. Short messages to and from the service user are actually required to be sent to the short message center via the Short Message Service Center Interface Module.

The results of all these operations are sent by the event manager to the appropriate output device. First, an operation instruction file is generated by using an operation instruction file generator for a service scenario to be provided. This action instruction file specifies what action to take. The runtime engine simply reads the action instruction at the corresponding position and executes the action defined there. This operation instruction file is composed of several cells.

One cell has several areas depending on the shape. The type is a cell number area, a name area of a cell defined by an operator, a cell type area, a content input area of a short message to be transmitted to a terminal, a next cell number area to be performed according to a user response, a cell execution area, and the like.

One cell may have one of the three forms above. In the case of responsive cell, it is the cell to perform the next process only after receiving the user's response, and the processed cell is the cell that processes the user's response and automatically moves to the next cell number. Becomes The cell information generated by this device is stored in the form of document in the file entered by the operator when creating the service scenario, and the previously created action instruction file is inquired, changed, deleted and displayed in the flow chart by the action instruction file generator. Is possible.

When the service request arrives from a new subscriber, the session manager checks whether the subscriber is confirmed, allocates the necessary memory for the subscriber, and stores information necessary for the service such as subscriber number, subscriber terminal type, service grade, and retry count.

The message format exchanged between the session manager and the runtime engine will be described with reference to the message processing flowchart between the session manager and the runtime engine of FIG. 3.

The 'START' message is a message that the session manager notifies the runtime engine about the start of a new user. The session number at this time is assigned by the session manager and serves as a key for identifying the subscriber. The terminal type is a type of terminal used by the subscriber and distinguishes between English only and native language.

The 'END' message is a message that the session manager informs the session manager that the user has terminated and contains the session number and the form of termination (no response from subscriber, abnormal termination, etc.).

The 'END_RESP' message is an end response message sent by the runtime engine to the session manager.

The 'WAITING' message indicates that the runtime engine is waiting for the next message from the current user to the session manager, and the session manager receiving the message sets the number of retries to zero. The message also includes the session number, the number of the cell currently being processed by the runtime engine, and the content of the message to be sent to the subscriber.

The 'NEW' message is a message that the session manager notifies the runtime engine that a new message has arrived from the current user.

If a short message arrives (300) by the user via SMAC and the short message is found to be the first message initiated by the new subscriber by the session manager, the session manager sends a START message to the runtime engine to initiate (310). You will be informed. The runtime engine then finds the first one in the action instruction file and takes the action 320 of the type specified in the action instruction.

For example, if a short message needs to be sent, the appropriate short message is requested according to the terminal type, and the session manager makes the retry count for the session to 0 at the time of receiving the message (320) (325). When there is no response after the time specified for 330, a timeout message is sent to the runtime engine, which receives the runtime engine and takes action to perform at timeout.

If the user sends a value that is not defined (340), the runtime engine sends a 'RETRY' message and the session manager that receives it increases the number of retries and then sends a 'END' message if it equals the number of retries defined by the system. To transmit 350. In this case, the termination type cell is indicated by the termination reason. According to this termination form, the runtime engine performs the corresponding termination cell. In this case, the session manager is notified that the processing is completed in the form of 'END_RESP' message, and the service is terminated. The same session manager requests to be sent to the connected SMSC using the short message service center interface.

If the connected SMSC changes, only the short message service center interface part needs to be changed. If a new message arrives from the subscriber, the session manager sends a message in the form of a new message to the runtime engine. At this time, since the current runtime engine includes the cell number to be processed, the runtime engine reads the cell number and processes the next operation according to the response code of the received message.

An operation method of the system will be described with reference to a flowchart of an interactive service generation method according to the present invention of FIG. 4. In operation of the system, in a wireless network environment in which a short service is provided, initializing a short service to be provided is performed (400). Then, a responsive cell is generated by the initialization process (410). A processed cell is generated according to the user response 420 for the cell. [0044] Thereafter, request for transmission to the user for the processed cell is requested (440, 450) and an error for transmission of the user is generated. Next, if there is an error by the checking process, an error processing cell is generated and terminated (480) (500). If there is no error by the checking process, a closing cell is generated and terminated. Operation 470 and 500 is performed.

The above operation will be described below by way of example. First, a file name of a service scenario to be created currently and a system parameter required for a service are specified as a screen configuration diagram of an initial cell according to the present invention of FIG. 5. The scenario file name is referenced by the runtime engine and the timeout or retry count is managed by the session manager.

Then select the responsive cell from the cell generation menu. A window for creating a responsive cell is a screen configuration diagram of the responsive cell according to the present invention of FIG. 6. Enter the appropriate contents in each area according to the defined scenario. In this case, if the user response digit is 2, up to 20 call numbers can be entered.

When this service is started, the runtime engine reads this cell and sends the content area in short to the session manager. In this embodiment, it is assumed that the content is only supported in Korean, but in the case of a terminal that does not support the native language according to the type of subscriber terminal, the English content may be transmitted.

The session manager sends the message received from the runtime engine to the subscriber via the short message service center interface. At this time, the operation status can be sent to the event manager so that the progress can be displayed to the operator or left in the system. When the subscriber sends a response to the received message in a short message, the next cell is processed according to the response.

For example, the runtime engine receives 0 from the session manager as a subscriber response for cell 1, reads cell 2, processes it, and if a response message out of the menu is received, it sends a message to be sent in error and increases the number of retries. Let's do it. If the subscriber retries for each cell is greater than the scenario presentation, the retry end cell is processed for that subscriber.If the response does not arrive within the specified time, the subscriber reverts to the timeout end cell. Will move.

Next, we create a processed cell for each user response. 7 is a screen configuration diagram of a processing cell according to the present invention. As shown in the figure, the processed cell requests to send the defined content to the terminal and moves to the next cell without waiting for the user's response. Each time this cell is performed, the number of times the cell is processed increases.

Then, when each error occurs, a cell is created as shown in the screen configuration diagram of the error-processing cell according to the present invention of Fig. 8 and the screen configuration diagram of the retry processing cell according to the present invention of Fig. 9. Through the error processing cell, the number of errors generated by each user may be counted.

Thereafter, a short message service is created by completing the termination cell according to the present invention of FIG. 10. In the above description, the present invention has been described and limited by way of example with reference to the drawings. However, it will be apparent to those skilled in the art that various changes and modifications can be made without departing from the spirit of the present invention. will be.

Therefore, it is to be understood that the invention is not limited to the specific forms referred to in the specification, but rather that the invention is defined by all the modifications, equivalents and equivalents within the spirit and scope of the invention as defined by the appended claims. It should be understood to include substitutes.

The present invention operating as described above has the effect that anyone can easily and quickly create and modify a new service by using a self-made tool that provides a service to a subscriber in a network environment in which a short service is provided.

Claims (17)

An operation instruction file generator for indicating a service flow by the network operator; An operation instruction file generated by the generator; A runtime engine that actually executes the file; A session manager for exchanging characteristic information of the user with the runtime engine; A short message service center interface used to request transmission of a short message to an actual short message center; An event manager which processes the events generated by the operation instruction file generator, the runtime engine, and the session manager and sends them to an appropriate output device; And And an output device for recording and displaying a system state, an operation state, and the like of an event processed by the event manager. The method of claim 1, wherein the operation instruction file, Comprised of a plurality of cells consisting of a cell number, a cell name defined by the operator, the type of the cell, the short content to be sent to the terminal, the next cell number to be performed according to the user response, the next cell number and the number of cell executions, Interactive service generation device using a short service. The form of a cell according to claim 2, wherein the cell is one of the elements constituting the cell. To receive the user's response to perform the following processing; Process the user's response and automatically move to the next cell number; The form meaning the last termination; Interactive service generation device using a short service, which is one of. The method of claim 1, wherein the session manager, And a message for notifying a start of a new user and information about a subscriber's terminal type to a runtime engine. The method of claim 1, wherein the session manager, And sending a form information such as a message indicating that the user is terminated and whether the termination message is a non-response or abnormal termination from the subscriber to the runtime engine. The method of claim 5, wherein the runtime engine, And send a termination response message for the termination message to a session manager. The method of claim 1, wherein the runtime engine, An apparatus for creating an interactive service using a short service, which transmits a message to the session manager that the next message is waiting for the current user to operate. The method of claim 7, wherein the session manager, And upon receiving the message, initialize the number of retries to zero. The method of claim 1, wherein the session manager, And inform the runtime engine of the information when a new message arrives from the current user. The method of claim 1, wherein the session manager, And a storage device such as a subscriber number, a subscriber station type, a service grade, a retry count, and the like, after allocating necessary storage areas for the subscriber. Initializing a short service to be provided; A response cell generation step by the initialization process; Generating a processed cell according to a user response to the responsive cell; Requesting transmission to a user for the processed cell; Error checking for transmission of the user; Creating and terminating an error handling cell if there is an error by the checking process; And And if there is no error due to the checking process, generating and terminating a termination cell. The method of claim 11, wherein the initializing step, A service file name is generated by a runtime engine that actually executes the file, and an initialization cell including contents such as a timeout time and a number of retries is generated by a session manager exchanging property information of the user with the runtime engine. How to create an interactive service using a short service. The method of claim 11, wherein the generating of the responsive cell comprises: The contents of the service, the number of digits of the user's response to the service at all times, the processing of the user's response, the contents of the transmission message in case of error, the number of the end cell in case of timeout, the number of the end cell in case of retry, the number of end cell in error An interactive service generation method using a short service, which generates an initialization cell including the contents of the. The method of claim 11, wherein the generation of the processed cell, A processing type including a number of the processing cell, a name of the processing cell, a number of the next cell to be moved after processing, a message content of a cell to be transmitted to the user from the processing cell, the number of times the processing cell is performed, and the like An interactive service creation method using a short service that creates a cell. The method of claim 11, wherein the error processing cell, The number of the error handling cell, the name of the error handling cell, the type of the error handling cell, the number of the next cell to be moved after processing, the message content of the cell to be sent to the user from the error handling cell, the number of times the error handling cell has been performed, and the like. An interactive service generation method using a short service, which generates an error handling cell including the contents of the. The method of claim 11, wherein the error processing cell generation step, And a retry processing cell generation step including the number of cells, the name of the cell, the type of the cell, the number of the next cell to be moved after processing, the contents of the message to be sent to the user, the number of retries, and the like. How to create an interactive service. The method of claim 11, wherein the termination cell, A short service for generating a cell including contents of a cell number of the terminal cell, a cell name of the terminal cell, a type of the terminal cell, contents of a message to be sent to a user, and a number of times the terminal cell is performed; How to create an interactive service.