KR101523997B1 - A Method and Appartus for providing a presence service - Google Patents

Abstract

A terminal and a method for providing a presence service for a user according to an embodiment of the present invention comprise: a step for collecting first presence information of the user containing a list of presence services the user of the terminal is using based on applications installed on the terminal; a step for registering the collected first presence information of the user and an address book of the user on a presence server; and a step for acquiring second presence information about buddies included in the address book of the user from the presence server. The second presence information about the buddies is a concatenation of presence fragments for each of the presence services enumerated in the first presence information.

Description

TECHNICAL FIELD [0001] The present invention relates to a method and apparatus for providing a presence service,

The present invention relates to a method of providing a presence service based on presence information of users and a terminal and a presence server for executing the method.

The IP multimedia subsystem (IMS) network is an environment in which a wired and wireless network is constructed based on IP to provide multimedia services based on all IP, and various communication services can be provided independently of the platform. The IMS network provides multimedia multimedia services such as voice, video, audio and data using the IP protocol. Presence services are included in the multimedia service provided through the IMS network.

The presence service receives the presence information indicating whether the user is using and the user's personal information, and registers the presence information in the presence server in the IMS network. When a user registered in the presence server requests it, the presence server delivers the presence information of the buddy requested by the user. Presence services include services based on, for example, instant messaging, Voice over IP (VoIP), email, voice or video capabilities, user mobility, and the like. The presence server manages the presence information of the user, and the user can register / modify his / her presence information through the presence server and obtain the presence information of the buddy.

Disclosure of Invention Technical Problem [8] The present invention has been made in view of the above problems, and it is an object of the present invention to facilitate expansion and integration of presence services based on an IMS network and a non-IMS network by separating a presence server from an IMS network and using a presence gateway for connection between an presence server and an IMS network And to reduce the overhead of transactions between the presence server and the terminals by unifying the presence information for the multiple presence services.

The technical problem to be solved by the present invention is not limited to the technical problems described above, and other technical problems can be deduced from the embodiments of the present invention.

A method of providing a presence service to a user according to an exemplary embodiment of the present invention includes providing a presence service to a user including a list of presence services being used by a user of the terminal, Collecting first presence information; Registering the first presence information of the collected user and the address book of the user on the presence server; And obtaining second presence information for buddies included in the address book of the user from the presence server, wherein the second presence information for the buddies includes information about the buddies that are listed in the first presence information Presence fragments for each of the presence services are combined.

A method of providing a presence service to a terminal according to another embodiment of the present invention includes receiving a first presence information of the user including a list of presence services used by a user of the terminal, Receiving a registration request message including an address book from the terminal; Collecting presence fragments of each of the presence services enumerated in the first presence information for buddies included in the address book of the user; Combining the collected presence fragments to generate second presence information for the buddies; And a presence response message including the second presence information to the terminal.

There is provided a computer-readable recording medium having recorded thereon a program for executing the above-described method according to another embodiment of the present invention.

According to another embodiment of the present invention, a terminal for providing a presence service to a user includes: an RF module for transmitting and receiving a radio signal; A storage unit for storing applications installed in the terminal, an address book of the user, and a presence agent; And a processor for executing the presence agent stored in the storage unit and controlling the RF module and the storage unit, wherein the processor is configured to execute the presence agent stored in the storage unit in the list of presence services The first presence information of the user and the address book of the user are registered in the presence server through the RF module and are included in the address book of the user from the presence server, Wherein the second presence information for the buddies is obtained by combining presence fragments for each of the presence services listed in the first presence information, will be.

According to another embodiment of the present invention, a presence server that provides a presence service to a terminal includes a first presence information of the user including a list of presence services used by a user of the terminal, A receiving unit for receiving a registration request message from the terminal; Collecting presence fragments of each of the presence services listed in the first presence information with respect to buddies included in the address book of the user and combining the collected presence fragments with the buddies A processor for generating second presence information for the first presence information; And a transmitter for transmitting a presence response message including the second presence information to the terminal.

According to an embodiment of the present invention, expansion and combination of presence services based on non-IMS network as well as presence services based on IMS network can be performed through the presence server and presence gateway separated from the IMS network without additional server And it is possible to reduce the overhead of transactions between the presence server and the terminal by unifying the presence information of the multiple presence services and storing the unified presence information in the local terminal in the local database.

The effects of the present invention are not limited to the effects described above, and other effects can be deduced from the embodiments of the present invention.

1 is a diagram illustrating an environment of a presence service based on a non-IMS network and an presence service based on an IMS network.
2 is a diagram illustrating an environment of a presence service according to an embodiment of the present invention.
3 is a flowchart illustrating a method of registering presence information of a terminal according to an embodiment of the present invention.
4 is a flowchart illustrating a method of registering presence information of a terminal according to another embodiment of the present invention.
5 is a flowchart illustrating a method of requesting presence information of a terminal according to an embodiment of the present invention.
6 is a flowchart illustrating a method of requesting presence information of a terminal according to another embodiment of the present invention.
7 is a flowchart illustrating a method of registering presence information in a presence server according to an embodiment of the present invention.
8 is a flowchart illustrating a method of providing presence information of a presence server according to an embodiment of the present invention.
9 is a flowchart illustrating a method of providing a presence service according to an embodiment of the present invention.
10 is a view for explaining presence information according to an embodiment of the present invention.
11 to 15 are views illustrating messages in a presence service providing method according to embodiments of the present invention.
16 is a diagram illustrating a terminal according to an embodiment of the present invention.
17 is a diagram illustrating a presence server according to an embodiment of the present invention.

Hereinafter, preferred embodiments according to the present invention will be described in detail with reference to the accompanying drawings. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The following detailed description, together with the accompanying drawings, is intended to illustrate exemplary embodiments of the invention and is not intended to represent the only embodiments in which the invention may be practiced. The following detailed description includes specific details in order to provide a thorough understanding of the present invention. However, those skilled in the art will appreciate that the present invention may be practiced without these specific details.

In some instances, well-known structures and devices may be omitted or may be shown in block diagram form, centering on the core functionality of each structure and device, to avoid obscuring the concepts of the present invention. In the following description, the same components are denoted by the same reference numerals throughout the specification. In addition, the specific terms used in the following description are provided to aid understanding of the present invention, and the use of such specific terms may be changed into other forms without departing from the technical idea of the present invention.

