KR20120094809A - Presence management system using the list query and presence management method of the same - Google Patents

Abstract

PURPOSE: A presence management system and method are provided to offer a desired result value for inquiry into presence management information in each subscriber by creating the presence management information for the subscribers. CONSTITUTION: A permanent presence managing book(210) analyzes a detailed inquiry filed from the whole filed of the subscribers from a PIDF(Presence Information Data Format) document including an operation execution command received from an aggregation proxy(100). A detailed inquiry database(220) manages the detail inquiry field. The detailed inquiry field is set by a system manager and is ID(Identification) in an SNS(Social Network Service), an email, MDN(Mobile Device Number), and URI(Uniform Resource ID).

Description

Presence management system and management method using list inquiry {PRESENCE MANAGEMENT SYSTEM USING THE LIST QUERY AND PRESENCE MANAGEMENT METHOD OF THE SAME}

The present invention relates to an IP Multimedia Subsystem Network (IMS) technology, and more particularly, to a management system and a method of managing presence information for each subscriber.

IMS (IP Multimedia System) proposed by the 3rd Generation Partnership Project (3GPP) is an all-IP based next generation communication service platform, which is the foundation for integrating wired and wireless networks and enabling various broadcasting communication services. The IMS network integrates the existing Internet network to provide mobile users with multimedia and multisession applications, guarantee the Quality of Service (QoS), and provide operation for billing. By using IMS networks, you can also standardize interfaces that allow third-party vendors to develop new applications for users and developers.

Protocols used for the main interfaces provided by IMS networks include Diameter (Sh, Dh, Ro, Rf), SIP protocol (ICS, Gm), and XCAP (Ut). In order to provide various services based on IMS to a user, the user's presence must be managed in common, and the necessary information can be easily defined in each service. You should be able to check. As a solution to this, the IMS network proposes the presence information management based on the XML Configuration Access Protocol (XCAP) and the event processing using the Session Initiation Protocol (SIP).

The OMA (Open Mobile Alliance), as multimedia content services are provided to mobile terminals, establishes a service method that can accommodate them and open standards for enablers, so that regardless of country, network operator, terminal, or communication method, Provide compatible mobile services.

The technical problem to be achieved by the present invention is to provide a management system and a management method for obtaining the detailed items of the presence information for each subscriber on the IMS network at once without multiple inquiries.

