KR20050088084A - Method and system for session management wherein a client session identifier is used - Google Patents

Abstract

An application server (113) receives, from a client mobile terminal (101), a request to initiate a first client application session, as well as first client specific data, where said data comprises a first mobile terminal identifier, e.g. a mobile station integrated wervices digital network number and a hash code. An association is made in the server (113) of a first client session identifier with the first mobile terminal identifier. The first client session identifier is then stored in a session management database (115). Maintenance of communication between the client terminal (101) and the application session is then enabled, including receiving a communication request and verifying that the communication request originate from the first client terminal (101).

Description

Method and system for session management where a client session identifier is used}

The present invention relates to a client session management method and a client session management system in an application server connected with a digital mobile communication system.

Increasingly, users are attempting to access services available through the Internet using mobile communication terminals. This desire will be fulfilled by both network operators and service providers, as part of which network operators and service providers are providing new innovative data services such as mobile e-mail access, for example.

Mobile client terminal devices used to access new innovative data services have significant advantages as well as limitations when compared to access devices such as conventional personal computers.

Special features are required to take advantage of the significant benefits of mobile clients such as mobile communication terminals.

However, special features are also required to overcome the limitations of these mobile access devices, which inevitably have limited data communication, processing and display capabilities compared to conventional personal computer access devices.

In other words, there is a need to provide new and innovative services to mobile client access devices.

Published International Patent Application No. WO 01/50701 describes a system for adapting service request fields and interfaces to service requests. The patent application describes how a plurality of mobile communication terminals communicate with an application server on a network.

Application session management allows a user to access an application from a first terminal and then maintain the session when the user accesses the application on a second terminal.

However, with regard to the prior art, an inherent problem with mobile communication is the intermittency of the communication channel between the mobile client device and the application server.

Such intermittence can cause problems such as disconnection due to radio communication interference while circuits are switching connections, and interruptions during circuit switching connections.

The intermittency may also be a matter of choice when disconnected packet switching communication is used. Connectionless communication is becoming increasingly common as mobile communication systems evolve into the so-called "3rd generation" and as the terminal supports software applications that can communicate with server applications on the Internet.

In addition, a problem may arise due to the connection between the mobile client device and the access service in the application server if the protocols that work together when the mobile client device requests a service are different. Therefore, better session management is required to provide better service to mobile client devices.

1 structurally illustrates a mobile communication system coupled with a packet switching network including a system according to an embodiment of the present invention.

2 is a flowchart of a method for installing and managing a client session according to an embodiment of the present invention.

An object of the present invention is to solve the above-mentioned problems in the session management method and system.

The object of the invention is realized by the method according to claims 1 and 15, the system according to claim 10 and the computer program according to claims 17 and 18, the details of which are as follows.

The present invention relates to a client session management method in an application server. The client application server may communicate with at least one client mobile communication terminal via a connectionless communication protocol, where the terminal is located in a digital mobile communication system.

The client session management method includes, in the most general aspect, maintaining at least a first client session identifier, wherein the client session identifier is associated with a client terminal identifier.

The client session management system according to an embodiment of the present invention is configured to communicate with at least one client mobile communication terminal through a connectionless communication protocol in a digital mobile communication system.

The system, in the most general aspect, comprises means for maintaining at least a first client session identifier, wherein the first client session identifier is associated with a client terminal identifier.

In another aspect, the present invention solves the problems of the prior art by providing a client session management method in an application server in a digital mobile communication system.

The application server communicates with the client mobile communication terminal using successive connectionless communication protocol messages. The server receives a service request from a service application through a service application server.

The server then determines a first client session identifier associated with the client terminal identifier based on the request. Then, the first client session identifier associated with the client terminal identifier of the client mobile communication terminal is maintained. The session identifier indicates a session with the client terminal between successive messages.

In one preferred embodiment of the present invention, the method and system of the present invention comprise a plurality of steps and a plurality of means for performing the steps.

The steps include receiving a request to initiate a first client application session from a client terminal, receiving first client specific data, wherein the data is, for example, a mobile station integrated service digital network number and hash. A first mobile terminal identifier such as a code.

For example, an association establishes between the first mobile terminal identifier and the first client session identifier by calculation.

The first client session identifier is stored in a session management database. Continuous communication is possible between the client terminal and the application session, the continuation of which includes receiving a communication request and confirming that a communication request originated from the first client terminal.

A preferred embodiment of the present invention may further comprise using a timeout procedure to disable communication between the client terminal and the application server. Disabling communication between the client terminal and the application server depends on the timeout limit.

In one preferred embodiment of the invention, the process of processing an e-mail message is described in the section on processing a list of messages.

The message includes a number of headers of items retrieved from the email server inbox to the application server, wherein a number of headers can be sent from the application server to the mobile terminal taking into account the constraints of the system used.

