KR100873805B1 - Method, system and apparatus for interworking between ims domain and non-ims domain in phone number based mobile messenger service - Google Patents

Abstract

A method for interworking an IMS-based mobile messenger service with a non-IMS based mobile messenger service is provided to remove the trouble to install messenger applications of each messenger service provider separately. A method for interworking between an IMS-based mobile messenger service and a non-IMS based mobile messenger service comprises the following steps. An IMS-based mobile messenger server receives a request for the registration of a companion of conversation from an IMS messenger subscriber(S301), and then obtains domain information of the conversation companion to check whether the conversation companion is a non-IMS messenger subscriber. The conversation companion is added/recorded/stored to a conversation companion list of the IMS messenger subscriber, together with the domain information(S311).

Description

METHOD, SYSTEM AND APPARATUS FOR INTERWORKING BETWEEN IMS DOMAIN AND NON-IMS DOMAIN IN PHONE NUMBER BASED MOBILE MESSENGER SERVICE}

1 is a diagram illustrating a network configuration of a conventional mobile communication system.

2 is a diagram illustrating a network environment of a mobile communication system for interworking an IMS-based messenger service and a non-IMS-based messenger service according to the present invention.

3 is a signal flow diagram illustrating a process in which an IMS domain subscriber adds a non-IMS domain subscriber to a conversation partner in the system of FIG. 1.

4 is a signal flow diagram illustrating a conversation process between an IMS domain subscriber and a non-IMS domain subscriber in the system of FIG. 1.

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

210: IMS subscriber terminal 240: IMS messenger server

250: gateway 310: non-IMS messenger server

330: non-IMS subscriber terminal 400: authentication server

The present invention relates to a mobile messenger, and more particularly to a mobile messenger based on a telephone number.

The instant messenger service is a service that can instantly send and receive messages with users who are online, and supplements the shortcomings of e-mail, which may take a long time to send and check a message. In addition, the wireless messenger service is to implement a messenger service in a wireless environment using a mobile communication terminal.

Even in a mobile communication system environment, such an instant messenger service can be provided through mobile communication terminals. The messenger service in the mobile communication system provides a messenger service to a mobile communication terminal which is provided with a messenger server in a mobile communication network environment. The user accessing the messenger server through the mobile communication terminal registers a buddy list in the messenger server, and thus can exchange messages with the buddies in the buddy list.

Most instant messenger services in such mobile communication systems are provided based on phone numbers. The instant messenger service in the Internet environment registers a buddy by using an e-mail account and provides a messenger service. The instant messenger service in a mobile communication system registers a buddy by using a phone number and provides a messenger service. The instant messenger service in the mobile communication system has adopted the messenger service of the Internet environment as it is. For example, MSN messenger, NateOn messenger and Daum messenger of internet environment are applied to mobile communication terminal to provide messenger service based on phone number.

However, with the development of mobile communication technology, 3GPP has applied new IP Multimedia Subsystem (IMS) domain to mobile communication by applying IP-based open architecture and service platform configuration to support the rapid deployment of new multimedia-based services. Adopted the system structure to be introduced to the core. The basic service goal of IMS is to provide a combination of multimedia such as voice, audio, video and data based on the IP protocol. These characteristics make IMS a key technology to lead the market with the introduction of WCDMA system. The IMS domain also provides instant messenger service based on IP. The instant messenger service in the IMS domain is provided based on a phone number like the instant messenger service (MSN, NateOn, etc.) of the non-IMS domain.

However, as described above, the instant messenger service based on the IMS domain and the instant messenger service based on the non-IMS domain are both based on a phone number, but are not interworked at all. The messenger server of the IMS domain manages only the information of the IMS subscriber, and the messenger server of the non-IMS domain manages only the information of the non-IMS subscriber, thereby providing services based on telephone numbers, but cannot interwork with each other. It will be described in more detail with reference to FIG.

