CN101636999B - Methods and apparatus for notifying clients in communication network - Google Patents

Methods and apparatus for notifying clients in communication network Download PDF

Info

Publication number
CN101636999B
CN101636999B CN2007800522372A CN200780052237A CN101636999B CN 101636999 B CN101636999 B CN 101636999B CN 2007800522372 A CN2007800522372 A CN 2007800522372A CN 200780052237 A CN200780052237 A CN 200780052237A CN 101636999 B CN101636999 B CN 101636999B
Authority
CN
China
Prior art keywords
client
data
watching
server
message delivery
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Fee Related
Application number
CN2007800522372A
Other languages
Chinese (zh)
Other versions
CN101636999A (en
Inventor
安德斯·林德伦
克里斯特·博贝格
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of CN101636999A publication Critical patent/CN101636999A/en
Application granted granted Critical
Publication of CN101636999B publication Critical patent/CN101636999B/en
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/54—Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42365—Presence services providing information on the willingness to communicate or the ability to communicate in terms of media capability or network connectivity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
    • H04M3/53—Centralised arrangements for recording incoming messages, i.e. mailbox systems
    • H04M3/5322—Centralised arrangements for recording incoming messages, i.e. mailbox systems for recording text messages
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/006—Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP), including next generation networks with a packet-switched transport layer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/303—Terminal profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2203/00—Aspects of automatic or semi-automatic exchanges
    • H04M2203/20—Aspects of automatic or semi-automatic exchanges related to features of supplementary services
    • H04M2203/205—Broadcasting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42025—Calling or Called party identification service
    • H04M3/42085—Called party identification service
    • H04M3/42093—Notifying the calling party of information on the called or connected party
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42348—Location-based services which utilize the location information of a target
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
    • H04M3/53—Centralised arrangements for recording incoming messages, i.e. mailbox systems
    • H04M3/533—Voice mail systems
    • H04M3/53366—Message disposing or creating aspects
    • H04M3/53375—Message broadcasting

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Human Resources & Organizations (AREA)
  • Economics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Operations Research (AREA)
  • Game Theory and Decision Science (AREA)
  • Educational Administration (AREA)
  • Marketing (AREA)
  • Development Economics (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Telephonic Communication Services (AREA)

Abstract

A method and arrangement for providing client data of an observed client (B) to plural watching clients (A1, A2, A3). A client data server (402) sends a common notification (4:4) to an information delivery server (400) with client data of the observed client for the watching clients. The information delivery server can then customise client data from the common notification message according to at least one delivery rule and any data filters, for delivery to the watching clients in individual notification messages. The client data server thus transfers the common notification with client data once to the information delivery server, instead of transferring the same client data in multiple individual notification messages.

Description

The method and apparatus of notifying clients in communication network
Technical field
Present invention relates in general to be used at communication network to a plurality of method and apparatus of watching client (watchingclient) the announcement incident relevant with observing client (observed client).
Background technology
Along with the appearance of 3G mobile phone, developed the packet-based communication technology of new use IP (Internet protocol) and supported multi-media radio communication.For example, the communication protocol among GPRS (GPRS) and the WCDMA (WCDMA) is supported the multimedia service of packet switching and traditional circuit-switched voice call.
Third generation partner program (3GPP) has been developed " IP Multimedia System " network architecture (IMS) of a kind of being called, as the platform of in packet domain, handling multimedia service and session based on the IP transmission.Therefore, the IMS network can be used for initiating and control Multimedia session to any terminal with IP function of the access network that is connected to any type.Various session management nodes by in the IMS network are controlled these sessions, and these session management nodes comprise known IMS node S-CSCF (service call conversation control function), I-CSCF (query call conversation control function) and P-CSCF (Proxy Call Session Control Function).In addition, main Database Unit HSS (home subscriber server) stores user data and the verify data that is used to subscribe to client.
The signaling protocol of this being called as " SIP " (Session initiation Protocol) is often used in controlling Multimedia session in IMS network and other business network.Therefore, the terminal and the server that have the SIP function can use this agreement to initiate and stop multimedia communication (for example, by the IMS network).Though below will come to describe prevailingly each execution mode, and when embodiment of the present invention, also can use the business network of other suitable type and agreement to carry out session control to IMS and SIP.
By can reside within the IMS network or outside various application servers enable and carry out these multimedia services.The concrete example of the business that can adopt by means of IMS network or other business network is so-called " presenting (presence) " business, presents business and comes down to make that the data relevant with particular clients can be obtained by other client.
In this manual, generic term " client data " is used to represent state or the relevant any information of situation with client and his/her equipment, and corresponding term " presents data " and is generally used for appearing business.Be commonly referred to the application server place maintain customer end data of " client data server ", this application server is served relevant client.With regard to presenting business, client present storage in presence server, then, can it be offered and subscribe to this and present the client of data.
Client data or present data and can represent following exemplary client states:
-ownness, for example, available, have much to do, have a meeting, spend a holiday etc.
-the SOT state of termination, for example, in start/shutdown, the work, out of reach etc.
The geographical position of-client/terminal.
-terminal capability, for example, functions such as SMS, MMS, chat, IM, video.
-terminal is selected, for example, and calling transfer, language etc.
-other client-side information for example, interest, work, individual character, mood, individual human head picture, depends on the head portrait of current mood etc.
Therefore; As long as introduced, upgrade, change or deleted any data that appear of client, just such information for example is stored in the presence server continuously based on the issue of the what is called " client event " that receives from client or from their access network.Therefore, client can also be subscribed to the data that appear of selected one or more other client of being crossed by application server processes equally.
In this manual, term " client " ordinary representation communication terminal and user thereof.In addition; " watch client " and be and subscribe to or request presents the client (being sometimes referred to as " information requester (Watcher) ") of data, and " observation client " be issue to through mandate watch arbitrarily client can with the client that presents data (being sometimes referred to as " informant (Presentity) ").
Observing client uses the sip message that is called as " SIP issues (SIP PUBLISH) " that their data that appear are sent to presence server and issue usually.This SIP PUBLISH can be used for initiating the available data of new data, modification available data, " refreshing (refresh) " available data (that is, confirming that data remain valid) and termination no longer valid.
Watch client to use another sip message that is called as " SIP SUBSCRIBE (sip subscribe) " to subscribe to and observe the data that appear of client, and only just have the right to receive this data through the client of authorizing.Sip subscribe message comprises usually and can be used to determine when and finish to subscribe to and announcement by watching the client to bring in the timeout parameter or the TTL (life span) of setting.Presence server can use another sip message that is called as " SIP NOTIFY (SIP announcement) " to come the data that appear after the subscription client provides renewal.
As stated, above-mentionedly be used for the issue client terminal data and present business, also can be used in other business (like PoC (moveable push-to-talk) and IM (instant message transmission)) to watching client to provide the mechanism of the announcement of the client data of being issued to be used in.
Fig. 1 illustration be used to provide the current conventional procedure that presents data, this process to relate to watch customer end A, observe customer end B and serve the presence server 100 of customer end B.Be associated with presence server 100 present maintain customer end in the database 102 present data B, and be used for that control data transmits present rale store at rule database 104.Presenting rule, whom can indicate which data be addressable etc. for.In Fig. 1, represent customer end A and B by portable terminal, although this process also can be applied to fixed terminal.
First step 1:1a ordinary representation the observation customer end B issue and present data through send the SIP PUBLISH to presence server 100.Can also send some data from the access network (not shown) of customer end B, for example position data and SOT state of termination data to customer end B.Next step 1:1b has represented to be utilized in the new data that receives in the issue of step 1:1a and has upgraded and present database 102.Basically, according to general routine, as long as issued and presented data to customer end B, just continuation step 1:1a and step 1:1b on the backstage.
Customer end A can be subscribed to and presents data through creating the dialogue that wherein can receive announcement with presence server 100.Therefore at step 1:2, customer end A is sent the SIP SUBSCRIBE message that presents data of requesting client B, and has also specified timeout parameter TTL in the message that is used for talking with.If TTL is set to zero, what then customer end A can receive only customer end B presents data once, and if the duration that timeout parameter is set to expect, then he can continue to receive and presents data.SIP SUBSCRIBE message among the step 1:2 can also comprise the preference of the information category that customer end A wants to receive or do not want to receive him, and this preference is designated hereinafter simply as " data filter ".For example, customer end A possibly be positioned at where (position) is interested to customer end B, but his/her current mood or terminal is not provided with etc. interested.
Then at next step 1:3, presence server 100 is used through inspection database 104 and is generally presented rule arbitrarily, with confirm customer end A whether through mandate some that can receive customer end B available present data.If, then step 1:4 from database 102, take out customer end B for customer end A can with present data.In addition, at next step 1:5, use data filter (if any), and finally in notice message SIPNOTIFY, data are sent to customer end A, shown in step 1:6 according to the subscribe request of step 1:2.Therefore, the data that appear that can be transmitted among the step 1:6 according to generally presenting rule and allow/be limited in the rule database 104, and/or according to the data filter that receives from customer end A the data that appear that among step 1:6, transmitted are filtered.
Shown in the dotted arrow among the step 1:6, customer end A can receive regularly in the subscription period and include this announcement that presents data to other situation, perhaps as long as the data change that appears of B just receives.In order to prolong or " refreshing " this subscription, customer end A can be sent another SIP SUBSCRIBE message when this TTL is just overtime, and then, presence server 100 can be safeguarded and should subscribe to and transmit further announcement.
Watch client to subscribe to the data that appear of a considerable amount of observation clients usually.In order to reduce to arrive specific announcement traffic of watching client; Can use the message delivery server that is called as RLS (" resource list server "); This resource list server is collected the announcement that these observe client by so-called " rear end subscription ", and this message delivery server watches client to send to the public announcements of all observing client to this.This mechanism is called as " distributor (exploder) " function, and watches under the situation of client mobile, and expectation reduces the message traffic on the wave point in this manner.
Fig. 2 show according to prior art, be used for observing the RLS that presents data 200 of the group of customer end B, C and D to watching customer end A to provide.Suppose in customer end B, C and D presence server 202B, 202C and 202D separately, to issue respectively and store their data that appear, shown in arrow p.RLS 200 is also connected to user list server 204, and user list server 204 is safeguarded various predetermined user tabulations (such as phone directory and group of contacts).Watch client can also be in specified special (ad hoc) group of request message requesting client present data.
At the 2:1 of step shown in first, terminal A tabulates and sends SIPSUBSCRIBE message through consulting predetermined user, and the group of the indicated customer end B of this SIP SUBSCRIBE message request, C, D presents data.According to SIP, this message can be set to: " event:Presence, list=l ".As its response, at step 2:2, RLS 200 takes out institute's requesting users tabulation from user list server 204, and therefore, this tabulation has identified observation customer end B-D and their presence server 202B-D.SIP SUBSCRIBE message can also comprise data filter, and is of the step 1:2 of Fig. 1.
Afterwards, RLS 200 brings in subscription data by each application server that subscribe to from application server 202B-D the rear end to their clients separately, usually by step 2:3, shown in 2:4 and the 2:5.If 2:1 has received data filter in above-mentioned steps, then each rear end is subscribed to and is also comprised this data filter.Present data (if desired, alternatively through application data filter) afterwards collecting from server 202B-D, at final step 2:6, RLS 200 sends the public announcements that the expectation that includes the whole customer end B-D in the tabulation presents data to customer end A.Therefore, can allow/limit and/or filter the data that transmitted according to aforesaid way, here though also not shown.Can send customer end A to subscribing to the further announcement that presents data that will include customer end B-D in the period, with the example class of Fig. 1 seemingly.
But, watch client and the subscription of ongoing rear end according to various representatives, the announcement total amount that sends to RLS from presence server maybe be very huge, and this is great burden as far as the resource that is used for sending and handle these announcements.
Fig. 3 illustration according to prior art, when RLS 300 to a plurality of customer end A of watching 1, A 2And A 3Provide observe customer end B present data the time this problem.In this example, only show three and watch client, but should be understood that, possibly have bigger quantity watch client (for example, hundreds of magnitudes watch client) to same observation client to present data interested.
In Fig. 3, suppose to watch customer end A 1, A 2And A 3That has asked to observe customer end B presents data (suppose independently of one another), and RLS 300 created with the rear end of the presence server that presents data 302 of maintain customer end B and subscribe to, that is, each watches rear end subscription of client.RLS 300 also watches the preference of client to come to presence server 302 supply data filters according to these.Therefore, each watch client can expect to meet he data filter present data.In addition, these watch client can visit the data that appear of customer end B according to different modes, as with in the rule database 304 that server 302 is associated appear rule indicated.
First step 3:1 ordinary representation in server 302 issue and storage customer end B present data, this can obtain all watching the announcement of client.Can also transmit these announcements regularly, and present data independence with when issuing.Next step 3:2 had represented before transmitting watching the rule of client application from rule database 304.At step 3:3, can also be to watching client that arbitrary data filter 306 is applied to appear data individually.
Then, presence server 302 is subscribed to according to the rear end, in announcement of watching client to each, sends the data that appear of customer end B to RLS 300.Therefore, in these announcements, in above-mentioned steps 3:2 and step 3:3 to watching client and separately through permissions/restriction and/or filter present data possibility difference.In this example, step 3:4 has represented that basis from server 302 is to customer end A 1Effective regular R 1And data filter F 1The announcement of handling, step 3:5 has represented that basis is to customer end A 2Effective regular R 2And data filter F 2The announcement of handling, and step 3:6 has represented that basis is to customer end A 3Effective regular R 3And data filter F 3The announcement of handling.
At last, at step 3:7,3:8 and 3:9, RLS 300 is to watching customer end A 1, A 2And A 3Transmit above-mentioned each announcement.Though not shown here, watch customer end A 1, A 2And A 3In any one can also come to receive the same announcement other according to the described mode of Fig. 2 certainly and observe the data that appear of client from RLS 300.In addition, can be in the announcement among transfer step 3:7,3:8 and the 3:9 independently of the different moment.
Shown in step 3:4,3:5 and 3:6, current must to each watch customer end A 1, A 2And A 3Include the independent announcement that presents data of issuing from presence server 302 to RLS 300 transmissions to same observation customer end B.As stated, if relate to a large amount of clients of watching, even then these announcements possibly comprise same information, but still the announcement by these nodes transmission and processing that can produce a myriad of.
Therefore, expectation reduces traffic carrying capacity total amount and the announcement quantity between client data server (it is safeguarded to the client data of observing client) and the message delivery server (it transmits the announcement that includes the client data of issuing to observing client to a plurality of clients of watching).Also expectation reduces in these two nodes, to handle the burden of this announcement.
Summary of the invention
The objective of the invention is to address the above problem.Specifically, the object of the present invention is to provide a kind of can reducing usually to a plurality of needed signaling of announcement of the client data that client provides same observation client and solutions of message number of watching.
The present invention relates to a kind of message delivery server and client data server, this message delivery server is announced to watching client to send, and this client data server is safeguarded the client data of observing client.Message delivery server can be RLS, and client data server can be a presence server, though the present invention is not limited to these specific nodes.
These and other purpose can realize through the method and apparatus according to appended independent claims.
According to an aspect, the invention provides a kind of by message delivery server carry out in communication network to a plurality of methods of watching client that the client data of observing client is provided.Receive each subscribe request from said a plurality of clients of watching to the client data of said observation client.Represent said a plurality of client of watching to bring in then and create rear end subscription, wherein, safeguard said client data by client data server to the client data of said observation client.Subscribe to according to these rear ends, receive from said client data server the client data that includes said observation client to said a plurality of public announcements of watching client.Then, through use to said a plurality of watch in the client one or more to watch client effectively at least one transmits rule and comes to be said a plurality of client terminal to customize client datas of watching.At last, in each announcement, the client data that customizes is sent to said a plurality of client of watching.
According on the other hand, the invention provides a kind of in communication network to a plurality of message delivery servers of watching client that the client data of observing client is provided.This message delivery server comprises: be used for from said a plurality of devices of watching client to receive each subscribe request of the client data that is directed against said observation client; And be used to represent said a plurality of client of watching to bring in the device that establishment is subscribed to the rear end of the client data of said observation client, wherein, safeguard said client data by client data server.
This message delivery server also comprises: be used for from said client data server receive the client data that comprises said observation client to said a plurality of devices of watching the public announcements of client; Be used for through use to said a plurality of watch client one or more watch client effectively at least one transmit rule and is said a plurality of devices of watching the client terminal to customize client data; And be used for sending the client data that customizes to said a plurality of device of watching client in each announcement.
According to more on the one hand; The invention provides and a kind ofly in communication network, come the method and the client data server of watching client to provide observing the client data of client to a plurality of by message delivery server, wherein said client data server is safeguarded said client data.Receive the said a plurality of rear end subscribe request of watching client of representative to the client data of said observation client from said message delivery server, each rear end subscribe request includes the corresponding identifier of watching client.Then; With sending to said message delivery server, make said message delivery server can before transmitting, be the said client terminal to customize client data of watching one public announcements to said a plurality of client datas of the said observation client of client of watching.
Can understand further feature of the present invention and advantage thereof according to following detailed description.
Description of drawings
Illustrate in greater detail the present invention through illustrative embodiments and with reference to accompanying drawing, in the accompanying drawing:
Fig. 1 show according to prior art, be used for to watching customer end A that the block diagram of the process that present data relevant with observing customer end B is provided.
Fig. 2 show according to prior art, be used for coming block diagram to the process that presents data of the group of watching customer end A to provide observing customer end B, C and D by resource list server RLS.
Fig. 3 show according to prior art, be used for coming to a plurality of customer end A of watching by resource list server RLS 1, A 2And A 3The block diagram of the process that presents data of observing customer end B is provided.
Fig. 4 show according to an execution mode, be used for coming to a plurality of customer end A of watching by message delivery server 1, A 2And A 3The block diagram of the process of the client data of observing customer end B is provided.
Fig. 5 be basically according to the block diagram of Fig. 4, when flow chart to a plurality of processes of carrying out by message delivery server when watching client that the client data of observing client is provided.
Fig. 6 be basically according to the block diagram of Fig. 4, when the flow chart that comes by message delivery server to a plurality of processes of carrying out by client data server when watching client that the client data of observing client is provided.
Embodiment
In brief, the present invention can be used for reducing the signaling traffic amount between the client data server of message delivery server (be used for watch client to provide including the client data of observing client to a plurality of announcement) and this observation client.This message delivery server can be RLS, and this client data server can be a presence server, wherein, between these nodes, uses the SIP signaling, though the present invention is not limited to this.
According to this solution; Can once in public announcements message, will be sent to these a plurality of client datas of client of watching and be delivered to this message delivery server, rather than repeatedly transmit in different each notice messages of watching client from this client data server.Then, message delivery server can extract suitable customization client data from this public announcements message, watch client in each notice message, to send to.
In different execution modes, this public announcements message can also comprise that the identifier of watching client reaches the indication of one or more being watched the effectively any transmission rule of client.Alternatively, which client data of this observation client of having watched client subscription this reception message delivery server can identify, and can from addressable rule database, obtain their relevant transmission rule.
Transmitting rule can be to the different availability or the accessibility of watching client indication client data in public announcements.For example, these transmit rules and can indicate client data X should only send customer end A, B, C to and do not send other client to, and/or client data Y must not send client D, E, F to, etc.
In addition; If watch client optionally to ask client data, that is to say, if should some client data be omitted from transmit according to each data filter; Then can store and use these data filter at the message delivery server place, thus the customization client data.Here, term " customization " is used to represent that all are directed against particular clients and adjustment that the client data content is carried out.
Illustrate in greater detail different execution mode of the present invention with reference to following accompanying drawing, but be not restriction entire scope of the present invention.Fig. 4 show according to an execution mode, be used for to a plurality of customer end A of watching 1, A 2And A 3The equipment of the client data of observing customer end B and the block diagram of process are provided.
Suppose customer end A 1, A 2And A 3Asked the client data of customer end B independently of one another to message delivery server 400 by subscribe request (not shown).Message delivery server 400 can be RLS, and subscribe request can be used as SIP SUBSCRIBE message and send.In addition, client data server 402 (it can be a presence server) receives and safeguards the client data of this customer end B constantly, shown in dotted arrow among the figure.
One or more watches client can also come optionally requesting client data through specific data filter or equivalent in client data request usually.In practice, can come optionally requesting client data, for example,, be referred to as " data filter " in this manual through specifying a type of should in transmission, comprise or get rid of or multiclass client data more according to different modes.Therefore, data filter has been controlled usually to observing client and has been watched client to want the information that receives.
In this example, each customer end A 1, A 2And A 3Specified data filter F at him respectively in for the subscribe request of message delivery server 400 1, F 2And F 3First step 4:1 has represented that when receiving subscribe request one by one, message delivery server 400 is stored in these data filter in the suitable data storage part, so that when each watches client to send announcement, use these filters after a while.
Next, message delivery server 400 is represented customer end A to the client data of customer end B 1, A 2, A 3Create with the rear end of client data server 402 and subscribe to, that is, watch client and send independent subscribe request to each, shown in illustrated steps 4:2.According to common standards, server 400 has also comprised the related suitable identifier of watching client in each rear end subscribe request.But, in subscribe request, send data filter F to client data server 402 1, F 2And F 3(as traditional Fig. 2 is in the process of Fig. 3) is not necessary, and this is because according to this solution, can be safeguarded and the application data filter by message delivery server 400, is explained after a while.
At this moment, usually when decide to a plurality of announcements of watching client to send the client data that comprises this observations client, and determine should which client it be addressed to by client data server 402.For example, when having issued new client data, can trigger client data server 402 and send announcement to customer end B.
At next step 4:3, client data server 402 is obtained respectively for customer end A from rule database 404 then 1, A 2And A 3Effectively can use and transmit regular R 1, R 2And R 3In this schematic example, watch the client to bring in obtaining to each and transmit rule, even same transmission rule possibly be effectively for the more than one client of watching, or some clients possibly not submit to any transmission rule, etc.Should also be noted that observing client has defined these and transmit rule, so that his/her client data is controlled the availability or the accessibility of other client, and watch client that data filter is defined as preference.
At next step 4:4; The public announcements message that client data server 402 is sent the client data that includes customer end B to message delivery server 400, rather than in pointing to the different independent notice messages of watching client, send same client data three times basically.Can in SIPNOTIFY message, send this public announcements.
Public announcements can also comprise destination client A 1, A 2And A 3Identifier, and the regular R of corresponding effective transmission that obtains at step 4:3 1, R 2And R 3Or to effective at least some suitable indications that transmit rule.For example, this public announcements can comprise complete rule clearly, or comprises transmitting regular R 1, R 2And R 3Implicit quoting rather than complete rule self, make message delivery server 400 can use these to quote the actual transmission rule that visits in the rule database 404.If server 400 maintains trusting relationship with server 402, then back a solution is feasible.
If do not comprise this identifier and rule in the public announcements; In any case then receiving message delivery server, can be all this to be watched client identification be to have subscribed to the client data of observing client; Then, from rule database 404, obtain their transmission rule.
In order to save the space in the public announcements message, client data server 402 can be got rid of all from this message in no case can be by any client data of watching client to allow, like the transmission rule R that is obtained 1, R 2And R 3Shown in.
In practice, can come the information in message delivery server 400 transmission public announcements according to different modes.In a substitute mode, the SIP tunnel of between client data server and message delivery server, being created before can using.A current available solution is between RLS and presence server, to create the SIP tunnel, is used between these nodes, exchanging various requests at ongoing SIP dialog, and the SIP tunnel can be used under this environment.In another substitute mode, the existing ID parameter that is arranged in SIP NOTIFY header is used in public announcements provides the identifier of all watching client.Can illustrate in greater detail these two replacement execution modes after a while.
When receiving public announcements message; At next step 4:5; Message delivery server 400 is discerned the related client of watching according to client identifier (if in public announcements message, having provided); Or be user, and obtain the corresponding data filter F of in step 4:1, being stored to the client data that receives with the related client identification of watching 1, F 2And F 3
Then, message delivery server 400 is through using transmission rule R indicated in this message 1, R 2And R 3And the data filter F that is obtained 1, F 2And F 3, watch the client data of client to customize to will sending to of in public announcements message, receiving.Should be noted in the discussion above that usually not all client of watching all must be obeyed this rule and filter, although in this schematic example, be like this.
At last, at step 4:6,4:7 and 4:8, server 400 sends the client data of customization to watch client in each notice message.Like this, just adjusted the customization client data that is transmitted respectively to watching client, so that in each announcement, the different client side data content is provided according to various effective transmission rules and data filter.
Fig. 5 be basically according to the block diagram of Fig. 4, when flow chart to a plurality of processes of carrying out by message delivery server when watching client that the client data of observing client is provided.First step 500 ordinary representations from watching client to receive each subscribe request to the client data of observing client.Can receive these requests independently in the different moment, although be illustrated as single step here.At next step 502, message delivery server pair is stored with all data filter that this request receives, so that using during customization client data content to sending after a while.
At next step 504, in response to the subscribe request of step 500, to the client data of observing client, the representative request is watched the client to bring in establishment and is subscribed to the rear end of the client data server of this observation client.Basically, at every turn can repeating step 500-504 when watching client to receive the subscribe request to client data, shown in dotted arrow.
At next step 506; Subscribe in response to the rear end; To watching client to receive the public announcements message that includes the client data of observing client early or late from client data server; Rather than be received in the same client data (for example, shown in the step 3:4-3:6 of Fig. 3) that repeats in a plurality of independent announcements basically.Thus, avoided the repetition of client data.
Except the client data of observing client, the public announcements message that receives can also comprise that the identifier of watching client and at least one watch client effectively to transmit the indication of rule to one or more.Transmitting regular indication can be one or more complete rule that clearly provides, or is stored in the rule in the addressable transmission rule database or points in the look-up table predetermined rule etc. and impliedly represent quoting of one or more rule etc. through sensing.If do not comprise this identifier and rule in the public announcements, then receiving message delivery server, can these to be watched client identification be to have subscribed to the client data of observing client, then, from rule database, obtains their transmission rule.
At next step 508; Corresponding data filter (if any) through being applied in institute's stored watching client in the above-mentioned steps 502 and according at least one indicated rule in receiving public announcements customizes to the client data of watching the client to bring in being included in the public announcements.In final step 510; Client data with customization in each announcement sends to and watches client; Therefore it is effectively regular and different more or less each other that the client data that customizes depends on that the data filter of watching client reaches, thereby be adapted to watch client.
Fig. 6 be equally basically according to the block diagram of Fig. 4, when another flow chart of the process of coming by message delivery server when a plurality of requests watch client that the client data of observing client is provided, to carry out by client data server.Therefore, client data server receives and safeguards the client data of observing client, as stated.
At first step 600, client data server representative request watches client to receive the request of the client data of observing client being carried out the rear end subscription from message delivery server, and is for example, of the step 4:2 of Fig. 4.These rear end subscribe request comprise the identifier that each watches client, and normally independently receive in the different moment, though be illustrated as single step here.
At next step 602, from rule database, obtain at least one and watch client effectively to transmit rule one or more, for example, of the step 4:3 of Fig. 4.Then, client data server is created the public announcements that includes the active client data of observing client.Public announcements can also comprise this identifier of watching client and this is watched effectively rule (if any) of client.At last, in step 604, client data server sends to message delivery server with public announcements.Then, message delivery server can come to watching client to transmit each announcement based on this public announcements, like the step 508 of Fig. 5 and 510 said.
As stated, can the information in the public announcements be passed to message delivery server from client data server, though the present invention is not limited to concrete scheme or method arbitrarily usually according to different modes.But, illustrate in greater detail two different feasible suggestions now.
According to first substitute mode, can between client data server and message delivery server, create the SIP tunnel, the SIP tunnel is a kind of ongoing SIP dialog, can share dialogue through this and be used for transmitting the various message in a plurality of subscription.Use a plurality of independent SIP dialog to compare with being directed against a plurality of subscription, this can all reduce processing expenditure and memory usually at two node places and use.Now, can this mechanism be expanded to and comprise that transmitting target is to watch the required additional data of public announcements of client, is described below.
The current structure that has comprised subscription information through the SIP tunnel is used the particular header of a kind of being called as " x-sub-data ", and this header comprises these fields:
“x-sub-data:To＝W，From＝P，Sub-state＝1300，Sub-id＝2234”
Wherein, " W " is target information requestor (watching client), and " P " is informant's (observation client), and " Sub-state " is subscription status, and " Sub-id " is the unique subscription parameters as parameters for tunnel.Therefore, through in announcement, comprising a plurality of " x-sub-data " header, this header structure can be used for a plurality of beholders' public announcements in current solution.So in the example of Fig. 4, the public announcements among the step 4:4 just comprises to target watches customer end A 1, A 2And A 3Following three headers:
“x-sub-data:To＝K1，From＝B，Sub-state＝1300，Sub-id＝2234”
“x-sub-data:To＝K2，From＝B，Sub-state＝2400，Sub-id＝235”
“x-sub-data:To＝K3，From＝B，Sub-state＝1567，Sub-id＝56f4”
In this solution; Can be associated with his/her rear end subscription to specific " sub-id " information of client of watching; Known like message delivery server; Then, message delivery server can watch the client to bring in the correct rear end subscription in location to each by this " sub-id " information pointer.Can comprise in the public announcements one or more is watched the effectively indication of at least one transmission rule of client; For example; In one or more " x-sub-data " header as added field, or in message as additional header or other data field.
According to second substitute mode, existing " id " parameter in " Event " header of SIP NOTIFY can be used for indicating the unique subscription in the SIP dialog.This can be used in the current solution; Make message delivery server can bring in the single SIP dialog of creating with client data server to whole clients of watching of the client data of having subscribed to same observation client; Then, use " id " parameter in " Event " header to indicate actual subscription.Therefore, client data server can comprise the tabulation of " id " parameter in to the public announcements of watching client, and then, receiving message delivery server can come to watch the correct rear end of client location to subscribe to each by these " id " parameters.
In these two substitute modes; After having identified correct rear end subscription as stated; Message delivery server can customize the client data in the public announcements through at least one transmission rule of using the data filter (if any) of being stored and received, and correspondingly transmits the client data of customization.
According to above-mentioned each execution mode,, utilize the present invention can greatly reduce to the required signaling of a plurality of client datas of watching client to send single observation client through sending single public announcements to message delivery server from client data server.Should be noted in the discussion above that otherwise, each independent announcement relates to sends a plurality of message, between these nodes, to create and to stop dialogue times without number.
Though to specific exemplary embodiments the present invention has been described, this specification only is intended to illustration invention thought usually, and should it be regarded as the restriction to the scope of the invention that is defined by the following claims.When above-mentioned each execution mode of explanation, used IMS technology and SIP signaling protocol, be suitable for realizing other standard and agreement arbitrarily of the present invention although can use basically.

Claims (18)

  1. One kind in communication network to a plurality of client (A that watch 1, A 2, A 3) method of the client data of observing client (B) is provided, this method comprises the following steps of being carried out by message delivery server (400):
    -receive the subscribe request step, receive each subscribe request from said a plurality of clients of watching to the client data of said observation client;
    -create the rear end subscription step, represent said a plurality of client of watching to bring in and create rear end subscription (4:2) to the client data of said observation client, wherein, safeguard said client data by client data server (402);
    -reception public announcements step; Receive from said client data server the client data that comprises said observation client to said a plurality of public announcements (4:4) of watching client; Wherein, Create the SIP tunnel as using said SIP tunnel to transmit the said message delivery server of said public announcements and the ongoing SIP dialog between the said client data server; And wherein, comprise a plurality of SIP tunnel headers in the said public announcements, each header all relates to a specific target and watches client;
    -customization step, through use to said a plurality of watch in the client one or more to watch client effectively at least one transmits rule (R 1, R 2, R 3) come to be said a plurality of said client datas of client terminal to customize of watching; And
    -transfer step, the client data with said customization in each announcement sends said a plurality of client of watching to.
  2. 2. method according to claim 1, wherein, said public announcements also comprises said a plurality of the watch identifier of client and the indication of said at least one transmission rule.
  3. 3. method according to claim 2, wherein, said transmission rule indication explicitly has been stipulated the rule that one or more is complete.
  4. 4. method according to claim 2; Wherein, The indication of said transmission rule is stored in the rule in the addressable transmission rule database or points to predetermined rule in the look-up table through sensing, has implicitly stipulated to represent said one or more regular quoting.
  5. 5. method according to claim 1; Wherein, Said message delivery server is a client data of having subscribed to said observation client with said a plurality of client identifications of watching, and from addressable rule database, obtains said at least one transmission rule.
  6. 6. according to any described method in the claim 1 to 5, wherein, receive said a plurality of data filter of watching client, and said customization step also comprises the said data filter of application with said each subscribe request.
  7. 7. method according to claim 2, wherein, the appointment in said public announcements " x-sub-data " header of said a plurality of identifiers of watching client.
  8. One kind in communication network to a plurality of client (A that watch 1, A 2, A 3) message delivery server (400) of the client data of observing client (B) is provided, this message delivery server (400) comprising:
    -be used for from said a plurality of devices of watching client to receive each subscribe request of the client data that is directed against said observation client;
    -be used to represent said a plurality of client of watching to bring in the device of establishment to the rear end subscription (4:2) of the client data of said observation client, wherein, safeguard said client data by client data server (402);
    -be used for from said client data server receive the client data that comprises said observation client to said a plurality of devices of watching the public announcements (4:4) of client; Wherein, Create the SIP tunnel as using said SIP tunnel to transmit the said message delivery server of said public announcements and the ongoing SIP dialog between the said client data server; And wherein; Comprise a plurality of SIP tunnel headers in the said public announcements, each header all relates to a specific target and watches client;
    -be used for through use to said a plurality of watch client one or more watch client effectively at least one transmit rule (R 1, R 2, R 3) come to be said a plurality of devices of watching the said client data of client terminal to customize; And
    -be used for sending to said a plurality of device of watching client at each client data of announcing said customization.
  9. 9. message delivery server according to claim 8, wherein, said public announcements also comprises said a plurality of the watch identifier of client and the indication of said at least one transmission rule.
  10. 10. message delivery server according to claim 9, wherein, said transmission rule indication explicitly has been stipulated the rule that one or more is complete.
  11. 11. message delivery server according to claim 9; Wherein, The indication of said transmission rule is stored in the rule in the addressable transmission rule database or points to predetermined rule in the look-up table through sensing, has implicitly stipulated to represent said one or more regular quoting.
  12. 12. message delivery server according to claim 9, this message delivery server also comprises:
    Being used for said a plurality of client identifications of watching is the device of having subscribed to the client data of said observation client; And
    Be used for obtaining the device of said at least one transmission rule from addressable rule database.
  13. 13. any described message delivery server in 12 according to Claim 8; Wherein, If received said a plurality of data filter of watching client with said each subscribe request, the then said device that is used to customize said client data is suitable for using said data filter.
  14. 14. message delivery server according to claim 9, wherein, the appointment in said public announcements " x-sub-data " header of said a plurality of identifiers of watching client.
  15. 15. one kind is come to a plurality of client (A that watch by message delivery server (400) in communication network 1, A 2, A 3) method of the client data of observing client (B) is provided, this method comprises the following steps of being carried out by the client data server (402) of safeguarding said client data:
    The said a plurality of clients of watching of-representative receive a plurality of rear ends subscription (4:2) request to the client data of said observation client from said message delivery server, and each rear end subscribe request all comprises the corresponding identifier of watching client; And
    -to said a plurality of clients of watching, send the public announcements (4:4) of the client data that comprises said observation client to said message delivery server.
  16. 16. method according to claim 15; Wherein, From rule database, obtain to said a plurality of watch in the client one or more to watch client effectively at least one transmits rule; And wherein, comprised said a plurality of at least one transmission rule (R that watches the identifier of client and obtained in the said public announcements 1, R 2, R 3) indication.
  17. 17. one kind is come to a plurality of client (A that watch by message delivery server (400) in communication network 1, A 2, A 3) client data server (402) of the client data of observing client (B) is provided, this client data server (402) comprising:
    -be used to represent said a plurality of a plurality of rear ends of watching client to receive the client data that is directed against said observation client from said message delivery server to subscribe to the device of (4:2) request, each rear end subscribe request all comprises the corresponding identifier of watching client; And
    -be used for to said a plurality of clients of watching; Send the device of the public announcements (4:4) of the client data that comprises said observation client to said message delivery server; Wherein, Create the SIP tunnel as using said SIP tunnel to transmit the said message delivery server of said public announcements and the ongoing SIP dialog between the said client data server; And wherein, comprise a plurality of SIP tunnel headers in the said public announcements, each header all relates to a specific target and watches client.
  18. 18. client data server according to claim 17, this client data server also comprises:
    Be used for from rule database obtain to said a plurality of watch the client one or more to watch client effectively at least one transmits the device of rule; Wherein, comprised said a plurality of at least one transmission rule (R that watches the identifier of client and obtained in the said public announcements 1, R 2, R 3) indication.
CN2007800522372A 2007-03-19 2007-03-19 Methods and apparatus for notifying clients in communication network Expired - Fee Related CN101636999B (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/SE2007/000267 WO2008115100A1 (en) 2007-03-19 2007-03-19 A method and apparatus for notifying clients in a communication network.

Publications (2)

Publication Number Publication Date
CN101636999A CN101636999A (en) 2010-01-27
CN101636999B true CN101636999B (en) 2012-11-07

Family

ID=39766125

Family Applications (1)

Application Number Title Priority Date Filing Date
CN2007800522372A Expired - Fee Related CN101636999B (en) 2007-03-19 2007-03-19 Methods and apparatus for notifying clients in communication network

Country Status (4)

Country Link
US (1) US20100094952A1 (en)
EP (1) EP2127306A1 (en)
CN (1) CN101636999B (en)
WO (1) WO2008115100A1 (en)

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7640267B2 (en) 2002-11-20 2009-12-29 Radar Networks, Inc. Methods and systems for managing entities in a computing device using semantic objects
US7433876B2 (en) * 2004-02-23 2008-10-07 Radar Networks, Inc. Semantic web portal and platform
JP2009206601A (en) * 2008-02-26 2009-09-10 Funai Electric Co Ltd Information distribution system
EP2371107B1 (en) 2008-12-19 2012-10-24 Telefonaktiebolaget L M Ericsson (publ) A method and arrangement for handling resource data
EP2396940B1 (en) * 2009-02-13 2018-05-30 Telefonaktiebolaget LM Ericsson (publ) A method and an arrangement for handling resource data
WO2010120934A2 (en) 2009-04-15 2010-10-21 Evri Inc. Search enhanced semantic advertising
WO2010120925A2 (en) 2009-04-15 2010-10-21 Evri Inc. Search and search optimization using a pattern of a location identifier
US8200617B2 (en) 2009-04-15 2012-06-12 Evri, Inc. Automatic mapping of a location identifier pattern of an object to a semantic type using object metadata
WO2010120929A2 (en) 2009-04-15 2010-10-21 Evri Inc. Generating user-customized search results and building a semantics-enhanced search engine
CN102209313A (en) * 2010-03-29 2011-10-05 华为技术有限公司 Presence information subscribing method and system, resource list server and presence server
WO2011162646A1 (en) * 2010-06-21 2011-12-29 Telefonaktiebolaget Lm Ericsson (Publ) Method and arrangement for notifications in a communication network
MY168733A (en) * 2010-11-02 2018-11-29 Ericsson Telefon Ab L M Methods and devices for media description delivery
US8805939B2 (en) 2010-11-03 2014-08-12 Microsoft Corporation Gaming notifications aggregator
EP2692185A4 (en) * 2011-03-29 2014-10-08 Ericsson Telefon Ab L M Method and arrangement for providing update notifications in a telecommunication network
US9736587B2 (en) * 2012-08-31 2017-08-15 Qualcomm Incorporated Smart tool for headphones
US10454802B2 (en) * 2015-06-30 2019-10-22 T-Mobile Usa, Inc. Backend polling based on nonzero SIP subscribe expiration
US9913252B2 (en) * 2016-01-11 2018-03-06 Mavenir Systems, Inc. Communication system and method for multi-line, multi-device service with user capability discovery
US10846420B2 (en) * 2018-06-29 2020-11-24 Forcepoint Llc Domain controller agent subscription to kerberos events for reliable transparent identification
JP6712682B1 (en) * 2018-12-25 2020-06-24 楽天株式会社 Arrangement location determination method, transportation system, and information processing apparatus

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1901517A (en) * 2005-07-15 2007-01-24 日本电气株式会社 Information exchange system and management server, terminal device and method for reducing network load

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4644681B2 (en) * 2003-12-05 2011-03-02 リサーチ イン モーション リミテッド Apparatus and method for controlling unnecessary traffic addressed to wireless communication apparatus
US20050210104A1 (en) * 2004-03-19 2005-09-22 Marko Torvinen Method and system for presence enhanced group management and communication
US7607138B2 (en) * 2004-06-17 2009-10-20 Cisco Technology, Inc. System and method for optimizing inter-domain event services
US7796603B1 (en) * 2005-01-14 2010-09-14 Acme Packet, Inc. Method and system for controlling media sessions in networks that use communication protocols with distinct signaling and media channels
US20070033278A1 (en) * 2005-08-08 2007-02-08 Kelley Sean S Method and apparatus for providing a list-based service
US9392069B2 (en) * 2005-11-18 2016-07-12 Aol Inc. Promoting interoperability of presence-based systems through the use of ubiquitous online identities
US20080005294A1 (en) * 2006-06-30 2008-01-03 Morris Robert P Method and system for exchanging messages using a presence service
US20090054039A1 (en) * 2007-02-21 2009-02-26 Van Wijk Jacques Methods and Systems for Presence-Based Filtering of Notifications of Newly-Received Personal Information Manager Data

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1901517A (en) * 2005-07-15 2007-01-24 日本电气株式会社 Information exchange system and management server, terminal device and method for reducing network load

Also Published As

Publication number Publication date
WO2008115100A1 (en) 2008-09-25
US20100094952A1 (en) 2010-04-15
CN101636999A (en) 2010-01-27
EP2127306A1 (en) 2009-12-02

Similar Documents

Publication Publication Date Title
CN101636999B (en) Methods and apparatus for notifying clients in communication network
CN101558623B (en) A method and arrangement for handling a subscription for client data
JP4215645B2 (en) Service access and conference system and method in communication network
CN101355797B (en) Method for obtaining user terminal equipment information and communication service function entity
US8068866B2 (en) Group communication server
JP5436571B2 (en) Method and apparatus for providing communication history
KR101181001B1 (en) Method and system for Joining Chat PoC Group Session by Invitation Reservation
US8054843B2 (en) Method for securing privacy in automatic answer mode of push-to service
US20060035656A1 (en) Method and system for merging multiple push-to-talk over cellular sessions
CN100580655C (en) Method and system for determining server having controlling function
US9392070B2 (en) Method and arrangement for handling resource data
WO2007076673A1 (en) A method, system and device for sharing presence information
CN101171822A (en) A method and arrangement for handling client-related information in an application server
EP2178247B1 (en) Sharing status information across a pluarlity of communication networks
JP2008517396A (en) Server determining method and system having control function
EP2396940B1 (en) A method and an arrangement for handling resource data
US8229454B1 (en) Personal location information management
WO2009054661A1 (en) Procedure for managing data synchronization under multiple devices environment
JP5304700B2 (en) Status notification method and communication system
EP1983725B1 (en) Information delivery system and information delivery method using the same
TW201021490A (en) System and method for re-publication of information in a network-based communication system
WO2007083876A1 (en) Session invitation reservation method in sip based communication service
KR20080013703A (en) Method for securing privacy in the automatic answer mode of push-to service
KR20090042124A (en) Procedure for managing data synchronization under multiple devices environment
WO2010075870A1 (en) Filtering of user availability information

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant
CF01 Termination of patent right due to non-payment of annual fee
CF01 Termination of patent right due to non-payment of annual fee

Granted publication date: 20121107

Termination date: 20200319