In the following description, presence information refers to presence and service availability of a presence service (eg, login status, away, offline, other service, during meal, during a conference, (Eg, accessibility, service type, service version), presence information (eg, profile information, mood state, image, video, schedule) UUID, mobility support, power on / off), software status (eg, service application version, service application installation, supported language), and depending on the type of presence service provided, . The presence fragment is a subset of the data that constitutes the presence information, and the presence fragment required may vary depending on the presence service. However, the presence fragment refers to any functionally or logically meaningful data field, and the randomly extracted data is excluded from the presence fragment. The buddy refers to another user included in the address book of the user terminal. The first presence information refers to the presence information of the terminal user, and the second presence information refers to the presence information of the buddy. A terminal includes a device having a wired or wireless communication function such as a user equipment (UE), a mobile station (MS), a PMP, a PDA, a navigation system, a laptop, and a desktop.

1 is a diagram illustrating an environment of a presence service based on a non-IMS network and an presence service based on an IMS network.

Referring to FIG. 1, the presence service environment includes a first presence server 140, a second presence server 150, and terminals 110, 130, and 150. Although the first presence server 140 is shown separately from the IMS network 120, the first presence server 140 may be an entity within the IMS network 120. The second presence server 140 may be an entity of the non-IMS network 130.

The IMS network 120 includes a home IMS network and a third-party IMS network. The non-IMS network 130 may include a core network such as GSM, UMTS, and E-UTRA other than the IMS network, or a WLAN and an Internet network. A backhaul interface (not shown) may exist between the non-IMS network 130 and the IMS network 120.

In the following description, the presence service may include an IMS network-based presence service and a non-IMS network-based presence service. The presence service based on the IMS network conforms to the standard of the service according to the IMS network for interworking with the other IMS network. For example, the commercially available 'Join' mobile messenger service is an IMS network-based presence service. The presence service based on the non-IMS network may be exemplified by an instant messaging service by third party applications, a multimedia providing service that operates only within a mobile communication provider network, and an Internet based SNS service.

The first presence server 140 provides the presence service based on the IMS network, and the second presence server 150 provides the presence service based on the non-IMS network. The first presence server 140 and the first terminal 110 transmit and receive data based on SIP (session initiation protocol) / XCAP (XML Configuration Access Protocol).

A protocol that specifies the procedures for SIP terminals to identify each other, find its location, and initiate or change sessions. The protocol includes a request / response structure that controls creation, modification, and termination of presence service sessions for telephone calls, voicemail, and instant messaging. define. SIP can be transmitted through Transmission Control Protocol (TCP) and User Datagram Protocol (UDP), and identifies the user through the SIP URL, so that the user can be distinguished from the IP address independently. XCAP is a protocol that supports the function to inquire, register or modify presence information. Hypertext transfer protocol (HTTP) is used to manage documents of presence information based on XML. The HTTP PUT command is used to register presence information, the HTTP GET command is used to inquire presence information, and the HTTP DELETE command is used to delete presence information.

The first presence server 140 includes an address book server 141, an address book DB 143, a PS server 142, and a PS DB 144. The address book server 141 and the address book DB 143 register and manage the address book of the user and the PS server 142 and the PS DB 144 register the second presence information about the registered address book buddies and the user information 1 Presence information is viewed, registered and managed. According to the standard, the address book server 141 and the PS server 142 are separated into entities having different network addresses.