FIG. 1 is a diagram illustrating a network configuration of a conventional mobile communication system. As shown in FIG. 1, a WCDMA network 110 and a CDMA network 120 coexist in a mobile communication system. It has a messenger server and provides messenger services. In the WCDMA network 110, a messenger server 115 is implemented in an IMS domain to provide WCDMA inter-subscriber messenger services, and in the CDMA network 120, a messenger server 121 is implemented in a non-IMS domain, that is, a packet-switched network. It provides a messenger service.

Both the IMS-based messenger server 115 and the non-IMS-based messenger server 121 register and manage a buddy list based on a phone number. Therefore, when the WCDMA subscriber 111 registers the phone number of the CDMA subscriber 123 as a buddy list, the phone number of the CDMA subscriber 123 is registered as a buddy list in the IMS-based messenger server 115. However, when the WCDMA subscriber 111 selects the CDMA subscriber 123 from the buddy list and requests a conversation invitation, the CDMA subscriber 123 is not a user registered in the IMS domain and thus cannot send the conversation invitation.

Therefore, the messenger service user has to install a plurality of messenger programs according to the messenger type of the conversation partner, and has to troubleshoot buddy registration again.

The present invention has been proposed to solve the above problems, and an object thereof is to provide a method and system for interworking a service between an IMS domain and a non-IMS domain in a phone number based messenger service, and a mobile messenger device for the same.

Other objects and advantages of the present invention can be understood by the following description, and will be more clearly understood by the embodiments of the present invention. Also, it will be readily appreciated that the objects and advantages of the present invention may be realized by the means and combinations thereof indicated in the claims.

In accordance with a first aspect of the present invention for achieving the above object, an interworking method of an IMS (IP Multimedia Subsystem) based mobile messenger service and a non-IMS based mobile messenger service includes registering a contact from an IMS messenger subscriber in an IMS based mobile messenger server. Receiving a request; Determining whether the contact is a non-IMS messenger subscriber by acquiring domain information of a contact who has been requested to register; And in the case of the non-IMS messenger subscriber, adding the corresponding contact to the contact list of the IMS messenger subscriber and storing and storing domain information together.

In addition, in accordance with a second aspect of the present invention for achieving the above object, an interworking method of an IMS (IP Multimedia Subsystem) -based mobile messenger service and a non-IMS-based mobile messenger service, the non-IMS messenger subscriber in the IMS-based mobile messenger server Receiving a conversation request message with an IMS messenger subscriber; Confirming domain information of the non-IMS messenger subscriber; Transmitting a conversation request message to a non-IMS based mobile messenger server corresponding to the verified domain information; And receiving, from the non-IMS-based mobile messenger server, an acceptance message according to the acceptance of the conversation of the non-IMS messenger subscriber.

In addition, an IMS-based mobile messenger service system for interworking with a non-IMS-based mobile messenger service in a mobile communication network according to a third aspect of the present invention for achieving the above object, stores and manages domain information of a mobile messenger service subscriber. Authentication server; And a messenger server which, when receiving a contact registration request from a messenger subscriber, obtains the domain information of the chat partner from the authentication server and records and stores the contact information in the contact list of the messenger subscriber.

In addition, according to a fourth aspect of the present invention for achieving the above object, an IMS-based mobile messenger device interoperating with a non-IMS-based mobile messenger device in a mobile communication network, the storage means for storing a contact list for each messenger subscriber; List management means for acquiring and storing domain information of a chat partner in the storage means when requesting a chat partner registration from a messenger subscriber; And upon receiving a chat request with a specific chat partner from the messenger subscriber, checks the domain information of the chat partner, and if the chat partner is a non-IMS-based messenger subscriber, transmits a chat request message to the non-IMS-based mobile messenger device. Chat service means for providing a chat service by receiving the acceptance message according to the feature.