In order to solve the above technical problem, the presence management system according to an embodiment of the present invention parses only a detailed lookup field among all fields of a subscriber in a PIDF document included in an operation execution command issued from an aggregation proxy ( permanent presence management block parsing; And a detail query database for separately storing and managing only the detail query field parsed by the permanent presence management block.

The detailed lookup field is a field preset by the system administrator and is at least one of an ID, an e-mail, an MDN, and a subscriber URI (User_URI) for each social network service (SNS) of each subscriber.

 The operation performs any one of creation, update, deletion, and inquiry.

The response to the result of the operation is any one of 1XX, 2XX, 3XX, 4XX, 5XX and 6XX responses.

The presence management system inquires the detail query field included in the body (BODY) of the inquiry command received from the aggregation proxy, and sends a detailed item list query block for transmitting the query for each item to the detail query database. It includes more.

When the database receives the inquiry request from the detail list inquiry block, the database searches for the subscriber URI corresponding to the detail inquiry field, and then transmits a response including the subscriber URI to the detail list inquiry block. .

According to another aspect of the present invention, there is provided a method for managing a presence field of a presence management system connected to an aggregation proxy and a presence server, the method including: receiving an operation execution command including a PIDF document from the aggregation proxy; Parsing at least one detail lookup field among all fields of a subscriber of the PIDF document; And transmitting a command to perform an operation on the parsed detail query field and managing the same in a detail query database.

The detailed lookup field is a field preset by a system administrator and is at least one of an ID, an e-mail, an MDN, and a subscriber URI (User_URI) for each social network service (SNS) of each subscriber.

The operation execution command performs any one of the generation, update, deletion, and inquiry of the detail inquiry field.

The transmitting of the operation execution command further includes storing a corresponding detail search field for each subscriber in the database when the operation execution command is a generation command.

The presence field management method includes the step of the database receiving the detail query field and performing an operation corresponding to the command; And returning a response to the result of performing the operation to the aggregation proxy.

The presence field management method may include: inquiring at least one detailed lookup field included in the command when a POST command is received from the aggregation proxy; And transmitting a query to the database for each of the inquired detail query fields.

The presence field management method may further include: receiving, by the database, the inquiry request; Querying the subscriber URI corresponding to each of the detail query fields included in the inquiry request; And returning the information included in the response for each inquired subscriber URI.

The presence field management method may further include: receiving a respective response and generating a presence result list including the subscriber URI and the detailed lookup field; And transmitting the presence result list to the aggregation proxy.

Presence information for each subscriber can be simultaneously created, changed or deleted by the presence management system and the presence field management method according to an embodiment of the present invention. You can get it.

1 is a block diagram schematically showing a presence management system according to an embodiment of the present invention.
2 is a call flow diagram for input and inquiry of presence information of an XCAP server in an IMS network.
3 is a call flow diagram for input and inquiry of presence information in an IMS service according to an embodiment of the present invention.
4 is a flowchart illustrating an operation performed in a permanent presence management block and a detailed item list inquiry block according to an embodiment of the present invention.
5 is a database table XML_PS_DOC of a permanent presence management block according to an embodiment of the present invention.
FIG. 6 is a field table (XML_STALK_IDX) generated by the persistent presence management block by parsing only detail lookup fields for transmission to a detail lookup database according to an embodiment of the present invention.
7 is an XCAP message for inputting the updated Twitter ID to the presence inquiry system through the XCAP interface.
FIG. 8 is an XCAP message for updating the Twitter ID shown in FIG. 7 in a detailed query database according to an embodiment of the present invention.
FIG. 9 is a PIDF document including detailed lookup fields of a subscriber receiving the message shown in FIG. 8 and stored in a detail lookup database according to an embodiment of the present invention.
10 is an XCAP message sent by the terminal to query one or more other subscribers in the presence management system according to an embodiment of the present invention.
11 is an XCAP message sent by the detail list inquiry block to the detail query database according to an embodiment of the present invention.
12 is an XCAP message that a detailed item list inquiry block sends to a detailed query database according to an embodiment of the present invention.
FIG. 13 is a POST response message generated by a detailed item list inquiry block according to an embodiment of the present invention to collect and send a response received from a detailed query database to a terminal.

In order to fully understand the present invention, operational advantages of the present invention, and objects achieved by the practice of the present invention, reference should be made to the accompanying drawings and the accompanying drawings which illustrate preferred embodiments of the present invention. BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the preferred embodiments of the present invention with reference to the accompanying drawings. Like reference symbols in the drawings denote like elements.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. In the present specification, the singular form includes plural forms unless otherwise specified in the specification. It is noted that the terms "comprises" and / or "comprising" used in the specification are intended to be inclusive in a manner similar to the components, steps, operations, and / Or additions.

1 is a block diagram schematically showing a presence management system according to an embodiment of the present invention.

Referring to FIG. 1, the IMS network 1000 includes an XCAP server 20 and a presence server 30.

The XCAP server 20 directly connects to the subscriber terminal 10 through a Ut interface (XML Configuration Access Protocol (hereinafter referred to as XCAP)) and includes an aggregation proxy 100 and a presence inquiry system 200.

XCAP used in the Ut interface is an HTTP-based XML document access standard defined by IETF's SIMPLE (SIP for Instant Messaging and Presence Leveraging Extensions) working group.

 Since XCAP is an addressing standard based on the HTTP protocol, it uses the HTTP request / response syntax. XCAP can create, modify, query, or delete XML documents in PIDF (Presence Information Data Format) format. Use the HTTP PUT method to create and modify XML document information, use GET to query, and DELETE to delete. That is, XCAP inquires (GET), changes (PUTs), or deletes (DELETEs) information of an XML document using a specific HTTP method.

The XCAP server 20 receives the XCAP / HTTP message from the XCAP client (terminal 10) and analyzes the XCAP URI set in the HTTP method and the HTTP Request-URI. The XCAP server 20 performs the requested operation and returns the result to the client (terminal 10).

In this process, the XCAP server 20 parses an XML document and proceeds to XML Schema Validation. In addition, the XCAP server 20 generates, updates, deletes, or retrieves an XML document, an XML element, and an XML attribute. In addition, the XCAP server 20 performs a SIP profile reception processing function, content generation, and notification transmission upon changing an XML document in order to perform an XCAP document change function.

Aggregation Proxy (100) provides a function for authenticating XCAP messages transmitted by subscribers and routing to a subscriber profile database (not shown) for each service.

The presence management system 200 includes a permanent presence management block 210, a detail query database 220, and a detail list inquiry block 230. The presence management system 200 is implemented in a shared XDMS (XDMS) according to the XDMS system standard.

The permanent presence management block 210 parses only the detail lookup field of all the subscriber's fields in the PIDF document included in the operation execution command received from the aggregation proxy 100. In this case, the operation may be any one of operation, generation, update, deletion, and inquiry. Document Management, subscription and notification of XDM Resource Changes, access permission, search, history and restore, sharing by reference It can perform functions such as share or forwarding. 5 to 6 will be described in detail below.

The detail query database 220 stores and manages only the detail query field parsed by the permanent presence management block 210 as a separate table. The detailed lookup field is at least one field preset for each subscriber by a system administrator such as social network service (SNS) ID, e-mail, MDN, and subscriber URI (User_URI) such as Twitter, Facebook, and MeToday.

In addition, the detail query database 220 performs an operation corresponding to the command with respect to the detail query field received from the permanent presence management block 210, and then returns a response to the result of the operation performing the presence management block 210. ). At this time, the response to the result of the operation is any one of 1XX, 2XX, 3XX, 4XX, 5XX and 6XX responses.

