U.S. patent application number 12/593533 was filed with the patent office on 2010-05-06 for system and method for the solicitation of presence information from presence source.
Invention is credited to Wuk Kim, Jae-Kwon Oh.
Application Number | 20100115112 12/593533 |
Document ID | / |
Family ID | 39808446 |
Filed Date | 2010-05-06 |
United States Patent
Application |
20100115112 |
Kind Code |
A1 |
Oh; Jae-Kwon ; et
al. |
May 6, 2010 |
SYSTEM AND METHOD FOR THE SOLICITATION OF PRESENCE INFORMATION FROM
PRESENCE SOURCE
Abstract
Disclosed is a system and method for directly requesting and
receiving presence information from a presence source. The system
for providing a presence service, which includes a presence source
which stores presence information about at least one presentity,
previously registers presence information elements, which the
present source can publish, in a SIP/IP (Session Initiation
Protocol/Internet Protocol) core in accordance with corresponding
each media feature tag value, and publishes presence information
according to media feature tag values when specific presence
information is requested; a SIP/IP core which allows presence
information elements registered by the presence source to each
media feature tag value so as to store the presence information
elements, allows the media feature tag value described in the
message to correspond to a previously registered media feature tab
value of the presence source so as to identify a presence source to
which the message for requesting the presence information will be
published when the SIP/IP core receives the presence information
from the presence server, and transmits the message for requesting
the presence information to corresponding presence source; and a
presence server, which allows a media feature tag value regarding
the corresponding presence information to be included in the
message for requesting presence information so as to request
specific presence information from the presence source, and then
transmits the message for requesting presence information, which
selectively includes a publication rule regarding corresponding
presence information of the corresponding source.
Inventors: |
Oh; Jae-Kwon; (Seoul,
KR) ; Kim; Wuk; (Gyeonggi-do, KR) |
Correspondence
Address: |
THE FARRELL LAW FIRM, LLP
290 Broadhollow Road, Suite 210E
Melville
NY
11747
US
|
Family ID: |
39808446 |
Appl. No.: |
12/593533 |
Filed: |
March 27, 2008 |
PCT Filed: |
March 27, 2008 |
PCT NO: |
PCT/KR2008/001722 |
371 Date: |
September 28, 2009 |
Current U.S.
Class: |
709/228 |
Current CPC
Class: |
H04L 51/043 20130101;
H04L 67/24 20130101; H04L 65/1006 20130101; H04W 4/02 20130101 |
Class at
Publication: |
709/228 |
International
Class: |
G06F 15/16 20060101
G06F015/16 |
Foreign Application Data
Date |
Code |
Application Number |
Mar 29, 2007 |
KR |
10-2007-0031186 |
Claims
1. A system for directly requesting presence information from a
presence source, comprising: a presence source which stores
presence information about at least one presentity, previously
register the presence information elements, which the presence
source can publish, in a SIP/IP (Session Initiation
Protocol/Internet Protocol) core in accordance with each
corresponding each media feature tag value, and publishes presence
information according to the media feature tag value when specific
presence information is requested; the SIP/IP core for storing the
presence information elements in accordance with (based on)
corresponding media feature tag values registered by the presence
source a presence server transmitting a message for requesting
specific presence information so as to request the specific
presence information from the presence source.
2. The system as claimed in claim 2, wherein the media feature tag
value is a value showing each presence information element, which
the presence source can publish, or presence information
publication capability of the presence source.
3. The system as claimed in claim 1, wherein the presence source
stores pieces of presence information about one presentity and
allows the information publication capability thereof to correspond
to a media feature tag value so as to previously register the
information publication capability in the SIP/IP core.
4. The system as claimed in claim 3, wherein, when a request for
registration of the media feature tag value is received from the
presence source, the SIP/IP core stores the received request.
5. The system as claimed in claim 1, wherein the presence server
allows the media feature tag value regarding corresponding presence
information to be included in the message and then transmits the
message for requesting presence information.
6. The system as claimed in claim 5, wherein the presence server
allows a publication rule showing a scheme for publishing
corresponding presence information by the presence source to be
selectively included in the message for requesting presence
information and transmits the message.
7. The system as claimed in claim 1, wherein when the SIP/IP core
receives the message for requesting presence information from the
presence server, the SIP/IP core allows the media feature tag value
described within the message to correspond to a previously
registered media feature tag value of the presence source so as to
identify a presence source to which the message for requesting
presence information is published, and transmits the message for
requesting presence information to the corresponding presence
source.
8. The system as claimed in claim 1, wherein when the presence
source receives the message for requesting presence information,
the presence source publishes corresponding information to the
presence server.
9. The system as claimed in claim 8, when the presence source
receives the message for requesting presence information, which
includes a publication rule, the presence source publishes
corresponding presence information to the presence server according
to the publication rule.
10. The system as claimed in claim 9, wherein the publication rule
can at least describe when the presence source publishes presence
information about a corresponding presentity, whether the presence
source publishes presence information whenever corresponding
information is updated, whether the presence source immediately
publishes a present state regardless of updating, or in which
period the presence source publishes corresponding information,
etc., or describe accuracy of presence information to be published
or until when a corresponding rule is valid.
11. The system as claimed in claim 9, wherein the publication rule
can describe that all existing publication rules of the presence
source are cancelled.
12. The system as claimed in claim 1, wherein the message for
requesting presence information is one among SIP REFER, SIP
MESSAGE, and SIP PUBLISH.
13. The system as claimed in claim 1, further comprising a watcher
transmitting the message for requesting presence information, which
includes a notification rule, wherein when the presence server
receives specific presence information and a request for a
notification rule regarding the presence information from the
watcher, the presence server transmits a message for requesting
presence information, which includes a publication rule allowing a
corresponding source to publish corresponding presence information
according to the notification rule, to the presence source, and
wherein corresponding presence information is published from the
presence source to the present server according to the message for
requesting presence information, and the presence server notifies
the watcher of the corresponding presence information in accordance
with the notification rule described in the message for requesting
presence information from the watcher.
14. The system as claimed in claim 13, wherein the notification
rule can describe at least a scheme for publishing the
corresponding presence information in a predetermined period or a
scheme for publishing a current snapshot of the corresponding
presence information.
15. The system as claimed in claim 13, wherein the presence server
allows the publication rule showing a requested publication scheme
to be included in the message for requesting presence information
so as to transmit the message.
16. The system as claimed in claim 15, wherein when the presence
source receives the message for requesting presence information,
which includes the publication rule, the presence source publishes
corresponding information to the presence server according to the
publication rule.
17. A method for directly requesting presence information from a
present source in a system for providing a presence service, which
includes a presence source storing pieces of presence information
about at least one presentity, a watcher who is a user receiving
the presence information, a presence server for publishing presence
information to the watcher, and a SIP/IP (Session Initiation
Protocol/Internet Protocol) core, which is a communication channel
between the presence source, the watcher, and the presence server,
the method comprising the steps of: previously registering, by the
presence source, the presence information elements in the SIP/IP
core, which the presence source can publish, in accordance with
corresponding correspond to each media feature tab value; allowing,
by the presence server, the media feature tag value regarding
corresponding presence information to be included in a message for
requesting presence information so as to request specific presence
information from the presence source, and transmitting the message
for requesting presence information, which electively includes a
publication rule regarding corresponding presence information of a
corresponding source, and identifying a presence source to which
the message for requesting presence information will be published
and transmitting the message for requesting presence information to
the presence source when the SIP/IP core receives the message for
requesting presence information from the presence server; and
publishing presence information according to the media feature tag
value included in the message for requesting presence information
when the presence source receives the message for requesting
presence information.
18. The method as claimed in claim 17, wherein the media feature
tag value is a value showing each presence information element
which the presence source can publish or presence information
publication capability of the presence source.
19. The method as claimed in claim 17, wherein the step of
registering is a step where the presence source stores presence
information about one presentity, and previously registers the
presence information publication capability in the SIP/IP core in
accordance with corresponding media feature tag value.
20. The method as claimed in claim 19, where the step of
registering is a step of storing a request for registration when
the SIP/IP core receives the request for registration of the media
feature tag value from the presence source.
21. The method as claimed in claim 17, wherein the step where the
presence server transmits the message for requesting presence
information is a step where the presence server allows the media
feature tag value regarding corresponding presence information to
be included in the message for requesting presence information, and
then transmits the message.
22. The method as claimed in claim 21, wherein the step where the
presence server transmits the message for requesting presence
information is a step where the presence server allows the
publication rule showing a scheme for publishing corresponding
presence information to be selectively included in the message for
requesting presence information and then transmits the message.
23. The method as claimed in claim 17, wherein the step where the
SIP/IP core transmits the message for requesting presence
information to a corresponding presence source is a step where the
SIP/IP core allows the media feature tag value described in the
message to correspond to a previously registered media feature tag
value of the presence source so as to identify a presence source to
which the message for requesting presence information will be
published, and transmits the message for requesting presence
information to the corresponding presence source when the SIP/IP
core receives the message for requesting presence information from
the presence server.
24. The method as claimed in claim 17, wherein the step where the
presence source publishes the presence information is a step where
the presence source publishes a corresponding information to the
presence server when the presence source receives the message for
requesting presence information.
25. The method as claimed in claim 24, wherein the step where the
presence source publishes the presence information is a step where
the presence source publishes corresponding presence information to
the presence server according to the publication rule when the
presence source receives the message for requesting presence
information including the publication rule.
26. The method as claimed in claim 25, wherein the publication rule
can describe at least one of when the presence source publishes
presence information about the corresponding presentity, whether
the presence source publishes presence information whenever
corresponding information is updated, whether the presence source
immediately publishes a present state regardless of updating, or in
which period the presence source publishes corresponding
information, etc., or can describe at least one of accuracy of
presence information to be published or until when a corresponding
rule is valid.
27. The method as claimed in claim 25, where the publication rule
can describe that all exiting publication rules of the presence
source are cancelled.
28. The method as claimed in claim 17, wherein the message for
requesting presence information is one message among SIP REFER, SIP
MESSAGE, and SIP PUBLISH.
29. The method as claimed in claim 17, further comprising the steps
of transmitting, by the watcher, the message for requesting
presence information, which includes the notification rule;
transmitting, by the presence server, the message for requesting
presence information, which includes the publication rule allowing
a corresponding source to publish corresponding presence
information according to the notification rule, to the presence
source when the presence server receives the request for specific
presence information and the notification rule regarding the
presence information from the watcher; and notifying the watcher of
the corresponding presence information according to the
notification rule described in the message for requesting presence
information from the watcher when the corresponding presence
information is published from the presence source to the presence
server according to the message for requesting presence
information.
30. The method as claimed in claim 29, wherein the notification
rule can describe at least a scheme for notifying corresponding
presence information in a predetermined period or a scheme for
notifying a current snapshot of corresponding presence
information.
31. The method as claimed in claim 29, wherein the presence server,
transmits the message for requesting presence information to the
presence source after receiving a request for specific presence
information and the notification rule regarding the presence
information from the watcher, and the presence server transmits the
message for requesting presence information, which includes the
publication rule showing a requested notification scheme
32. The method as claimed in claim 31, further comprising the step
of publishing, by the presence source, corresponding presence
information to the presence server according to the publication
rule when the presence source receives the message for requesting
presence information, which includes the publication rule.
Description
BACKGROUND OF THE INVENTION
[0001] 1. Field of the Invention
[0002] The present invention relates to a system and a method for
providing a presence service, and more particularly to a system and
a method for directly requesting and receiving presence information
from a presence source.
[0003] 2. Description of the Related Art
[0004] In general, a presence service refers to a service for
properly notifying a series of objects interested in a certain
subject of concern, such as a user or a group, of information
regarding a current state of communication of the subject, through
a series of devices. Based on published state information about a
subject of concern, the series of objects can understand a current
situation of communication about the subject of concern, and can
also select a communication means, which is optimized, i.e. has the
highest probability of success, at a desired time so as to try to
make contact with the subject of concern. At this time, a user
which is a subject to be observed refers to a presentity,
communication state about the user refers to presence information,
and a user who receives the information refers to a watcher.
[0005] With reference to FIG. 1, a simplified architecture of a
presence service is shown. A subject of concern in the presence
service refers to a presentity, and presence sources 120 collect
information regarding the presentity, i.e. presence information,
and publishes the information to a presence server 110. The
presence server 110 composes pieces of presence information,
generates aggregated presence information about the presentity, and
notifies objects interested in the presentity, i.e. watchers 100,
of the aggregated presence information.
[0006] A signal flow between such functional entities of the
presence server will be described with reference to FIG. 2.
[0007] Whenever presence information of a presentity is changed,
the presence source 120 publishes changed presence information to
the presence server 110 by using SIP (Session Initiation Protocol)
PUBLISH, which is defined in "RFC3903 "SIP Extension for Event
State Publication"", through a SIP/IP (Session Initiation
Protocol/Internet Protocol) core 140. Then, the presence server 110
composes many pieces of presence information published from the
presence source 120 into one piece of presence information so as to
maintain the latest presence information about the presentity. Such
a step where the presence source 120 publishes changed presence
information to the presence server 110 by using SIP PUBLISH
according to the change of presence information may be illustrated
in steps 200, 203, 212, and 215.
[0008] Meanwhile, in a case where a watcher 100 requests presence
information about a corresponding presentity from the presence
server 110 according to presence event package defined in "RFC3856
"A Presence Event Package for the SIP"", the presence server 110
notifies the watcher 100 of the requested presence information by
using SIP NOTIFY through SIP/IP core 140. Also, a step of
notifying, by the presence server 110, the watcher 100 of presence
information about a presentity by using SIP NOTIFY may be
illustrated in steps 208 to 211.
[0009] Also, in a case where the presence source 120 publishes
changed presence information to the presence server 110 by using
SIP PUBLISH according to change of presence information in steps
212 to 215, the presence server 110 notifies the watcher 100 of the
presence information by using SIP NOTIFY through steps 216 to 219.
Particularly, the presence server 110 notifies the watcher 100 of
the latest presence information by using SIP NOTIFY whenever
presence information about a corresponding presentity is
changed.
[0010] In the case of FIG. 2, the presence server 110 collects
presence information about the presentity only when the presence
source 120 publishes the presence information thereto.
Particularly, collection of presence information about a presentity
in the presence server 110 is entirely up to voluntary publication
performed by the presence source 120.
[0011] In order to complement this, a method for allowing the
presence server 110 to directly request information publication
from the presence source 120 by using SIP REFER defined in "RFC3515
"The SIP REFER Method"".
[0012] As such, the flow of a signal for allowing the presence
server 110 to directly request the presence source 120 to publish
presence information will be described with reference to FIG. 3.
Firstly, a step where the presence source 120 publishes changed
presence information to the presence server 110 by the can be
illustrated in steps 300 to 303.
[0013] Then, when the watcher 100 requests presence information
about a corresponding presentity from the presence server 110 by
using SIP SUBSCRIBE, the presence server 110 notifies the watcher
100 of the presence information about the presentity according to
the request. A step of requesting presence information of a
presentity and a step of publishing presence information according
to the request may be illustrated in steps 304 to 311.
[0014] Meanwhile, the presence server 110 requests presence
information from the presence source 120 by using SIP REFER.
According to the request, the presence source 120 publishes the
requested presence information to the presence server 110 by using
SIP PUBLISH. Accordingly, the presence server 110 updates presence
information about the corresponding presentity and notifies the
watcher 100 of the presence information by using SIP NOTIFY. As
such, a step where the presence server 110 directly requests
presence information about a presentity from the presence source
120, and after receiving presence information, notifies the watcher
100 of the presence information will be described in the same
manner as steps 312 to 323.
[0015] As described above, in the prior art, in order to improve a
problem in that collection of presence information about a
presentity in the presence server 110 has no choice but to be
entirely up to voluntary publication performed by the presence
source 120, such a manner that the presence server 110 directly
requests presence information about a presentity from the presence
source 120, receives the presence information, and notifies the
watcher 100 of the presence information has been developed.
[0016] However, the prior art discloses only the fact that the
presence server 110 directly requests presence information about a
presentity from presence source 120, receives presence information,
and notifies the watcher of the presence information as shown in
FIG. 3. But, the prior art does not disclose how the presence
server 110 identifies a specific presence source and routes SIP
REFER requesting presence information about a corresponding
presentity to a corresponding presence source 120 through the
SIP/IP core 140.
[0017] Also, in the above described method as shown in FIG. 3, only
the fact that the presence server 110 requests presence information
about a corresponding presentity from the presence source is
described, and how the presence source 120 publishes the
corresponding presence information is not described.
[0018] Also, in the method as shown in FIG. 3, where presence
server 110 requests presence information from the presence source
120 is not described.
SUMMARY OF THE INVENTION
[0019] Accordingly, the present invention has been made to solve
the above-mentioned problems occurring in the prior art, and the
present invention provides a presence system and method for
directly requesting and receiving presence information from a
presence source.
[0020] In accordance with an aspect of the present invention, there
is provided a system for providing a presence service, which
includes a presence source which stores presence information about
at least one presentity, previously registers presence information
elements, which the present source can publish, in a SIP/IP
(Session Initiation Protocol/Internet Protocol) core in accordance
with corresponding each media feature tag value, and publishes
presence information according to media feature tag values when
specific presence information is requested; a SIP/IP core which
allows presence information elements registered by the presence
source to each media feature tag value so as to store the presence
information elements, allows the media feature tag value described
in the message to correspond to a previously registered media
feature tab value of the presence source so as to identify a
presence source to which the message for requesting the presence
information will be published when the SIP/IP core receives the
presence information from the presence server, and transmits the
message for requesting the presence information to corresponding
presence source; and a presence server, which allows a media
feature tag value regarding the corresponding presence information
to be included in the message for requesting presence information
so as to request specific presence information from the presence
source, and then transmits the message for requesting presence
information, which selectively includes a publication rule
regarding corresponding presence information of the corresponding
source.
[0021] In accordance with another aspect of the present invention,
there is provided a method for directly requesting presence
information from a present source in a system for providing a
presence service, which includes a presence source storing pieces
of presence information about at least one presentity, a watcher
who is a user receiving the presence information, a presence server
for publishing presence information to the watcher, and a SIP/IP
(Session Initiation Protocol/Internet Protocol) core ,which is a
communication channel between the presence source, the watcher, and
the presence server, the method comprising the steps of previously
registering, by the presence source, the presence information
elements in the SIP/IP core, which the presence source can publish,
in accordance with corresponding correspond to each media feature
tab value; allowing, by the presence server, the media feature tag
value regarding corresponding presence information to be included
in a message for requesting presence information so as to request
specific presence information from the presence source, and
transmitting the message for requesting presence information, which
electively includes a publication rule regarding corresponding
presence information of a corresponding source, and identifying a
presence source to which the message for requesting presence
information will be published while the media feature tag value
corresponds to a previously registered media feature tag value, and
transmitting the message for requesting presence information to the
corresponding presence source when the SIP/IP core receives the
message for requesting presence information from the presence
server; and publishing presence information according to the media
feature tag valued included in the message for requesting presence
information when the presence source receives the message for
requesting presence information; and publishing corresponding
information according to a method for publishing presence
information in a case where the method is in included in the
message for requesting presence information.
[0022] Also, the present invention provides a system for providing
presence service, which includes a watcher which requests specific
presence information from the presence server and transmits a
message requesting presence information, which includes a
notification rule describing a notification rule where the presence
server selectively notifies the watcher of corresponding presence
information; and; the presence server which allows a media feature
tag value regarding corresponding presence information when the a
request for presence information of the watcher and a method of
notifying presence information are received, transmitting the
message requesting presence information, which selectively includes
a method of publishing presence information of a corresponding
source, to the presence source according to the method, notifying
corresponding presence information to the watcher according to the
notification rule described in the message requesting presence
information from the watcher when the corresponding presence
information is published from the presence source according to the
requested method.
[0023] A method for requesting presence information from a presence
sever in a system for providing a presence service, which includes
a watcher as a user who requests presence information from a
presence server and receives it according to a requested method,
and a presence server which receives requested presence information
from a presence source and notifies the presence information to the
watcher according a requested method, the method including the
steps of transmitting a message requesting presence information,
which includes desired presence information and selectively
includes a notification rule describing a rule of notifying
presence information to the watcher; allowing, the presence server,
a specific presence information of the watcher, which is included
in the message requesting presence information and a media feature
tag value regarding the corresponding presence information
according to the notification rule to be included when the message
requesting presence information is published from the watcher to
the presence server; transmitting the message requesting presence
information, which selectively includes a notification rule
regarding corresponding presence information of a corresponding
presence source describing a rule of notifying presence information
to the watcher to the presence source according to the described
notification method; and notifying the presence information to the
watcher according to the notification rule described in the message
requesting presence information from the watcher when the presence
source receives requested presence information according to a
method requested from the presence source.
BRIEF DESCRIPTION OF THE DRAWINGS
[0024] The above and other aspects, features and advantages of the
present invention will be more apparent from the following detailed
description taken in conjunction with the accompanying drawings, in
which:
[0025] The above and other aspects, features and advantages of the
present invention will be more apparent from the following detailed
description taken in conjunction with the accompanying drawings, in
which:
[0026] FIG. 1 is a view illustrating an architecture implementing a
typical presence service;
[0027] FIG. 2 is a flow chart of a signal for requesting and
providing typical presence information;
[0028] FIG. 3 is a flow chart illustrating a procedure where a
conventional presence server requesting presence information from a
presence source;
[0029] FIG. 4 is a flow chart of improved signals for allowing a
presence server to request presence information from a presence
source and for regulating the way the presence source publishing
presence information according to an embodiment of the present
invention;
[0030] FIG. 5 is a view illustrating a message format used when a
presence source registers presence information publication
capability thereof according to an embodiment of the present
invention;
[0031] FIG. 6 is a view illustrating a message format used when a
presence server requests presence information from presence source
according to an embodiment of the present invention;
[0032] FIGS. 7a to 7c are views illustrating a message format used
when a presence server requests presence information from a
presence source, and also requests a publication rule about
presence information of the presence source according to an
embodiment of the present invention;
[0033] FIGS. 8a and 8b are views illustrating a SIP message format
and a SIP PUBLISH format, which are used when a presence server
requests presence information from a presence source according to
an embodiment of the present invention;
[0034] FIG. 9 is a view illustrating a procedure where a watcher
requests a scheme for notifying presence information from a
presence server according to an embodiment of the present
invention;
[0035] FIG. 10 is a view illustrating a procedure where a watcher
requests a presence server to periodically notify the watcher of
presence information according to an embodiment of the present
invention;
[0036] FIG. 11 is a view illustrating a message format used when
the watcher requests the presence server to periodically notify the
watcher of presence information as shown in FIG. 10 according to an
embodiment of the present invention;
[0037] FIG. 12 is a view illustrating a procedure where a watcher
requests a presence server to notify a watcher of a snapshot of
presence information according to an embodiment of the present
invention; and
[0038] FIG. 13 is a view illustrating a message format used when
the watcher requests the presence server to notify the watcher of
the snapshot of presence information as shown in FIG. 12.
DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENT
[0039] The present invention provides a scheme for making it
possible that a presence server identifies a specific presence
source and performs SIP routing to an identified presence source.
Also, according to the present invention, a presence source
previously registers its own presence information publication
capability in a SIP/IP core by using a media feature tag suggested
in the present invention according to a method described in
"RFC3840 "Indicating User Agent Capabilities in the SIP"". The
presence server allows a media feature tag suggested in the present
invention to be included a accept-contact SIP header by using a
method described in "RFC3841 "Caller Preferences for the SIP"", so
that the presence server suggests that SIP REFER for requesting a
specific presence information be routed to a presence source in
charge of publication of a corresponding presence information
through the SIP/IP core.
[0040] FIG. 4 is a signal flow showings a procedure where the
present server requests presence information from the presence
source according to an embodiment of the present invention.
[0041] The present invention suggests that a new media feature tag
for showing presence information publication capability of the
presence source 430 be used according to "RFC3840 "Indicating User
Agent Capabilities in the SIP"". Also, in the present invention,
the new media feature tag is named as "+g.presence.publish". Also,
in the present invention, the presence source 430 arrays presence
information elements which can be published by using the value of
such a media feature tag so that the presence source 430 suggests
that its own presence information publication capability be
registered in the SIP/IP core 420. Particularly, pieces of presence
information, which can be published, are constituted of presence
information elements and correspond to each media feature tag value
so as to be registered in the SIP/IP core 420.
[0042] The presence source 430, which has its own presence
information publication capability registered in the SIP/IP core
420, shows a request for presence information from the presence
server 410 can be processed by a media feature tag having a name
equal to "+g.presence.publish", and shows which kind of presence
information elements can be published by media feature values tag
having a name equal to "+g.presence.publish". As such, it can be
performed through steps 10 and 11 that the presence source 430
registers presence information publication capability in the SIP/IP
core 420 by using a media feature tag.
[0043] For example, FIG. 5 shows an example of a message for
registering a capability, of which the presence source 430 capable
of publishing location information can publish presence information
about the location of a presentity addressed
"sip:brian@example.com", in the SIP/IP core 420 by means of a
method suggested in the present invention.
[0044] Meanwhile, through steps 12 to 15, the presence source 430
publishes changed presence information to the presence server 410
through the SIP/IP core 420 according to the change of presence
information. Then, when the watcher 400 requests presence
information about a corresponding presentity from the presence
server 410 by means of SIP SUBSCRIBE through steps 16 to 23, the
presence serer 410 notifies the watcher 400 of presence information
about the corresponding presentity through the SIP/IP core 420
according to the request.
[0045] Also, in the present invention, it is suggested that request
for specific presence information about a specific presentity be
published to the presence source 430 in charge of publication of
presence information by using an accept-contact SIP header defined
in "RFC3840 "Indicating User Agent Capabilities in the SIP"".
Particularly, the presence server 410 requests presence information
in such a manner that a media feature tag, such as the above
defined "+g.presence.publish", and the kind of presence information
to be requested, are clearly described as the value of the
accept-contact SIP header so that the presence server 410 allows
the SIP/IP core 420 to publish the request to the present source
430 which can accomplish it. It can be performed in steps 24 to 27
that specific presence information about a specific presentity is
requested.
[0046] For example, FIG. 6 shows an example of a message used when
the presence server 410 requests presence information about the
location of a presentity addressed "sip:brian@example.com" in such
a manner the presence server 410 allows
"*;+g.presence.publish="location";require;explicit" to be included
in the accept-contact SIP header suggested in the present invention
of SIP REFER.
[0047] Then, the SIP/IP core 420, which has received the SIP REFER,
which is a message for requesting presence information about a
specific presentity as shown in FIG. 6, performs publication of
presence information about the location of the presentity addressed
"sip:brian@example.com" with a reference described in the
accept-contact SIP header, and identifies the presence source, in
which presence information publication capability is registered as
described above, and publishes corresponding SIP REFER to the
presence source 430. In FIG. 6, "require" and "explicit" are used
in a matching rule described in "RFC3840 "Indicating User Agent
Capabilities in the SIP"", and shows the fact that only the
presence source, in which presence information publication
capability of "+g.presence.publish="location"" has been registered,
will be matched so as to be identified. Also, according to the
preference of the presence server 410, other kinds of matching
rules described in "RFC3840 "Indicating User Agent Capabilities in
the SIP"" can be used.
[0048] The presence source 430, to which the message for requesting
presence information about the specific presentity has been
published as described above, transmits the requested presence
information to the presence server 410 by using SIP PUBLISH through
the SIP/IP core 420. As such, it can be performed in steps 28 to 31
that the presence source 430 transmits the requested presence
information to the presence server 410 by using the SIP
PUBLISH.
[0049] As shown in steps 24 and 25 of FIG. 4, in the present
invention, the presence server 410 suggests that it can publish a
publication rule for controlling publication operation of the
presence source 430 together with a request for presence
information from the presence source 430. The presence source 430
suggests that presence information be published according to the
requested publication rule.
[0050] Then, it is suggested that such a publication rule for
controlling a request for presence information and publication
operation of the presence source 430 may include contents as
described below.
[0051] Firstly, it may be described when the presence source 430
publishes presence information about a corresponding presentity,
i.e. whether the presence source 430 publishes presence information
whenever a corresponding information is updated, whether the
presence source 430 immediately publishes the presence state
regardless of updating, or whether the presence source periodically
publishes a corresponding information, etc. Also, in a case of
periodical publication, it has to be described in which cycle the
corresponding information is published.
[0052] Secondly, accuracy of presence information to be published
may be described. For example, in a case of location information,
it may be described in which degree of accuracy location
information is published. For example, it may be described that
location information is published accurately with a dimension of
100 m. Thirdly, it may be described until when a corresponding rule
is valid.
[0053] The above described contents can be included in a message
for requesting for presence information so as to be transmitted.
Also, if there is rule information for another kind of publication
additionally to the above described contents, corresponding
information can be included according to necessity.
[0054] Also, such publication rules in a type of XML can be
included in a body of a SIP request for presence information
described above, and "application/publication-rule+xml" can be used
as a MIME type of such a publication rule.
[0055] For example, with reference to FIGS. 7a to 7c, examples
where a publication rule is described together with a request for
presence information from the presence source 430 by using the
above described SIP REFER are shown.
[0056] Above all, FIG. 7a shows a message requesting the presence
source 430, which publishes location information of the presentity
addressed "sip:brian@example.com", to periodically publish a
corresponding information per ten minutes until 08:00 UTC+9, Dec.
4, 2007. This message is described with the "10" value of a child
element of a <publication_rule> root element, the "periodic"
value of "method" attribute of a <trigger> child element, and
the "2007-12-04T08:00+09:00" value of "till" attribute of a
<valid> child element.
[0057] FIG. 7b shows a message requesting the presence source 430,
which publishes location information of the "sip:brian@example.com"
presentity, to publish corresponding information whenever new
update occurs and for requesting continuous validity of such a
rule. This message is described with the "new" value of "method"
attribute of a <trigger> child element of a
<publication_rule> root element and an empty <valid>
child element.
[0058] Finally, FIG. 7c shows a message requesting the presence
source 430, which publishes location information of the
"sip:brian@example.com" presentity, to cancel all existing
publication rules regarding presence information about
"sip:brian@example.com" presentity. This is described with an empty
<cancel> element of a <publication_rule> root element.
If the presence source 430 receives such a message shown in FIG.
7c, the presence source 430 deletes all existing publication rules
and then publishes presence information according to a default
publication rule which has been previously set. In most cases,
according to the default publication rule, which has been
previously set, the presence source 430 publishes presence
information whenever an update of presence information about a
corresponding presentity occurs.
[0059] Also, in steps 24 and 25 of FIG. 4 according to the present
invention, the presence server 410 suggests that when there is a
request for presence information about a specific presentity from
the presence source 430, it is possible to use a SIP MESSAGE
defined in "RFC3428 "Session Initiation Protocol (SIP) Extension
for Instant Messaging"" or SIP PUBLISH defined in "RFC3903 "Session
Initiation Protocol (SIP) Extension for Event State Publication""
in addition to such SIP REFER.
[0060] If presence information is requested by using the SIP
MESSAGE or the SIP PUBLISH, equally to the above described SIP
REFER, a routing technique is applied to the presence source 430 by
using a media feature tag of the accept-contact SIP header. At this
time, the above described publication rule is also described. There
is a difference in comparison with the SIP REFER, in which a
description of a publication rule is optional.
[0061] Above all, FIG. 8a shows an example of a SIP MESSAGE
transmitted in a case where presence information is requested by
using the SIP MESSAGE will be described. FIG. 8a shows a message
for requesting the presence source 430, which publishes location
information of "sip:brian@example.com" presentity, to publish
present location information of the "sip:brian@example.com"
presentity by using a SIP MESSAGE and a publication rule. This
message is described with the "current" value of "method" attribute
of the <trigger> child element of the <publication
rule> root element.
[0062] Then, with reference to FIG. 8b, an example of a SIP PUBLISH
transmitted in a case where there is a request for presence
information by using the SIP PUBLISH will be described below. FIG.
8b shows a message for requesting the presence source 430, which
publishes location information of the "sip:brian@example.com"
presentity, to publish present location information of the
"sip:brian@example.com" presentity by using a SIP PUBLISH and a
Publication Rule. This is described with the "current" value of
"method"attribute of the <trigger> child element of the
<publication_rule> root element
[0063] As described above, in FIG. 4, the presence server 410
allows a publication rule regarding presence information to be
included in a message for requesting presence information, and
transmits the message to the presence source 430 through the SIP/IP
core 420. As such, is can be triggered due to various situations
that the presence server 410 suggested by the present invention
requests presence information from the presence source 430.
[0064] In the present invention, among methods for triggering the
operation of the presence server 410, which requests presence
information from the presence source 430, a case where the watcher
400 requests the presence server 410 to notify presence information
of a specific presentity according to a specific method is
suggested. As an example of this, there may be a case where the
watcher 400 requests the presence server 410 to periodically notify
the watcher of presence information about a specific presentity,
and a case where the watcher 400 requests the presence server 410
to notify the watcher of a present snapshot of the presence
information about a specific presentity.
[0065] Firstly, with reference to FIG. 9, it is suggested that the
watcher 400 describes such a notification method as a notification
rule, transmits it to the presence server 410, and requests it from
the presence server 410.
[0066] Firstly, steps 900 and 911 are procedures equal to steps 10
and 11 in FIG. 4, in which the presence source 430 registers a
presence information publication capability in the SIP/IP core 420
by using a media feature tag.
[0067] Also, steps 902 to 905 are procedures equal to steps 12 to
15 in FIG. 4, which are described above, in which the presence
source 430 publishes presence information to the presence server
410 according to change of presence information.
[0068] In the present invention, in order to describe a
notification rule, it is suggested that the watcher 400 expands
filter description defined in "RFC4660 "Functional Description for
Event Notification Filtering"" so as to use it According to
"RFC4660 "Functional Description for Event Notification
Filtering"", the watcher 400 can describe that filter description
is included when a present event package using SIP SUBSCRIBE is
requested, and presence information of specific part described in
"<what> element" of filter description is notified. Also, the
watcher 400 can describe that corresponding presence information is
notified to the watcher in a case how contents of presence
information of a specific part was changed according to a method
described in "<trigger> element" of filter description. In
the present invention, it is suggested that through expansion of
the "<trigger> element" of such filter description, the
watcher 400 describes that the watcher 400 periodically requests a
corresponding presence information, or requests a snapshot of the
presence information, and this description is included in SIP
SUBSCRIBE to be published to the presence server 410. Hereinafter,
a case where the watcher 400 periodically requests corresponding
presence information from the presence server 410, and the presence
server 410 periodically requests presence information from the
presence source 430, will be described with reference to FIG. 10.
Also, a case where the watcher 400 requests the presence server 410
to notify a present snapshot, and the presence server 410 requests
a snapshot from the presence source 430 will be described with
reference to FIG. 12.
[0069] As such, a procedure where the watcher 400 allows
information about a notification rule regarding the presence
information notification to be included in a request when the
watcher 400 requests presence information and transmits the request
to the presence server 410 can be shown in steps 906 to 910. Also,
the presence server 410 notifies the watcher 400 of presence
information according to the notification rule requested through
steps 911 to 914 and steps 923 to 926.
[0070] Then, according to the method described in steps 24 to 27 of
FIG. 4, the presence server 410, which receives such a notification
request from the watcher 400, can request the presence source 430
to publish a specific presence information according to the request
by means of a method described in a publication rule. A procedure
where the presence server 410 publishes SIP REFER, which is a
message for requesting presence information, including a
publication rule, and receives a corresponding response is the same
manner as steps 915 to 918.
[0071] Then, the presence source 430 publishes a corresponding
presence information to the presence server 410 according to the
publication rule requested through steps 919 to 922.
[0072] After this, through steps 923 to 926, the presence source
430 notifies the watcher 400 of presence information received from
the presence source 430 according to the notification rule.
[0073] Then, examples of signal flow and a message, which allow the
watcher 400 to request that specific presence information be
periodically notified to the watcher 400 by using filter
description according to a method provided by the present
invention, will be described with reference to FIGS. 10 and 11.
[0074] Firstly, steps 1050 and 1051 are procedures equal to steps
10 and 11 in FIG. 4, and are procedures where the presence source
430 registers presence information publication capability in the
SIP/IP core 420 by using a media feature tag.
[0075] Also, steps 1052 to 1055 are procedures equal to steps 12 to
15 in FIG. 4, and are procedures where the presence source 430
publishes presence information to the presence server 410 according
to the change of presence information.
[0076] After this, according to an embodiment of the present
invention, the watcher 400 describes the fact that the watcher 400
periodically requests corresponding presence information by using a
filter description, allows the description to be included in SIP
SUBSCRIBE, and publishes the SIP SUBSCRIBE to the presence server
410. As such, a procedure for allowing notification rule
information for periodical notification to be included in SIP
SUBSCRIBE for requesting presence information, publishing the SIP
SUBSCRIBE, and receiving a corresponding response, can be
illustrated in the same manner as steps 1056 to 1059.
[0077] The presence server 410, which has received the SIP
SUBSCRIBE, notifies the watcher 400 of initial presence
information, which is currently noted in steps 1060 to 1063.
[0078] Also, the presence server 410, which has received such a
request for periodical notification from the watcher, requests the
presence source 430 to periodically publish specific information
according to the request for periodical notification in such a
manner that the request is included in a publication rule according
to the method described in steps 24 to 27 in FIG. 4. A procedure
where the presence server 410 publishes SIP REFER, which is a
message for requesting presence information, including the
periodical publication rule and receives a corresponding response,
is the same as steps 1064 to 1067.
[0079] Then, according to such a request for periodical
notification of presence information, the present source 430
publishes presence information to the presence server 410 in each
corresponding period as shown in steps 1068 to 1071 and steps 1076
to 1079.
[0080] The presence server 410, which has received presence
information in each corresponding period as described above,
notifies the watcher 400 of the received presence information as
shown in steps 1072 to 1075 and steps 1080 to 1083.
[0081] Then, an example of a message, which the watcher 400
publishes so as to request the presence server 410 to periodically
notify the watcher of presence information in step 1056, will be
described with reference to FIG. 11. A message shown in FIG. 11 is
an example of a message used when the watcher 400 describes a
request for notification of location information of the
"sip:brian@example.com" presentity per ten minutes as a
<periodic> element obtained by expanding a <trigger>
element of filter description within the SIP SUBSCRIBE and the "10"
value thereof, and requests the presence server 410 to notify the
location information of the "sip:brian@example.com" presentity per
ten minutes.
[0082] If the presence server 410 receives the SIP SUBSCRIBE shown
in FIG. 11, the presence server 410 requests the presence source
430 to publish location information of the "sip:brian@example.com"
presentity per ten minutes according to the request of the watcher
400 by means of a method provided by the present invention.
[0083] Then, a corresponding presence source 430 publishes location
information of the "sip:brian@example.com" presentity per ten
minutes to the presence server 410 according to the request of the
presence server 410, and the presence server 410 notifies the
watcher 400 of the location information.
[0084] Then, examples of signal flows and messages, which allow the
watcher 400 to request notification of a snapshot of specific
presence information by using a filter description according to a
method suggested by the present invention, will be described with
reference to FIGS. 12 and 13.
[0085] Firstly, steps 1200 and 1201 are equal to steps 10 and 11 in
FIG. 4 and are procedures where the present source 430 registers
presence information publication capability in the SIP/IP core 420
by using a media feature tag.
[0086] Also, steps 1202 to 1205 are equal to steps 12 to 15 in FIG.
4 and are procedures where the presence source 430 publishes
presence information to the presence server 410 according to change
of the presence information.
[0087] After this, according to an embodiment of the present
invention, the watcher 400 describes a request for notification of
a snapshot of corresponding present information, i.e. a present
state, and the description is included in SIP SUBSCRIBE so as to be
published to the presence server 410. As such, a procedure for
allowing notification rule information for requesting notification
of a snapshot of present presence information to be included in SIP
SUBSCRIBE for requesting presence information, publishing the SIP
SUBSCRIBE, and receiving a corresponding response can be shown in
steps 1206 to 1209.
[0088] Then, as shown in the method described in steps 24 to 27 in
FIG. 4, the present server 410, which has received such a request
for notification of a snapshot from the watcher 400, requests the
presence source 430 to publish current snapshot of a specific
presence information according to the request by means of a method
described in a publication rule. A procedure where the presence
server 410 publishes SIP REFER, which is message for requesting
presence information including a publication rule about a snapshot,
and receives a corresponding response is the same as steps 1201 to
1213.
[0089] Then, the presence source 430 publishes a current snapshot
of presence information to the presence server 410 according to the
publication rule as shown steps 1214 and 1217.
[0090] After this, the presence server 410 notifies the watcher 400
of the published current snapshot of presence information through
steps 1218 to 1221.
[0091] Now, an example of a message, which the watcher 400
publishes so as to request the presence server 410 to publish the
current snapshot of presence information, will be described with
reference to FIG. 13. A message shown in FIG. 13 is an example of a
message used when the watcher 400 describes a request for
notification of current location information of the
"sip:brian@example.com" presentity as a <snapshot> element
obtained by expanding a <trigger> element of a filter
description within SIP SUBSCRIBE and requests the presence server
410 to notify the current location information.
[0092] If the presence server 410 receives the SIP SUBSCRIBE shown
in FIG. 13, the presence server 410 requests the presence source
430 to publish current location information of the
"sip:brian@example.com" presentity according to the request of the
watcher 400 by means of a method provided by the present
invention.
[0093] Then, a corresponding presence source 430 publishes current
location information of the "sip:brian@example.com" presentity to
the presence server 410 according to the request of the presence
server 410, and the presence server 410 notifies the watcher 400 of
the current location information of the "sip:brian@example.com"
presentity.
[0094] In FIG. 12 according to an embodiment of the present
invention, in accordance with a SIP SUBSCRIBE request of the
watcher 400 regarding a snapshot, the presence server 410 receives
a snapshot of a corresponding presence information from the
presence source 430 and notifies the watcher 400 of a result
obtained by the snapshot rather than directly notifying the watcher
400 of presence information that the presence server 410 has
recognized. However, as described in "[RFC3856 "A Presence Event
Package for the SIP", it is possible that the presence server 410
directly notifies presence information, which the presence server
410 has recognized, in accordance with a SIP SUBSCRIBE request of
the watcher 400 regarding a snapshot, and also receives a snapshot
of a corresponding presence information from the presence source
430 so that the presence server 410 can additionally notify the
watcher 400 of a result obtained by the snapshot.
[0095] According to the present invention, the presence server can
directly receives presence information from the presence source in
an active manner, and the presence server can control the
publication operation of the presence source. Also, the watcher can
actively request desired presence information and a method for
notifying the watcher of the presence information.
* * * * *