The second presence server 150 includes an address book server 151, an address book DB 153, a PS server 152, and a PS DB 154. Each configuration of the second presence server 150 can be understood from the description of the first presence server 140. [ The exchange of information between the second presence server 150 and the first terminal 110 may be performed based on SIP / XCAP, but is not limited thereto. Since the second presence server 150 does not conform to the standard standard required in the IMS network, an arbitrary protocol can be used according to the selection of the presence server operator.

The presence service provided by the first presence server 140 and the presence service provided by the second presence server 150 do not share address book and presence information with each other and the data exchange interfaces defined with the first terminal 110 are also mutually The presence server is installed for each presence service. In other words, in order to provide a new type of presence service, there is a problem that a new presence server needs to be added.

The first terminal 110 is provided with a PS application # 0 for providing a presence service based on a non-IMS network and PS applications # 1 to N for providing an IMS network-based presence service. At this time, since the (N + 1) PS applications operate independently of each other, the first and second presence servers individually register the first presence information and the address book for each of the applications, and acquire the second presence information. Even if the PS applications # 1 to #N all need the common address book and the first and second presence information, the PS applications # 1 to #n can share the address book and the first and second presence information with each other Is not defined. As a result, each of the PS applications # 1 to N exchanges data with the first presence server 140, thereby causing a high transaction overhead.

2 is a diagram illustrating an environment of a presence service according to an embodiment of the present invention. The description overlapping with the above description is omitted.

2, the presence service environment includes a presence gateway 240, a presence server 250, a presence DB 253, and a terminal 210.

Both the presence GW 240 and the presence server 250 are located outside the IMS network 220. The presence GW 240 is connected to the IMS network 220 and the presence server 250 accesses the IMS network 220 via the presence GW 240.

Since the presence server 250 does not directly exchange data with the IMS network 220, the presence server 250 may be configured differently from the standard specification required by the IMS network. Instead of installing the separate address book server and the PS server in the presence server 250, the address book function module 251 and the presence function module 252 are implemented through software. Presence server 250 provides both an IMS network-based presence service and a non-IMS network-based presence service. Also, through the presence DB 253, address book and presence information for multiple presence services are integrated and managed. Therefore, regardless of whether it is a presence service based on a non-IMS network or an presence service based on an IMS network, addition of a new presence service can be easily implemented through an existing presence server 250 have.

Although the presence server 250 is shown as a single entity in FIG. 2 for convenience of description, multiple hardware entities may be configured as a single logical presence server 250 in order to balance load balancing and network processing. have. In addition, the presence DB 253 or the presence GW 240 may be implemented as a single entity logically or physically with the presence server 250.

The exchange of data between the presence server 250 and the terminal 210 may be performed in accordance with the determination of the operator of the presence server 250. For example, an HTTP rest protocol that can reduce transactions compared to SIP / XCAP can be used. When the HTTP rest protocol is used instead of the SIP / XCAP protocol supported in the IMS network, a problem may arise in the provision of the presence service based on the IMS network. That is, if the HTTP rest based message is transmitted to the IMS network, the meaning of the message defined by the operator of the presence server 250 in the IMS network 220 is unknown. Therefore, the message transmitted to the IMS network must be created based on the SIP / XCAP protocol as shown in FIG.

According to an embodiment of the present invention, the sessions before the access to the IMS network 220, the presence GW 240, the presence server 250, and the terminal 210 use an HTTP rest protocol capable of reducing transactions The SIP / XCAP protocol is used between the IMS network 220 and the presence GW 240. For this purpose, the presence GW 240 performs format conversion and inverse conversion between the HTTP rest protocol based message and the SIP / XCAP protocol based message.

The terminal 210 includes a PS agent 211. The PS agent 211 mediates the procedure of registering the address book between the presence server 250 and the PS applications # 0 to #N, the first presence information of the user or the second presence information of the buddies. The PS agent 211 obtains the integrated second presence information for the multiple presence services from the presence server 250. The PS agent 211 stores the acquired second presence information in a local DB (not shown) in the terminal 210. Each of the PS applications # 0 to #N obtains the presence fragment required in the local DB instead of accessing the presence server 250 through the network. At this time, the PS agent 211 includes an application program interface (API) for providing presence fragments to the PS applications # 0 to #N. The PS agent 211 extracts only the presence fragments among the second presence information stored in the local DB and provides the extracted presence fragments to the PS applications # 0 to #N. Hereinafter, more detailed embodiments of the operation of the presence server 250, the terminal 210, and the presence GW 240 will be described in the context of FIG.

3 is a flowchart illustrating a method of registering presence information of a terminal according to an embodiment of the present invention.

Referring to FIG. 3, the terminal detects PS applications that provide presence services among a plurality of applications installed in the terminal (step 305). An indicator indicating presence service provision may be included in the PS application to determine whether the terminal is a PS application. Alternatively, the terminal may determine whether it is a PS application through previously input information, for example, an application identifier, a name, and the like.

The terminal reads the presence fragment of the user from each of the detected PS applications (310). For example, assuming that Fragments 1 to 6 shown in FIG. 10 constitute first presence information, Fragments 1 to 5 are extracted from the PS application # 1, and the presence fragments read out by the UE may be different for each PS application. , And Fragment 6 can be extracted from the PS application # 4. For example, if the PS application is an instant messenger, at least one of the user's profile, screen name, ID, information about the service login status and service version, the user's picture, and the user's mood state can be read as presence fragments. In addition to the listed information, the terminal can read the user's presence fragments from the PS application. The terminal can store the presence fragment of the user read from the PS application in the local DB.

The terminal may combine the information read from each PS application with the presence fragments of the user and combine them into the first presence information. For the purpose of explanation of this embodiment, it is assumed that Fragment 1 to 6 of FIG. 10 constitute the first presence information of the user. The terminal reads fragments 1 to 5 from PS application # 1 and reads fragments 5 from PS application # 4. The terminal merges the fragments 1 to 6 read from the PS applications # 1 and # 4 into one first presence information. Fragments 1, 3, and 4 can also be read through the PS application # 2. According to an embodiment of the present invention, when the fragments of PS application # 2 and # 1 overlap, the terminal may omit reading presence fragment from PS application # 2.

The first presence information may include a list of presence services that the user of the terminal is using. For example, if the PS application # 1 is the first service, the PS application # 2 is the second service, the PS application # 3 is the third service, and the PS application # 4 is the fourth service, A list of fourth services may be included. The first presence information thus generated may be stored in a local database included in the terminal.

The terminal transmits a registration request message to register the first presence information stored in the local database with the presence server (315). According to an embodiment of the present invention, the registration of the first presence information can be periodically performed according to the network synchronization timer of the presence agent installed in the terminal. For example, if the network synchronization timer expires, the terminal may send a registration request message to the presence server to register the first presence information with the presence server. According to another embodiment, the presence agent of the terminal may trigger an event of transmission of the registration request message because the first presence information stored in the local database is changed. According to another embodiment, the transmission of the registration request message may be triggered according to the request of the specific PS application.

The registration request message may include the first presence information, the address book of the terminal user, and the authentication information. The address book of the terminal user may be the address book of the terminal itself or the address book read from the PS applications. The user authentication information may include at least one of an identifier of the presence services, an identifier of the user within each presence service, and an access key assigned from the presence server.

The identifier of the presence services means information for identifying which presence service the corresponding registration request message is for. The identifier of the user in the presence service means information for distinguishing the users of the terminal from other users using the presence service. The access key allocated from the presence server is information for determining whether or not the user is authorized to access the presence server.

According to an embodiment of the present invention, the registration request message transmitted from the terminal to the presence server may be a message based on the HTTP rest. 11 (b) illustrates a registration request message of a terminal according to an embodiment of the present invention. 11 (b) is a message generated based on the HTTP rest protocol, and is a message requesting registration of the address book of the terminal to the presence server. "PUT /1.0/AIA/{CTN}/Presence/Buddy_Lists HTTP / 1.1" is a command requesting registration, and Buddy_Lists HTTP indicates that the payload of the message is an address book. &Quot; SERVICE_ID ": "TEST_ROA_SERVICE_ID" indicates that the registration request message is related to the presence service TEST_ROA_SERVICE_ID, and "CP_ID ":" TEST_ROA_CP_ID " Data includes the names and phone numbers of the buddies included in the address book. FIG. 11 (b) illustrates the registration of the address book for the purpose of explanation, and the scope of rights of the present invention is not limited thereto .

Returning to FIG. 3, the presence server authenticates the user through the authentication information included in the registration request message (320). If the authentication is successful, the presence server registers the first presence information and the address book of the user in the presence server, and the terminal receives the registration response message from the presence server (325). The registration response message includes a first hash value generated based on the registered first presence information and the address book of the user. 12 (b) illustrates a registration response message based on the HTTP rest protocol according to an embodiment of the present invention. HTTP / 1.1 200 OK indicates that the registration is successful, and etag means a first hash value generated based on the registered first presence information and the address book of the user.

4 is a flowchart illustrating a method of registering presence information of a terminal according to another embodiment of the present invention. The description overlapping with the above description is omitted. For the present embodiment, it is assumed that Fragment 3 in FIG. 10 is a presence fragment of the user.

Referring to FIG. 4, the terminal changes the specific presence fragment of the user of the local DB in the terminal through the PS application # 1 (405). For example, PS Application # 1 changes Fragment 3 of FIG. 10 as the user's specific presence fragment.

The terminal determines whether the PS application # 2 uses the user's specific presence fragment (410). For example, it is determined whether the PS application # 2 uses Fragment 3 or not.

If PS Application # 2 uses Fragment 3, the terminal changes the information of the terminal user of PS Application # 2 to Fragment 3 changed in the local DB.

The terminal sends 420 a registration request message to the presence server in order to synchronize the specific presence fragment of the changed user in the local DB with the presence server. The registration request message may include the entire first presence information of the user stored in the local DB, but may include only the specific presence fragments of the changed user. In addition, the terminal may include the presence service identifier in the registration request message in order to specify which presence service is concerned while transmitting the registration request message. For example, the terminal may include the identifier of service 1 if the user's specific presence fragment is used only in PS application # 1, and the identifier of services 1 and 2, if used in PS applications # 1 and 2, in the registration request message. According to another embodiment of the present invention, a registration request message may be transmitted without specifying a service.

The terminal receives the registration response message from the presence server (425). The registration response message includes a first hash value for the first presence information of the registered user.

The terminal may then transmit the first hash value of the registration response message to the presence server to confirm whether the first presence information of the user registered in the presence server matches the first presence information of the user stored in the local DB (430). The transmission of the first hash value may be performed periodically or in accordance with the execution of any PS application.

The presence server determines whether the first hash value of the first presence information stored in the current presence DB matches the first hash value received from the terminal (435). The presence server notifies the terminal whether the first hash values match.

If the first hash values are inconsistent with each other, the UE transmits a registration request including the first presence information stored in the local DB to the first presence information stored in the local DB and the first presence information registered in the presence server, The message is transmitted to the presence server (440). Although the first embodiment has been described as an example of changing the first presence information, those skilled in the art can understand that the change of the address book of the terminal can be similarly performed.

5 is a flowchart illustrating a method of requesting presence information of a terminal according to an embodiment of the present invention. The description overlapping with the above description is omitted.

First, the terminal transmits a PS request message including authentication information to the presence server (505). The PS request message is a message requesting the presence server for the second presence information. The authentication information may include at least one of an identifier of presence services requiring the second presence information, an identifier of the user in the presence services, and an access key assigned from the presence server. 13 (b) illustrates a PS request message based on the HTTP rest protocol.

The presence server performs user authentication (510).

If the authentication is successful, the terminal receives a PS response message from the presence server (515). The PS response message relates to presence services of users registered in the presence server, and includes presence information of buddies included in the address book registered in the presence server. For example, assume that user A has registered the presence services 1, 2, 3 and the address book that it is using with the presence server, and the buddy B, C, D is stored in the address book of user A. It is also assumed that buddies B, C, and D use services 1, 2, and 3. When the terminal of the user A transmits a PS request message to the presence server, the presence server transmits the second presence information = {Fragment (Service 1, Buddy B), Fragment (Service 1, Buddy C), Fragments (Service 1, Buddy D) (Service 2, buddy C), fragment (service 2, buddy D), fragment (service 3, buddy B), fragment (service 3, buddy C), fragment , Buddy D)}. That is, the second presence information is a combination of presence fragments for each of the presence services enumerated in the first presence information.