The detail item list inquiry block 230 may include a query list including at least one detail query field in the body BODY of a POST inquiry command received through the aggregation proxy 100 at the terminal 10. Inquiry is sent, and the inquiry request is sent to the detail inquiry database 220 for each inquiry detail field.

In addition, when the detailed item list inquiry block 230 sends a response including the subscriber URI from the detailed query database 220 according to the inquiry request, the detailed item list inquiry block 230 generates a presence result list by collecting the response. The detail item list inquiry block 230 completes the presence result list corresponding to the query list and returns to the aggregation proxy 100.

The presence server 30 notifies the status of another subscriber (buddy) in real time based on the information of the detail query field collected by the XCAP server 20.

2 is a call flow diagram for input and inquiry of presence information of an XCAP server in an IMS network.

Referring to FIG. 2, the terminal 10 inputs a newly generated SNS ID (eg, Twitter ID) to the PIDF document of the corresponding terminal 10 through the XCAP interface Ut to the aggregation proxy 100. Transmit (S10). The PUT command is a command for generating or changing an element. In FIG. 2, the PUT command is a command for generating an element for an SNS ID among detailed lookup fields.

Aggregation proxy 100 routes the command to the permanent presence management block 210 after authenticating the terminal 10 (S11). The permanent presence management block 210 that receives this inputs the SNS ID (Twitter ID) to the subscriber's PIDF for the terminal 10 and then returns to the terminal 10 via the proxy 100 again. OK) is transmitted (S12, S13).

After the subscriber registers with the SNS ID, the subscriber goes to the permanent presence management block 210 having the presence information of the subscribers via the proxy 100 in the terminal 10 to find a friend (the other subscriber), and “sip: stalk01@sktims.com”. A request for the presence information of another subscriber having a subscriber URI of S14 and S15 is requested. The permanent presence management block 210 searches the entire element field of the subscribers in the PIDF document, finds the Twitter ID of the subscriber whose subscriber URI is "sip: stalk01@sktims.com," and issues the response again. Return to one terminal 10 (S16, S17). In this case, the response may be one of 1XX, 2XX, 3XX, 4XX, 5XX, and 6XX.

