KR20010058742A - Connection and traffic management classified by the ESME in the SMSC system - Google Patents

Abstract

PURPOSE: A method for managing connection and traffic between ESMEs(External Short Message Entities) in a short message system is provided to support an efficient operation of a network, by making a TCP/IP connection status monitored and controlled. CONSTITUTION: A SMSC(Short Message Service Center) reads an environment setting file to secure a memory area, and initializes it(1). An ESME records that there is an access request to a client database(2). The ESME records what kind of service has requested an access and has succeeded in the access(3). The SMSC module exchanges data with the ESME(4). The SMSC module increases an attribute value by one whenever it receives and transmits data(5). The SMSC module checks the traffic(6), and stores the checked traffic in a traffic file(8). If there is not a change in the traffic, the SMSC module stops the connection with the ESME, and forces a client to perform a socket polling for making the access again(9,10).

Description

{Connection and traffic management classified by the ESME in the SMSC system}

The present invention relates to an ESME connection and traffic management method of a short message system, and in particular, to detect and control the connection status and traffic between external ESME interworking with a Short Message Service Center (SMSC) The present invention relates to an ESME connection and traffic management method of a short message system that manages connection status and traffic between external ESMEs that interoperate with SMSC to support more efficient network operation.

1 is a schematic block diagram showing a network configuration using a text message service in general.

Referring to FIG. 1, a network configuration using a text message service is a voice message system (VMS) that provides a voice mail service required for SMSC 200 and SMSC 200 to provide a short message using a wireless network. 10, Information Service Provider (ISP) 20, ESME 100 acting as a client, Home Location Register (HLR) and mobile switching center connected to SMSC 200 (MSC: Mobile Switching Center) (30).

At this time, ESME (External Short Message Entity) 100 mainly uses TCP / IP and uses SMPP and SMCI as communication protocols between application program layers. These communication protocols provide functions such as flow control, data error checking, and connectivity. SMPP defines communication protocols related to Alsdiscon's SMSC and provides functions such as Connect, Send, Reeceive, Cancel, Query, Link, Close to ESME so that SMSC and ESME can send and receive messages.

SMCI is a communication protocol defined by NewNet, and provides functions such as Connect, Send, Reeceive, Cancel, and Query.

Figure 2 shows a message processing procedure by the communication protocol between the ESME and SMSC. In FIG. 2, (a) indicates SMPP transmission, (b) indicates SMPP reception, and (c) indicates SMCI.

As shown, the ESME, as a client, sends a message for connection to the server, SMSC, and if this is successful, the SMSC sends a normal ACK. Then, the ESME transmits data and transmits a result according to the functions provided by the communication protocol.

The ESME uses its IP address, name, and password to request a connection. The server accordingly determines the type of service and has a processing procedure accordingly. The SMSC manages the connection state by recording the connection time according to the service and the ID of the generated process in the client's database.

However, the ESME tries to connect to send a message to the SMSC, and if successful, performs the functions provided by the communication protocol. The SMSC registers the resource in the client data DB after allocating the resource successfully according to the client's connection request. It is classified based on IP address, name and password of client side. In addition, this is done by the ESME and normal procedures, and problems in the subsequent message delivery can be overlooked.

In this case, even if either of the blocking state is maintained while the connection is maintained and the message is not transmitted or received, the connection remains in a normal state, making it difficult to detect whether there is a problem in the interface between the ESME and the SMSC. This is a disadvantage that can cause a big problem in the service management between the ESME operator.

The present invention was created to solve the above problems, and detects the connection status and traffic between the external ESME interworking with the Short Message Service Center (SMSC), and monitors the abnormal TCP / IP connection status and The purpose of the present invention is to provide an ESME connection and traffic management method of the SMSC system that manages the connection status and traffic between the SMSC and the external ESME interworking with the SMSC to support more efficient operation of the network.

1 is a schematic block diagram illustrating a network configuration generally using a text message service.

2 is a flowchart illustrating a message processing procedure based on a communication protocol between an ESME and an SMSC.

Figure 3 is a schematic block diagram showing the configuration of a connection management and traffic management system for the continuous service between the ESME and SMSC in accordance with the present invention.

4 is a flowchart illustrating a connection management and traffic management procedure for each ESME of the SMSC system.

<Explanation of symbols for main parts of the drawings>

10: VMS 20: ISP

30: HLR / MSC 100: ESME

200: SMSC 210: SMSC main module

220: configuration file unit 230: ESME

231: client memory unit 232: client DB

233: traffic file unit 234: alarm unit

240: GUI I / F

In order to achieve the above object, the ESME-specific connection and traffic management method of the short message system according to the present invention includes a client DB and a memory area in itself for connection and traffic management between clients in the SMSC system; When connected to the ESME acting as a client, it records in the client DB what kind of service requests the connection and the connection is successful. When the resource is successfully allocated according to the connection request from the client side, an empty space is found in the memory area. Setting a flag; counting the number of times while performing data transmission / reception with the connected ESME, checking the connection state and the traffic state, and disconnecting the ESME when there is no traffic change in the connected state, thereby reconnecting the ESME. And attempting to try.

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