On the other hand, if an identifier of the presence services is specified in the presence request message, the presence server may provide only the presence fragment for the presence service to the terminal. The PS response message may include a second hash value generated based on the second presence information.

15 illustrates a PS response message in accordance with an embodiment of the present invention. Although it is assumed in FIG. 15 that information about one presence service and one buddy is received for convenience of explanation, it is understood by those skilled in the art that information on a plurality of buddies and a plurality of presence services can be received . Referring to Fig. 15, "etag ": " 114daa2f646e000000000000c628565f " represents a second hash value. The " tuple "is a presence fragment, and can be distinguished by service or buddy. In this embodiment, " tuple" "Id:" "aia-t0" is the identifier of the tuple, "service-id": "all-ip-agent: voice" indicates that the buddy is an all- , DeviceID indicates the unique identifier of the buddy terminal, and contact indicates the buddy's SIP identifier. tuple Here, device is the information about the terminal, person is the name and information of the subscriber, ims-ip is the IP address in the IMS network, internet-ip is the IP address in the Internet network, activities are on / off line status, And the update time of the information, respectively.

The terminal stores the received second presence information in the local DB (520), and synchronizes the second presence information and the PS applications stored in the local DB (525). Synchronization of the second presence information and PS applications stored in the local DB may be performed without access to the presence server. For example, the terminal extracts at least one presence fragment corresponding to a specific presence application from second presence information stored in the local DB. 10, it is assumed that the specific presence application is presence application # 3. At this time, the terminal extracts Fragment 1, 2, 4, 5 from the second presence information stored in the local DB. The terminal provides the extracted Fragment 1,2,4,5 to the presence application # 3.

According to one embodiment of the present invention, synchronization with presence applications can be triggered periodically according to the presence synchronization agent's local synchronization timer installed in the terminal. For example, the terminal may perform synchronization in batch with presence applications when the local synchronization timer expires. According to another embodiment, the synchronization may be event triggered according to a command of the presence agent. According to another embodiment, the synchronization may be triggered by a separate synchronization request of the presence application. FIG. 6 is a flowchart illustrating a method of requesting presence information of a terminal according to another embodiment of the present invention. The description overlapping with the above description is omitted.

The terminal receives a request for the presence fragment included in the second presence information from the presence application # 1 (605). For example, according to the user operation or the periodic synchronization schedule of the presence application # 1, the terminal is requested to inquire the presence fragment included in the second presence information. The lookup request for a presence fragment may be for one buddy, but it may be for many buddies.

The terminal transmits a second hash value received via the PS response message to the presence server (610). For example, "etag ": " 114daa2f646e000000000000c628565f"