The above objects, features and advantages will become more apparent from the following detailed description taken in conjunction with the accompanying drawings, whereby those skilled in the art may easily implement the technical idea of the present invention. There will be. In addition, in describing the present invention, when it is determined that the detailed description of the known technology related to the present invention may unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted. Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

2 is a diagram illustrating a network environment of a mobile communication system for interworking an IMS-based messenger service and a non-IMS-based messenger service according to the present invention. Here, the IMS-based messenger service and the non-IMS-based messenger service are phone number-based messenger services, and the IMS-based messenger server 240 and the non-IMS-based messenger server 310 register and manage a buddy using a messenger subscriber's phone number. Do

As shown in FIG. 2, the mobile communication system includes a WCDMA network 200 and a CDMA network 300. The WCDMA network 200 includes a wireless network domain, a packet switched service domain, and an IMS domain, and the CDMA network 200 includes a wireless network domain and a packet switched service domain.

First, the wireless network domain of the WCDMA network 200 is composed of a mobile terminal 210 which is a messenger service subscriber, a base station NodeB and a base station controller RNC responsible for accessing the mobile terminal 210 through a wireless section.

In addition, the packet switched service domain of the WCDMA network 200 is SGSN responsible for the transfer of user packet data between the wireless network domain and the external network or IMS domain and provides the mobility management and PDP context activation services of the mobile terminal 210 and Gateway GPRS support node (GGSN).

In FIG. 2, the WCDMA network 220 may be understood to refer to the wireless network domain and the packet switched service domain.

In addition, the IMS domain of the WCDMA network 200 includes a call session control function (CSCF) 230 that handles registration and multimedia call processing using the SIP (Session Initiation Protocol) protocol developed by the IETF, and a home location register of an existing network ( It consists of HSS (Home Subscriber Server) which integrates functions for mobility management and authentication of IP multimedia users. In FIG. 2, CSCF 230, IMS messenger server 240, and gateway 250 are components of an IMS domain. The gateway 250 provides interworking with the CDMA network 300, and converts a messenger protocol.

Next, the wireless network domain of the CDMA network 200 is composed of a mobile terminal 330 which is a messenger service subscriber, a base station (BTS) and a base station controller (BSC) that are in charge of accessing the mobile terminal 300 through a wireless section. do. The packet switched service domain of the CDMA network 200 includes a Packet Data Service Node (PDSN) serving as an interface for packet transmission between the wireless network domain and a fixed network, and a Packet Control Function (PCF) connecting the PDSN and the wireless network domain. ) And the like. In FIG. 2, the CDMA network 320 can be understood as a wireless network domain and a packet switched service domain. In addition, in FIG. 2, the non-IMS messenger server 310 provides a phone number based messenger service in a packet switching service domain.

As shown in FIG. 2, the mobile communication system according to the present invention includes an authentication server 400. The authentication server 400 stores and manages the information of the messenger service subscribers of the WCDMA network 200 and the CDMA network 300. Specifically, the authentication server 400 stores and manages the messenger subscriber's phone number, the messenger information of the subscriber, the network information of the subscriber, and the like.

In addition, as shown in FIG. 2, the IMS messenger server 240 of the IMS domain includes a chat service unit 241, a list manager 243, and a storage unit 245.

The list manager 243 registers and manages a buddy list of IMS domain subscribers. At this time, when the list management unit 243 receives a buddy registration request from the IMS domain subscriber, the list manager 243 authenticates the registered buddy through the authentication server 400. In detail, the list manager 243 checks messenger information, network information, etc. of the buddy requested to be registered. The list manager 243 stores the information of the buddy requested to be registered and the authentication result in the storage unit 245, and transmits the buddy's authentication result to the IMS domain subscriber who has requested the registration.