The next available message includes a predetermined number of headers and a message list substantially in the header lists.

An advantage of the present invention is that the mobile communication terminal can be used more flexibly when accessing a service in a connectionless environment such as, for example, the Internet.

In connection with FIG. 1, the mobile client terminal 101 is connected to the digital mobile communication network 105 via the air interface 103. The digital mobile communication network 105 is a network structure apparent to those skilled in the art, such as a very widely used GSM / GPRS system.

A short message service center (SMSC) 107 is connected to the mobile network 105. The SMSC 107 may receive a text message from the mobile terminal 101, another mobile terminal connected to the mobile network 105, and send the message to a receiver in the packet switching data network 109, for example, as described below. Transfer to the application server 113.

The short message service center 107 is connected to a packet switching (Internet) network 109 and utilizes HTML, HTTP, and TCP / IP Internet network protocols. Short messages are sent between the service center 107 and the mobile station.

The user sends a short message containing the service identifier to the short message service center 107 to process the short message in the application server 113.

The application server 113 recognizes the requested service and transmits the message to the service application server 117 capable of processing the service.

According to the service request, the service is transmitted to the mobile client device 101 through the application server 113, and the mobile client device receives the requested information in the short message. The mobile station 101 processes the received message and returns the message to the user according to the selected procedure.

The service center 107 is connected to the mobile communication network through a gateway (not shown), as will be apparent to those skilled in the art.

For example, the service center 107 is assigned as a dedicated ISDN number is assigned in a number space of a GSM network, and the mobile terminal is assigned an ISDN number for addressing a short message to the service center 107. Use

The mobile network 105 and the packet switching data network 109 are interconnected via a path 121, which may include any function necessary to transfer information between the networks.

For example, the path 121 may include a gateway switching center (GMSC) that will be apparent to those skilled in the art.

As a message is sent, the user is charged through a common billing system used by a telecommunications provider, such as a telephone service provider. For example, the user sends an SMS message to the application server 113.

The wireless network 105 operator may bill this service separately through the user's cell phone bill and use it at additional or lower rates in addition to including service usage charges.

The short message service gateway 111 (SMS gateway) and the application server 113 are connected to the packet switching network 109.

Each time the terminal sends a session request to the application server 113, the request is forwarded to the SMS gateway 111 by the SMSC 107 and the packet switching network 109.

The SMS gateway 111 converts the request and transmits the request to the application server 113. The request carries information including a mobile terminal identifier, such as, for example, a mobile station integrated service digital network number (MSISDN), when sent by the SMS gateway 111.

The application server 113 updates the session management database 115 and sends a response back to the terminal 101 via the SMS gateway 111.

Subsequent requests of the terminal 101 are processed at the application server 113 by using the session object in the application server session management database 115. As a result, the application server 113 can track the information transmitted to the mobile terminal 101.

The application server 113 executes session management software that can support a plurality of client terminals, such as the mobile terminal 101 shown in FIG. 1, and terminal users can reach an application running on the application server 113. To help.

Such an application can be a variety of applications, for example, an e-mail application can be used as described below.

The application server 113 receives a request from the client mobile terminal 101, preferably based on a command sent by the user. The command is included in a predetermined communication command list held by the application server 113. For example, a list of commands in the application session management database 115.

 In this case, the application server 113 maintains an e-mail message service so that the connection between the user and the server is not continuous unlike when the application server 113 runs an application that requires some constant interaction with the user. .

The application server 113 also maintains a communication database 119 to identify the user and tracks the commands in the sent messages sent earlier by the user.

The communication database 119 maintains the information for a predetermined time interval so that the user can take advantage of the pre-transmitted command even if there is a later request if the previously sent command is transmitted within a predetermined time interval.

For example, in an E-mail session, the user sends "m", which creates an active list for a predetermined timeout period, for example 20 minutes. These mails can be accessed by sending a predetermined identifiable message (eg 1,2, next, etc.) within the application server 113. Based on the command, the application server 113 starts not maintaining the session.

When a user requests a mail by entering "m" or entering a folder, the result is mainly an ordered list of items as follows.

1. Denver Jona: Project Status

2. Stones Tina: Copyright

McAllen Mar: Meeting Schedule

Within a mailing list, the sender and the mail subject are truncated to fit within the SMS message.

Send the number 1 from the list and retrieve the item within the time limit.

In the mail list, the contents of the mail (1) are

"This project is well underway. Research is included in the schedule. We don't have enough sales managers. Get ready by May. Have a great day. Jonathan"

The contents of the folder in the folder list are: subfolders and mail.

The numbers in the mail list can be used with commands such as reply, send, delete, mark read, and header.

The list is valid for a new list or for a certain time period (e.g. 20 minutes).