The presence server determines whether the second hash value of the presence server matches the second hash value received from the terminal (615). The presence server notifies the terminal whether the second hash values match each other. If the second hash values match each other, the terminal provides the presence fragment from the second presence information stored in the local DB to the PS application # 1.

If the hash values do not match, the terminal receives a PS response message containing the updated second presence information from the presence server (620).

The terminal determines whether to synchronize with the PS application # 2 according to whether the presence fragments of the second presence information used by the PS application # 1 and the PS application # 2 are the same (625). For example, if PS Application # 1 uses Fragment 1 through 5 and Fragment 1 through Fragment 5 change as shown in FIG. 10, synchronization with PS Application # 2 is required. Also, if there is no change in Fragment 6, synchronization with PS application # 4 is not required.

If the presence fragments of the second presence information used by the PS application # 1 and the PS application # 2 are not the same, the terminal stores the second presence information received from the presence server in the local DB, Synchronization is performed (630).

Alternatively, if the second presence information used by the PS application # 1 and the PS application # 2 are the same, the terminal stores the second presence information received from the presence server in the local DB and synchronizes with the PS applications # 1 and # 2 (635). On the other hand, in order to synchronize with the PS application # 2, the terminal extracts Fragment 1, 3, 4 from the second presence information. The terminal provides the extracted Fragment 1, 3, 4 to the PS application # 2. As such, PS applications can acquire presence fragments separately from the local database of the terminal.

7 is a flowchart illustrating a method of registering presence information in a presence server according to an embodiment of the present invention. The description overlapping with the above description is omitted.

Referring to FIG. 7, the presence server receives a registration request message from the terminal (705). The terminal authenticates the user using the authentication information included in the registration request message (710).

If the user authentication is successful, the presence server stores the first presence information and the address book included in the registration request message in the presence database (715).

The presence server generates a first hash value using the first presence information and the address book stored in the presence DB, and transmits a registration response message including the first hash value (720).

8 is a flowchart illustrating a method of providing presence information of a presence server according to an embodiment of the present invention. The description overlapping with the above description is omitted.

Referring to FIG. 8, the presence server receives a PS request message from the terminal (805). The presence server performs user authentication using the authentication information included in the PS request message (810).

If the user authentication is successful, the presence server reads the first presence information and the address book of the user stored in the presence DB (815). The presence server can grasp the list of presence services being used by the user of the terminal through the first presence information. In addition, the buddies associated with the second presence information can be determined through the address book.

The presence server determines whether the first service among the presence services listed in the first presence information is an IMS network-based service (820). Presence server may be provided with pre-information about which Presence Service is an IMS network-based service and which Presence Service is a non-IMS network-based service.

If it is determined that the first service is a service based on the IMS network, it is determined 825 whether the first buddy among the buddies included in the address book is a subscriber of the third-party IMS network. If the subscriber is a subscriber of the IMS network, the presence fragment of the first buddy is stored in the presence DB, so that the presence fragment of the first buddy can be read from the presence DB (840).

On the other hand, if the subscriber is a subscriber of a third-party IMS network, since the presence fragment of the first buddy should be obtained from the third-party IMS network, the presence server specifies the first service and the first buddy to the presence GW and requests presence fragments (830). In the present embodiment, one first buddy is illustrated for convenience of description, but it is understood by those skilled in the art that a plurality of buddies stored in the address book can be simultaneously performed.

If it is determined in step 820 that the first service is a non-IMS network-based service, the presence server determines whether the first service is a service based on the non-IMS network provided by the presence server (835). If the first service is a service based on a non-IMS network provided by a third party, the presence server requests and receives the presence information by specifying the first service and the first buddy to the presence gateway (830). The non-IMS network-based service provided by the third party can illustrate, for example, an instant messaging service by a third party application or an SNS based on the Internet network.

If it is determined in step 835 that the first service is a non-IMS network-based service provided by the service provider, the presence server reads out the presence fragment of the first buddy of the first service from the presence database (840).

The presence server combines the presence fragments collected through 830 and 840 to generate 845 the second presence information. The generated second presence information is stored in the presence DB. The presence server generates the second hash value using the second presence information.

The presence server transmits a PS response message including the hash value and the second presence information to the terminal (850).

9 is a flowchart illustrating a method of providing a presence service according to an embodiment of the present invention. The description overlapping with the above description is omitted.

First, the terminal transmits a first type registration request message to the presence server (905). For example, the terminal transmits the message of FIG. 11 (b) to register the first presence information and the address book.

The presence server sends a registration response message of the first type to the terminal (910). For example, the presence server provides the second presence information to the terminal through the message of Fig. 12 (b).

The terminal transmits a first type PS request message to the presence server (915). For example, the terminal requests the second presence information through the message of Fig. 13 (b).

The presence server transmits a first type PS request message to the presence GW for presence fragments constituting the second presence information (920). The PS request message of 920 may be a subset of the 915 PS request message. That is, the presence server requests the presence GW for the remaining fragments excluding the presence fragments readable from the presence DB.

The presence GW stores data included in the PS request message of the first type received from the presence server into the first request data related to the presence service based on the third party IMS network and the second request with respect to the presence service based on the third party provided non- Divided into days. For example, the second request data may be data requesting a presence fragment for an SNS service provided on the Internet network.

The presence GW converts the first request data included in the first type PS request message received from the presence server into the second type PS request message. For example, the presence GW converts the first request data included in the PS request message based on the HTTP rest protocol shown in FIG. 13 (b) into the PS request message based on the SIP / XCAP protocol shown in FIG. 13 (a). 13 (a) is a PS request message based on the SIP / XCAP protocol, and sip: 010xxxx@lte-lguplus.co.kr is information for identifying a user of the terminal in the IMS network.

Also, the presence GW converts the second request data included in the first type PS request message received from the presence server into the third type PS request message. The third type may be a protocol according to the open API disclosed by the SNS service provider.

The presence GW transmits 925 a second type PS request message to the IMS network and receives 935 a second type PS response message from the IMS network. For example, the presence GW transmits the message of Fig. 13 (a) to the IMS network and receives the message of Fig. 14 from the IMS network from the IMS network. Fig. 14 shows a PS / PS response message based on the SIP / XCAP protocol. The message < presence xmlns = "urn: ietf: params: xml: ns: pidf" xmlns: c = "urn: ietf: params: xml: ns: pidf: xmlns: op = "urn: oma: xml: ns: pidf: rpid" xmlns: pdm = "urn: ietf: params: xml: ns: : xmlns: opd = "urn: oma: xml: pde: pidf: ext" entity = "sip: user1@lte-lguplus.co.kr"> defines the format of the XML document .

