EP1961190A1 - Verfahren und netzwerk zur bereitstellung gemischter dienste für einen abonnenten - Google Patents

Verfahren und netzwerk zur bereitstellung gemischter dienste für einen abonnenten

Info

Publication number
EP1961190A1
EP1961190A1 EP06845467A EP06845467A EP1961190A1 EP 1961190 A1 EP1961190 A1 EP 1961190A1 EP 06845467 A EP06845467 A EP 06845467A EP 06845467 A EP06845467 A EP 06845467A EP 1961190 A1 EP1961190 A1 EP 1961190A1
Authority
EP
European Patent Office
Prior art keywords
information
subscriber
phone
services
message request
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
EP06845467A
Other languages
English (en)
French (fr)
Other versions
EP1961190B1 (de
Inventor
Markus Andreas Hofmann
Kristin Freya Kocan
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alcatel Lucent SAS
Original Assignee
Lucent Technologies 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 Lucent Technologies Inc filed Critical Lucent Technologies Inc
Publication of EP1961190A1 publication Critical patent/EP1961190A1/de
Application granted granted Critical
Publication of EP1961190B1 publication Critical patent/EP1961190B1/de
Not-in-force legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00—Television systems
    • H04N7/16—Analogue secrecy systems; Analogue subscription systems
    • H04N7/162—Authorising the user terminal, e.g. by paying; Registering the use of a subscription channel, e.g. billing
    • H04N7/163—Authorising the user terminal, e.g. by paying; Registering the use of a subscription channel, e.g. billing by receiver means only
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1043—Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/47—End-user applications
    • H04N21/478—Supplemental services, e.g. displaying phone caller identification, shopping application
    • H04N21/4788—Supplemental services, e.g. displaying phone caller identification, shopping application communicating with other users, e.g. chatting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/47—End-user applications
    • H04N21/488—Data services, e.g. news ticker
    • H04N21/4882—Data services, e.g. news ticker for displaying messages, e.g. warnings, reminders
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00—Television systems
    • H04N7/16—Analogue secrecy systems; Analogue subscription systems
    • H04N7/173—Analogue secrecy systems; Analogue subscription systems with two-way working, e.g. subscriber sending a programme selection signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/253—Telephone sets using digital voice transmission
    • H04M1/2535—Telephone sets using digital voice transmission adapted for voice communication over an Internet Protocol [IP] network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/57—Arrangements for indicating or recording the number of the calling subscriber at the called subscriber's set
    • H04M1/575—Means for retrieving and displaying personal data about calling party

Definitions

  • the present invention in general relates to a communication network and method of providing blending of services to a subscriber of the network and a TV delivery system.
  • the IP Multi-Media Subsystem is an IP multimedia and telephony core network defined by 3GPP and 3GPP2 standards and organizations based on IETF Internet protocols.
  • a 3GPP/IMS network is access independent as it supports IP to IP session over wire line IP, 802.11 , 802.15, CDMA, packet data along with GSM/EDGE/UMTS and other packet data applications.
  • the 3GPP/IMS services architecture is a unified architecture that supports a wide range of services enabled by the flexibility of Session Initiation Protocol (SIP).
  • SIP is a signalling protocol for Internet conferencing, telephony, event notification and instant messaging.
  • SIP was developed within the Internet Engineering Task Force (IETF) Multiparty Multimedia Session Control working group.
  • IETF Internet Engineering Task Force
  • SIP can also invite participants to already existing sessions, such as multicast conferences. Media can be added to (and removed from) an existing session.
  • SIP transparently supports name mapping and redirection services, which supports personal mobility — users can maintain a single externally visible identifier regardless of their network location.
  • IPTV Internet Protocol Television
  • Exemplary embodiments of the present invention are directed to a method and communication network for providing blending of services to a subscriber of one or more services of the communication network and one or more services of a TV delivery system in communication with the network utilizes a server broker function.
  • the service broker function may be configured to execute service package information associated with services of the TV delivery system subscription to include obtaining and delivering caller ID information of the calling party.
  • the service broker function may be configured to alter information in the message request to generate a modified message request that is sent to a phone of the subscriber to modify alerting of the subscriber's phone, while sending the caller ID information of the calling party to an application of the TV delivery system for display.
  • FIG. 1 is a block diagram of an IMS services architecture in accordance with an exemplary embodiment of the present invention.
  • FIG. 2 is a flow diagram for illustrating a method of providing blending of services to a subscriber in accordance with an exemplary embodiment of the present invention.
  • FIGS. 3A and 3B illustrate relationships between the service architectures of a communications network and a TV delivery system.
  • FtG. 1 is a block diagram of an IMS services architecture in accordance with an exemplary embodiment of the present invention.
  • an example IMS services architecture for an IMS communication network is described below.
  • the IMS services architecture 100 of a communication network such as a 3GPP/IMS core netowrk can support multiple application servers providing traditional telephony services and non-telephony services such as instant messaging, push-to-talk, video streaming, multimedia messaging, etc.
  • the services architecture 100 is a collection of logical functions, which can be divided into three layers: a Transport and Endpoint Layer 110, a Session Control Layer 120 and an Application Server Layer 130. Transport and endpoint layer
  • the transport and endpoint layer 110 initiates and terminates SIP signaling to set up sessions and provide bearer services such as conversion of voice from analog or digital formats to IP packets using Realtime Transport Protocol (RTP).
  • RTP Realtime Transport Protocol
  • This layer provides the media gateways for converting the Voice of internet Protocol (VoIP) bearer streams to PSTN TDM format.
  • the media server provides many media related services including conferencing, playing announcements, collecting in-band signaling tones, speech recognition, speech synthesis, etc [0014]
  • the media server resources are shared across all applications. Consequently, each application that requires playing announcements, or collecting digits, for example, can use a common server. These applications include voicemail, advanced 800, interactive VoiceXML (VXML) services, among others.
  • the media servers can also support non-telephony functions such as replicating media for push- to-talk (PTT) service.
  • PTT push- to-talk
  • the session control layer 120 contains the Call Session Control Function (CSCF) 127, which provides the registration of the endpoints and routing of the SIP signaling messages to. the appropriate application server.
  • the (CSCF) 127 is thus a proxy server which provides session control for subscribers accessing services within the IMS.
  • the CSCF 127 may also be referred to as a SIP Server.
  • the CSCF 127 interworks with the transport and endpoint layer 110 to guarantee Quality of Service (QoS) across all services.
  • the session control layer 120 may communicate with a user database such as a Home Subscriber Server (HSS) database 126 that maintains the unique service profile for each end user.
  • HSS Home Subscriber Server
  • HSS 126 is accessible by the session control layer 120 and also the application server layer 110 (dotted line) for user profile data and or subscribed to services, for example.
  • the end user's service profile stores all of the user service information and preferences in a central location. This includes an end user's current registration information (i.e., IP address), roaming information, telephony services (i.e., call forwarding information), instant messaging service information (i.e., buddies list), voice mail box options (i.e., greetings), etc.
  • IP address IP address
  • telephony services i.e., call forwarding information
  • instant messaging service information i.e., buddies list
  • voice mail box options i.e., greetings
  • the session control layer 120 also includes a Media Gateway Control Function (MGCF) 128, which interworks the SIP signaling with the signaling used by the media gateway (i.e., H.248).
  • MGCF Media Gateway Control Function
  • the MGCF 128 manages the distribution of sessions across multiple media gateways.
  • MSFC Media Server Function Control
  • the application server layer 130 contains the application servers, which provide the end-user service logic.
  • the application server layer 130 may also communicate with HSS 126 to access user profile data.
  • Example serves include parlay and SIP application servers.
  • the IMS architecture and SIP signaling is flexible so as to support a variety of telephony and non-telephony application servers. For example, SIP standards have been developed for telephony services and instant messenger (IM) services.
  • the IMS standards define a function in the sub-layer of the services layer between call/connection control and the services layer proper for feature interaction management. This function is termed "Service Coordination and Interaction Manager" (SCIM). The precise operation and capabilities of the SCIM are not defined in the standards, nor are the means by which it would be configured.
  • the example IMS services architecture 100 may include a service capabilities interaction manager (SCIM), referred to herein as a service broker 125 (or service broker function) that can share application state and status information between applications.
  • SCIM service capabilities interaction manager
  • the service broker 125 resides at the session control layer 120 and has corresponding interfaces into the interworking applications.
  • the service broker 125 thus provides critical functionality such as integrating multiple applications into meaningful service offerings, allowing participating applications to be unaware of each other, and providing programmability with an application programming interface (API) for combining services.
  • API application programming interface
  • the service broker 125 is fully consistent with this aspect of the IMS architecture as it is inherently endpoint/access neutral.
  • the service broker 125 manages the integration and coordination of services to control service interaction and/or to provide enriched end-user experiences. Further, service broker 125 accommodates users who can span different endpoints, such as analog, softphones, or wireless phones, and can customize service presentation based on the user's endpoint capabilities, such as voice only, voice/data, or voice/data/multimedia.
  • the service broker 125 can save and use variable user data and session context data to achieve multi-session awareness and manage simultaneous and sequential context- sensitive interactions.
  • the service broker 125 can be used to share network services such as media servers across multiple applications by intercepting their commands and adapting them to a selected media server command interface, although other components in the IMS architecture could provide such sharing.
  • the service broker 125 may, in conjunction with other systems in the maintenance infrastructure, bring about the consolidation of information for billing and operations support systems and an abstracted view to the other elements in the communication network.
  • FIG. 2 is a flow diagram for illustrating a method of providing blending of services to a subscriber in accordance with an exemplary embodiment of the present invention.
  • a subscriber of services provided by a communication network such as a 3GPP/IMS and TV delivery system such as an IPTV may utilize services architectures of these two platforms in order to take advantage of a blending of services.
  • the subscriber's communication network receives a message request (210) from a calling party.
  • the network is a 3GPP/1MS network and the message request is a SIP INVITE message from the calling party.
  • SIP is based on an HTTP-like request/response transaction model. Each transaction consists of a request that invokes a particular method, or function, on the server and at least one response.
  • a transaction may begin with
  • Alice's softphone (a softphone is a multi-media application that works in association with VoIP technology enabling the user to make calls direct from their PC or laptop) sending a message request (SIP-INVITE) addressed to "Bob""s uniform resource identifier (URI).
  • SIP-INVITE message request
  • URI uniform resource identifier
  • An INVITE request message (SIP-INVITE) is an example of a SIP method that specifies the action that the requestor (Alice) wants the server (Bob) to take.
  • the SIP-INVITE contains a number of header fields, which are named attributes that provide additional information about a message.
  • the header fields present in a StP-INVITE may include at least a unique identifier for the call, the destination address, Alice's address, and information about the type of session that Alice wishes to establish with Bob.
  • the message request may be directly received by a service broker function in the communication network.
  • the service broker 125 in the session control layer 120 may receive the message request.
  • a server in the communication network receives the message request from the calling party and directs the message request to a service broker function in the 3GPP/IMS network.
  • this may be a SIP proxy server such as the CSCF 127 in FIG. 1.
  • the service broker function in addition to executing service package information based on the message request to provide caller ID information to the TV delivery system, alters or modifies information (220) in the message request, and sends (230) (either directly or via a proxy server) the modified message request to a phone of the subscriber so that alerting of the subscriber's phone is modified while caller ID information of the calling party is displayed on the subscriber's TV delivery system.
  • the service broker function has the ability to modify an "Alert Info" header field in the SIP-INVITE header so as to change the alerting (ringing, tones, visual indication or otherwise) of the subscriber's phone.
  • alerting on the subscriber's phone can be suppressed while the caller ID information is being displayed on the subscriber's TV delivery system, so as not to interfere with the sound of a program being viewed by the subscriber.
  • the service broker function such as service broker 125 serves as a SCIM in the communications network and provides the capability to blend services utilizing other service delivery architectures, such as that of a TV delivery system.
  • the service broker 125 is a programmable element and has an API, two example scenarios described with respect to the corresponding relationships between different service architectures, in order to convey the range of capabilities of the service broker 125 and its potential to enrich end-user experience.
  • FIGS. 3A and 3B illustrate relationships between the service architectures of a communications network and a TV delivery system.
  • the wireless communications network may be a 3GPP/IMS core network
  • the TV delivery system may be an IPTV system
  • the example methodology may be applied to other platforms besides IPTV for the blending of • services.
  • FIGS. 3A and 3B there is shown a streaming architecture part 300 of an IPTV delivery system and a session control layer of IMS 350 of a communication network.
  • the session control layer of IMS 350 includes a service broker 355 in communication with server 357, which may be a SIP server (CSCF 127) or other proxy server, for example.
  • the service broker 355 is configured to execute an IPTV service package 352 based on the services the subscriber has subscribed to, as reflected in a subscriber database 356.
  • the subscriber database 356 may be a Home Subscriber Server (HSS), which may be several physical databases. This depends on the number of subscribers and the extent of the services which need to be supported.
  • HSS holds variables and identities for the support, establishment and maintenance of calls and sessions made by subscribers.
  • the server 357 and/or service broker 355 may have interfaces to endpoints such as the subscriber's handset 304, which may be a WiFi/GSM handset registered with the IMS, and the subscriber's cell phone 354.
  • the content streaming architecture 300 on the IPTV side includes an IPTV server 305 which may process TV stream data for display at IPTV 310 and communicates with a subscriber input device (not shown), such as a remote control or browser interface, to process TV control data.
  • the IPTV system may or may not support an interface between the IPTV server 305 and the service broker 355 for accepting caller ID data for display on IPTV 310.
  • caller ID and Modified Alerting with IPTV - scenario 1 [0036]
  • Alice's IPTV delivery system supports an interface to the communication system or network (e.g., IMS 350) that accepts caller ID and displays it on the user's (Alice's) TV.
  • the IPTV Set Top Box (not shown in FIG. 3A) supports an application such as a browser capability (see browser window 315), whereby the user can click on a link as desired.
  • the IMS 350 includes the service broker 355, which is able to provide originating and terminating service brokering.
  • the service broker 355 provides the caller ID information to an IPTV application at IPTV server 305 when terminating calls to Alice's home phone 304 (which supports SIP and may also be referred to as a SIP phone) and when terminating calls to Alice's WiFi/GSM handset (mobile phone) 354 (i.e., cell phone) when it is registered in the IMS 350.
  • the service broker 355 is able to modify or suppress normal alerting (e.g., ringing) in these phones by modifying the Alert Info header field in the SIP INVITE that is sent to the terminating devices. The scenario is described in more detail below with reference to FIG. 3A.
  • the Alert Info header may be set to result in a "ping" or other less-intrusive alert.
  • Alice is relaxing and watching TV. Calls come in, but Alice is able to see who the calls are from on the TV set since she subscribes to a caller ID service. She is also able to activate a modified alerting feature, which in this example may be called "Silent Alerting", which prevents her phone(s) from alerting. She can even see those who are trying to reach her on her GSM/WiFi cell phone 354, since when she is at home it is registered in the IMS 350.
  • Alice turns on her TV 310 and selects a program from the IPTV program guide provided via the STB (not shown in FIG.
  • a call comes into the IMS for Alice's home phone 304. Since Alice is subscribed to a blended service, the server 357 directs the SIP INVITE message to the service broker 355. [0039] If not cached, the service broker 355 retrieves Alice's terminating service package information from subscriber database 356 (such as an HSS) and begins to execute the IPTV service package 352. If the calling name is not encapsulated in the SIP INVITE message (as it could be for a call coming in from the PSTN), the service broker 355 may query a calling name web server (nor shown) to obtain this information.
  • subscriber database 356 such as an HSS
  • the service broker 355 may query a calling name web server (nor shown) to obtain this information.
  • the service broker 355 sends the SIP INVITE message to Alice's home phone 304 via the server 357, and sends the calling name information (caller ID information 320) to the IPTV application at IPTV server 305 on its proscribed interface.
  • the service broker 355 could be configured to receive this SIP INVITE message directly.
  • the service broker 355 may include an invitation to activate Silent Alerting.
  • Another call comes into the IMS for Alice's home phone 304 and the server 357 directs the SIP INVITE message to the service broker 355.
  • the service broker 355 retrieves Alice's terminating service package information from subscriber database 356, which now indicates that Silent Alerting is active, and begins to execute the service package 352. If the calling name is not encapsulated in the SIP INVITE message, the service broker 355 queries a calling name web server to obtain this information. [0045] Since Silent Alerting is active, the service broker 355 sets the Alert-Info in the SIP INVITE message to "0" to alter the field.
  • the service broker 355 sends the modified SIP INVtTE message to Alice's home phone via the server 357 (or directly if no server 357 present), and sends the caller ID information 320 to the IPTV application at server 305 on its proscribed interface.
  • Alice sees the caller ID on the TV 310, but the phone 304 does not ring since Alice's phone 304 received the modified SIP INVITE and interprets the Alert- Info set to "0" as indicating no alerting. The call is urgent, so Alice picks up the phone 304 and answers the call.
  • Another call comes into the IMS 350 for Alice, but this time it is for her mobile (GSM/WiFi) phone 354.
  • the call came to the IMS 350 since Alice is at home with her mobile phone 354 and it had registered with the IMS.
  • the server 357 directs the SIP INVITE message to the service broker 355.
  • the service broker 355 could be configured to receive this SIP INVITE message directly.
  • the service broker 355 retrieves Alice's terminating service package information from the subscriber database 356, which now indicates that Silent Alerting is active, and begins to execute the service package 352.
  • the service broker 355 may query a calling name web server to obtain this information.
  • the service broker 355 Since Silent Alerting is active, the service broker 355 sets the Alert Info in the header field of the SIP INVITE to "0". Then the service broker 355 sends the modified SIP INVITE to Alice's mobile phone 354 via the server 357, and sends the caller ID information 320 to the IPTV application of server 305 on its proscribed interface. Assuming the interface allows additional text, the service broker 355 includes an indication that it is Alice's mobile phone 354 that is being called.
  • Alice sees the caller ID on the TV 310 along with the indication that it is Alice's mobile phone 354 that is being called, but the phone 354 does not ring since the phone 354 received the modified SIP INVITE and interprets the Alert-Info set to "0" as indicating no alerting.
  • the call is urgent, so Alice picks up the mobile phone
  • Scenario 1 thus illustrates a blended service of TV caller ID with modified alerting (silent alerting) which takes advantage of the SIP Alert-Info header.
  • the SIP VoIP is designed to support and correctly interpret the Alert-Info setting, and the service broker 355 alters the Alert-Info header based on the information it obtains from the user over its HTTP interface.
  • a further feature of this blended service is to provide caller ID and silent alerting for calls to the mobile phone 354. This is possible with GSM/WiFi Roaming and having the service broker
  • both an IMS architecture for communication/session services and an IPTV content streaming architecture participated in this blended service.
  • the IP access (utilizing DSL) is shared by both architectures.
  • the service broker 355 plays the role of the SCIM and serves to meld the two service architectures by sending event data from the IMS 350 to the IP TV system 300.
  • the service broker 355 is thus configured to receive a specific activation request from a user and to modify SIP messages based on specific application blending logic (including the activation information). Caller ID and Modified Alerting with IPTV - Scenario 2
  • the TV delivery system 300 does not support an interface to the communication system (IMS 350) for caller ID.
  • a Set Top Box 320 is used that has a window-like environment that can run an application (client software 325) that is able to set a focus window to receive events from the TV remote control (e.g., the events may map to keystroke events).
  • client software 325) that is able to set a focus window to receive events from the TV remote control (e.g., the events may map to keystroke events).
  • the service broker 355 in the IMS 350 of the network is able to communicate with the client software 325 in the STB 318 and handle incoming SIP INVITE messages, depending on TV remote control events. The scenario is described in more detail below with reference to FIG. 3B.
  • Bob turns on his TV 310 and selects a program from the IP TV program guide provided via the STB 318.
  • a call comes into the IMS 350 for Bob's home phone 304.
  • the server 357 directs the SIP INVITE to the service broker 355.
  • the service broker 355 could be configured to receive this SIP INVITE message directly.
  • the service broker 355 retrieves Bob's terminating service package information from the subscriber database 356 (if not cached) and begins to execute the service package 352. If the calling name is not encapsulated in the SIP INVITE (as it could be for a call coming in from the PSTN), the service broker 355 queries a calling name web server to obtain this information.
  • the service broker 355 sends the SIP INVITE message to Bob's home phone 304 via the server 357, and sends caller ID information 320' to the client software application 325 on Bob's STB 318.
  • the phone 304 rings and Bob simultaneously sees the caller ID on the TV, along with clickable (via the TV remote control) links to reject the call, send the call to voice mail, and activate Silent Alerting for a given duration.
  • the service broker 355 retrieves Bob's terminating service package information from the subscriber database 356, which now indicates that Silent Alerting is active, and begins to execute the service package 352. If the calling name is not encapsulated in the SIP INVITE, the service broker 355 queries a calling name web server to obtain this information.
  • the service broker 355 Since Silent Alerting is active, the service broker 355 sets the Alert-Info in the SIP INVITE to "0". Then the service broker 355 sends the modified SIP INVITE message to Bob's home phone 304 via the server 357 (or directly if no server 357 present), and sends the caller ID information 320' to the client software application 325 on Bob's STB 318.
  • the TV caller ID service allows independence of the IP TV delivery system, that is, so long as the IP TV client software application 325 can operate in a windows-like environment and the STB 318 supports a windows-like environment.
  • Added capabilities with this version could be based on the client software 325 picking up the TV remote events and sending HTTP messages to the service broker 355 to affect call treatment.
  • more sophisticated capabilities may be possible if the client software 325 on the STB 318 would provide an API so that the software client interacting with the service broker 355 can have more complete information.
  • An example might be indicating what program is being viewed. In such a case, a parental alert and control capability (such as described for incoming and outgoing calls) could be implemented for certain programs.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Computer Security & Cryptography (AREA)
  • General Engineering & Computer Science (AREA)
  • Telephonic Communication Services (AREA)
  • Information Transfer Between Computers (AREA)
EP06845467.7A 2005-12-15 2006-12-14 Verfahren und netzwerk zur bereitstellung gemischter dienste für einen abonnenten Not-in-force EP1961190B1 (de)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US11/300,418 US20070140299A1 (en) 2005-12-15 2005-12-15 Method and network for providing service blending to a subscriber
PCT/US2006/047794 WO2007070652A1 (en) 2005-12-15 2006-12-14 Method and network for providing service blending to a subscriber

Publications (2)

Publication Number Publication Date
EP1961190A1 true EP1961190A1 (de) 2008-08-27
EP1961190B1 EP1961190B1 (de) 2015-02-11

Family

ID=37836804

Family Applications (1)

Application Number Title Priority Date Filing Date
EP06845467.7A Not-in-force EP1961190B1 (de) 2005-12-15 2006-12-14 Verfahren und netzwerk zur bereitstellung gemischter dienste für einen abonnenten

Country Status (6)

Country Link
US (1) US20070140299A1 (de)
EP (1) EP1961190B1 (de)
JP (2) JP2009520410A (de)
KR (1) KR101275421B1 (de)
CN (1) CN101331732A (de)
WO (1) WO2007070652A1 (de)

Families Citing this family (48)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070209054A1 (en) * 2005-09-30 2007-09-06 Bellsouth Intellectual Property Corporation Methods, systems, and computer program products for providing communications services
US20070209065A1 (en) * 2005-09-30 2007-09-06 Bellsouth Intellectual Property Corporation Methods, systems, and computer program products for providing network convergence of applications and devices
US8804695B2 (en) * 2005-09-30 2014-08-12 At&T Intellectual Property I, L.P. Methods, systems, and computer program products for providing alerts and notifications
US8223938B2 (en) 2005-09-30 2012-07-17 At&T Intellectual Property I, L.P. Methods, systems, and computer program products for providing caller identification services
US20070208619A1 (en) * 2005-09-30 2007-09-06 Bellsouth Intellectual Property Corporation Methods, systems, and computer program products for providing targeted advertising to communications devices
US7890552B2 (en) * 2005-09-30 2011-02-15 At&T Intellectual Property I, L.P. Methods, systems, and computer program products for implementing media content analysis, distribution, and re-allocation services
US9008293B2 (en) * 2005-11-25 2015-04-14 At&T Intellectual Property I, L.P. Caller ID information to internet protocol television displays
US7693270B2 (en) * 2005-12-15 2010-04-06 Alcatel-Lucent Usa Inc. Method and network for providing service blending to a subscriber
ATE487314T1 (de) * 2006-02-24 2010-11-15 Ericsson Telefon Ab L M Ims-befähigter steuerkanal für iptv
JP2007251232A (ja) * 2006-03-13 2007-09-27 Oki Electric Ind Co Ltd 電話機能を備えた映像再生装置
US20070217399A1 (en) * 2006-03-15 2007-09-20 Joseph Gigo K Hotline implementation using session initiation protocol legacy telephones
US20070250845A1 (en) * 2006-03-31 2007-10-25 Sbc Knowledge Ventures, L.P. System and method of delivering calls
US20070250884A1 (en) * 2006-04-10 2007-10-25 Sbc Knowledge Ventures, Lp System and method of providing call source information
US8631078B2 (en) * 2006-07-07 2014-01-14 Google Inc. Method and system for embedded personalized communication
US7912070B1 (en) * 2006-07-12 2011-03-22 Nextel Communications Inc. System and method for seamlessly switching a half-duplex session to a full-duplex session
US8135342B1 (en) 2006-09-15 2012-03-13 Harold Michael D System, method and apparatus for using a wireless cell phone device to create a desktop computer and media center
US7894585B2 (en) * 2007-03-28 2011-02-22 Verizon Patent And Licensing Inc. Calling party name provisioning
CN101330547A (zh) * 2007-06-20 2008-12-24 朗迅科技公司 在VoIP网络中分布的用于提供服务的媒体资源
WO2009006630A1 (en) * 2007-07-05 2009-01-08 Starent Networks, Corp System and method for reducing latency in call setup and teardown
WO2009024071A1 (fr) * 2007-08-17 2009-02-26 Huawei Technologies Co., Ltd. Système, procédé et dispositif pour réaliser une sécurité de contenu multimédia iptv
WO2009024006A1 (fr) * 2007-08-21 2009-02-26 China Mobile Communications Corporation Contrôleur de session locale, sous-système multimédia ip et procédé d'enregistrement de session
EP2157744A4 (de) * 2007-08-21 2012-08-22 Huawei Tech Co Ltd Verfahren und system zur authorisationssteuerung eines dienstmittels
EP2051472A1 (de) * 2007-10-19 2009-04-22 Koninklijke KPN N.V. System zur Verwaltung von Dienstinteraktionen
EP2164223A1 (de) 2008-09-12 2010-03-17 Koninklijke KPN N.V. System zur Verwaltung von Dienstinteraktionen
CN101855883A (zh) * 2007-10-19 2010-10-06 皇家Kpn公司 用于管理服务交互的系统
WO2009052650A1 (en) * 2007-10-26 2009-04-30 Lucent Technologies Inc. Method and terminal for forwarding an iptv program to an sip terminal
KR101163526B1 (ko) * 2007-12-21 2012-07-11 남기원 아이 피 티브이를 이용한 외부 데이터 인터페이스 시스템및 그 방법
EP2081362B1 (de) * 2008-01-21 2013-07-24 Alcatel Lucent Ressourcenarbitrierung in einer konvergierten Multimediaumgebung
US20090219953A1 (en) * 2008-02-28 2009-09-03 Lucent Technologies Inc. Method and apparatus for allowing non-ip based networks to interact with iptv-based systems
US8060655B1 (en) 2008-02-29 2011-11-15 Sprint Communications Company L.P. User interface for customer premises communications gateway
US20090238168A1 (en) * 2008-03-18 2009-09-24 Paraxip Technologies Inc. Communication node and method for handling sip communication
WO2009120030A2 (ko) * 2008-03-28 2009-10-01 삼성전자 주식회사 Iptv 통신 서비스를 제공하는 응용에 대한 정보 수신 방법 및 장치
GB2460651B (en) * 2008-06-03 2012-09-12 Metaswitch Networks Ltd Delivery of media data
US8763086B2 (en) * 2008-08-29 2014-06-24 Telefonaktiebolaget L M Ericsson (Publ) Service sharing among IMS users
KR101609219B1 (ko) 2008-10-29 2016-04-06 삼성디스플레이 주식회사 액정표시장치 및 이의 제조방법
CN102227898B (zh) * 2008-12-01 2015-07-22 艾利森电话股份有限公司 用于处理ims通信系统中的通信会话的媒体类型的方法和移动用户设备以及ims节点
US9317856B2 (en) * 2009-01-19 2016-04-19 Alcatel Lucent System, method and computer readable medium for application placement
US8433304B2 (en) * 2009-01-22 2013-04-30 Centurylink Intellectual Property Llc System and method for displaying cellular caller ID on TV
US8584188B2 (en) * 2009-01-22 2013-11-12 Centurylink Intellectual Property Llc System and method for displaying call status on TV
US9374307B2 (en) * 2009-01-27 2016-06-21 Telefonaktiebolaget Lm Ericsson (Publ) Group session management for policy control
US8374172B2 (en) * 2009-04-03 2013-02-12 At&T Intellectual Property I, L.P. Method and apparatus for managing communication sessions
CN102457772B (zh) * 2010-10-29 2014-04-02 华为终端有限公司 信息显示方法及设备
US8406234B2 (en) * 2010-12-08 2013-03-26 Motorola Solutions, Inc. Method and apparatus for processing multiple incoming calls in a single device
KR20120065612A (ko) * 2010-12-13 2012-06-21 삼성전자주식회사 디지털 티브이에서 통신 단말기의 이벤트 발생 알림 방법 및 장치
US8811281B2 (en) 2011-04-01 2014-08-19 Cisco Technology, Inc. Soft retention for call admission control in communication networks
KR20140099359A (ko) * 2013-02-01 2014-08-12 (주)휴맥스 콘텐츠 재생 방법 및 장치
US10644893B2 (en) * 2018-08-06 2020-05-05 At&T Intellectual Property I, L.P. Ensuring correctness of session identifiers in call duration records in mobile networks
CN110276644A (zh) * 2019-06-24 2019-09-24 重庆物联利浪科技有限公司 一种在线服务资源的动态融合方法和装置

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH0556190A (ja) * 1991-08-28 1993-03-05 Matsushita Electric Ind Co Ltd テレビシステム
US5825862A (en) * 1995-11-30 1998-10-20 Bell Atlantic Network Services, Inc. Method of altering the destination telephone number of an incoming call
US6427003B1 (en) * 2000-05-05 2002-07-30 Joseph C. Corbett Video caller identification systems and methods
JPH10240656A (ja) * 1997-02-25 1998-09-11 Fujitsu Ltd 着信制御方式
DE69841461D1 (de) * 1997-04-18 2010-03-11 British Telecomm Netzwerk mit computer telefon integration
JPH11331800A (ja) * 1998-05-19 1999-11-30 Nec Eng Ltd ホテル用テレビジョン制御装置
JP2000138773A (ja) * 1998-10-29 2000-05-16 Sanyo Electric Co Ltd テレビジョン受像機
DE60024750D1 (de) * 1999-10-01 2006-01-19 Nortel Networks Ltd Aufbau von Verbindungen über ein Kommunikationsnetzwerk
KR20010109966A (ko) * 2000-06-05 2001-12-12 구자홍 Ｉｐ를 기반으로 하지 않는 네트워크에서 인터넷 서비스를제공하는 장치 및 방법
AU2002241645A1 (en) * 2000-12-14 2002-06-24 Powerhouse Technology, Inc. Circuit switched cellulat network to internet calling
US20030055981A1 (en) * 2001-09-20 2003-03-20 Requena Jose Costa Provision of call features
US6678362B2 (en) * 2002-01-31 2004-01-13 Sony Corporation System and method for effectively managing telephone functionality by utilizing a settop box
US20040261115A1 (en) * 2003-06-23 2004-12-23 Eyal Bartfeld Voice over IP receiver assisted call control
ATE467971T1 (de) * 2004-04-13 2010-05-15 Research In Motion Ltd Verfahren für ein push-to-talk-endgerät für eine initiierungsprotokoll-sitzung zur anzeige des antwortbetriebsmodus für einen push-to-talk- netzwerkserver eines internetprotokolls
US7532712B2 (en) * 2004-12-01 2009-05-12 Time Warner Cable, Inc. System and method for providing caller ID service in a multi-region cable network

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO2007070652A1 *

Also Published As

Publication number Publication date
JP2013218724A (ja) 2013-10-24
US20070140299A1 (en) 2007-06-21
EP1961190B1 (de) 2015-02-11
KR20080084954A (ko) 2008-09-22
KR101275421B1 (ko) 2013-06-14
CN101331732A (zh) 2008-12-24
JP2009520410A (ja) 2009-05-21
WO2007070652A1 (en) 2007-06-21

Similar Documents

Publication Publication Date Title
EP1961190B1 (de) Verfahren und netzwerk zur bereitstellung gemischter dienste für einen abonnenten
US7693270B2 (en) Method and network for providing service blending to a subscriber
US9071880B2 (en) System and method for control of a set top box
US7458084B2 (en) Methods and systems for converged service creation and execution environment applications
US7103644B1 (en) Systems for an integrated data network voice-oriented service and non-voice-oriented service converged creation and execution environment
US8098805B2 (en) System and method for providing telephone call notification and management in a network environment
EP1263244B1 (de) Anruferprofilpresäntationsdienst in einem Multimedianetzwerk
US20150189073A1 (en) Displaying call log information on a display device
US20070058637A1 (en) Method for multi-channel multi-device call transfer
US7440445B1 (en) Method and apparatus for storing and activating universal resource locators and phone numbers
EP1263242B1 (de) Anklopfdienst in einem Multimedianetzwerk
US8072968B2 (en) Method and apparatus for supporting multiple active sessions on a per user basis
EP1890463A1 (de) Zugriff auf interaktive Dienste über das Internet
Ahuja et al. VoIP: What is it Good for? If you think VoIP is just an IP version of telecom-as-usual, think again. A host of applications are changing the phone call as we know it.
US8625754B1 (en) Method and apparatus for providing information associated with embedded hyperlinked images
US20080031232A1 (en) Web services and plug-in framework in VOIP environment
Ensor et al. Blending IPTV Services
Dianda et al. Programmable service platforms for converged voice/data services
US8799976B1 (en) Method and apparatus for providing a web session with a commercial advertiser
Müller Service Architectures in H. 323 and SIP–A Comparison

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20080526

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

RAP3 Party data changed (applicant data changed or rights of an application transferred)

Owner name: LUCENT TECHNOLOGIES INC.

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: ALCATEL LUCENT

DAX Request for extension of the european patent (deleted)
17Q First examination report despatched

Effective date: 20130327

111Z Information provided on other rights and legal means of execution

Free format text: AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

Effective date: 20130410

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: ALCATEL LUCENT

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602006044471

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0029060000

Ipc: H04M0001253000

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

RIC1 Information provided on ipc code assigned before grant

Ipc: H04N 7/16 20110101ALI20140829BHEP

Ipc: H04N 21/488 20110101ALI20140829BHEP

Ipc: H04L 29/06 20060101ALI20140829BHEP

Ipc: H04L 29/08 20060101ALI20140829BHEP

Ipc: H04N 21/4788 20110101ALI20140829BHEP

Ipc: H04M 1/253 20060101AFI20140829BHEP

Ipc: H04M 1/57 20060101ALI20140829BHEP

Ipc: H04N 7/173 20110101ALI20140829BHEP

INTG Intention to grant announced

Effective date: 20140924

D11X Information provided on other rights and legal means of execution (deleted)
GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 710229

Country of ref document: AT

Kind code of ref document: T

Effective date: 20150315

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602006044471

Country of ref document: DE

Effective date: 20150319

REG Reference to a national code

Ref country code: NL

Ref legal event code: VDEP

Effective date: 20150211

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 710229

Country of ref document: AT

Kind code of ref document: T

Effective date: 20150211

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150211

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150211

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150211

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150211

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150611

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150211

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150211

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150512

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150211

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150211

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150211

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150211

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150211

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150211

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602006044471

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150211

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 10

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150211

26N No opposition filed

Effective date: 20151112

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150211

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150211

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151214

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150211

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20151231

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20151214

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20151231

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 11

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150211

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20061214

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150211

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150211

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 12

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150211

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602006044471

Country of ref document: DE

Representative=s name: MENZIETTI WETZEL, DE

Ref country code: DE

Ref legal event code: R081

Ref document number: 602006044471

Country of ref document: DE

Owner name: PROVENANCE ASSET GROUP LLC, PITTSFORD, US

Free format text: FORMER OWNER: ALCATEL LUCENT, BOULOGNE BILLANCOURT, FR

REG Reference to a national code

Ref country code: GB

Ref legal event code: 732E

Free format text: REGISTERED BETWEEN 20190418 AND 20190426

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20201019

Year of fee payment: 15

Ref country code: GB

Payment date: 20201029

Year of fee payment: 15

Ref country code: DE

Payment date: 20201027

Year of fee payment: 15

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602006044471

Country of ref document: DE

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20211214

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20211214

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220701

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20211231