If the user receives a message stating "There is no mail on the list," it means that the list has expired since 20 minutes have elapsed, or the user has sent another command to create a new list to maintain a new session. Means that the requested number is not on the list.

Automatic notification brings a new list or mail during the timeout period while the user has an active list. The application server 113 creates a parallel session (buffer) for this list or mail.

The message starts with a zero slash and the message associated with the mail or list must be carried out by inserting the same symbol at the beginning of the text message. The user acquires the following,

1/3

0/

(Denver Jona:

FWD: Applied)

Then send 0 / to fetch the next text message page. In certain circumstances, the message may begin with another number, for example 1 / or 2 /.

During the limited time period (e.g. 20 minutes), the notification message brings another list of E-mail messages. Start with 0 /. This message is received in the inbox after the 20 minute session has started but prior to the limited time period.

These e-mail messages can be accessed by sending 0/1, 0/2, 0 / next, and the like. E-mail messages arrive after "m" has been sent or after an active list has been created.

Active list:

1. Denver Jona: Project Status

2. Stones Tina: Copyright

OR-list by notification message

0/

Smith Steve: Re: Update

Brown Jane:

The session manager software running on the application server 113 may also execute commands sent by the user and multi-user platforms (e.g., running multiple client applications) that enable processing of multiple clients on the server 113. Contains the command platform to interpret.

 For example, by sending an SMS message, the user is initially connected to the application server 113 with the mobile communication terminal.

The platform session management software application in the server 113 stores the identification code and is preferably based on a command sent by the user in the terminal's identification number or message, such as the mobile terminal's MSISDN. This information is stored in the communication database 119 which has its own unique information for each user.

The information regarding each user includes time information such as user name and password corresponding to various MSISDNs and at least, for example, the time when the session is initiated.

The information also includes a relative network address, such as where to go to find an e-mail server, for example, to extract unread e-mail messages within the e-mail account inbox. When "m" is reached, the server will start looking for the user's email message header that has been deployed to the user and identified.

The session management software then selects the selected message to send it to the mobile terminal 101. The header in this sentence means, for example, the number of marks specified from the "From field" to the title of the message.

The session management software determines whether to maintain the session and process the incoming command within the same session or another session based on the received command.

For example, the incoming command may be processed in a parallel session or in a single session in a manner that separates commands used by the same session or user and thus only one session may be maintained. As a result, if the user command causes a new session, only a new session will be maintained.

The session management software also sends a request corresponding to a command in a message received for the user to a software application that manages the user's email account.

The information defined by the command is selected and takes into account predefined criteria such as limitations of the communication protocol used by the user or user elements such as user terminals, user defined commands, and the like.

In the case where communication is via SMS messaging, the limitation is that only a certain number of E-mail headers can be sent to the mobile terminal 101 in one transmission.

The session manager maintains information of messages sent to the mobile terminal 101 and a possible list of notified messages that occur after the session is started.

After obtaining the requested information from the software application that manages the e-mail account, the server 113 sends the obtained information to the user using the same communication protocol as the SMS message.

Within a period of time, where the user is then connected to the server 113 and using a series of commands, the session management software interprets the commands and sends them to the software that manages the user's email account.

This allows for the transmission of consecutive information, taking into account an e-mail account, wherein the information is dependent on previous commands during the first connection.

After a period of time has elapsed, the user identification code and associated instructions are deleted, so that continuous communication is considered initial communication.

With reference to FIG. 2, the method according to the invention is described with a number of steps performed within the application server 113 and other components of the system shown in FIG. 1.

First, in the initialization step 201, the mobile terminal 101 initializes a connectionless session with the application server 113. The terminal 101 transmits the designated SMS request to the application server 113 in the transmission step (203).

After receiving the request in receipt step 205, in the assignment step 207, the session management software running in the application server 113 is assigned to the session object for the mobile terminal 101, and schedule information therefrom. Will be present in the application server.

Although communication between the application server 113 and the mobile terminal is connectionless communication, the session object performs a function of maintaining session data and terminal information in order to continuously communicate with the mobile terminal 101.

The communication session identifier is a unique MSISDN number with a hash code, whereby the user communicates via messaging and the server 113 is identified by the terminal 101.

The session management software tracks messages sent to the mobile terminal 101 and messages received from the service server 117. The session management software transmits a message not yet transmitted among the messages from the application server 113 to the mobile terminal 101 and then changes the status of the message in the application server 113. Let's do it.