The presence GW transmits a third type of PS request message to the Internet network (930) and receives a third type of PS response message from the Internet network (940).

The presence GW converts the second type PS response message and the third type PS response message into a first type PS response message, respectively, and transmits the message to the presence server (945). For example, the presence GW converts the SIP response message based on the SIP / XCAP protocol shown in Fig. 14 into a PS response message based on the HTTP rest protocol shown in Fig. 15 and transmits the message to the presence server.

The presence server transmits a first type of PS response message received from the presence server to the terminal (950).

Meanwhile, the subscriber (buddy) of the third-party IMS network can request the first presence information for the user of the terminal. In this case, the presence GW receives a second type PS request message from the IMS network (955). The presence GW converts the second type PS request message to a first type PS request message and transmits it to the presence server (960). The presence server sends 965 a first type of PS response message containing the first presence information to the presence GW. The presence GW converts the first type of PS response message including the first presence information into a second type of PS response message and transmits it to the IMS network (970).

Hereinafter, the structure of the terminal, the presence server, and the presence gateway will be described with reference to FIGS. The description overlapping with the above description is omitted, and a person skilled in the art can understand the configuration of the terminal, the presence server and the presence gateway from the above description.

16 is a diagram illustrating a terminal according to an embodiment of the present invention.

16, the terminal 210 includes a transmitter 212, a receiver 213, a storage 214, and a processor 215. The transmitting unit 212 transmits a radio frequency (RF) signal, and the receiving unit 213 receives a radio frequency (RF) signal. The transmitting unit 212 and the receiving unit 213 may be implemented as one RF module 216. The storage unit 214 stores PS applications, a presence agent, an address book, and a local DB. The processor 215 executes the presence agent to control the RF module and the storage unit. In addition, in the above-described embodiments and the following description, the operation of the terminal can be understood as a behavior of the presence agent from a software point of view, and from a hardware point of view it can be understood that it is controlled by the processor 215 by execution of a presence agent .

