WO2006118529A2 - A method and arrangement for handling client-related information in an application server - Google Patents
A method and arrangement for handling client-related information in an application server Download PDFInfo
- Publication number
- WO2006118529A2 WO2006118529A2 PCT/SE2006/000525 SE2006000525W WO2006118529A2 WO 2006118529 A2 WO2006118529 A2 WO 2006118529A2 SE 2006000525 W SE2006000525 W SE 2006000525W WO 2006118529 A2 WO2006118529 A2 WO 2006118529A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- client
- registration
- application server
- message
- validity
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
-
- 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/14—Session management
-
- 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/14—Session management
- H04L67/147—Signalling methods or messages providing extensions to protocols defined by standardisation
-
- 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/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
Definitions
- the present invention relates generally to a method and arrangement for handling client-related information in an application server connected to a telecommunication network.
- the invention is concerned with reducing the amount of signalling when a client state is maintained in the application server.
- IP Internet Protocol
- IMS Multimedia Subsystem
- 3GPP 3 rd Generation Partnership Project
- IMS is a platform for enabling services based on IP transport, more or less independent of the access technology used and basically not restricted to any limited set of specific services.
- a specification for session setup has been defined called "SIP” (Session Initiation Protocol, according to the standard IETF RFC 3261 et al) , which is an application-layer control (signalling) protocol for creating, modifying and terminating sessions over a packet-switched logic.
- SIP Session Initiation Protocol, according to the standard IETF RFC 3261 et al
- SIP Session Initiation Protocol
- Fig. 1 illustrates schematically a basic network structure for providing multimedia services by means of an IMS service network. It should be noted that the figure is greatly simplified and only shows a selection of network nodes helpful to understand the context of the present invention.
- a calling mobile terminal A is connected to a first radio access network 100 and communicates with a called mobile terminal B connected to a second radio access network 102, in a communication session S involving one or more multimedia services.
- terminal A may communicate with a fixed terminal or computer or a content server delivering some multimedia content to the terminal, such as a piece of music, a film or a game.
- An IMS network 104 is connected to the first radio access network 100 and handles the session with respect to terminal A, as initiated by its user.
- the IMS network 104 receives and processes any service requests or data from the user of terminal A.
- a corresponding IMS network 106 handles the session on behalf of terminal B, and the two IMS networks 104 and 106 may be controlled by different operators.
- the IMS network 106 receives and processes any service requests or data from the user of terminal B.
- terminals A and B may of course be connected to the same access network and/or belong to the same IMS network.
- the illustrated session S is managed, using SIP signalling, by a node called S-CSCF (Serving Call Session Control Function) 108 assigned to terminal A in the IMS network 104, and the used multimedia service is enabled and executed by an application server 110.
- S-CSCF Serving Call Session Control Function
- the S-CSCF node 108 serves as a proxy for the application server 110 towards terminal A and sends SIP messages from terminal A to the IMS network 106 of terminal B, as indicated by a dashed arrow.
- a main database element HSS (Home Subscriber Server) 112 stores subscriber and authentication data as well as service information, among other things, that the application server 110 may need to fetch for executing services for clients.
- HSS Home Subscriber Server
- the S-CSCF node 108 fetches information from the HSS 112 to determine which application server 110 to handle a service requested by terminal A, as determined by "triggers" in the HSS 112.
- I-CSCF Interrogating Call Session Control Function
- P-CSCF Proxy Call Session Control Function
- the IMS network 104 contains numerous other nodes and functions, such as further S-CSCF nodes and application servers, which are not shown here for the sake of . simplicity.
- the IMS network 106 comprises the same type of nodes as network 104.
- the shown application server 110 may be configured to provide one or more specific multimedia services to clients.
- IM Instant Messaging
- Presence is basically a dynamic and variable state profile of a client
- the presence services basically involve the publishing of "presence data” of a client to make it available for other users, which furthermore can be used to control other services in turn.
- Presence data basically defines the state of a client and his/her equipment in any predefined respect.
- a personal status e.g. available, busy, in a meeting, on holiday, etc.
- a terminal status e.g. switched on/off, engaged, out of coverage, etc.
- the geographic location of the client/terminal The geographic location of the client/terminal.
- Terminal capabilities e.g. functionality for SMS, MMS, chat, IM, video, etc.
- Terminal selections e.g. call forwarding, language, etc.
- Other client information e.g. interests, occupations, personal characteristics, moods, personal logos, logo depending on the current mood, etc.
- This information, or any selected parts thereof, is stored in an application server in the IMS network, based on so-called "publications of events" received from the network or a client, whenever the client changes any of his/her presence data.
- a client may also subscribe for selected presence data of one or more other users, e.g. according to a list of users.
- Such presence subscriptions are typically also handled by an application server in the IMS network.
- a SIP message called "SIP PUBLISH” is generally used by clients, or rather “User Agent Clients (UAC)", to upload dynamic data to an application server in the IMS network. Publication of data can be used by any service for this purpose, such as PoC, IM, and Presence services.
- Another SIP message called “SIP SUBSCRIBE” is used by clients to subscribe for dynamic data of other clients, as handled by the application server.
- client state will be used to represent the maintenance of client-related information in an application server during a limited time period as determined by a pre- set expiry time, sometimes referred to as TTL (Time To Live) .
- TTL Time To Live
- Such client-related information may relate to published client data or a client' s subscription for data of other users.
- these services may result in a large amount of messages that are sent from clients towards the IMS network, in particular for Presence services.
- a client state for published client data or requested data subscriptions must have an expiry time, such that the published data or data subscription becomes invalid as the time expires. If no expiry time is provided by the client, the application server will use a default expiry- time, typically one hour in the Presence case. In the current service implementation and according to the different standards of IETF, 3GPP and OMA, the data publication or subscription must be frequently refreshed in order to maintain the data/subscription valid in the application server, even if the data/subscription is not changed during this period.
- a client terminal 200 has been powered-on by its user and is currently connected to an access network, not shown, in order to communicate with other terminals and also with a multimedia service network 202, such as an IMS network as described above.
- the service network 202 includes, among other nodes and components, a "registration unit" 204, an application server 206 and an HSS 208, e.g. in accordance with the IMS network shown in Fig. 1.
- the registration unit 204 may thus be an S-CSCF node as described above, and generally handles the client's registration with the service network 202.
- a temporary IP address has been assigned to the terminal such that the terminal can generally communicate over IP.
- terminal 200 sends a registration request message to registration unit 204, in order to become registered as an active terminal in the service network 202.
- the terminal becomes registered in the HSS 208, as indicated in a step 2:2, according to conventional routines, not further described here.
- the terminal is obliged to refresh the registration by frequently sending "re-register" messages or the like to the registration unit 204, as generally indicated by dashed arrows 2:3.
- a re-register message must be sent every 30-60 minutes in order to maintain the registration.
- terminal 200 sends a client data publication message, e.g. a SIP PUBLISH message, to application server 206, in a step 2:4.
- Application server 206 will then store the new client data, which will remain valid during a time-out period, e.g. set to 30 minutes or one hour.
- the client data publication message results in the activation of a "client state" in the application server 206 during which the published data is valid.
- the terminal In order to maintain this client state, i.e. the published data, in the application server 206, the terminal must refresh the published data by frequently sending a "re-publish" message before the time- out period expires, as generally indicated by dashed arrows 2:5, even if the data has not changed. If a client has a multitude of various active client states in the network 104, the burden of sending such refreshing messages can be significant. If the terminal 200 is eventually turned off, a
- “de-register” message is finally sent to the registration unit 204, in a step 2:6.
- the terminal is also obliged to send a "de-publish” message, not shown, to the application server 206 to inactivate the published data. Otherwise, the published data will remain valid in the application server 206 until the time-out period finally expires, as from the last re-publish message was sent, even though the terminal has been turned off. This may result in irrelevant active client states after the client has logged off and until the TTL has expired. In particular, this would be the case if terminal 200 accidentally looses its radio connection, e.g. due to battery failure, thereby preventing the sending of a de-publish message.
- the same procedure would be used when the client sends a subscription request for data of other clients, as described above.
- the message of step 2:4 would be a subscription request message, e.g. a SIP SUBSCRIBE message, resulting in the activation of another client state in the application server 206.
- the refreshing messages of step 2:5 would be a frequently-sent "re-subscribe" message in order to maintain this client state.
- the client's terminal 200 frequently sending re- publish and/or re-subscribe messages, as explained below.
- the client must either refresh the published data or data subscription with quite high frequency, or increase the expiry time for the published data, for the following reasons.
- a client state e.g. published data or a data subscription
- a major reason for having a short expiry time is also the fact that the application server 206 will not know whether a client has been shut down without sending a de-publish or de-subscribe message to change the state of the data or subscription to "off".
- the client state is then maintained in vain and unnecessary notifications may be frequently sent towards a terminal that cannot receive them but still has an active subscription for data of other clients, until the TTL expires.
- the object of the present invention is to address at least some of the problems outlined above.
- it is an object to enable reduced signalling load from clients having active client states in application servers.
- Another object is to enable that client-related information in an application server can be kept up-to-date using a minimum of signalling messages.
- the message received from the client may include the publication of client data or a subscription request for client data, or may be a session initiation message, e.g. SIP INVITE.
- Monitoring registration events may include creating a subscription for registration events, or registration events of a third party may be monitored.
- the received registration event notification typically indicates that the client's registration with the telecommunication network has been inactivated.
- the client's registration may have been inactivated when receiving a de- register message from the client.
- the client's registration with the telecommunication network has a limited time of validity and the client' s registration with the telecommunication network may have been inactivated when the time of registration validity has expired.
- the client state is preferably inactivated in the application server in response to inactivation of the client's registration with the telecommunication network.
- the client state in the application server has a limited time of validity, and the expiry time of client state validity is then preferably set significantly longer than the expiry time of registration validity.
- the expiry time of state validity may be set to at least 10 times the expiry time of registration validity.
- the telecommunication network may be an IMS network, and said registration event notification is then received from an S-CSCF node that handles the client's registration with said IMS network.
- SIP is used for communicating messages with the client.
- An arrangement in an application server connected to a telecommunication network, for handling client-related information for a client who has registered with said telecommunication network, is also provided.
- the arrangement includes means for receiving a message from the client that results in the activation of a client state in the application server, means for monitoring registration events, i.e. events when said client registration is changed, means for receiving a registration event notification concerning the client, and means for updating said client state in response to the received registration event notification.
- the arrangement may further comprise means for receiving said message from the client including the publication of client data, means for receiving said message from the client including a subscription request for client data, and means for receiving said message from the client as a session initiation message, e.g. SIP INVITE.
- the means for monitoring registration events may be adapted to create a subscription for registration events, or to monitor registration events of a third party.
- the arrangement may further comprise means for receiving said registration event notification indicating that the client's registration with said service network has been inactivated.
- the client's registration with said service network may have been inactivated when receiving a de-register message from the client.
- the client's registration with said service network has a limited time of validity, and the client's registration with said service network may have been inactivated when the time of registration validity has expired.
- the arrangement may further comprise means for inactivating said client state in response to inactivation of the client' s registration with the telecommunication network.
- the client state in the application server has a limited time of validity.
- the arrangement may then further comprise means for setting the expiry time of client state validity significantly longer than the expiry time of registration validity, and preferably means for setting the expiry time of client state validity to at least 10 times the expiry time of registration validity.
- the telecommunication network is typically an IMS network, and said registration event notification is then received from an S-CSCF node that handles the client's registration with said IMS network.
- SIP is used for communicating messages with the client.
- Fig. 1 is a schematic overview of a basic communication scenario in which the present invention can be used.
- Fig. 2 is a block diagram illustrating a conventional procedure for maintaining client data in an application server.
- - Fig. 3 is a block diagram illustrating a procedure for handling client-related information in an application server, in accordance with one embodiment.
- Fig. 4 is a signalling diagram illustrating a procedure for maintaining client data, in accordance with another embodiment .
- the present solution can utilise the existing routine of the client sending re-registration messages to a registration unit, e.g. as described in step 2:3 of Fig. 2 above, to also "refresh" any client states activated in an application server, e.g. for published data or data subscriptions.
- a registration unit e.g. as described in step 2:3 of Fig. 2 above
- any client states activated in an application server e.g. for published data or data subscriptions.
- published data or data subscriptions can be automatically refreshed without having the client frequently sending specific re-publish and re- subscribe messages to the application server.
- terminal 200 sends a registration request message in a first step 3:1, and the terminal is registered in the HSS 208 in a next step 3:2. Further, it is still required that the terminal frequently sends re-registration messages to the registration unit 204, indicated by a step 3:3, in order to keep the registration "alive" and valid.
- terminal 200 sends a message to application server 206, in a step 3:4, that generally results in the activation of a client state in the application server.
- this message is typically a client data publication message or a data subscription request message, but may also be a session initiation message, e.g. SIP INVITE, if the session remains active for a long time.
- Application server 206 will then maintain a client state involving some client-related information, typically relating to published data or a subscription for data.
- the application server 206 starts to monitor registration events related to the client's registration.
- the application server 206 sends a subscription request for registration events to the registration unit 204, in a step 3:5.
- registration events of a third party may be monitored.
- registration events refers to any events when the client registration is changed, as handled by the registration unit 204 in this example.
- One important registration event is when the client has sent a de-register message, as in step 2:6 of Fig. 2 above, and the client's registration is consequently inactivated in the service network 202.
- the client's registration may also be inactivated if no refreshing re- registration messages has been received during the latest time-out period, e.g. due to lost radio contact or empty battery.
- the registration unit 204 receives a de- register message from the client 200, in a step 3:6, it will send a registration event notification concerning the client to the application server 206, in a next step 3:7, informing the application server that the client is no longer registered as active in the service network 202.
- the same registration event notification may be sent if the registration has timed-out without being refreshed.
- the application server 206 will finally update the client state in response to the received registration event notification. Typically, it will inactivate the client state in response to inactivation of the client's registration with the service network.
- the terminal is not required to refresh the published data by frequently sending a "re- publish" message, although it may of course send further publish messages, as in step 3:4, whenever the published data has changed.
- the application server can now rely on registration event notifications from the registration unit 204 for controlling the client state, the expiry time for the client state can be set very long to ensure that practically no refreshing re-publish or re-subscribe messages are sent from the client 200.
- the expiry time for the client state is set significantly longer than the expiry time for the client registration, e.g. 10 times or more. This will significantly decrease the amount of signalling from the client, and the client-related information stored in the application server will still be kept up-to-date.
- the client may still send a specific de-publish or de-subscribe message, not shown, to the application server 206 to inactivate the client state, which however does not affect the present inventive solution.
- FIG. 4 An exemplary signalling procedure according to a preferred embodiment will now be described for a client publishing data, with reference to Fig. 4.
- the figure shows a User Agent Client UAC 400a operating in a client terminal, a registration unit 400b, an HSS 400c and an application server 40Od, which may all be equal to the corresponding elements in Fig. 3.
- SIP signalling is used in an IMS network. It should be noted that in an IMS network, basically all the signalling with the client is actually handled by a P-CSCF node, as described in the background section, although omitted in this figure for the sake of simplicity.
- a User Agent Client UAC When the client starts his/her terminal 400a, a User Agent Client UAC therein will send a SIP REGISTER message to the registration unit 400b, in a first step 402, to register a "Public User Identity, PUI" and tie it to the IP-address assigned to the terminal.
- the UAC 400a is registered in the network by means of a signalling dialog between the registration unit 400b and the HSS 400c, as schematically illustrated in a step 404.
- registration unit 400b After establishing the client's registration, registration unit 400b sends a SIP 200 OK message to UAC 400a, in a step 406.
- the UAC 400a will also frequently send refresh REGISTER messages, not shown, to the registration unit 400b to maintain the registration.
- the registration unit 400b will keep the registration active and use a timer function determining when the registered PUI shall be de-registered if the timer has expired. When the registration has expired, that PUI is unavailable for communication on that device.
- a UAC wants to initiate, modify or remove data on application server 40Od, generally referred to as the publishing of data, it will send a new PUBLISH message to the application server 40Od. It should be noted that several different UACs may use the same terminal, and any of those can send PUBLISH messages to initiate or modify its particular service data.
- an initial SIP PUBLISH message is sent from UAC 400a for a certain PUI to the application server 40Od.
- application server 40Od initiates a subscription for registration events, by sending a subscription request, SIP SUBSCRIBE (reg. Events), in a step 410 to the registration unit 400b, in order to be informed on any changes in the registration state of the PUI.
- SIP SUBSCRIBE subscribed to the registration unit 400b
- the registration unit 400b may use third party registrations to always send registration events to the application server 40Od.
- the application server 40Od will now know when a PUI has been de-registered since the registration unit 400b has a time-out function related to the registration TTL, without requiring the UAC to send re-PUBLISH messages.
- application server 40Od may only subscribe for de-registering events, since there is- no point for the application server 40Od to be informed about registration refreshing messages.
- the application server 40Od needs no active timer for the published data at all, since it can safely trust that it will be informed by the registration unit 400b if a de-registration occurs.
- the UAC 400a may still send PUBLISH messages to the application server 40Od as usual whenever the state of the published data needs to be changed, as indicated by optional steps 412.
- a SIP REGISTER (off) message is sent from UAC 400a to the registration unit 400b in a step 414.
- the published data is then invalidated as registration unit 400b sends a SIP NOTIFY (reg. Event (off)) message to application server 40Od, in a final step 416.
- SIP NOTIFY Reg. Event (off)
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2008509977A JP5100637B2 (en) | 2005-05-04 | 2006-05-02 | Method and apparatus for processing client related information in an application server |
CA002604652A CA2604652A1 (en) | 2005-05-04 | 2006-05-02 | A method and arrangement for handling client-related information in an application server |
US11/913,139 US20080172486A1 (en) | 2005-05-04 | 2006-05-02 | Method and Arrangement for Handling Client-Related Information in an Application Server |
NO20076247A NO20076247L (en) | 2005-05-04 | 2007-12-04 | Method and apparatus for handling client-related information in an application server |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
SE0501043-4 | 2005-05-04 | ||
SE0501043 | 2005-05-04 | ||
EP05445042A EP1720320B1 (en) | 2005-05-04 | 2005-06-09 | A method and arrangement for handling client-related information in an application server |
EP05445042.4 | 2005-06-09 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2006118529A2 true WO2006118529A2 (en) | 2006-11-09 |
WO2006118529A3 WO2006118529A3 (en) | 2007-01-18 |
Family
ID=37308410
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/SE2006/000525 WO2006118529A2 (en) | 2005-05-04 | 2006-05-02 | A method and arrangement for handling client-related information in an application server |
Country Status (3)
Country | Link |
---|---|
KR (1) | KR20080003397A (en) |
CA (1) | CA2604652A1 (en) |
WO (1) | WO2006118529A2 (en) |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2009063474A1 (en) * | 2007-11-14 | 2009-05-22 | Lucent Technologies Inc | A method and system for the automatic extension of registration period in an ims network |
US8250234B2 (en) | 2010-04-26 | 2012-08-21 | Microsoft Corporation | Hierarchically disassembling messages |
US8505030B2 (en) | 2007-11-16 | 2013-08-06 | Microsoft Corporation | Coordinating resources using a volatile network intermediary |
US8549538B2 (en) | 2010-03-18 | 2013-10-01 | Microsoft Corporation | Coordinating communication medium state for subtasks |
US8683030B2 (en) | 2009-06-15 | 2014-03-25 | Microsoft Corporation | Routing of pooled messages via an intermediary |
US8719841B2 (en) | 2007-11-16 | 2014-05-06 | Microsoft Corporation | Dispatch mechanism for coordinating application and communication medium state |
US9021503B2 (en) | 2007-11-16 | 2015-04-28 | Microsoft Technology Licensing, Llc | Coordinating application state and communication medium state |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040122896A1 (en) * | 2002-12-24 | 2004-06-24 | Christophe Gourraud | Transmission of application information and commands using presence technology |
EP1492307A1 (en) * | 2003-06-27 | 2004-12-29 | Hewlett-Packard Development Company, L.P. | Method and apparatus for automatically determining a presence status |
WO2005011298A2 (en) * | 2003-07-11 | 2005-02-03 | Motorola, Inc. , A Corporation Of The State Of Delaware | Wireless communications network and method for enabling wireless presence-based services |
EP1675353A1 (en) * | 2004-12-21 | 2006-06-28 | Alcatel | Scalable presence distribution system and method |
-
2006
- 2006-05-02 WO PCT/SE2006/000525 patent/WO2006118529A2/en active Application Filing
- 2006-05-02 CA CA002604652A patent/CA2604652A1/en not_active Abandoned
- 2006-05-02 KR KR1020077025494A patent/KR20080003397A/en not_active Application Discontinuation
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040122896A1 (en) * | 2002-12-24 | 2004-06-24 | Christophe Gourraud | Transmission of application information and commands using presence technology |
EP1492307A1 (en) * | 2003-06-27 | 2004-12-29 | Hewlett-Packard Development Company, L.P. | Method and apparatus for automatically determining a presence status |
WO2005011298A2 (en) * | 2003-07-11 | 2005-02-03 | Motorola, Inc. , A Corporation Of The State Of Delaware | Wireless communications network and method for enabling wireless presence-based services |
EP1675353A1 (en) * | 2004-12-21 | 2006-06-28 | Alcatel | Scalable presence distribution system and method |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2009063474A1 (en) * | 2007-11-14 | 2009-05-22 | Lucent Technologies Inc | A method and system for the automatic extension of registration period in an ims network |
US8505030B2 (en) | 2007-11-16 | 2013-08-06 | Microsoft Corporation | Coordinating resources using a volatile network intermediary |
US8719841B2 (en) | 2007-11-16 | 2014-05-06 | Microsoft Corporation | Dispatch mechanism for coordinating application and communication medium state |
US9021503B2 (en) | 2007-11-16 | 2015-04-28 | Microsoft Technology Licensing, Llc | Coordinating application state and communication medium state |
US8683030B2 (en) | 2009-06-15 | 2014-03-25 | Microsoft Corporation | Routing of pooled messages via an intermediary |
US8549538B2 (en) | 2010-03-18 | 2013-10-01 | Microsoft Corporation | Coordinating communication medium state for subtasks |
US8250234B2 (en) | 2010-04-26 | 2012-08-21 | Microsoft Corporation | Hierarchically disassembling messages |
US9015341B2 (en) | 2010-04-26 | 2015-04-21 | Microsoft Technology Licensing, Llc | Hierarchically disassembling messages |
Also Published As
Publication number | Publication date |
---|---|
KR20080003397A (en) | 2008-01-07 |
WO2006118529A3 (en) | 2007-01-18 |
CA2604652A1 (en) | 2006-11-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1720320B1 (en) | A method and arrangement for handling client-related information in an application server | |
US8589496B2 (en) | Method and arrangement for handling a subscription for client data | |
EP2096823B1 (en) | Methods and apparatus for registering a user to an IMS on the user's behalf by a SIP Application Server | |
US7853697B2 (en) | Handling suspended network state of a terminal device | |
US20040205212A1 (en) | Method and system for forwarding a service-related information to a network user | |
US8477688B2 (en) | Method, system and apparatus for notifying as of user state | |
US9392070B2 (en) | Method and arrangement for handling resource data | |
EP1875705B1 (en) | Message handling in an ip multimedia subsystem | |
US20100094952A1 (en) | Method and Apparatus for Notifying Clients in a Communication Network | |
WO2006118529A2 (en) | A method and arrangement for handling client-related information in an application server | |
EP2092686A1 (en) | A method and arrangement for handling client data | |
WO2009025509A2 (en) | System and method for controlling sip-specific event notification according to preference of subscriber | |
EP1925140B1 (en) | Method and apparatus for keeping information up to date at an ims client | |
US8630292B2 (en) | Method and system for distributing a multi-service message from a client to multiple related service applications | |
US9426711B2 (en) | Traffic control within an IP multimedia subsystem |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 200680014856.8 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
DPE1 | Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101) | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2604652 Country of ref document: CA |
|
ENP | Entry into the national phase |
Ref document number: 2008509977 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 8418/DELNP/2007 Country of ref document: IN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020077025494 Country of ref document: KR |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 11913139 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: RU |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 06733380 Country of ref document: EP Kind code of ref document: A2 |