WO2003019918A1 - Service mobility and recovery in communication networks - Google Patents

Service mobility and recovery in communication networks Download PDF

Info

Publication number
WO2003019918A1
WO2003019918A1 PCT/IB2002/003370 IB0203370W WO03019918A1 WO 2003019918 A1 WO2003019918 A1 WO 2003019918A1 IB 0203370 W IB0203370 W IB 0203370W WO 03019918 A1 WO03019918 A1 WO 03019918A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
terminal
sip
message
communication services
Prior art date
Application number
PCT/IB2002/003370
Other languages
French (fr)
Inventor
Petri Koskelainen
Original Assignee
Nokia Corporation
Nokia Inc.
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 Nokia Corporation, Nokia Inc. filed Critical Nokia Corporation
Priority to EP02767742A priority Critical patent/EP1419646A1/en
Publication of WO2003019918A1 publication Critical patent/WO2003019918A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/04Arrangements for maintaining operational condition
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/18Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data

Definitions

  • the present invention relates generally to the field of communications.
  • the invention relates to the mobility and recovery of communication services for user terminals in a wireless communication network.
  • a wireless communication network is typically comprised of several major portions: a plurality of mobile terminals (such as cellular phones), subscriber information, a radio access network, a switching system and network intelligence (primarily databases).
  • Each mobile terminal contains an electronic card identifying the user, such as a subscriber identity module (SIM) in Global System for Mobile Communications (GSM) networks, or has some other arrangement permitting the user to communicate over the radio access network.
  • SIM subscriber identity module
  • GSM Global System for Mobile Communications
  • the network contains a variety of elements and databases that contain customer information to check authorization for various communication services (e.g., voice, messaging, data and image services) and to process features in accordance with the communication services.
  • the switching system connects mobile terminals to other mobile terminals in the same network or to elements in other networks such as the Internet.
  • Third-generation (3G) wireless communication networks support advanced mobile terminals and allow a user to subscribe to and access a large number of different communication services.
  • An advanced mobile terminal supported by such a network and using the latest innovations in computers, software, displays and other technologies may access and receive many different advanced multimedia services in addition to conventional voice-based telephony services.
  • These services may be provided by different information sources in other networks and may be based on and built upon Internet applications (e.g., Internet web browsing, video streaming, instant messaging, etc.).
  • the services may include both pull services in which the specific transfer of information is initiated by the mobile terminal (i.e., web browsing, etc.) and push services in which the specific transfer of information is initiated by a network element (instant messaging, sports scores, news updates, etc.).
  • FIG. 1 depicts a general overall view of the main elements providing communication services in an IMS 100. (This depiction shows the functional architecture rather than a physical implementation.)
  • the Home Subscriber Server (HSS) 102 contains user related information such as user identification (UserlD), numbering, address information, and a user profile including, for example, subscription information, services and service specific information.
  • the Serving Call Session Control Function (S-CSCF) 101 provides call control, session control and service control for mobile terminals.
  • S-CSCF Serving Call Session Control Function
  • the visited network When a mobile terminal is visiting a network other than its home network, the visited network preferably utilizes a Proxy Call Session Control Function (P- CSCF) that enables the session control to be passed to the home network based S-CSCF providing service control for the mobile terminal.
  • P- CSCF Proxy Call Session Control Function
  • the communication services may be provided by an Application Server 103 within IMS 100 and connected directly to S-CSCF 101 or by an application server in another network or on the Internet, such as an Open Services Architecture (OSA) Application Server 105 connected to S-CSCF 101 indirectly through an OSA application programming interface (API) to OSA Service Capability Server (SCS) 104.
  • OSA Open Services Architecture
  • API OSA application programming interface
  • SCS OSA Service Capability Server
  • S-CSCF 101 utilizes the Session Initiation Protocol (SIP) developed by the Internet Engineering Task Force (IETF) or an extension or backward compatible revision thereof for all connections to other network elements.
  • SIP Session Initiation Protocol
  • IETF Internet Engineering Task Force
  • HTTP HyperText Transfer Protocol
  • SIP supports an advantageous event notification scheme.
  • the client such as a mobile terminal, sends a SUBSCRIBE message to a remote element, such as a server, indicating that it wants to receive a notification from the remote element when a specific event has occurred.
  • the SUBSCRIBE message includes To, From and Call-ID headers and an event header to indicate the specific event.
  • the provider of a communication service designates the event name (i.e., "soccer") for its service
  • a NOTIFY message is sent to the client.
  • the NOTIFY message copies the To, From and Call-ID headers from the SUBSCRIBE message and the content format is event specific and defined separately for each event.
  • the content format is extensible Markup Language (XML) format.
  • SIP is advantageous in wireless communication networks because the event notification scheme can utilize a SIP proxy network and SIP registrars.
  • a client subscribes to events using its SIP Uniform Resource Locater (URL) maintained by the SIP registrar instead of the direct contact address (e.g. numeric terminal IP address).
  • SIP Uniform Resource Locater URL
  • the requirement that the NOTIFY message must copy the To, From and Call-ID headers from the SUBSCRIBE message provides reasonable protection against spammers and other unwanted notifications.
  • the client can be set to accept only those NOTIFY messages which have the correct To, From and Call-ID headers.
  • HSS 102 of IMS 100 stores all of the subscription information necessary for user terminals and informs S-CSCF 101 whenever the subscription information changes for a user.
  • the subscription information in HSS 102 is used by S-CSCF 101 whenever the user visits another access network or uses a different terminal.
  • certain information generated by the mobile terminal e.g., To, From and Call- ID header information and Event name from SUBSCRIBE messages
  • the user terminal cannot filter incoming NOTIFY messages and prevent against spamming, etc.
  • the parameters and/or settings may include for instance communication networks parameters, such as General Packet Radio Service (GPRS) parameters or Universal Mobile Telecommunication System (UMTS) parameters, Wireless Application Protocol (WAP) parameters comprising a WAP Gateway address a Uniform Resource Locator (URL) for setup, a home page and favorites, World Wide Web (WWW) parameters comprising a Hyper Text Transfer Protocol (HTTP) proxy address, SMTP/POP3 addresses, public keys, Ipv4, Ipv6, and a Default Classmark for multi-classmark devices.
  • GPRS General Packet Radio Service
  • UMTS Universal Mobile Telecommunication System
  • WAP Wireless Application Protocol
  • WAP Gateway address a Uniform Resource Locator
  • URL Uniform Resource Locator
  • WWW World Wide Web
  • HTTP Hyper Text Transfer Protocol
  • SMTP/POP3 addresses public keys
  • Ipv4, Ipv6, and a Default Classmark for multi-classmark devices.
  • There may also be general information, such as network subscription and authorization information or calling plan information or lists
  • a user may need or prefer to user different terminals to receive different subscription services, possibly having different quality of service (QoS) requirements, on different respective mobile terminals that are better suited to receiving certain types of services.
  • QoS quality of service
  • a user may prefer to use a cellular phone for receiving phone calls and short alphanumeric text messages and to use a laptop computer, with a wireless connection, to receive streaming video.
  • a user may also need or prefer to use different terminals, for example, when receiving services through different access networks such as, for example, wireless local area networks (WLAN), Bluetooth networks or 3G WCDMA radio networks.
  • WLAN wireless local area networks
  • Bluetooth networks or 3G WCDMA radio networks.
  • a user may also simply want to exchange an older mobile terminal in favor of a newer model. In any event, there is a need to allow a user of a new terminal to easily obtain the information stored in a previous terminal when switching to the new terminal.
  • the example embodiments provide a solution which facilitates mobility and service recovery when there is a failure in a user's terminal or when the user switches between different terminals in a wireless communication network supporting many different types of communications services.
  • the information necessary for providing mobility and service recovery for users' communication services is maintained in a server rather than in the users' terminals.
  • a user terminal communicates with the server as desired to manage the communication services such as by requesting that the information be provided to the user terminal.
  • a particular aspect of the example embodiments involves an extension to SIP event notifications that allows fast service recovery (e.g., if a terminal fails) and mobility between different terminals by requesting that communication services be restored by a SIP registrar.
  • the terminal initiates the process by sending a specially designated SIP event notification message to the SIP registrar.
  • the SIP registrar re-registers the user with all of their ongoing communication services and includes information of all of the user's ongoing communication services in the payload of a message sent to the user terminal so that the user terminal may continue those communication services and manage them.
  • the message sent to the user terminal may also include additional information useful or necessary for communication services other than SIP communication services.
  • a particularly useful application of the example embodiments is for push services in which a specific transfer of information to the user terminal is not initiated by the user terminal.
  • the user terminal exchanges messages with a push proxy which manages the push services provided to the user terminal using status information for the terminal obtained from a presence server with which the user terminal is registered.
  • the push proxy re-registers the user terminal with push service providers or initiators after the terminal experiences a failure or the user switches terminals and provides information to the new or recovered user terminal so that the new or recovered user terminal can continue to receive the push services.
  • Fig. 1 illustrates the functional architecture of an exemplary IP Multimedia subsystem of a 3G wireless communication network in which the example embodiments may be carried out.
  • Fig. 2 is a flow diagram illustrating the steps performed in a service mobility and recovery method according to the example embodiments.
  • Fig. 3 illustrates the functional architecture of an exemplary network supporting SIP push communication services.
  • Fig. 4 is a flow diagram illustrating the steps performed in a SIP push communication service using the functional architecture shown in Fig. 3.
  • Fig. 5 illustrates an example of a message sent by a user terminal to obtain a push service through a push proxy using SIP event notification.
  • Fig. 6 illustrates a sequence of messages to provide for a push service through a push proxy when a user terminal sends a message to obtain a push service using SIP event notification.
  • Fig. 7 illustrates a sequence of messages sent to provide for a communication service to a user terminal, and to register the communication service for the user in a push proxy, when the user terminal sends a message to obtain the communication service.
  • Fig. 8 illustrates a sequence of messages providing for a push service to a user terminal after the user terminal registers with a presence server.
  • Fig. 9 illustrates a message sent by a user terminal to a push proxy to manage ongoing communication services.
  • the example embodiments are applicable for use with all types of cellular networks and local radio networks, including wireless local area networks (WLAN), and interconnected systems using SIP for voice, message, data and image transfers between systems in such networks.
  • WLAN wireless local area networks
  • 3 rd generation GSM networks include data networks using General Packet Radio Service (GPRS) technology for mobile data networking services and personal multimedia services, and Enhanced Data Rates for Global Evolution (EDGE) technology for high bit rate data services.
  • GPRS technology is used in GSM networks to enable users to connect at higher data rates and facilitate applications such as wireless email and web-browsing.
  • EDGE boosts data speeds and allows video and mobile multimedia applications with data rates as high as 473 kbps.
  • BlueTooth networks and/or Wideband CDMA (WCDMA) networks may be used in place of the wireless local area networks (WLAN).
  • WLAN wireless local area networks
  • WCDMA Wideband CDMA
  • the example embodiments use a new, specially designated subscribe message in the SIP event notification scheme to have information made available to a user's terminal.
  • the principles and features of the example embodiments are not restricted in their application to SIP, and can be applied to any messaging protocol providing for subscription messages and notification messages. Attention now is directed to the drawings and particularly to Fig. 2, which shows the flow diagram for a mobility and service recovery method according to the example embodiments, keeping in mind that the example embodiments may be carried out in a variety of different networks.
  • a user terminal must provide some identification to a network in order to gain access and receive communication services.
  • the identification may be anything that uniquely identifies the user, such as a SIM card or telephone number.
  • the user may arrange for a plurality of different communication services. Each individual one of these communications services may be provided by an application server located in the wireless communication network or an applications server located in other networks or on the Internet and delivered through the wireless communication network.
  • the communication services available to the user terminal include at least some SIP services that utilize the SIP event notification scheme.
  • the network contains a SIP registrar for the SIP services.
  • a SIP registrar is any network element that provides the functionality described herein. It may be any one of the application servers, a proxy server for the user terminal, or HSS 102 in IMS 100. It stores address bindings and contains information for the SIP services for users on the network in a database.
  • a user of a mobile terminal is receiving a plurality of ongoing communication services.
  • the user changes mobile terminals so as to change from a previous mobile terminal to a new mobile terminal.
  • the change of terminal may be for any reason.
  • the new mobile terminal sends a SIP SUBSCRIBE message to the SIP registrar according to the SIP event notification scheme.
  • the message is directed through the network and routed to the SIP registrar.
  • the event described by the SIP SUBSCRIBE message is a special event called, for example, "my services", but the message has a format and syntax which is otherwise the same as conventional SIP SUBSCRIBE messages..
  • the user may be identified simultaneously with, or separate from, the SIP subscribe message.
  • the identification information may be provided by the user terminal or by a network element which authenticates the user.
  • the SIP registrar obtains the information for all of the user's ongoing communications services from the database.
  • the database has a variety of information for users' ongoing communication services, preferably indexed or sortable by user identification.
  • the SIP registrar also sends a response 204-r to the SIP SUBSCRIBE message including the "my services" event to the new user terminal.
  • the payload response includes information necessary for the communication services to be received by the new user terminal.
  • the new terminal then examines the payload and determines therefore the data necessary to continue the communication services.
  • the payload may also include related parameters and/or settings necessary to receive the services.
  • the needed parameters and/or settings may include communication network related parameters such as GPRS parameters or UMTS parameters, WAP parameters comprising a WAP Gateway address, a Uniform Resource Locator (URL) for setup, a home page and favorites, WWW parameters comprising an HTTP proxy address, SMTP/POP3 addresses, public keys, Ipv4, Ipv6, and a Default Classmark for multi-classmark devices, software updates, applets, network storage location, a user preference list, firmware updates, etc. There may also be general information, such as network subscription and authorization information or calling plan information or lists of telephone numbers, stored in the user terminal and which is desired to be available to the user to enable or facilitate communications.
  • WAP parameters comprising a WAP Gateway address, a Uniform Resource Locator (URL) for setup, a home page and favorites
  • WWW parameters comprising an HTTP proxy address
  • SMTP/POP3 addresses public keys
  • Ipv4, Ipv6, and a Default Classmark for multi-classmark devices software updates, applets,
  • a push proxy 301 maintains the push services (e.g., user subscriptions, receiving push information from push initiators originating the push information, and sending notifications to users) and acts as a gateway between the user terminal and a plurality of different push initiators 302-1 to 302-n (which may use respectively different push protocols) which forwards/converts push messages to/from a client.
  • push services e.g., user subscriptions, receiving push information from push initiators originating the push information, and sending notifications to users
  • acts as a gateway between the user terminal and a plurality of different push initiators 302-1 to 302-n which forwards/converts push messages to/from a client.
  • a push initiator 302-1 to 302-n may provide push information to push service providers (not shown) using either SIP or another protocol.
  • the push service provider e.g., internet service provider or content provider
  • the push proxy provides information (which may be based, for example, on personal user profiles) and manages push proxy 301 for a user terminal, although the network operator may also provide notifications and advertisements.
  • a push initiator 302-1 to 302-n may be co-located in the push proxy or be combined with the push proxy itself.
  • a user terminal is registered as a client with presence server 303 through HSS 102 associated with IMS 100.
  • Presence server manages information indicating the presence, location and/or status of the user terminal.
  • Push proxy 301 is subscribed to presence server 303 and utilizes the information corresponding to the user as described below. When a user terminal changes its location, it re-registers to its presence server 303 to update its location (and other information). SIP is preferably used for these registrations.
  • Push proxy 301 is notified about the changes in the user status.
  • the push services use the address of push proxy 301 (e.g., user@domain.com) instead of real IP addresses in order to facilitate mobility of the user terminal.
  • the protocol between push proxy 301 and the user terminal and presence server 303 is SIP.
  • the protocol between push proxy 301 and the push initiators 302-1 to 302-n can be SIP or some other protocol, such as HTTP or SMTP as shown in Fig. 3.
  • a user When a user subscribes to a push service, it does so through push proxy 301 using the SIP SUBSCRIBE message or an out-of-band mechanism (e.g., world wide web).
  • the event identified in the SIP SUBSCRIBE message is "Push" and the payload in the SIP SUBSCRIBE message may contain optional XML content defining the user's preferences/policies (e.g., personal interests, terminal capabilities, bandwidth restrictions/preferences, etc.).
  • Fig. 5 shows a SIP SUBSCRIBE message indicating that the user receives no advertisements and the acknowledgement returned by the push proxy.
  • push proxy 301 receives the message from the user terminal (step 1 in Fig. 6), it then subscribes to presence server 303 (step 2 in Fig. 6) and receives a response including information indicating the location/status of the user terminal (step 3 in fig. 6).
  • push proxy 301 forwards a SIP NOTIFY message to the user terminal (step 5) using the information obtained in step 3.
  • presence server 303 receives information of the user terminal as a matter of due course from core network elements CSCF 101 and HSS 102 of IMS 100. If however, as shown in Fig. 8, there is no IMS or these elements are not otherwise available to presence server 303, then the user terminal must directly register with presence server 303, preferably using SIP as shown in step 1 of Fig. 8. The remaining steps can then proceed in the same manner as in Fig. 6.
  • presence server 303 hides the fact of whether there is an IMS or not from push proxy 301.
  • An example of a subscription to a push service according to the example embodiments of the invention is shown in Fig. 7.
  • the SIP SUBSCRIBE message from the user terminal identifies an event ("soccer") and a parameter ("game 1") (step 1).
  • push proxy 301 subscribes to presence server 303 (step 2), it subscribes to push initiator 302-n (step 3) using the same event and parameter as in the user terminal's original SIP SUBSCRIBE message.
  • Push proxy 301 may give additional subscription information to a push service provider such as, for example, the bandwidth for push services, terminal capabilities and personal interests.
  • push proxy 301 adds the event and parameter to the list of existing subscription for the user ("my services") and forwards a SIP NOTIFY message to the user terminal (step 5).
  • push proxy 301 delivers the push information from push initiator 302-n to the user's terminal using the terminal's current location information available to it from the presence server 303. If the user terminal is not available (e.g., it is out of range), push proxy 301 stores information (e.g., based on user preferences) and informs the user later. Push proxy 301 is also responsible for rate control (e.g., allowing a maximum rate of traffic to avoid momentary traffic peaks. If the user is subscribed to two push proxies, then the rate control must be more carefully adjusted (e.g., by advising both push proxies to allow a maximum of half of the total bandwidth capacity available for push services in the user terminal's access link).
  • rate control e.g., allowing a maximum rate of traffic to avoid momentary traffic peaks. If the user is subscribed to two push proxies, then the rate control must be more carefully adjusted (e.g., by advising both push proxies to allow a maximum of half of the total bandwidth capacity available for push services
  • Push information is always delivered to the user terminal using SIP NOTIFY and the same To, From and Call-ID headers in the service subscription.
  • push proxy 301 may utilize several push initiators 302-1 to 302-n and use different protocols (e.g., HTTP, email, SIP, RTP, non-IP protocols) for different push initiators.
  • the payload in the SIP NOTIFY message depends on the push type and the user terminal's capabilities.
  • the SIP NOTIFY message may carry, for example, XML or ascii payload.
  • the SIP NOTIFY payload includes the details of the streaming session. It may be, for example, a URL (e.g., RTSP URL) or SDP (to define a video call).
  • Fig. 4 is a flow diagram illustrating the steps performed in a SIP push communication service using the functional architecture shown in Fig. 3.
  • the user subscribes to the push service by sending a SIP SUBSCRIBE message such as the following to push proxy 301:
  • push proxy 301 responds with a 200 Ok message.
  • push proxy 301 responds with a 200 Ok message.
  • SIP SUBSCRIBE message such as the following to SIP registrar/presence server 303:
  • push proxy 301 immediately sends a SIP NOTIFY such as the following to the user terminal:
  • push proxy 301 subscribes to the push initiator 302-1 on behalf of the user
  • push proxy 301 may have already subscribed to push initiator 302-1 for other users) by sending a SIP SUBSCRIBE message such as the following:
  • Push proxy 301 then waits to receive a 200 Ok message from SIP registrar/presence server 303 in response to the SIP SUBSCRIBE message sent at step 403 and a 200 Ok message from push initiator 302-1 in response to the SIP SUBSCRIBE message sent at step 405 (steps
  • push proxy 301 Upon receipt of the 200 Ok messages in steps 406 and 407, push proxy 301 provides the push information to the user.
  • a message type push service may be provided by sending a SIP NOTIFY message such as the following to the user:
  • a streaming type push service may be provided by sending a SIP NOTIFY message such as the following to the user:
  • the user terminal can easily access all of the service information relating to it stored in push proxy 301 using a simple reference to the "my-services" list.
  • the "my-services" list can be accessed and used by the user terminal to manage subscriptions after the subscriptions have been created.
  • Fig. 9 shows examples of the "my-services" list in a database maintained by push proxy 301.
  • the list may be accessed by a SIP SUBSCRIBE message in which the event name is "my-services".
  • This allows mobility and service recovery for push services using the method illustrated in Fig. 2 and described above. It is particularly advantageous for push services which, from the perspective of the user, are intended to be delivered to the user without any request being made therefore.

Abstract

A method improves mobility and service recovery for a user in a wireless communication network (Fig. 2). Service information concerning the user is stored in a registrar. A subscription message is sent from a user terminal to the registrar. A header in the subscription message contains a unique indication. In response to the subscription message containing a unique indication in a header, the registrar returns a notification message to the user terminal. The payload of the notification message includes service information for the user to be used by the user terminal for communication services.

Description

SERVICE MOBILITY AND RECOVERY IN COMMUNICATION NETWORKS
TECHNICAL FIELD
The present invention relates generally to the field of communications. In particular, the invention relates to the mobility and recovery of communication services for user terminals in a wireless communication network.
BACKGROUND ART
A wireless communication network is typically comprised of several major portions: a plurality of mobile terminals (such as cellular phones), subscriber information, a radio access network, a switching system and network intelligence (primarily databases). Each mobile terminal contains an electronic card identifying the user, such as a subscriber identity module (SIM) in Global System for Mobile Communications (GSM) networks, or has some other arrangement permitting the user to communicate over the radio access network. The network contains a variety of elements and databases that contain customer information to check authorization for various communication services (e.g., voice, messaging, data and image services) and to process features in accordance with the communication services. The switching system connects mobile terminals to other mobile terminals in the same network or to elements in other networks such as the Internet.
Third-generation (3G) wireless communication networks support advanced mobile terminals and allow a user to subscribe to and access a large number of different communication services. An advanced mobile terminal supported by such a network and using the latest innovations in computers, software, displays and other technologies may access and receive many different advanced multimedia services in addition to conventional voice-based telephony services. These services may be provided by different information sources in other networks and may be based on and built upon Internet applications (e.g., Internet web browsing, video streaming, instant messaging, etc.). The services may include both pull services in which the specific transfer of information is initiated by the mobile terminal (i.e., web browsing, etc.) and push services in which the specific transfer of information is initiated by a network element (instant messaging, sports scores, news updates, etc.).
Technical Specification TS 23.228 N5.0.0 of the 3rd Generation Partnership Project (3GPP), discloses a 3G wireless communication network including an Internet Protocol Multimedia Core Network Subsystem (IMS) able to support multimedia communication services and is hereby incorporated by reference in its entirety as an example network environment. Figure 1 depicts a general overall view of the main elements providing communication services in an IMS 100. (This depiction shows the functional architecture rather than a physical implementation.) The Home Subscriber Server (HSS) 102 contains user related information such as user identification (UserlD), numbering, address information, and a user profile including, for example, subscription information, services and service specific information. The Serving Call Session Control Function (S-CSCF) 101 provides call control, session control and service control for mobile terminals. When a mobile terminal is visiting a network other than its home network, the visited network preferably utilizes a Proxy Call Session Control Function (P- CSCF) that enables the session control to be passed to the home network based S-CSCF providing service control for the mobile terminal. The communication services may be provided by an Application Server 103 within IMS 100 and connected directly to S-CSCF 101 or by an application server in another network or on the Internet, such as an Open Services Architecture (OSA) Application Server 105 connected to S-CSCF 101 indirectly through an OSA application programming interface (API) to OSA Service Capability Server (SCS) 104.
Other than the Cx interface to HSS 102, S-CSCF 101 utilizes the Session Initiation Protocol (SIP) developed by the Internet Engineering Task Force (IETF) or an extension or backward compatible revision thereof for all connections to other network elements. Unlike HyperText Transfer Protocol (HTTP), SIP supports an advantageous event notification scheme. In SIP event notification, the client, such as a mobile terminal, sends a SUBSCRIBE message to a remote element, such as a server, indicating that it wants to receive a notification from the remote element when a specific event has occurred. The SUBSCRIBE message includes To, From and Call-ID headers and an event header to indicate the specific event. Typically, the provider of a communication service designates the event name (i.e., "soccer") for its service When the specific event occurs, a NOTIFY message is sent to the client. The NOTIFY message copies the To, From and Call-ID headers from the SUBSCRIBE message and the content format is event specific and defined separately for each event. For example, in a presence case like instant messaging in which the specific event is when a specified person logs into the network, the content format is extensible Markup Language (XML) format. SIP is advantageous in wireless communication networks because the event notification scheme can utilize a SIP proxy network and SIP registrars. In such cases, a client subscribes to events using its SIP Uniform Resource Locater (URL) maintained by the SIP registrar instead of the direct contact address (e.g. numeric terminal IP address). The requirement that the NOTIFY message must copy the To, From and Call-ID headers from the SUBSCRIBE message provides reasonable protection against spammers and other unwanted notifications. The client can be set to accept only those NOTIFY messages which have the correct To, From and Call-ID headers.
However, SIP was developed with data-centric networks in mind rather than voice- centric wireless communications networks where value added services are mostly based on supplementary service and Intelligent Network (IN) architectures. The service framework in voice-centric wireless communication networks is quite static and it is quite difficult to add new advanced features. There are problems and disadvantages to implementing SIP in the supporting network and services for a wireless communication network such as IMS 100 shown in Fig. 1. For example, as mentioned in Part 5.1.5 of TS 23.228, HSS 102 of IMS 100 stores all of the subscription information necessary for user terminals and informs S-CSCF 101 whenever the subscription information changes for a user. Conventionally, the subscription information in HSS 102 is used by S-CSCF 101 whenever the user visits another access network or uses a different terminal. However, in some circumstances, such as the SIP event notification scheme described above, certain information generated by the mobile terminal (e.g., To, From and Call- ID header information and Event name from SUBSCRIBE messages) must be maintained in the user terminal rather than in the server(s) providing the subscription service or some other network element. If this information is not available to a user terminal, then the user terminal cannot filter incoming NOTIFY messages and prevent against spamming, etc. In addition to knowledge about ongoing communication services, there may also be other information, such as numerous parameters and/or settings, needed by the user terminal to receive those communication services. The parameters and/or settings may include for instance communication networks parameters, such as General Packet Radio Service (GPRS) parameters or Universal Mobile Telecommunication System (UMTS) parameters, Wireless Application Protocol (WAP) parameters comprising a WAP Gateway address a Uniform Resource Locator (URL) for setup, a home page and favorites, World Wide Web (WWW) parameters comprising a Hyper Text Transfer Protocol (HTTP) proxy address, SMTP/POP3 addresses, public keys, Ipv4, Ipv6, and a Default Classmark for multi-classmark devices. There may also be general information, such as network subscription and authorization information or calling plan information or lists of telephone numbers, stored in the user terminal and which is desired to be available to the user to enable or facilitate communications.
There may be a problem if the user's terminal malfunctions for any period of time (i.e., the terminal crashes and information is lost before it is stored in a memory device) or the terminal has a failure which causes it to lose any information (i.e., memory failure, loss of backup power, etc). There is thus a need for a solution that allows the user terminal to quickly recover in the case of a crash, etc. Furthermore, if a user switches to a different terminal, the new user terminal will not be able to access the stored information in the previous terminal and thus cannot easily continue to receive the subscription services. A user may switch terminals for any reason. For example, they may need or prefer to user different terminals to receive different subscription services, possibly having different quality of service (QoS) requirements, on different respective mobile terminals that are better suited to receiving certain types of services. For example, a user may prefer to use a cellular phone for receiving phone calls and short alphanumeric text messages and to use a laptop computer, with a wireless connection, to receive streaming video. A user may also need or prefer to use different terminals, for example, when receiving services through different access networks such as, for example, wireless local area networks (WLAN), Bluetooth networks or 3G WCDMA radio networks. A user may also simply want to exchange an older mobile terminal in favor of a newer model. In any event, there is a need to allow a user of a new terminal to easily obtain the information stored in a previous terminal when switching to the new terminal.
Although a user could contact a particular service to inform that service of the user's new terminal, that is inconvenient. Furthermore, there would still be a problem in any event if the user subscribes to many communication services andVor different types of communication services. There is thus a need for a solution that allows the information to be available if a user switches between different terminals. It is possible to have the user install the necessary service information when switching to a new terminal to be used. However, manual input is a poor solution because data input on a mobile terminal can be difficult, prone to human errors, and time-consuming. Even if an automatic system solution is used, when there are a large number or different types of communication services, the amount and types of information, parameters, and/or settings may require several automatic systems and it can be quite time consuming to download over a wireless communication network.
For at least these reasons, there is inadequate mobility and recovery of user services when a user switches between different mobile terminals, such as a cellular telephone, a personal digital assistant (PDA), etc., in a wireless communication network utilizing SIP and supporting may different types of communications services. Accordingly, there is a need for providing an effective solution for mobility and service recovery to a user switching between different terminals in a wireless communication network utilizing SIP and supporting may different types of communications services.
DISCLOSURE OF INVENTION
It is therefore an object of the following described example embodiments to overcome the above mentioned disadvantages. In particular, the example embodiments provide a solution which facilitates mobility and service recovery when there is a failure in a user's terminal or when the user switches between different terminals in a wireless communication network supporting many different types of communications services.
In the example embodiments, the information necessary for providing mobility and service recovery for users' communication services is maintained in a server rather than in the users' terminals. A user terminal communicates with the server as desired to manage the communication services such as by requesting that the information be provided to the user terminal.
A particular aspect of the example embodiments involves an extension to SIP event notifications that allows fast service recovery (e.g., if a terminal fails) and mobility between different terminals by requesting that communication services be restored by a SIP registrar. The terminal initiates the process by sending a specially designated SIP event notification message to the SIP registrar. The SIP registrar re-registers the user with all of their ongoing communication services and includes information of all of the user's ongoing communication services in the payload of a message sent to the user terminal so that the user terminal may continue those communication services and manage them. The message sent to the user terminal may also include additional information useful or necessary for communication services other than SIP communication services.
A particularly useful application of the example embodiments is for push services in which a specific transfer of information to the user terminal is not initiated by the user terminal. The user terminal exchanges messages with a push proxy which manages the push services provided to the user terminal using status information for the terminal obtained from a presence server with which the user terminal is registered. According to the example embodiments, the push proxy re-registers the user terminal with push service providers or initiators after the terminal experiences a failure or the user switches terminals and provides information to the new or recovered user terminal so that the new or recovered user terminal can continue to receive the push services.
BRIEF DESCRIPTION OF THE DRAWINGS
A more complete appreciation of the example embodiments, and many of the attendant advantages thereof, will become readily apparent as the same becomes better understood by reference to the following detailed description when considered in conjunction with the accompanying drawings in which like reference symbols indicate the same or similar components, wherein:
Fig. 1 illustrates the functional architecture of an exemplary IP Multimedia subsystem of a 3G wireless communication network in which the example embodiments may be carried out.
Fig. 2 is a flow diagram illustrating the steps performed in a service mobility and recovery method according to the example embodiments. Fig. 3 illustrates the functional architecture of an exemplary network supporting SIP push communication services.
Fig. 4 is a flow diagram illustrating the steps performed in a SIP push communication service using the functional architecture shown in Fig. 3.
Fig. 5 illustrates an example of a message sent by a user terminal to obtain a push service through a push proxy using SIP event notification.
Fig. 6 illustrates a sequence of messages to provide for a push service through a push proxy when a user terminal sends a message to obtain a push service using SIP event notification.
Fig. 7 illustrates a sequence of messages sent to provide for a communication service to a user terminal, and to register the communication service for the user in a push proxy, when the user terminal sends a message to obtain the communication service.
Fig. 8 illustrates a sequence of messages providing for a push service to a user terminal after the user terminal registers with a presence server.
Fig. 9 illustrates a message sent by a user terminal to a push proxy to manage ongoing communication services.
BEST MODE FOR CARRYING OUT THE INVENTION
The example embodiments are applicable for use with all types of cellular networks and local radio networks, including wireless local area networks (WLAN), and interconnected systems using SIP for voice, message, data and image transfers between systems in such networks. For example, 3rd generation GSM networks include data networks using General Packet Radio Service (GPRS) technology for mobile data networking services and personal multimedia services, and Enhanced Data Rates for Global Evolution (EDGE) technology for high bit rate data services. GPRS technology is used in GSM networks to enable users to connect at higher data rates and facilitate applications such as wireless email and web-browsing. EDGE boosts data speeds and allows video and mobile multimedia applications with data rates as high as 473 kbps. BlueTooth networks and/or Wideband CDMA (WCDMA) networks may be used in place of the wireless local area networks (WLAN). However, for the sake of simplicity, discussions will concentrate mainly on mobility and service recovery in a 3G cellular network such as that described in 3GPP TS 23.228 V5.0.0.
The example embodiments use a new, specially designated subscribe message in the SIP event notification scheme to have information made available to a user's terminal. However, the principles and features of the example embodiments are not restricted in their application to SIP, and can be applied to any messaging protocol providing for subscription messages and notification messages. Attention now is directed to the drawings and particularly to Fig. 2, which shows the flow diagram for a mobility and service recovery method according to the example embodiments, keeping in mind that the example embodiments may be carried out in a variety of different networks.
In general, a user terminal must provide some identification to a network in order to gain access and receive communication services. The identification may be anything that uniquely identifies the user, such as a SIM card or telephone number. Once authorized and granted access to the network, the user may arrange for a plurality of different communication services. Each individual one of these communications services may be provided by an application server located in the wireless communication network or an applications server located in other networks or on the Internet and delivered through the wireless communication network. The communication services available to the user terminal include at least some SIP services that utilize the SIP event notification scheme. The network contains a SIP registrar for the SIP services. A SIP registrar is any network element that provides the functionality described herein. It may be any one of the application servers, a proxy server for the user terminal, or HSS 102 in IMS 100. It stores address bindings and contains information for the SIP services for users on the network in a database.
As represented by step 201 in Fig. 2, a user of a mobile terminal is receiving a plurality of ongoing communication services. At step 202, the user changes mobile terminals so as to change from a previous mobile terminal to a new mobile terminal. The change of terminal may be for any reason. At step 203, the new mobile terminal sends a SIP SUBSCRIBE message to the SIP registrar according to the SIP event notification scheme. The message is directed through the network and routed to the SIP registrar. The event described by the SIP SUBSCRIBE message is a special event called, for example, "my services", but the message has a format and syntax which is otherwise the same as conventional SIP SUBSCRIBE messages.. The user may be identified simultaneously with, or separate from, the SIP subscribe message. The identification information may be provided by the user terminal or by a network element which authenticates the user. In response to the SIP SUBSCRIBE message including the "my services" event and suitable identification of the user (which may be provided simultaneously with, or separate from, the SIP SUBSCRIBE message), the SIP registrar obtains the information for all of the user's ongoing communications services from the database. The database has a variety of information for users' ongoing communication services, preferably indexed or sortable by user identification. When the user is identified and the information is returned from the database, the SIP registrar sends a SIP SUBSCRIBE message for each one of the ongoing communication services to the corresponding application server for that service. The SIP registrar also sends a response 204-r to the SIP SUBSCRIBE message including the "my services" event to the new user terminal. The payload response includes information necessary for the communication services to be received by the new user terminal. The new terminal then examines the payload and determines therefore the data necessary to continue the communication services. Optionally, the payload may also include related parameters and/or settings necessary to receive the services. The needed parameters and/or settings may include communication network related parameters such as GPRS parameters or UMTS parameters, WAP parameters comprising a WAP Gateway address, a Uniform Resource Locator (URL) for setup, a home page and favorites, WWW parameters comprising an HTTP proxy address, SMTP/POP3 addresses, public keys, Ipv4, Ipv6, and a Default Classmark for multi-classmark devices, software updates, applets, network storage location, a user preference list, firmware updates, etc. There may also be general information, such as network subscription and authorization information or calling plan information or lists of telephone numbers, stored in the user terminal and which is desired to be available to the user to enable or facilitate communications.
The method described with respect to Fig. 2 may be advantageously applied when SIP is used to provide push services. Conventionally, push services are different than SIP event notifications since, in push, the client does not initiate the transfer of information whereas a SIP event notification is initiated by a client sending a SIP SUBSCRIBE message. An example of a functional architecture for push services to a user terminal is shown in Fig. 3. A push proxy 301 maintains the push services (e.g., user subscriptions, receiving push information from push initiators originating the push information, and sending notifications to users) and acts as a gateway between the user terminal and a plurality of different push initiators 302-1 to 302-n (which may use respectively different push protocols) which forwards/converts push messages to/from a client. A push initiator 302-1 to 302-n may provide push information to push service providers (not shown) using either SIP or another protocol. The push service provider (e.g., internet service provider or content provider) provides information (which may be based, for example, on personal user profiles) and manages push proxy 301 for a user terminal, although the network operator may also provide notifications and advertisements. Instead of using a push service provider, a push initiator 302-1 to 302-n may be co-located in the push proxy or be combined with the push proxy itself.
A user terminal is registered as a client with presence server 303 through HSS 102 associated with IMS 100. Presence server manages information indicating the presence, location and/or status of the user terminal. Push proxy 301 is subscribed to presence server 303 and utilizes the information corresponding to the user as described below. When a user terminal changes its location, it re-registers to its presence server 303 to update its location (and other information). SIP is preferably used for these registrations. Push proxy 301 is notified about the changes in the user status. The push services use the address of push proxy 301 (e.g., user@domain.com) instead of real IP addresses in order to facilitate mobility of the user terminal. The protocol between push proxy 301 and the user terminal and presence server 303 is SIP. The protocol between push proxy 301 and the push initiators 302-1 to 302-n can be SIP or some other protocol, such as HTTP or SMTP as shown in Fig. 3.
When a user subscribes to a push service, it does so through push proxy 301 using the SIP SUBSCRIBE message or an out-of-band mechanism (e.g., world wide web). The event identified in the SIP SUBSCRIBE message is "Push" and the payload in the SIP SUBSCRIBE message may contain optional XML content defining the user's preferences/policies (e.g., personal interests, terminal capabilities, bandwidth restrictions/preferences, etc.). As an example, Fig. 5 shows a SIP SUBSCRIBE message indicating that the user receives no advertisements and the acknowledgement returned by the push proxy. (In an alternative out-of- band subscription, the user terminal must retain the subscription information (To, From, Call-ID headers) in order to do the notification filtering.) Once push proxy 301 receives the message from the user terminal (step 1 in Fig. 6), it then subscribes to presence server 303 (step 2 in Fig. 6) and receives a response including information indicating the location/status of the user terminal (step 3 in fig. 6). When the event designated in the SIP SUBSCRIBE message from the user terminal occurs (step 4), push proxy 301 forwards a SIP NOTIFY message to the user terminal (step 5) using the information obtained in step 3. Preferably, presence server 303 receives information of the user terminal as a matter of due course from core network elements CSCF 101 and HSS 102 of IMS 100. If however, as shown in Fig. 8, there is no IMS or these elements are not otherwise available to presence server 303, then the user terminal must directly register with presence server 303, preferably using SIP as shown in step 1 of Fig. 8. The remaining steps can then proceed in the same manner as in Fig. 6. Preferably, presence server 303 hides the fact of whether there is an IMS or not from push proxy 301. An example of a subscription to a push service according to the example embodiments of the invention is shown in Fig. 7. The SIP SUBSCRIBE message from the user terminal identifies an event ("soccer") and a parameter ("game 1") (step 1). After push proxy 301 subscribes to presence server 303 (step 2), it subscribes to push initiator 302-n (step 3) using the same event and parameter as in the user terminal's original SIP SUBSCRIBE message. (Push proxy 301 may give additional subscription information to a push service provider such as, for example, the bandwidth for push services, terminal capabilities and personal interests.) When push initiator 302-n responds (step 4), push proxy 301 adds the event and parameter to the list of existing subscription for the user ("my services") and forwards a SIP NOTIFY message to the user terminal (step 5).
While the user remains subscribed to the service, push proxy 301 delivers the push information from push initiator 302-n to the user's terminal using the terminal's current location information available to it from the presence server 303. If the user terminal is not available (e.g., it is out of range), push proxy 301 stores information (e.g., based on user preferences) and informs the user later. Push proxy 301 is also responsible for rate control (e.g., allowing a maximum rate of traffic to avoid momentary traffic peaks. If the user is subscribed to two push proxies, then the rate control must be more carefully adjusted (e.g., by advising both push proxies to allow a maximum of half of the total bandwidth capacity available for push services in the user terminal's access link).
Push information is always delivered to the user terminal using SIP NOTIFY and the same To, From and Call-ID headers in the service subscription. As shown in Fig. 3, push proxy 301 may utilize several push initiators 302-1 to 302-n and use different protocols (e.g., HTTP, email, SIP, RTP, non-IP protocols) for different push initiators. The payload in the SIP NOTIFY message depends on the push type and the user terminal's capabilities. For message type notifications (i.e., occasional events in sports matches), the SIP NOTIFY message may carry, for example, XML or ascii payload. For streaming type push information, the SIP NOTIFY payload includes the details of the streaming session. It may be, for example, a URL (e.g., RTSP URL) or SDP (to define a video call).
Fig. 4 is a flow diagram illustrating the steps performed in a SIP push communication service using the functional architecture shown in Fig. 3. At step 401, the user subscribes to the push service by sending a SIP SUBSCRIBE message such as the following to push proxy 301:
SUBSCRIBE sip:pushproxy.com SIP/2.0 To: sip:pushproxy.com From: sip:user@isp.com Call-ID: abc Event: presence
At step 402, push proxy 301 responds with a 200 Ok message. At step 403, push proxy
301 subscribes to the uac's SIP registrar/presence server 303 by sending a SIP SUBSCRIBE message such as the following to SIP registrar/presence server 303:
SUBSCRIBE sip:user@isp.com SIP/2.0 To: sip:user@isp.com From: sip: pushproxy.com Call-ID: abc Event: presence
At step 404, push proxy 301 immediately sends a SIP NOTIFY such as the following to the user terminal:
NOTIFY sip:user@isp.com SIP/2.0 Then, at step 405, push proxy 301 subscribes to the push initiator 302-1 on behalf of the user
(push proxy 301 may have already subscribed to push initiator 302-1 for other users) by sending a SIP SUBSCRIBE message such as the following:
SUBSCRIBE sip:pi.com SIP/2.0
Push proxy 301 then waits to receive a 200 Ok message from SIP registrar/presence server 303 in response to the SIP SUBSCRIBE message sent at step 403 and a 200 Ok message from push initiator 302-1 in response to the SIP SUBSCRIBE message sent at step 405 (steps
406 and 407). Upon receipt of the 200 Ok messages in steps 406 and 407, push proxy 301 provides the push information to the user. A message type push service may be provided by sending a SIP NOTIFY message such as the following to the user:
NOTIFY sip:user@isp.com SIP/2.0 EVENT: push Content-Type: text/plain
Status of soccer match: A-B 2-2 Scores: Player Name (77 min.)
A streaming type push service may be provided by sending a SIP NOTIFY message such as the following to the user:
NOTIFY sip:user@isp.com SIP/2.0
Event: push
Content-Type: application/html
<html>Breaking news from CNN! <a href=cnn.com/videol.ram>Live video feed from CNN</A><br> The important aspect of the example embodiments is that the user terminal can easily access all of the service information relating to it stored in push proxy 301 using a simple reference to the "my-services" list. Preferably, the "my-services" list can be accessed and used by the user terminal to manage subscriptions after the subscriptions have been created. Fig. 9 shows examples of the "my-services" list in a database maintained by push proxy 301.
Of course, the main advantage is that the list may be accessed by a SIP SUBSCRIBE message in which the event name is "my-services". This allows mobility and service recovery for push services using the method illustrated in Fig. 2 and described above. It is particularly advantageous for push services which, from the perspective of the user, are intended to be delivered to the user without any request being made therefore.
Of course, in a particular implementation, there is likely to be a combination of push services and other services. However, as just described, the same method can be used for mobility and recovery of both push services and other communication services when there is a terminal failure or the user switches terminals as described previously. As can be seen from the foregoing, using a special SIP SUBSCRIBE message for mobility and service recovery yields a fast and efficient solution which is easy to implement when there is a terminal failure or a change of terminals. While the invention has been described with reference to example embodiments, the description is illustrative and is not to be construed as limiting the invention. In particular, the various references to subscriptions refers merely to the terminology used in association with SIP and is not meant to imply that the communication services must necessarily be provided in exchange for monetary compensation.

Claims

CLAIMSWhat is claimed:
1. A method of mobility and service recovery for a user in a wireless communication network, said method comprising: storing service information concerning the user in a registrar; sending a subscription message from a user terminal to the registrar, a header in the subscription message containing a unique indication; and in response to said subscription message containing a unique indication in a header, returning a notification message to the user terminal, the payload of said notification message including service information for the user to be used by the user terminal for communication services.
2. The method as claimed in claim 1 , wherein the user has a plurality of ongoing communication services at the time that the subscription message containing a unique indication in a header is sent.
3. The method as claimed in claim 2, wherein the payload of said notification message includes service information for each one of said ongoing communication services.
4. The method as claimed in claim 1, wherein said subscription message is sent after said user terminal experiences a failure.
5. The method as claimed in claim 4, wherein said service information included in the payload of said notification message enables recovery of communication services to their state at the time of said terminal failure.
6. The method as claimed in claim 1, wherein said subscription message is sent by a new terminal after said user switches terminals from a previous terminal to said new terminal.
7. The method as claimed in claim 1, wherein said new terminal is a different type of mobile terminal than said previous mobile terminal.
8. The method as claimed in claim 1, wherein said communication services include a push service and the registrar is a push proxy.
9. The method as claimed in claim 8, wherein said push proxy automatically stores said service information when the user terminal subscribes to said communication services.
10. A network architecture, comprising: a plurality of terminals; a radio access network, said radio access network containing elements providing information indicating the presence, status and/or location of said plurality of terminals; a presence server, said presence server adapted to receive said information indicating the presence, status and/or location of said plurality of terminals; at least one communication service provider providing a plurality of communication services; and a proxy server, said proxy server adapted to provide said plurality of communication services to said plurality of user terminals upon subscription thereto, wherein the proxy server stores and maintains service information related to said plurality of communication services and provides said service information in a single message sent in response to a request therefore from a user terminal.
11. The network architecture as claimed in claim 10, wherein said proxy server provides said service information in the payload of a notification message sent to the requesting terminal in response to said request.
12. The network architecture as claimed in claim 11, wherein said presence server, said proxy server and said plurality of user terminals send messages to each other according to the Session Initiation Protocol (SIP) and the notification message comprises a SIP NOTIFY response.
13. The network architecture as claimed in claim 12, wherein said request comprises a SIP SUBSCRIBE message.
14. The network architecture as claimed in claim 11 , wherein, when said proxy server receives said request from a user terminal, it re-subscribes the user to the ongoing subscriptions for which service information is stored therein.
15. The network architecture as claimed in claim 11, wherein said user terminal sends said request after it experiences failure.
16. The network architecture as claimed in claim 11, wherein, when a user switches to a new user terminal from a previous user terminal, the new user terminal sends said request to said proxy server.
17. The network architecture as claimed in claim 16, wherein the new user terminal is a different type of user terminal than said previous user terminal.
18. The method as claimed in claim 1, wherein said registrar comprises a SIP registrar, said subscription message comprises a SIP SUBSCRIBE message, said header comprises an event header, and said notification message comprises a SIP NOTIFY response.
19. The method as claimed in claim 18, wherein the user has a plurality of ongoing communication services at the time that the SIP SUBSCRIBE message containing a unique indication in the event header is sent.
20. The method as claimed in claim 19, wherein the payload of said SIP NOTIFY response includes service information for each one of said ongoing communication services.
21. The method as claimed in claim 18, wherein said SIP SUBSCRIBE message is sent after said user terminal experiences a failure.
22. The method as claimed in claim 21, wherein said service information included in the payload of said SIP NOTIFY response enables recovery of communication services to their state at the time of said terminal failure.
23. The method as claimed in claim 18, wherein said SIP SUBSCRIBE message is sent by a new terminal after said user switches terminals from a previous terminal to said new terminal.
24. The method as claimed in claim 18, wherein said new terminal is a different type of mobile terminal than said previous mobile terminal.
25. The method as claimed in claim 18, wherein said communication services include a push service and the SIP registrar is a push proxy.
26. The method as claimed in claim 25, wherein said push proxy automatically stores said service information when the user terminal subscribes to said communication services.
27. A proxy server, said proxy server being adapted to: provide a plurality of communication services to a plurality of user terminals upon subscription of said user terminals to said communication services; store and maintain service information related to said plurality of communication services; and provide said service information in a single message sent in response to a request therefore from a user terminal.
28. The proxy server as claimed in claim 27, wherein said proxy server provides said service information in the payload of a notification message to the requesting user terminal.
29. The proxy server as claimed in claim 28, wherein the proxy server sends and receives message according to the Session Initiation Protocol (SIP) and the notification message comprises a SIP NOTIFY response.
30. The proxy server as claimed in claim 29, wherein said request comprises a SIP SUBSCRIBE message.
31. The proxy server as claimed in claim 28, wherein, when said proxy server receives said request from a user terminal, it re-subscribes the user to the ongoing subscriptions for which service information is stored therein.
32. A mobile terminal, said mobile terminal being adapted to: receive a plurality of communication services; send a subscription message to a registrar, a header in the subscription message containing a unique identification; receive a notification message sent from said registrar in response to said subscription message, the payload of said notification message including service information for said plurality of communication services; and using said service information included in the payload of said notification message to continue said plurality of communication services.
33. The mobile terminal as claimed in claim 32, wherein said subscription message is sent after said mobile terminal experiences a failure.
34. The mobile terminal as claimed in claim 33, wherein said service information included in the payload of said notification message enables recovery of communication services to their state at the time of said mobile terminal failure.
35. The mobile terminal as claimed in claim 32, wherein said subscription message is sent by said mobile terminal after said user switches to said mobile terminal from a previous mobile terminal.
36. The mobile terminal as claimed in claim 32, wherein said subscription message is a SIP SUBSCRIBE message, said header is an event header in the SIP SUBSCRIBE message and said notification message is a SIP NOTIFY response.
PCT/IB2002/003370 2001-08-24 2002-08-21 Service mobility and recovery in communication networks WO2003019918A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP02767742A EP1419646A1 (en) 2001-08-24 2002-08-21 Service mobility and recovery in communication networks

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US09/938,290 US6885861B2 (en) 2001-08-24 2001-08-24 Service mobility and recovery in communication networks
US09/938,290 2001-08-24

Publications (1)

Publication Number Publication Date
WO2003019918A1 true WO2003019918A1 (en) 2003-03-06

Family

ID=25471221

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2002/003370 WO2003019918A1 (en) 2001-08-24 2002-08-21 Service mobility and recovery in communication networks

Country Status (3)

Country Link
US (2) US6885861B2 (en)
EP (1) EP1419646A1 (en)
WO (1) WO2003019918A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005089049A2 (en) 2004-03-10 2005-09-29 Nokia Corporation System and method for pushing content to a terminal utilizing a network-initiated data service technique
WO2016086879A1 (en) * 2014-12-04 2016-06-09 Huawei Technologies Co., Ltd. Method of service capability discovery based on subscriptions for service notifications

Families Citing this family (148)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2001223622A1 (en) * 2000-12-04 2002-06-18 Nokia Corporation Communication system and method for establishing a connection to a serving network element
US20030125023A1 (en) * 2001-03-15 2003-07-03 Eyal Fishler Method and system for providing a wireless terminal communication session integrated with data and voice services
US7333452B2 (en) * 2001-06-12 2008-02-19 Lg Electronics Inc. Method and system for packet data transmission
GB0119819D0 (en) * 2001-08-14 2001-10-10 Ericsson Telefon Ab L M Communication networks
US20030046273A1 (en) * 2001-08-28 2003-03-06 Intel Corporation Personal assistance service with instant messaging
US20030048195A1 (en) * 2001-08-31 2003-03-13 Dirk Trossen Apparatus and method to sense and subscribe to presence information
CA2404552C (en) * 2001-09-21 2008-12-09 Corel Corporation System and method for secure communication
US7441016B2 (en) * 2001-10-03 2008-10-21 Accenture Global Services Gmbh Service authorizer
US7472091B2 (en) * 2001-10-03 2008-12-30 Accenture Global Services Gmbh Virtual customer database
GB0124261D0 (en) * 2001-10-09 2001-11-28 Nokia Corp Event related communications
GB0124436D0 (en) * 2001-10-11 2001-12-05 Nokia Corp Terminal-based instruction execution in an ip communications network
KR100456618B1 (en) * 2001-11-08 2004-11-10 한국전자통신연구원 Synchronization method of registration information within intra-domain
EP1452041B1 (en) * 2001-12-04 2010-10-27 Nokia Siemens Networks GmbH & Co. KG Method and network device for running especially personalised communication services in a communication system
AU2003217994A1 (en) 2002-03-08 2003-09-22 Aware, Inc. Systems and methods for high rate ofdm communications
US20050131921A1 (en) * 2002-04-19 2005-06-16 Kaustabh Debbarman Extended naming service framework
US6938090B2 (en) * 2002-04-26 2005-08-30 Nokia Corporation Authentication and protection for IP application protocols based on 3GPP IMS procedures
US7395336B1 (en) * 2002-05-14 2008-07-01 Sprint Spectrum L.P. Method for managing SIP registrations in a telecommunications network
US7313358B1 (en) * 2002-06-08 2007-12-25 Christopher P Ricci Communication system for redirecting communication with radio frequency devices
GB0213726D0 (en) * 2002-06-14 2002-07-24 Nokia Corp A communication system
FI20021378A0 (en) * 2002-07-12 2002-07-12 Comptel Oyj A method, means, and computer program product for controlling and / or limiting the use of a telecommunications connection
GB2391420A (en) * 2002-07-25 2004-02-04 Samsung Electronics Co Ltd Method for serving audio and image communication in web browser using session initiation protocol
US20040022226A1 (en) * 2002-07-31 2004-02-05 Peter Edlund Subscribe-notify function between PLMN nodes
DE60215335T2 (en) * 2002-08-07 2007-05-10 Lucent Technologies Inc. A method of creating an application initiated call to a mobile station in a CAMEL network, and a telecommunication system having a CAMEL network
AU2002368267B2 (en) 2002-10-09 2008-05-29 Nokia Technologies Oy A communication system
US20040078424A1 (en) * 2002-10-16 2004-04-22 Nokia Corporation Web services via instant messaging
GB2395402A (en) * 2002-11-16 2004-05-19 Hewlett Packard Co Advertising different protocols on a broadcast channel
ATE369684T1 (en) * 2002-11-25 2007-08-15 T Mobile Deutschland Gmbh METHOD AND SYSTEM FOR SIMPLIFYING ACCESS TO AN EMAIL ACCOUNT VIA A MOBILE NETWORK
US7020440B2 (en) * 2002-12-13 2006-03-28 Ntt Docomo, Inc. Method and apparatus for an SIP based paging scheme
US20040127200A1 (en) * 2002-12-31 2004-07-01 Shaw Venson M. Delivery of network services
US8046476B2 (en) * 2003-01-29 2011-10-25 Nokia Corporation Access right control using access control alerts
US20040196849A1 (en) * 2003-02-13 2004-10-07 Nokia Corporation Method for signaling streaming quality adaptation and control mechanisms in multimedia streaming
EP2276219A1 (en) * 2003-02-19 2011-01-19 Nokia Corporation Routing Messages via an IMS System
FR2851869A1 (en) * 2003-02-28 2004-09-03 France Telecom MULTI-DOMAIN MULTI-SUPPLIER MEDIATION BODY FOR THE NOTIFICATION OF EVENTS
US9451422B2 (en) * 2003-03-17 2016-09-20 Nokia Technologies Oy Method, system and network device for routing a message to a temporarily unavailable network user
JP4295284B2 (en) * 2003-03-25 2009-07-15 ノキア コーポレイション Routing subscription information
US7107010B2 (en) * 2003-04-16 2006-09-12 Nokia Corporation Short-range radio terminal adapted for data streaming and real time services
MXPA05011759A (en) * 2003-05-02 2006-01-26 Interdigital Tech Corp Method and architecture for accessing an internet protocol multimedia subsystem (ims) over a wireless local area network (wlan).
CA2524789C (en) * 2003-05-06 2010-09-28 Research In Motion Limited System and method of wireless device activity messaging
US20050021976A1 (en) * 2003-06-23 2005-01-27 Nokia Corporation Systems and methods for controlling access to an event
EP1652395A2 (en) * 2003-07-31 2006-05-03 Koninklijke KPN N.V. A method and system to enable email services for mobile devices
US7574528B2 (en) * 2003-08-27 2009-08-11 Cisco Technology, Inc. Methods and apparatus for accessing presence information
WO2005027485A1 (en) * 2003-09-12 2005-03-24 Nokia Corporation Method and device for handling missed calls in a mobile communications environment
JP4290568B2 (en) * 2004-01-07 2009-07-08 アルゼ株式会社 Mobile phone and mobile phone control method
US7974394B1 (en) * 2004-01-26 2011-07-05 Cisco Technology, Inc. System and method for distributed IP telephony tracking
KR100842589B1 (en) * 2004-01-29 2008-07-01 삼성전자주식회사 Method for providing push service to a mobile terminal in mobile communication network for high speed data transmission and push server apparatus using the same
US7406696B2 (en) * 2004-02-24 2008-07-29 Dialogic Corporation System and method for providing user input information to multiple independent, concurrent applications
CN100375424C (en) * 2004-03-22 2008-03-12 国际商业机器公司 Multimedia information receiving and transmitting method system, gateway and customer's equipment
US8081586B2 (en) * 2004-04-07 2011-12-20 Nokia Corporation Method and apparatus to convey a URI for content indirection use in SIP
KR100724975B1 (en) * 2004-04-09 2007-06-04 삼성전자주식회사 An electronic business card service system and method by using presence information
CN100345425C (en) * 2004-05-25 2007-10-24 中国移动通信集团公司 Method and system for transmitting information from information system to mobile terminal
CN100338929C (en) * 2004-05-25 2007-09-19 中国移动通信集团公司 Server information system and method for acquiring information through fireproof wall by mobile terminal
US20060080428A1 (en) * 2004-06-07 2006-04-13 Nokia Corporation Method, system and computer program to enable semantic mediation for SIP events through support of dynamically binding to and changing of application semantics of SIP events
US7269411B2 (en) * 2004-06-16 2007-09-11 The Boeing Company Methods and systems for providing information network access to a host agent via a guardian agent
US20050289096A1 (en) * 2004-06-23 2005-12-29 Nokia Corporation Method, system and computer program to enable SIP event-based discovery of services and content within a community built on context information
US8903820B2 (en) * 2004-06-23 2014-12-02 Nokia Corporation Method, system and computer program to enable querying of resources in a certain context by definition of SIP even package
US8856240B2 (en) * 2004-06-23 2014-10-07 Nokia Corporation Method, system and computer program to provide support for sporadic resource availability in SIP event environments
EP1610521A1 (en) * 2004-06-25 2005-12-28 Siemens Mobile Communications S.p.A. Method of and apparatus for application download in communication systems supporting presence services
US20060004924A1 (en) * 2004-06-30 2006-01-05 Nokia Corporation Method and system providing support for location and service category service discovery in a SIP environment using a SIP event package, forking and AOR registration
US20070294336A1 (en) * 2004-07-02 2007-12-20 Greg Pounds Proxy-based communications architecture
PT1763964E (en) * 2004-07-05 2010-12-27 Ericsson Telefon Ab L M Devices and methods for push message initiated service
EP1846832B1 (en) 2004-12-17 2012-04-11 Tekelec Methods, systems, and computer program products for clustering and communicating between internet protocol multimedia subsystem (IMS) entities
FI20041634A0 (en) * 2004-12-20 2004-12-20 Nokia Corp Setting up a supply session in a communication system
US7853697B2 (en) * 2005-01-03 2010-12-14 Nokia Corporation Handling suspended network state of a terminal device
DE102005007060B4 (en) * 2005-02-16 2008-11-13 Nokia Siemens Networks Gmbh & Co.Kg Signaling the failure of a network device via a communications network
TWI304550B (en) * 2005-11-03 2008-12-21 Wistron Corp The update method and the system of the network device
JP4977329B2 (en) * 2005-03-29 2012-07-18 日本電気株式会社 Presence service system, presence device, presence service method, and program
ES2317341T3 (en) * 2005-04-28 2009-04-16 Telefonaktiebolaget Lm Ericsson (Publ) MESSAGE MANAGEMENT IN A MULTIMEDIA IP SUBSYSTEM.
US20060274701A1 (en) * 2005-06-03 2006-12-07 Telefonaktiebolaget Lm Ericsson (Publ) Means and method for notification
CN1852136A (en) * 2005-07-19 2006-10-25 华为技术有限公司 Registering/logout system and method thereof
WO2007014751A1 (en) * 2005-08-04 2007-02-08 T-Mobile International Ag & Co. Kg Method for collecting user behavior during run-time in a mobile 3gpp ip-based multimedia subsystem (ims)
ES2402773T3 (en) 2005-09-02 2013-05-08 Swisscom Ag Procedure and system to provide media content to a user
EP1765028A1 (en) * 2005-09-14 2007-03-21 Siemens Aktiengesellschaft Method and system for controlling an access to a transmission
JP4327142B2 (en) * 2005-09-29 2009-09-09 パナソニック株式会社 Information processing system, tunnel communication device, tunnel communication method, proxy response device, and proxy response method
US20070070962A1 (en) * 2005-09-29 2007-03-29 Sony Ericsson Mobile Communications Ab Communication networks for establishing communication sessions between a registered internet protocol (IP) device and one or more subscribing IP devices and methods and computer program products for operating the same
KR100795558B1 (en) * 2005-11-15 2008-01-21 한국전자통신연구원 Context information management system and method
EP1833218A1 (en) * 2006-03-07 2007-09-12 BRITISH TELECOMMUNICATIONS public limited company Apparatus for and a method of delivering a message to a user
US20090172077A1 (en) * 2005-11-23 2009-07-02 David Roxburgh Apparatus for and a Method of Delivering a Message to a User
US8045473B2 (en) * 2005-11-28 2011-10-25 Cisco Technology, Inc. Tailored relief for congestion on application servers for real time communications
EP2099160A1 (en) * 2005-12-09 2009-09-09 BenQ Corporation Method for client-server-based communication over several interfaces and client supporting this method
US20070191007A1 (en) * 2006-02-14 2007-08-16 Claude Hayek Method and system for a processor that handles a plurality of wireless access communication protocols
US7577779B2 (en) * 2006-02-14 2009-08-18 Broadcom Corporation Method and system for a RFIC master
US20070214226A1 (en) * 2006-03-07 2007-09-13 Samsung Electronics Co., Ltd. Method and system for pushing electronic mail
EP1835686B1 (en) * 2006-03-13 2015-12-23 Vodafone Group PLC Method of providing access to an IP multimedia subsystem based on provided access network data.
US8316293B2 (en) * 2006-03-27 2012-11-20 Research In Motion Limited System and method for rendering presentation pages based on locality
US20070253405A1 (en) * 2006-04-27 2007-11-01 Motorola, Inc. Method and apparatus for initiating a user selected service when establishing a packet data connection
DK2044747T3 (en) * 2006-06-30 2016-12-19 ERICSSON TELEFON AB L M (publ) Technique for providing access to a media resource connected to a network detected devices
US8149725B2 (en) * 2006-07-31 2012-04-03 Tekelec Methods, systems, and computer program products for a hierarchical, redundant OAM&P architecture for use in an IP multimedia subsystem (IMS) network
US7756937B2 (en) * 2006-08-18 2010-07-13 Brother Kogyo Kabushiki Kaisha Network device
JP4245016B2 (en) * 2006-08-18 2009-03-25 ブラザー工業株式会社 E-mail communication apparatus and computer program
US20080235778A1 (en) * 2007-03-21 2008-09-25 Motorola, Inc. Communication network, an access network element and a method of operation therefor
US20080235185A1 (en) * 2007-03-21 2008-09-25 Motorola, Inc. Communication system and method of accessing therefor
EP2149243B1 (en) * 2007-05-19 2011-09-28 T-Mobile International AG IP multimedia subsystem (IMS) and method for routing an http message via an IMS
US20090006628A1 (en) * 2007-06-28 2009-01-01 Samsung Electronics Co., Ltd. System and method for controlling the presentation of dynamic information to a mobile device
CN101690099B (en) 2007-06-28 2014-03-19 摩托罗拉移动公司 Method and system for providing IMS session continuity to a user equipment across a plurality of communication networks
KR100875832B1 (en) 2007-07-10 2008-12-26 주식회사 케이티프리텔 Method for processing a various event in a lump, network device and network system for processing the same
CN101325742B (en) * 2007-07-24 2010-09-01 中兴通讯股份有限公司 Method for processing flexible ringer group busy for multiuser types
WO2009020332A2 (en) * 2007-08-06 2009-02-12 Samsung Electronics Co, . Ltd. Method and apparatus for providing/receiving web-based service of plurality of service providers
JP2009059160A (en) * 2007-08-31 2009-03-19 Sony Corp Server device, network system, content discovery notification method and computer program
CN101399782B (en) * 2007-09-30 2011-12-28 联想(北京)有限公司 Communication terminal, mail transferring system and method
KR101531166B1 (en) * 2007-11-27 2015-06-25 삼성전자주식회사 Method and apparatus for discovering IPTV service provider and IPTV service using SIP protocol
US8781528B2 (en) * 2007-12-31 2014-07-15 The Invention Science Fund I, Llc Automatic mobile device backup
US8477761B2 (en) * 2008-03-27 2013-07-02 Ittiam Systems (P) Ltd. Unified session signaling system for use in multimedia communications
US20110055412A1 (en) * 2008-06-05 2011-03-03 Telefonaktiebolaget L M Ericsson (Publ) System for Conversion of SIP Messages
US8560710B2 (en) * 2008-07-24 2013-10-15 International Business Machines Corporation System and method of using diameter based signaling to activate and deactivate subscriber centric, visually rendered, services
EP2150016A1 (en) * 2008-07-30 2010-02-03 Alcatel Lucent Method and system for selective call forwarding based on media attributes in telecommunication network
US8793384B2 (en) * 2008-08-22 2014-07-29 Microsoft Corporation Recovery of disconnected channels over a reliable protocol
US8335762B2 (en) 2008-10-06 2012-12-18 Microsoft Corporation Resource tracking
US9198222B2 (en) * 2008-10-22 2015-11-24 International Business Machines Corporation Telecommunication network
US7843809B2 (en) 2008-11-14 2010-11-30 At&T Intellectual Property I, L.P. Preserving stable calls during failover
US20100138501A1 (en) * 2008-12-03 2010-06-03 Microsoft Corporation End-to-end validation in a push environment
CN102257793A (en) * 2008-12-19 2011-11-23 爱立信电话股份有限公司 A method and arrangement for handling resource data
CN101478753B (en) * 2009-01-16 2010-12-08 中兴通讯股份有限公司 Security management method and system for IMS network access by WAPI terminal
EP2247077A1 (en) * 2009-04-03 2010-11-03 Hewlett-Packard Development Company, L.P. Method and apparatus for network communications
US20100268767A1 (en) * 2009-04-09 2010-10-21 Research In Motion Limited System and Method for Information Retrieval from a Context Aware Mechanism
JP5348013B2 (en) * 2009-05-26 2013-11-20 ソニー株式会社 Wireless communication apparatus, estimation server, wireless communication method, and estimation method
CN102045691B (en) * 2009-10-10 2014-06-11 中兴通讯股份有限公司 Method and device for acquiring grouped identifiers of machine type communication (MTC) equipment
US9307038B2 (en) * 2009-12-29 2016-04-05 Motorola Solutions, Inc. Method for presence notification based on a sequence of events
US8615237B2 (en) * 2010-01-04 2013-12-24 Tekelec, Inc. Methods, systems, and computer readable media for policy and charging rules function (PCRF) node selection
US8762549B2 (en) * 2010-01-18 2014-06-24 Telefonaktiebolaget L M Ericsson (Publ) System and method for IPTV node recovery
KR101682243B1 (en) * 2010-04-26 2016-12-13 삼성전자주식회사 Method for providing message and device therefor
US8843599B2 (en) * 2010-06-26 2014-09-23 Cisco Technology, Inc. Storing and synchronizing media device information
CN102347967B (en) * 2010-07-30 2014-01-01 华为技术有限公司 Method and device for cooperation between push equipment
US8433310B2 (en) * 2010-08-19 2013-04-30 At&T Mobility Ii Llc Systems, methods, and computer program products for providing device updates to a mobile device operating in a wireless telecommunications network
US8700409B1 (en) * 2010-11-01 2014-04-15 Sprint Communications Company L.P. Real-time versioning of device-bound content
US20120203620A1 (en) 2010-11-08 2012-08-09 Douglas Howard Dobyns Techniques For Wireless Communication Of Proximity Based Marketing
US9071925B2 (en) * 2011-01-05 2015-06-30 Alcatel Lucent System and method for communicating data between an application server and an M2M device
JP5950943B2 (en) 2011-02-04 2016-07-13 テケレック・インコーポレイテッドTekelec, Inc. Method, system, and computer-readable medium for supplying a Diameter binding repository
US9247404B2 (en) * 2011-02-09 2016-01-26 PlatinumTel Communications, LLC Delivery of advertisements over voice network
US8737304B2 (en) 2011-03-01 2014-05-27 Tekelec, Inc. Methods, systems, and computer readable media for hybrid session based diameter routing
WO2012118963A1 (en) 2011-03-01 2012-09-07 Tekelec, Inc. Methods, systems and computer readable media for dynamically learning diameter binding information
CN103477660B (en) 2011-03-01 2017-04-19 泰科来股份有限公司 Methods, systems, and computer readable media for sharing Diameter binding data
JP5732550B2 (en) 2011-03-03 2015-06-10 テケレック・インコーポレイテッドTekelec, Inc. Method, system, and computer-readable medium for enhancing Diameter signaling messages
US8929809B2 (en) 2011-03-22 2015-01-06 Radeum, Inc. Techniques for wireless communication of proximity based content
US8880100B2 (en) 2011-03-23 2014-11-04 Radium, Inc. Proximity based social networking
CN103535080B (en) 2011-05-06 2017-07-18 泰科来股份有限公司 Method, system and computer-readable media for changing user between access networks
CN103516588B (en) * 2012-06-30 2016-12-21 北京神州泰岳软件股份有限公司 A kind of client carries out the method and system of background process
US9319378B2 (en) 2013-01-23 2016-04-19 Tekelec, Inc. Methods, systems, and computer readable media for using a diameter routing agent (DRA) to obtain mappings between mobile subscriber identification information and dynamically assigned internet protocol (IP) addresses and for making the mappings accessible to applications
US9621228B2 (en) 2014-08-29 2017-04-11 Freelinc Technologies Spatially aware communications using radio frequency (RF) communications standards
US10164685B2 (en) 2014-12-31 2018-12-25 Freelinc Technologies Inc. Spatially aware wireless network
US10951519B2 (en) 2015-06-17 2021-03-16 Oracle International Corporation Methods, systems, and computer readable media for multi-protocol stateful routing
JP6584171B2 (en) 2015-07-02 2019-10-02 キヤノン株式会社 COMMUNICATION DEVICE, COMMUNICATION METHOD, AND PROGRAM
US10554661B2 (en) 2015-08-14 2020-02-04 Oracle International Corporation Methods, systems, and computer readable media for providing access network session correlation for policy control
US9668134B2 (en) 2015-08-14 2017-05-30 Oracle International Corporation Methods, systems, and computer readable media for providing access network protocol interworking and authentication proxying
US10084755B2 (en) 2015-08-14 2018-09-25 Oracle International Corporation Methods, systems, and computer readable media for remote authentication dial in user service (RADIUS) proxy and diameter agent address resolution
US9923984B2 (en) 2015-10-30 2018-03-20 Oracle International Corporation Methods, systems, and computer readable media for remote authentication dial in user service (RADIUS) message loop detection and mitigation
US9668135B2 (en) 2015-08-14 2017-05-30 Oracle International Corporation Methods, systems, and computer readable media for providing access network signaling protocol interworking for user authentication
EP3831028A4 (en) * 2018-08-01 2022-05-25 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatuses for enhancement to ip multimedia subsystem
US11283883B1 (en) 2020-11-09 2022-03-22 Oracle International Corporation Methods, systems, and computer readable media for providing optimized binding support function (BSF) packet data unit (PDU) session binding discovery responses

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4811377A (en) * 1987-07-31 1989-03-07 Motorola, Inc. Secure transfer of radio specific data
US5029233A (en) * 1987-10-09 1991-07-02 Motorola, Inc. Radio arrangement having two radios sharing circuitry
JPH02174448A (en) * 1988-12-27 1990-07-05 Sony Corp Telephone set
US5168517A (en) * 1989-03-13 1992-12-01 Herbert Waldman Apparatus and methods for selectively forwarding telephone calls
US5259018A (en) * 1989-03-17 1993-11-02 Technophone Limited Radio telephone system having a handset adapted to be removably connected and containing a NAM for storing a telephone number identifying the handset
US5222123A (en) * 1990-01-08 1993-06-22 Motorola, Inc. Registration and automatic call redirecting for cordless telephone systems
CA2059845C (en) * 1991-01-30 1997-05-06 Stefan G. Littig Universal radio with adaptive memory
US5313653A (en) * 1992-01-30 1994-05-17 Motorola, Inc. Method for a communication unit to maintain a data base of system services
US5600704A (en) * 1994-08-30 1997-02-04 Ericsson Inc. Systems and methods for prioritized routing of telephone calls to a subscriber
GB2310110B (en) * 1996-02-09 2000-05-10 Nokia Mobile Phones Ltd Transferring information
US6643504B1 (en) * 2000-07-10 2003-11-04 At&T Corp. Automatic wireless service activation in a private local wireless system
US20020147000A1 (en) * 2001-04-04 2002-10-10 Holmes-Kinsella David A. System and method for real-time addition of devices to a subscriber account
US7844055B2 (en) * 2001-06-26 2010-11-30 Link Us All, Llc Detecting and transporting dynamic presence information over a wireless and wireline communications network
US6912384B2 (en) * 2001-07-26 2005-06-28 Nokia Corporation Method and system for transferring a cellular phone call

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
DONOVAN STEVE: "IMPS - Instant Messaging and Presence using SIP", FALL VON DEVELOPERS CONFERENCE, 13 September 2000 (2000-09-13), pages 1 - 16, XP002959658 *
ROACH ADAM: "SIP-specific event notification", July 2001 (2001-07-01), pages 1 - 32, XP002189884 *

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005089049A2 (en) 2004-03-10 2005-09-29 Nokia Corporation System and method for pushing content to a terminal utilizing a network-initiated data service technique
WO2005089049A3 (en) * 2004-03-10 2006-11-16 Nokia Corp System and method for pushing content to a terminal utilizing a network-initiated data service technique
KR100885522B1 (en) 2004-03-10 2009-02-26 노키아 코포레이션 System and method for pushing content to a terminal utilizing a network-initiated data service technique
KR100948654B1 (en) * 2004-03-10 2010-03-18 노키아 코포레이션 System and method for pushing content to a terminal utilizing a network-initiated data service technique
US8085746B2 (en) 2004-03-10 2011-12-27 Core Wireless Licensing S.A.R.L. System and method for pushing content to a terminal utilizing a network-initiated data service technique
US8085741B2 (en) 2004-03-10 2011-12-27 Core Wireless Licensing S.A.R.L. System and method for pushing content to a terminal utilizing a network-initiated data service technique
US8416753B2 (en) 2004-03-10 2013-04-09 Core Wireless Licensing S.A.R.L. System and method for pushing content to a terminal utilizing a network-initiated data service technique
WO2016086879A1 (en) * 2014-12-04 2016-06-09 Huawei Technologies Co., Ltd. Method of service capability discovery based on subscriptions for service notifications

Also Published As

Publication number Publication date
US6885861B2 (en) 2005-04-26
EP1419646A1 (en) 2004-05-19
US7149522B2 (en) 2006-12-12
US20030040280A1 (en) 2003-02-27
US20050111441A1 (en) 2005-05-26

Similar Documents

Publication Publication Date Title
US7149522B2 (en) Service mobility and recovery in communication networks
EP1753199B1 (en) Method and system for subscribing a user to a service
EP1880528B1 (en) Service provisioning in a communications system
EP1988685B1 (en) Service provisioning in a communication system
KR100700734B1 (en) A method and system to subscription of events using sip protocol
EP1700499B1 (en) Method and communication system for automatically discovering the multmedia service capability
EP1760983B1 (en) Method and system for providing media content to a user
CN101179863B (en) Subscriber registrations in a mobile communication system
EP2452485B1 (en) Methods and apparatus for initiating provisioning of subscriber data in a hss of an ip multimedia subsystem network
US20040205212A1 (en) Method and system for forwarding a service-related information to a network user
US20060179115A1 (en) Controlling push operation in a communication system
WO2006072817A1 (en) Method, apparatus and computer program product handling the end of suspended network state of a terminal device
US20100099447A1 (en) Method and Apparatus for Use in a Communications Network
WO2005002176A1 (en) System and method for restricting event subscriptions through proxy-based filtering
EP2220842B1 (en) Ip-based interworking methods and apparatus for voice and data communications
Tosi An advanced architecture for push services
EP2898647B1 (en) Methods and apparatus for processing an ims session
EP1609322B1 (en) Service provisioning in a communication system
EP2028811B1 (en) Method for exchanging user information in a telecommunication network
KR20070087168A (en) Monitoring access to a mobile information server in a communication system
RU2417544C2 (en) Methods and devices for transmitting signal connection information relating to signal connection between terminal and proxy call session control function (p-cscf) in internet protocol multimedia subsystem (ims)

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BY BZ CA CH CN CO CR CU CZ DE DM DZ EC EE ES FI GB GD GE GH HR HU ID IL IN IS JP KE KG KP KR LC LK LR LS LT LU LV MA MD MG MN MW MX MZ NO NZ OM PH PL PT RU SD SE SG SI SK SL TJ TM TN TR TZ UA UG UZ VN YU ZA ZM

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SD SE SG SI SK SL TJ TM TN TR TT TZ UA UG UZ VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ UG ZM ZW AM AZ BY KG KZ RU TJ TM AT BE BG CH CY CZ DK EE ES FI FR GB GR IE IT LU MC PT SE SK TR BF BJ CF CG CI GA GN GQ GW ML MR NE SN TD TG

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR IE IT LU MC NL PT SE SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
WWE Wipo information: entry into national phase

Ref document number: 2002767742

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2002767742

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP

WWW Wipo information: withdrawn in national office

Ref document number: 2002767742

Country of ref document: EP