In order to search for another friend, the subscriber searches the presence information of another subscriber having the subscriber URI of "sip: stalk02@sktims.com" in the permanent presence management block 210 through the aggregation proxy 100 in the terminal 10 again. ) Is requested (S18, S19). The permanent presence management block 210 searches the entire element field of the subscribers in the PIDF document, finds the Twitter ID of the subscriber whose subscriber URI is "sip: stalk02@sktims.com," and sends the response to the inquiry request. Return to (10) (S20, S21). In this case, the response may be one of 1XX, 2XX, 3XX, 4XX, 5XX, and 6XX.

That is, as shown in FIG. 2, the existing terminal 10 requests the server 20 for an XCAP inquiry message for each subscriber and analyzes each response to obtain the presence information for a plurality of subscribers. Could get However, such a method may increase the transaction between the terminal 10 and the XCAP server 20 to generate a network load, and the processing speed of the terminal 10 may be delayed.

3 is a call flow diagram for input and inquiry of presence information in an IMS service according to an embodiment of the present invention.

Referring to FIG. 3, the terminal 10 transmits a PUT command to the aggregate proxy 100 to input a newly generated SNS ID (eg, Twitter ID) to the PIDF document of the corresponding terminal through the XCAP interface Ut. (S100).

The aggregation proxy 100 routes the PUT command to the permanent presence management block 210 after authenticating the terminal 10 (S101). Permanent presence management block 210 inputs the SNS ID (Twitter ID) to the subscriber's PIDF for the terminal 10, parsing the SNS ID in the PIDF document (S102), only the SNS ID The command to input (Insert) is transmitted to the detailed query database 220 (S103).

The detail query database 220 generates, inputs and stores a detail query field such as the SNS ID for each subscriber, and transmits a response to the success status to the permanent presence management block 210 (S104). The permanent presence management block 210 returns a response back to the terminal 10 (S105, S106). In this case, the response may be one of 1XX, 2XX, 3XX, 4XX, 5XX, and 6XX.

After registering the SNS ID, the subscriber creates a query list for the presence information of one or more other subscribers from the terminal 10 from the terminal 10 in order to find a friend (other subscriber) and requests an inquiry with a POST message (S107). . The aggregation proxy 100 transmits the inquiry request to the detail item list inquiry block 230 (S108).

The detail item list inquiry block 230 makes an inquiry request to the detail query database 220 for each entry included in the query list. At this time, the number of entries, that is, the inquiry request to the detailed query database 220 by the number of one or more other subscribers (S109).

For example, the detail item list inquiry block 230 requests the friend A's SNS ID to the detail query database 220 first (S110), and the detail query database 220 queries the detail query field table of the friend A. The response including the desired result is transmitted to the detailed item list inquiry block 230 (S111). Subsequently, the detailed item list inquiry block 230 requests the SNS ID of the friend B to the detail query database 220 first (S112), and the detail query database 220 queries the detail query field table of the friend B to search for the desired information. The response including the result value is transmitted to the detailed item list inquiry block 230 (S113).

The detailed item list inquiry block 230 creates a result list including the presence information of one or more friends requested to be queried based on the responses, and transmits the result list to the aggregation proxy 100 (S114). The aggregation proxy 100 transmits the result to the terminal 10 (S115).

According to the presence field management method according to an embodiment of the present invention as described above, the presence information required on the IMS network service can be performed at once without multiple inquiries, thereby reducing the network load between the terminal and the server, and in-terminal processing speed. Can bring improvement.

Meanwhile, FIG. 3 illustrates an example of generating a detailed lookup field such as an XML element of the PIDF document, that is, an SNS ID, for convenience of description. It can be applied to any task that creates, updates, or deletes an attribute.

4 is a flowchart illustrating an operation performed in a permanent presence management block and a detailed item list inquiry block according to an embodiment of the present invention.

Referring to FIG. 4 (a), the permanent presence management block 210 first receives an input (PUT) command from the terminal 10 through the XCAP interface Ut of the aggregation proxy 100 (S120). The permanent presence management block 210 analyzes the command to check whether there is a detail lookup field such as an SNS ID, and if there is a detail lookup field, parsing it (S121). The parsed detail query field is included in an Insert command and transmitted in order to be stored in the detail query database 220 (S122). Permanent presence management block 210 receives the response to the storage in the detailed query database 220, if the success response message (200 OK) generates a response message containing the subscriber URI (S123). The response message is transmitted to the terminal 10 via the aggregation proxy 100 again (S124).