3 is a schematic block diagram illustrating a configuration of a connection management and traffic management system for continuous service between an ESME and an SMSC according to the present invention.

As shown, the connection management and traffic management system for each ESME of the SMSC system according to the present invention includes an SMSC main module 210 that operates as a server for providing a short message service to the ESME 100 operating as a client, and an SMSC server. Configuration file unit 220 for configuration of the traffic storage and management procedures in the network, the ESME management area 230 to manage the connection and traffic between ESME clients, and the management status of the connection and traffic between ESME clients It consists of a GUI interface 240 that serves as an interface with the operator so that the operator can know.

ESME-specific management areas 230 separately provided to manage the connection and traffic between ESME clients themselves are connected to the SMSC server and the client memory unit 231 for allocating resources according to the client's connection request. Client database (DB) 232 for recording and managing the status of the connection and traffic for each ESME client, the traffic file unit for storing the traffic file, and the failures occurring when managing the connection and traffic for each client. It is composed of an alarm unit 234 for processing.

As described above, the connection management and traffic management system for each ESME of the SMSC system according to the present invention has a separate management area for each ESME managed by the SMSC while maintaining all configuration states between the ESME and the SMSC.

To this end, the SMSC server has its own client DB 232 and memory area 231 to manage connections and traffic between clients.

Table 1 shows the memory field structure of the client DB to be managed by SMSC.

Structure of Memory Fields to be Managed by SMSC Field name Contents Flag Setting value for current use Process ID Pid of the server that received the connection request Connect Time Connection time Total Number Sum of send / receive Send Number Cumulative number of times sent from SMSC to ESME Receive Number Cumulative number of transfers from ESME to SMDC Before Total Number Total number before count Before Send Number Sends before Count Before Receive Number Receive before count ESME Name Name of connected ESME ESME Password Password of the connected ESME

As shown in Table 1, the Flag field indicates the setting value of the current use, the Process ID field indicates the pid of the server that received the connection request, the Connect Time field indicates the time when the connection was made, and the Total Number field indicates the transmission / reception. The sum of the number of receptions.

The Send Number field shows the cumulative number of times sent from SMSC to ESME, the Receive Number field shows the cumulative number of times sent from ESME to SMDC, the Before Total Number field shows the total number before counting, and the Before Send Number field shows the count before sending. The Receive Number field indicates the number of receptions before counting, the ESME Name field indicates the name of the connected ESME, and the ESME Password field indicates the password of the connected ESME.

4 is a flowchart illustrating a connection management and traffic management procedure for each ESME of a short message system. Looking at the connection management and traffic management procedures for each ESME of the SMSC system with reference to Figure 4, the SMSC main module 210, which operates as a server first, reads the configuration file unit 220 at initial startup to secure a memory area and initializes it. (Step 1). At the time when the ESME attempts the initial connection (step 2), it records that there is one connection request to the client DB 232. Afterwards, a banner message is sent and received, and a record of what kind of service is requested by access is successful (step 3).

On the other hand, when the SMSC main module 210 successfully allocates resources according to the client's connection request, the SMSC main module 210 searches for an empty space in the memory area 231 and sets a flag. Then, data is transmitted and received with the connected ESME 100 (step 4). In addition, whenever the processing to be transmitted to the ESME 100 and received from the ESME 100 is performed (step 5), the traffic flowing in the connected state is checked (step 6) while adding to the value of the attribute (step 5). The file 233 is stored. Depending on whether the check result is normal (step 8), if normal, data transmission and reception with the ESME 100 continuously connected is performed, and if the check result is not normal, that is, either side is blocked while maintaining the connection. If the message is not sent and received, the connection is normally maintained, but the traffic data does not increase anymore. Therefore, if there is no change in traffic, the connection is disconnected and the client performs socket polling to induce reconnection (steps 9 and 10).

The traffic storage and management procedure as above allows to decide whether to use or not to save and through the configuration, and to accumulate data in the designated file.

As described above, according to the present invention, an abnormal TCP / IP connection state can be monitored and traffic flow can be monitored and controlled for each service. In addition, it is possible to provide alarms and GUIs so that operators can easily recognize them, and ultimately, they can contribute to the improvement of service quality and stability of ESME-specific services.

Claims (1)

A client DB and a memory area are provided in the SMSC system for client connection and traffic management by itself; When connected to the ESME acting as a client, it records in the client DB what kind of service requests the connection and the connection is successful. When the resource is successfully allocated according to the connection request from the client side, an empty space is found in the memory area. Setting a flag; Counting the number of times while performing data transmission / reception with the connected ESME, and checking the connection state and the traffic state so that the connection with the ESME is disconnected when there is no traffic change in the connected state, thereby causing the ESME to reconnect. ESME connection and traffic management method of a short message system characterized in that the.