In addition, the list manager 243 may receive a buddy registration request for the non-IMS domain messenger subscriber from the IMS messenger subscriber station 210. The list manager 243 authenticates the buddy registration request non-IMS domain messenger subscriber through the authentication server 400. In detail, the authentication server 400 receives the buddy registration target phone number from the list manager 243, checks messenger information, network information, etc. of the buddy registration target, and transmits the result to the list manager 243. . The list manager 243 adds the authentication result transmitted from the authentication server 400, that is, the phone number of the buddy registration target person, the messenger information of the target person, the network information, and the like to the buddy list of the buddy registration requester 210 and stores the storage unit ( 245).

The list manager 243 transfers some information from the authentication result received from the authentication server 400 to the IMS messenger subscriber station 210, and the subscriber station 210 stores the transferred information and later stores the information in the corresponding non-IMS domain. When chatting with a messenger subscriber, the chat service is transferred to the chat service unit 241.

The chat service unit 241 provides a chat service between messenger subscribers. The chat here includes text chat, voice chat and video chat. When the chat service unit 241 receives the chat service request signal including the contact information from the IMS messenger subscriber terminal 210, the chat service unit 241 transmits a chat invitation message to the chat partner using the chat buddy information, and the chat partner chats. Accepting the invitation message provides a chat service between the IMS messenger subscriber station 210 and the conversation partner. Herein, the contact information includes messenger information, network information, etc. of the corresponding contact.

Therefore, when the chat partner is a user who uses a messenger service of a non-IMS domain, the chat service unit 241 transmits a chat invitation message to the gateway 250. Gateway 250 performs messenger protocol conversion between the IMS domain and the non-IMS domain. The gateway 250 converts the conversation invitation message transmitted from the chat service unit 241 into a messenger protocol of a non-IMS domain and transmits the message to the non-IMS messenger server 310, and an acceptance message is received from the non-IMS messenger server 310. When the acceptance message is converted into a messenger protocol of the IMS domain, the message is transmitted to the chat service unit 241.

3 is a signal flow diagram illustrating a process in which an IMS domain subscriber adds a non-IMS domain subscriber to a conversation partner in the system of FIG. 1.

As shown in FIG. 3, first, the IMS domain messenger subscriber inputs the telephone number of the non-IMS domain messenger subscriber to the terminal 210 and requests buddy registration to add the non-IMS domain messenger subscriber to the buddy list. Accordingly, the IMS domain subscriber station 210 transmits a contact registration request message including the telephone number of the non-IMS domain messenger subscriber to the IMS messenger server 240 (S301).

Upon receiving the contact registration request, the IMS messenger server 240 requests contact information from the authentication server 400 to authenticate the contact requesting registration (S303). Preferably, the IMS messenger server 240 requests the contact information by transmitting the phone number of the contact requested to be registered to the authentication server 400.