As a result, the SNS ID corresponding to the detailed lookup field is registered in the subscriber's presence information.

Referring to FIG. 4B, the detail item list inquiry block 230 first receives a POST request for a detail query field from the aggregation proxy 100 (S130). The detail item list inquiry block 230 analyzes the body BODY of the inquiry request command and checks a query list having a detail inquiry field (S131). The detail item list inquiry block 230 receives a response to the inquiry request to the detail item database 220 for each detail inquiry field included in the query list (S132). The detailed item list inquiry block 220 creates a result list based on the at least one response (S133), and transmits a response message including the result list back to the terminal 10 (S134).

As a result, the terminal 10 receives the presence information for at least one detailed lookup field at a time.

5 is a database table XML_PS_DOC of a permanent presence management block according to an embodiment of the present invention.

Referring to FIG. 5, the entire XML document including the detail lookup field is stored in a DOC field of a BLOB type. That is, since the permanent presence management block 210 manages the document as one field in the database as an entire XML, it can include not only the detail query field but also other contents, so that the extension and flexibility of the XML document can be expected.

FIG. 6 is a field table (XML_STALK_IDX) generated by the persistent presence management block by parsing only detail lookup fields for transmission to a detail lookup database according to an embodiment of the present invention.

Referring to FIG. 6, when the permanent presence management block 210 receives a PUT command, a social network ID or email such as MDN, TWITTER, FACEBOOK, NATECONN or ME2DAY, etc. Check that the query list including the detail query fields (EMAIL) is in the body of the PUT command. If at least one detail lookup field is included in the query list, the persistent presence management block 210 parses the detail lookup field to create, update, or delete a table called XML_STALK_IDX including the item. The XML_STALK_IDX table may be generated for each subscriber and basically include a table for a subscriber URI, creation and update time items. However, the name of the table is not limited to the above embodiment and may be variously named according to the embodiment.

7 is an XCAP message for inputting the updated Twitter ID to the presence inquiry system through the XCAP interface.

The terminal 10 transmits the PIDF document including the detailed lookup field to be updated to the permanent presence management block 210. At this time, the PUT command includes a detailed lookup field to be entered in the subscriber's presence information. The XCAP message shown in FIG. 7 is a PUT command for inputting a Twitter ID having an ID of "kkkk" into a subscriber's presence information and detailed lookup field.

FIG. 8 is an XCAP message for updating the Twitter ID shown in FIG. 7 in a detailed query database according to an embodiment of the present invention.

The permanent presence management block 210 processes element input requests for PIDF documents. This is to update the PIDF document including the subscriber's full presence information. Afterwards, the permanent presence management block 210 parses only the detail lookup field of the PIDF document and inputs the XML_STALK_IDX table.

Referring to FIG. 8, the illustrated XCAP message is for updating by inputting the Twitter ID "kkkk" in the XML_STALK_IDX table of the detailed query database 220 of the subscriber whose URI (User_URI) is "sip: stalk001@sktims.net". will be.

FIG. 9 is a PIDF document including detailed lookup fields of a subscriber receiving a message shown in FIG. 8 and stored in a detail lookup database according to an embodiment of the present invention.

Referring to FIG. 9, the detailed lookup database 220 stores a PIDF document including a detailed lookup field for a subscriber whose subscriber URI (User_URI) is "sip: stalk001@sktims.net". As shown in FIG. 9, there are detailed search fields for a twitter id, a facebook id, a me2day id, and a nateconn id.

According to an embodiment, the detailed query database 220 may receive the message illustrated in FIG. 8, that is, the message of updating the Twitter ID, and update the Twitter ID to “kkkk” in the PIDF document of FIG. 9.

10 is an XCAP message sent by the terminal to query one or more other subscribers in the presence management system according to an embodiment of the present invention.