The processor 215 collects the first presence information of the user including the list of presence services used by the user of the terminal based on the applications stored in the storage 214. [ The processor 215 registers the first presence information of the user and the address book of the user on the presence server through the RF module 216. [ The processor 215 obtains second presence information for buddies contained in the user's address book from the presence server. Here, the second presence information for the buddies may be a combination of presence fragments for each of the presence services enumerated in the first presence information.

The processor 215 detects presence applications that provide presence services among the applications stored in the storage unit 214. [ The processor 215 reads from the detected presence applications at least one of information about the user's profile, screen name, ID, service login status, and service version. Presence services include IMS (IP Multimedia subsystem) network based services and non-IMS network based services. The processor 215 controls the RF module 216 to transmit and receive data based on the HTTP rest protocol with the presence server.

The processor 215 transmits to the presence server, via the RF module 216, a registration request message including authentication information for authentication with the presence server, first presence information, and an address book. The processor 215 receives via the RF module 216 a registration response message including a first hash value generated based on the first presence information and the address book when authentication with the presence server is successful.

The processor 215 transmits, through the RF module 216, a presence request message containing authentication information for authentication with the presence server to the presence server. If authentication with the presence server is successful, the processor 215, via the RF module 216, sends a presence response message containing a second hash value generated based on the second presence information and the second presence information . Here, the authentication information may include at least one of an identifier of the presence services, an identifier of the user in the presence services, and an access key assigned from the presence server.

Processor 215 extracts presence fragments for each of the presence services from the second presence information. The processor 215 selectively provides the presence applications with the extracted presence fragments. The processor 215 stores the second presence information in the local database included in the storage unit 214. [ The presence applications selectively obtain the presence fragments from the local database.

On the other hand, the presence agent can provide the presence application with an application program interface (API) for accessing the local database.

17 is a diagram illustrating a presence server according to an embodiment of the present invention.

17, the presence server 250 includes a transmission unit 254, a reception unit 255, a storage unit 256, and a processor 257.

The receiver 255 receives from the terminal a registration request message including the first presence information of the user including the list of presence services being used by the user of the terminal and the address book of the user.

Processor 257 collects the presence fragments of each of the presence services enumerated in the first presence information for the buddies contained in the user's address book. The processor 257 combines the collected presence fragments to generate second presence information for the buddies.

The transmitter 256 transmits a presence response message including the second presence information to the terminal.

The processor 257 authenticates the user based on the authentication information included in the registration request message. The processor 257 stores the first presence information and the address book in the presence database when the user authentication is successful. The processor 257 controls the transmitting unit 255 to transmit the registration response message including the first hash value and the first hash value generated based on the address book to the terminal.

Meanwhile, the receiving unit 255 receives a presence request message including authentication information from the terminal. The processor 257 authenticates the user based on the authentication information, and the presence response message includes a second hash value generated based on the second presence information. Here, the authentication information may include at least one of an identifier of the presence services, an identifier of the user in the presence services, and an access key of the terminal.

The processor 257 determines whether the first presence service among the presence services enumerated in the first presence information is an IMS (IP Multimedia subsystem) network-based service. The processor 257 determines whether the buddies are subscribers of the third party network if the first presence service is determined to be an IMS network-based service. The processor 257 requests the presence node for the buddies of the first presence service to the presence gateway connected to the IMS network if the buddies are subscribers of the third party network. The processor 257 reads the presence fragments for buddies of the first presence service from the presence database located outside the IMS network, if the buddies are judged to be subscribers of the first network.

The processor 257 transmits and receives data based on the HTTP rest protocol with the terminal and the presence gateway through the receiving unit 255 or the transmitting unit 254. [

Meanwhile, the presence gateway transmits and receives data based on the IMS network and the SIP (Session Initiation Protocol) / XCAP (XML Configuration Access Protocol) protocol. The presence gateway converts the presence fragment request for the buddies of the first presence service received on the basis of the HTTP rest protocol from the transmission unit 255 into a SIP / XCAP protocol based message. The presence gateway transmits a SIP / XCAP protocol-based message to the IMS network. The presence gateway converts the presence fragment of the buddies of the first presence service received from the IMS network based on the SIP / XAP protocol into a message based on the HTTP rest protocol and transmits the message to the reception unit 255.

The above-described embodiments of the present invention can be implemented by various means. For example, embodiments of the present invention may be implemented by hardware, firmware, software, or a combination thereof.

In the case of hardware implementation, the method according to embodiments of the present invention may be implemented in one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs) , Fragment Programmable Gate Arrays (FPGAs), a processor, a controller, a microcontroller, a microprocessor, or the like.

In the case of an implementation by firmware or software, the method according to embodiments of the present invention may be implemented in the form of a module, a procedure or a function for performing the functions or operations described above. The software code can be stored in a memory unit and driven by the processor. The memory unit may be located inside or outside the processor, and may exchange data with the processor by various well-known means.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The foregoing description of the preferred embodiments of the invention disclosed herein has been presented to enable any person skilled in the art to make and use the present invention. While the present invention has been particularly shown and described with reference to preferred embodiments thereof, it will be understood by those skilled in the art that various changes and modifications may be made therein without departing from the spirit and scope of the invention as defined by the appended claims. For example, those skilled in the art can utilize each of the configurations described in the above-described embodiments in a manner of mutually combining them. Accordingly, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

The present invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. Accordingly, the above description should not be construed in a limiting sense in all respects and should be considered illustrative. The scope of the present invention should be determined by rational interpretation of the appended claims, and all changes within the scope of equivalents of the present invention are included in the scope of the present invention. In addition, claims that do not have an explicit citation in the claims can be combined to form an embodiment or included as a new claim by amendment after the application.

Claims (39)

A method for providing a presence service to a user of a terminal,
Collecting first presence information of the user including a list of presence services used by a user of the terminal based on applications installed in the terminal;
Registering the first presence information of the collected user and the address book of the user on the presence server;
Obtaining second presence information on buddies included in the address book of the user from the presence server;
Storing the obtained second presence information in a local database included in the terminal; And
And synchronizing with the presence applications providing the presence services using the second presence information stored in the local database,
Wherein the second presence information for the buddies is a combination of presence fragments for each of the presence services listed in the first presence information. The method of claim 1, wherein collecting the first presence information of the user comprises:
Reading at least one presence fragment corresponding to each of the presence applications providing the presence services;
Combining the presence fragments read from the respective presence applications to generate the first presence information; And
And storing the first presence information in the local database. 3. The method of claim 2,
Wherein the registering of the first presence information with the presence server comprises registering the first presence information stored in the local database with the presence server,
Wherein the registration of the first presence information is periodically performed according to a network synchronization timer of a presence agent installed in the terminal, or the presence agent triggers the event according to the change of the first presence information, Lt; / RTI &gt; The method according to claim 1,
Wherein the presence services include a service based on an IMS (IP Multimedia subsystem) network and a service based on a non-IMS network, and transmitting and receiving data based on a hypertext transfer protocol (HTTP) rest protocol between the terminal and the presence server. The method of claim 1, wherein registering the first presence information and the address book of the user comprises:
Transmitting a registration request message including authentication information for authentication with the presence server, the first presence information, and the address book to the presence server; And
And if the authentication with the presence server is successful, receiving a registration response message including the registered first presence information and a first hash value generated based on the address book. The method of claim 1, wherein the obtaining of the second presence information comprises:
Transmitting a presence request message including authentication information for authentication with the presence server to the presence server; And
And if the authentication with the presence server is successful, receiving a presence response message comprising a second hash value generated based on the second presence information and the second presence information. The information processing apparatus according to claim 5 or 6,
The identifier of the presence services, the identifier of the user in the presence services, and the access key assigned from the presence server. delete 2. The method of claim 1, wherein synchronizing with the presence applications comprises:
Extracting at least one presence fragment corresponding to a first presence application of the presence applications from second presence information stored in the local database; And
And providing the extracted at least one presence fragment to the first presence application. The method according to claim 1,
Synchronization with the presence applications is performed on the local database without access to the presence server,
Wherein synchronization with the presence applications is triggered periodically according to a local synchronization timer of a presence agent installed in the terminal or is triggered according to an instruction of the presence agent or triggered by a separate synchronization request of the presence applications . The method of claim 1, wherein the method for providing the presence service to the user by the terminal is performed through a presence agent installed in the terminal. A method for providing a presence service to a terminal by a presence server,
Receiving a registration request message including a first presence information of the user including a list of presence services being used by a user of the terminal and an address book of the user from the terminal;
Collecting presence fragments of each of the presence services enumerated in the first presence information for buddies included in the address book of the user;
Combining the collected presence fragments to generate second presence information for the buddies; And
And transmitting a presence response message including the second presence information to the terminal,
Wherein the second presence information is stored in a local database contained within the terminal and used to synchronize with presence applications providing the presence services. 13. The method of claim 12,
Authenticating the user based on the authentication information included in the registration request message;
Storing the first presence information and the address book when the user authentication is successful; And
Further comprising transmitting to the terminal a registration response message including a first hash value generated based on the first presence information and the address book. 13. The method of claim 12,
Receiving a presence request message including authentication information from the terminal; And
Further comprising authenticating the user based on the authentication information,
Wherein the presence response message comprises a second hash value generated based on the second presence information. 15. The method according to claim 13 or 14,
An identifier of the presence services, an identifier of the user in the presence services, and an access key of the terminal. 13. The method of claim 12, wherein collecting presence fragments for the presence services comprises:
Determining whether the first presence service among the presence services enumerated in the first presence information is an IMS (IP Multimedia Subsystem) network based service;
Determining whether the buddies are subscribers of a third party network if the first presence service is determined to be an IMS network based service; And
Requesting a presence fragment for the buddies of the first presence service to a presence gateway connected to the IMS network if the buddies are subscribers of the third party network. 17. The method of claim 16, wherein collecting presence fragments for the presence services comprises:
Further comprising reading a presence fragment for the buddies of the first presence service from a presence database located outside the IMS network if the buddies are determined to be subscribers of the first network. 17. The method of claim 16,
The presence server transmits and receives data based on the HTTP rest protocol with the terminal and the presence gateway, and the presence gateway transmits and receives data based on an SIP (Session Initiation Protocol) / XCAP (XML Configuration Access Protocol) protocol with the IMS network , Way. 19. The apparatus of claim 18, wherein the presence gateway comprises:
Converting a presence fragment request for the buddies of the first presence service received based on the HTTP rest protocol from the presence server to the SIP / XCAP protocol based message;
Transmitting the converted SIP / XCAP protocol based message to the IMS network; And
Further comprising converting a presence fragment for the buddies of the first presence service received from the IMS network based on the SIP / XCAP protocol into a message based on the HTTP rest protocol and transmitting the message to the presence server . A computer-readable recording medium storing a program for executing the method according to any one of claims 1 to 12. A terminal for providing a presence service to a user,
An RF module for transmitting and receiving a radio signal;
A storage unit for storing applications installed in the terminal, an address book of the user, and a presence agent; And
And a processor for executing the presence agent stored in the storage unit to control the RF module and the storage unit,
The processor collects the first presence information of the user including a list of presence services that the user of the terminal uses based on the applications stored in the storage unit, 1 presence information and the address book of the user to a presence server, acquires second presence information on buddies included in the address book of the user from the presence server, and transmits the obtained second presence information to the presence server Storing the received presence information in a local database included in the storage unit, synchronizing with presence applications providing the presence services using the second presence information stored in the local database,
Wherein the second presence information for the buddies is a combination of presence fragments for each of the presence services listed in the first presence information. 22. The computer-readable medium of claim 21, wherein the processor for collecting the first presence information of the user further comprises:
Detecting the presence applications among the applications stored in the storage unit, reading at least one presence fragment corresponding to each of the detected presence applications from the detected presence applications, Combine fragments to generate the first presence information, and store the generated first presence information in the local database. The method of claim 22, wherein the processor for registering the first presence information in the presence server registers the first presence information stored in the local database in the presence server by executing the presence agent,
Wherein the registration of the first presence information is performed periodically according to a network synchronization timer of the presence agent, or the presence agent triggers the event according to the change of the first presence information, or is triggered according to a request of the presence applications, Terminal. 22. The method of claim 21,
Wherein the presence services include a service based on an IMS (IP Multimedia subsystem) network and a service based on a non-IMS network, and the processor controls the RF module to transmit / receive data based on an HTTP rest protocol with the presence server . The apparatus of claim 21, wherein the processor for registering the first presence information and the address book of the user further comprises:
The first presence information, the first presence information, and the address book to the presence server, and when authentication with the presence server is successful, the first presence information and the second presence information are transmitted to the presence server, And receiving a registration response message including a first hash value generated based on the address book. 23. The apparatus of claim 21, wherein the processor for obtaining the second presence information further comprises:
And a presence server for transmitting a presence request message including authentication information for authentication with the presence server to the presence server, and when the authentication with the presence server is successful, the authentication server transmits the presence information generated based on the second presence information and the second presence information And a presence response message containing a 2 hash value. 27. The method according to claim 25 or 26,
An identifier of the presence services, an identifier of the user in the presence services, and an access key assigned from the presence server. delete 22. The method of claim 21, wherein the processor in synchronization with the presence applications executes the presence agent,
Extracting at least one presence fragment corresponding to a first one of the presence applications from second presence information stored in the local database and providing the extracted at least one presence fragment to the first presence application, Terminal. 22. The method of claim 21,
Synchronization with the presence applications is performed on the local database without access to the presence server,
Wherein synchronization with the presence applications is triggered periodically according to a local synchronization timer of the presence agent or is triggered according to an instruction of the presence agent or is triggered by a separate synchronization request of the presence applications. 22. The method of claim 21, wherein the presence agent comprises:
Wherein the presence applications provide an application program interface (API) for accessing the local database to the presence applications. 1. A presence server for providing a presence service to a terminal,
A receiving unit for receiving, from the terminal, a registration request message including the first presence information of the user and the address book of the user including a list of presence services being used by the user of the terminal;
Collecting presence fragments of each of the presence services listed in the first presence information with respect to buddies included in the address book of the user and combining the collected presence fragments with the buddies A processor for generating second presence information for the first presence information; And
And a transmitter for transmitting a presence response message including the second presence information to the terminal
Wherein the second presence information is stored in a local database contained within the terminal and used to synchronize with presence applications providing the presence services. 33. The apparatus of claim 32,
Authenticating the user based on the authentication information included in the registration request message, storing the first presence information and the address book in the presence database if the user authentication is successful, and based on the first presence information and the address book, And controls the transmitting unit to transmit a registration response message including the generated first hash value to the terminal. 33. The method of claim 32,
Wherein the receiver receives a presence request message including authentication information from the terminal, the processor authenticates the user based on the authentication information, and the presence response message includes a second presence information generated based on the second presence information, A presence server that contains a hash value. 35. The method as claimed in claim 33 or 34,
An identifier of the presence services, an identifier of the user within the presence services, and an access key of the terminal. 33. The apparatus of claim 32, wherein the processor for collecting presence fragments for the presence services comprises:
Wherein the presence server determines whether the first presence service among the presence services listed in the first presence information is a service based on an IMS (IP Multimedia Subsystem) network, and if the first presence service is determined to be an IMS network based service, And if the buddies are subscribers of the third party network, request a presence fragment of the buddies of the first presence service to a presence gateway connected to the IMS network. 37. The processor of claim 36, wherein the processor for collecting presence fragments for the presence services comprises:
And if the buddies are determined to be subscribers of the first network, read presence fragments of the buddies of the first presence service from a presence database located outside the IMS network. 37. The apparatus of claim 36, wherein the processor, via the receiver or the transmitter,
Wherein the presence gateway transmits and receives data based on the HTTP rest protocol with the terminal and the presence gateway, and the presence gateway transmits and receives data with the IMS network based on SIP (Session Initiation Protocol) / XCAP (XML Configuration Access Protocol) protocol. 39. The method of claim 38, wherein the presence gateway comprises:
XCAP protocol based message received from the sender based on the HTTP rest protocol to the SIP / XCAP protocol based message, and transmits the SIP / XCAP protocol based message to the IMS network And transmits a presence fragment for the buddies of the first presence service received from the IMS network based on the SIP / XCAP protocol to a message based on the HTTP rest protocol and transmits the message to the receiver.

Images