The session management software also maintains information about the available commands. Requesting additional information of a specific E-mail message in the mobile terminal 101 will be processed as if a request made earlier was processed in the same session and the request would be an E-mail (service application) server or an application management server ( Initiate retrieval of specific information from the location where the user information is embodied.

The session management software retrieves information and stores new content in the application server 113 accessible through commands sent from the user mobile terminal 101. As a result, the limitations within the user terminal 101 and the communication protocol used will affect the amount of content that can be transmitted to the mobile terminal 101 at one time.

An alternative method for communication between the mobile terminal and the application server is to use WAP or other available communication methods such as GPRS, UTMS, and the like.

The session management software can be generated by using a known software programming framework, and the software can be embodied in the form of a computer program comprising program code stored on a software medium transmitted from a software source server using an associated delivery technique. Can be.

The best embodiments have been disclosed in the drawings and specification above. Although specific terms have been used herein, they are used only for the purpose of describing the present invention and are not used to limit the scope of the present invention as defined in the meaning or claims. Therefore, those skilled in the art will understand that various modifications and equivalent other embodiments are possible from this. Therefore, the true technical protection scope of the present invention will be defined by the technical spirit of the appended claims.

Claims (18)

A method of managing a client session in an application server 113 capable of communicating with at least one client mobile communication terminal 101 in a digital mobile communication system 105 via a connectionless communication protocol, Maintaining at least a first client session identifier associated with the client terminal identifier. The method of claim 1 wherein the method is Receiving a request from the client terminal 101 to initiate a first client application session; Receiving first client specific data comprising a first mobile terminal identifier from the client terminal 101; Associating a first client session identifier with the first mobile terminal identifier; Storing said first client session identifier in a session management database (115); Maintaining communication between the client terminal 101 and the application session, receiving at least one communication request and confirming that at least one communication request originated from the first client terminal 101. Characterized by client session management methods. 3. The method of claim 2, wherein the association of a first client session identifier with the first mobile terminal identifier comprises a calculation relating to the first client session identifier. The method of claim 2 or 3, wherein the step of continuing communication between the client terminal 101 and the applicator server 113 prevents communication between the client terminal 101 and the application server 113. And use of a timeout procedure, wherein disabling said communication is determined by a timeout restriction. 5. A method according to claim 4, wherein the communication session includes a plurality of connection requests from a plurality of client terminals (101) and a service search to the terminal within a certain time limit. 6. The method of any one of claims 2 to 5, wherein receipt of the first client specific data comprises receipt of a mobile station integrated service digital network number and hash code. 7. A method according to any one of claims 2 to 6, wherein said session management depends on commands received from said client mobile communication terminal (101). 7. The method according to any one of claims 2 to 6, wherein any of the messages not yet transmitted are sent from the application server 113 to the mobile terminal 101 and thereafter within the application server 113. Changing the state of the message to the transmitted state. 7. The method of any of claims 2 to 6, wherein the next available message in the message list is transmitted. A client session management system arranged to communicate with one or more client mobile communication terminals 105 through a connectionless communication protocol in a digital mobile communication system 105. Means for maintaining at least a first client session identifier associated with the client terminal identifier. The system of claim 10 wherein the system is Means for receiving a request for initiating a first client application session from the client terminal (101); Means for receiving first client specific data comprising a first mobile terminal identifier from the client terminal (101); Means for associating a first client session identifier with the first mobile terminal identifier; Means for storing said first client session identifier in a session management database (115); Means for sustaining communication between the client terminal 101 and the application session, wherein the client session management comprises receiving at least one communication request and confirming that it originated from the first client terminal 101. system. 12. The client session management system of claim 11 wherein the means for associating a first client session identifier with the first mobile terminal identifier comprises means for calculation relating to the first client session identifier. The method of claim 11 or 12, wherein the means for continuing the communication between the client terminal 101 and the applicator server 113 can communicate between the client terminal 101 and the application server 113. And timeout means for disabling, wherein disabling said communication is determined by a timeout restriction. 10. A client session management system according to any one of claims 7 to 9, wherein the means for receipt of the first client specific data comprises means for receipt of a mobile station integrated service digital network number and hash code. . A method for managing a client session of an application server 113 in a digital mobile communication system 105, Communicating with the client mobile communication terminal 101 in a successive connectionless communication protocol message; Receiving a service request from the service application through the service application server 117; Setting a first client session identifier associated with a client terminal identifier based on the request; Maintaining the first client session identifier associated with a client terminal identifier of the client mobile communication terminal 101, wherein the session identifier includes indicating the session with the client terminal between the consecutive messages. Characterized by client session management methods. The method of claim 15, wherein at least a portion of a service of the service application is retrieved from the service application to the application server 113 and the session identifier is passed through the service application server 117 to the client terminal 101 and the application. Client session management method, characterized in that the same during communication between the server (113) and between the client terminal (101) and the service application. A computer program comprising software instructions for performing a method according to any of the preceding claims. The computer program according to claim 15 or 16, comprising software instructions for performing the method.