Referring to FIG. 10, the terminal 10 transmits an inquiry request including at least one other subscriber to a query list to the presence management system 200. The illustrated XCAP message is a POST command in which a subscriber whose subscriber URI is “sip: stalk001@sktims.net” requests a query to find a friend whose Twitter ID is “kkkk” and a friend whose Facebook ID is “def”. That is, the terminal 10 transmits the presence information of friends (other subscribers) who want to make an inquiry request to the presence management system 200 by including it in the query list.

FIG. 11 is an XCAP message that a detailed item list query block sends to a detailed query database according to an embodiment of the present invention. FIG. 12 is an XCAP message that a detailed item list inquiry block sends to a detailed query database according to an embodiment of the present invention.

11 to 12, the detailed item list inquiry block 230 analyzes the body of the POST command and includes a detailed query field when the detailed query field is included. The detailed inquiry database 220 is transmitted. At this time, an inquiry request is performed as many as the number of entries of the detail inquiry field included in the body of the POST command, and the detail item list inquiry block 230 receives a response as many as the inquiry request.

Referring to FIG. 11, the illustrated XCAP message is a message for requesting a search for a subscriber URI having a Twitter ID "kkkk" in the XML_STALK_IDX table of the detail query database 220. The detailed search database 220 finds the presence information of the subscriber having the Twitter ID "kkkk" and returns the subscriber URI (user_uri) "sip: stalk001@sktims.net" of the subscriber as a response.

Referring to FIG. 12, the illustrated XCAP message is a message for requesting inquiry of a subscriber URI having a Facebook ID "def" in the XML_STALK_IDX table of the detail query database 220. The detail query database 220 finds the presence information of the subscriber having the Facebook ID "def" and returns the subscriber's subscriber URI (user_uri) "sip: 01110001002@sktims.net" as a response.