Receiving a contact information request, the authentication server 400 extracts messenger information and / or network information of a contact from previously stored information, and transmits a contact information response including the extracted information to the IMS messenger server ( In step 240, it is transmitted.

The IMS messenger server 240 adds the contact information received from the authentication server 400 to the buddy list of the IMS domain messenger subscriber (S307). That is, the IMS messenger server 240 adds the contact's phone number to the buddy list of the IMS domain messenger subscriber and records the contact's network information and / or messenger information received from the authentication server 400 together.

Next, the IMS messenger server 240 lowers the information of the contact person registered in the buddy list to the terminal 210 of the IMS domain messenger subscriber (S309). The IMS domain messenger application mounted on the terminal 210 of the IMS domain messenger subscriber adds and stores the information of the contact transmitted from the IMS messenger server 240 to the buddy list (S311). Therefore, a new contact is added to the buddy list in the messenger application of the terminal 210 of the IMS domain messenger subscriber, and the network information and / or messenger information of the added contact is recorded and stored together.

4 is a signal flow diagram illustrating a conversation process between an IMS domain subscriber and a non-IMS domain subscriber in the system of FIG. 1.

As described with reference to FIG. 3, the IMS domain subscribers register non-IMS domain subscribers. Subsequently, the IMS domain subscriber selects the non-IMS domain subscriber and requests a conversation from the terminal 210 to chat with the buddy-registered non-IMS domain subscriber. The terminal 210 of the IMS domain subscriber transmits a conversation request message including the information of the non-IMS domain subscriber to the IMS messenger server 240 (S401). The conversation request message includes a phone number, network information, and messenger information of a non-IMS domain subscriber.

Upon receiving the conversation request message, the IMS messenger server 240 checks information of the conversation partner included in the conversation request message, that is, information of a non-IMS domain subscriber (S403). The IMS messenger server 240 checks the information of the chat partner, that is, network information, messenger information, and the like, and transmits a chat request message to the gateway 250 since the chat partner is a subscriber of the non-IMS domain (S405).

The gateway 250 converts the conversation request message transmitted from the IMS messenger server 240 into a messenger protocol of the non-IMS domain (S407), and transmits the converted conversation request message to the messenger server 310 of the non-IMS domain. (S409). The non-IMS messenger server 310 transmits the received conversation request message to the terminal 330 of the corresponding non-IMS domain messenger subscriber (S411).

When the non-IMS domain messenger subscriber accepts the conversation request, an acceptance message is transmitted from the terminal 330 of the non-IMS domain messenger subscriber to the non-IMS messenger server 310 (S413), and the non-IMS messenger server 310 accepts the conversation. The message is transmitted to the gateway 250 (S415). The gateway 250 converts the acceptance message received from the non-IMS messenger server 310 according to the protocol of the IMS domain and transmits it to the IMS messenger server 240 (S417). The IMS messenger server 240 transmits the acceptance message to the IMS. The terminal transmits the message to the terminal 210 of the subscriber (S419). After receiving the acceptance response to the conversation request as described above, the IMS messenger subscriber and the non-IMS messenger subscriber use the chat service.

In the above-described embodiment, the IMS messenger server 240 checks the information (eg, network information, messenger information, etc.) of the contact requested to be registered through the authentication server 400 with respect to the buddy registration request of the IMS messenger subscriber. The information is transmitted to the terminal 210 of the IMS messenger subscriber. The terminal 210 of the IMS messenger subscriber records the information of the conversation partner received from the IMS messenger server 240 and transmits the information of the conversation partner to the IMS messenger server 240 in a later chat with the conversation partner. The IMS messenger server 240 confirms that the corresponding contact is a messenger subscriber of a non-IMS domain based on the received contact information. However, the present invention is not limited thereto, and the IMS messenger server 240 may not send down the network information and / or messenger information of the contact confirmed through the authentication server 400 to the terminal 210. In this case, when the message request message is received from the terminal 210, the IMS messenger server 240 checks the contact information in the internal information and checks whether the contact is an IMS domain or a non-IMS domain.

In addition, in the above-described embodiment, the IMS messenger subscriber only registers a non-IMS messenger subscriber and requests a conversation, but the present invention can be applied even when the non-IMS messenger subscriber registers and requests a conversation with the IMS messenger subscriber. . The non-IMS messenger server 310 confirms the information of the contact requested to be registered through the authentication server 400, stores the information therein, and then lowers the information to the terminal 330 of the non-IMS messenger subscriber. In addition, when the non-IMS messenger server 310 receives a chat request message from the terminal 330 of the non-IMS messenger subscriber, the non-IMS messenger server 310 transmits a chat request message to the IMS messenger server 240 and confirms the information of the contact. Receive a message to provide a chat service.

As described above, the method of the present invention may be implemented as a program and stored in a recording medium (CD-ROM, RAM, ROM, floppy disk, hard disk, magneto-optical disk, etc.) in a computer-readable form. Since this process can be easily implemented by those skilled in the art will not be described in more detail.

The present invention described above is capable of various substitutions, modifications, and changes without departing from the technical spirit of the present invention for those skilled in the art to which the present invention pertains. It is not limited by the drawings.

As described above, the present invention enables interworking between heterogeneous networks of a messenger service provided based on a phone number, and solves the inconvenience of installing a separate messenger application for each messenger service provider. The service gap can be eliminated.

Claims (12)

As an interworking method of IMS (IP Multimedia Subsystem) based mobile messenger service and non-IMS based mobile messenger service, (a) receiving a request to register a contact from an IMS messenger subscriber in an IMS-based mobile messenger server; (b) obtaining domain information of a contact who has been requested to be registered and determining whether the contact is a non-IMS messenger subscriber; And (c) in the case of the non-IMS messenger subscriber, adding the corresponding contact to the contact list of the IMS messenger subscriber and storing domain information together; and storing the domain information together with the IMS-based mobile messenger service and the non-IMS-based mobile messenger service. Interlock method. The method of claim 1, And transmitting and storing the obtained domain information of the non-IMS messenger subscriber to the IMS messenger subscriber. The method according to claim 1 or 2, The domain information is, An interworking method of an IMS-based mobile messenger service and a non-IMS-based mobile messenger service, characterized in that it is network information and messenger information. The method of claim 3, wherein The mobile messenger service, A method of interworking between an IMS-based mobile messenger service and a non-IMS-based mobile messenger service, which is based on a phone number. As an interworking method of IMS (IP Multimedia Subsystem) based mobile messenger service and non-IMS based mobile messenger service, (a) receiving a conversation request message with a non-IMS messenger subscriber from an IMS messenger subscriber in an IMS-based mobile messenger server; (b) verifying domain information of the non-IMS messenger subscriber; (c) sending a conversation request message to a non-IMS based mobile messenger server corresponding to the verified domain information; And (d) receiving an acceptance message according to accepting a conversation of the non-IMS messenger subscriber from the non-IMS-based mobile messenger server; and a method of interworking an IMS-based mobile messenger service and a non-IMS-based mobile messenger service. The method of claim 5, wherein Step (c) is, Converting the protocol of the conversation request message to correspond to the verified domain information; And And transmitting the converted conversation request message to a non-IMS-based mobile messenger server corresponding to the verified domain information. The method according to claim 5 or 6, Step (b) is, The interworking method of the IMS-based mobile messenger service and the non-IMS-based mobile messenger service, characterized in that the domain information of the non-IMS messenger subscriber is checked from the conversation list information of the internally stored IMS messenger subscriber. The method according to claim 5 or 6, Step (b) is, Method for interworking between the IMS-based mobile messenger service and the non-IMS-based mobile messenger service, characterized in that the domain information is confirmed from the conversation request message received in the step (a). An IMS-based mobile messenger service system for interworking with a non-IMS-based mobile messenger service in a mobile communication network, An authentication server for storing and managing domain information of a mobile messenger service subscriber; And And a messenger server configured to obtain domain information of a contact from the authentication server and record and store the contact information on the contact list of the messenger subscriber when receiving a contact registration request from a messenger subscriber. The method of claim 9, A gateway for performing protocol conversion between the IMS-based network and the non-IMS-based network; The messenger server, When receiving a chat request with a specific chat partner from a messenger subscriber, if the chat partner is a non-IMS domain messenger subscriber, the chat request message is transmitted to the non-IMS-based mobile messenger server through the gateway and receives an acceptance message accordingly. Mobile messenger service system, characterized in that. The method according to claim 9 or 10, The domain information is, A mobile messenger service system comprising network information and messenger information. An IMS-based mobile messenger device interoperating with a non-IMS-based mobile messenger device in a mobile communication network, Storage means for storing a contact list for each messenger subscriber; List management means for acquiring and storing domain information of a chat partner in the storage means when requesting a chat partner registration from a messenger subscriber; And When receiving a chat request with a specific contact from a messenger subscriber, the contact information is checked, and if the chat partner is a non-IMS-based messenger subscriber, the chat request message is transmitted to the non-IMS-based mobile messenger device and accordingly And a chat service means for receiving a message of acceptance and providing a chat service.

Images