That is, the detailed item list inquiry block 230 performs an inquiry request twice (the number of entries of the detail query field included in the body of the POST command, the Twitter ID "kkkk" and the Facebook ID "def"), and the details. The item list query block 230 receives two responses to the inquiry request (subscriber's subscriber URI (s): sip: stalk001@sktims.net and sip: 01110001002@sktims.net).

FIG. 13 is a POST response message generated by a detailed item list inquiry block according to an embodiment of the present invention to collect and send a response received from a detailed query database to a terminal.

The detail item inquiry list block 230 performs an inquiry request and receives a response, and analyzes a result value included in each response. The detail item inquiry list block 230 collects the subscriber URIs, which are the respective result values, creates a result list, and transmits the result list to the terminal by including it in the response message 200 OK.

Referring to FIG. 13, the detailed item inquiry list block 230 receives a response by inquiring at least one other subscriber as shown in FIGS. 11 through 12, and analyzes a result value of each response. . The detail item inquiry list block 230 collects all the analyzed result values and creates a result list showing the result values for each of the detail query fields (Twitter ID and Facebook ID). That is, the result list indicating that the subscriber URI is "sip: stalk001@sktims.net" for the Twitter ID "kkkk" and that the subscriber URI is "sip: 01110001002@sktims.net" for the Facebook ID "def". Generate and return to the terminal (10).

The detailed item list inquiry block 230, the permanent presence management block 210, or the detailed query database 220 according to an embodiment of the present invention may be implemented as a module. In the present specification, a module may mean hardware capable of performing functions and operations according to each name described in this specification, or computer program code capable of performing specific functions and operations. Or an electronic recording medium, for example, a processor, on which computer program code can perform specific functions and operations. In other words, a module may mean a functional and / or structural combination of hardware for performing the technical idea of the present invention and / or software for driving the hardware.

Presence field management method according to an embodiment of the present invention is implemented in the form of program instructions that can be executed by various computer means may be recorded on a computer readable medium. The computer readable medium may include program instructions, data files, data structures, etc. alone or in combination. The program instructions recorded on the medium may be those specially designed and constructed for the present invention or may be available to those skilled in the art of computer software. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tape, optical media such as CD-ROMs, DVDs, and magnetic disks such as floppy disks. Hardware devices specially configured to store and execute optical instructions and program instructions such as ROM, RAM, flash memory and the like. Examples of program instructions include machine code, such as produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter or the like. The hardware device described above may be configured to operate as one or more software modules to perform the operations of the present invention, and vice versa.

In practicing the present invention, the following OMA-AD-XDM-V2_0 (XDM Architecture), OMA-TS-XDM-Core (XDM Specification), RFC 4825 (The XCAP), RFC 3863 (Presence Information Data Format; PIDF) References herein It is hereby incorporated by reference.

Although the present invention has been described with reference to one embodiment shown in the drawings, this is merely exemplary, and those skilled in the art will understand that various modifications and equivalent other embodiments are possible therefrom. Therefore, the true technical protection scope of the present invention will be defined by the technical spirit of the appended claims.

10: terminal
20: XCAP server
30: Presence Server
100: Aggregate Proxy
200: Presence Management System
210: Permanent Presence Management Block
220: detailed search database
230: Detailed item list search block
1000: IMS Network

Claims (18)

A permanent presence management block for parsing only the detail lookup field of all the subscriber's fields in the PIDF document included in the operation instruction received from the aggregation proxy; And
Presence management system including a detailed query database for storing and managing only the detail query field parsed by the permanent presence management block. The method of claim 1, wherein the detail lookup field is
Presence management system which is at least one of ID, email, MDN and subscriber URI (User_URI) for each subscriber's social network service (SNS) as a field preset by the system administrator. The method of claim 2, wherein performing the operation
Presence management system that performs any one of creation, update, delete, and lookup. The method of claim 3, wherein the detailed query database
And performing a response corresponding to the command on the detailed inquiry field received from the permanent presence management block, and transmitting a response to the result of the operation to the presence management block. The method of claim 4, wherein the response to the operation performance result is
Presence management system, which is one of 1XX, 2XX, 3XX, 4XX, 5XX, and 6XX responses. The method of claim 5,
And a detailed item list query block for querying a detailed query field included in a body of an inquiry command received from the collective proxy and transmitting the item-specific query request to the database. The method of claim 6, wherein the database,
When the inquiry request is received from the detail item list inquiry block, the presence management system for inquiring a subscriber URI corresponding to the detail inquiry field and transmitting a response including the subscriber URI to the detail item list inquiry block. . The method of claim 7, wherein the detail item list lookup block,
A presence management system that collects the responses received from the database, creates a presence result list, and returns the presence result list to the aggregation proxy. In the presence field management method of the presence management system connected to the aggregation proxy and the presence server,
Receiving an operation execution command including a PIDF document from the aggregation proxy;
Parsing at least one detail lookup field among all fields of a subscriber of the PIDF document; And
Presence field management method comprising the step of transmitting an operation execution command for the parsed detail query field in the detail query database. 10. The method of claim 9, wherein the detail lookup field is
Presence field management method for the presence field, which is at least one of a social network service (SNS) ID, an email, an MDN, and a subscriber URI (User_URI) of each subscriber. 11. The method of claim 10, wherein the operation execution command
Presence field management method for performing any one of the creation, update, deletion and inquiry of the detail query field. The method of claim 11, wherein the managing in the database comprises:
And storing the detailed lookup field for each subscriber in the database when the operation execution command is a generation (PUT) command. The method of claim 11,
Receiving, by the database, the detail lookup field and performing an operation corresponding to the command; And
And returning a response to the result of performing the operation to the aggregation proxy. The method of claim 13, wherein the response to the operation performance result is
Presence field management method that is one of 1XX, 2XX, 3XX, 4XX, 5XX, and 6XX responses. 15. The method of claim 14,
Retrieving at least one detail query field included in the command when a POST command is received from the aggregation proxy; And
And transmitting a query to the database for each of the inquired detail query fields. 16. The method of claim 15,
The database receiving the inquiry request;
Querying the subscriber URI corresponding to each of the detail query fields included in the inquiry request; And
The presence field management method further comprising the step of returning by including in the response (response) for each inquired subscriber URI. The method of claim 16,
Receiving each response and creating a presence result list including the subscriber URI and the detailed lookup field; And
And transmitting the presence result list to the aggregation proxy. The method according to any one of claims 9 to 17,
And recording and implementing the presence field management method in a program instruction form that can be executed by various computer means.

Images