EP1897343A1 - Dienstfehlerhandhabung in einem kommunikationsnetz - Google Patents
Dienstfehlerhandhabung in einem kommunikationsnetzInfo
- Publication number
- EP1897343A1 EP1897343A1 EP06765812A EP06765812A EP1897343A1 EP 1897343 A1 EP1897343 A1 EP 1897343A1 EP 06765812 A EP06765812 A EP 06765812A EP 06765812 A EP06765812 A EP 06765812A EP 1897343 A1 EP1897343 A1 EP 1897343A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- request
- service
- specific data
- user
- control device
- 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
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- 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/1063—Application servers providing network services
-
- 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
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/143—Termination or inactivation of sessions, e.g. event-controlled end of session
- H04L67/145—Termination or inactivation of sessions, e.g. event-controlled end of session avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session
-
- 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/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
Definitions
- the present invention relates to service error handling in a communications network.
- the invention relates to processing error responses received by a control entity.
- Fig. 1 shows a basic architecture of an Internet Protocol (IP) Multimedia Subsystem (IMS) .
- IP Internet Protocol
- IMS Internet Multimedia Subsystem
- UEs User Equipments
- UEs access the IMS network to be able to use services provided by the IMS network.
- UEs communicate with the IMS network by attaching to a packet switched (PS) network, such as General Packet Radio Service (GPRS) network.
- PS packet switched
- GPRS General Packet Radio Service
- the UE may access the IMS network over a radio access network (RAN) or over a fixed line access network, such as Digital Subscriber Line (DSL) access.
- RAN radio access network
- DSL Digital Subscriber Line
- the IMS network comprises Session Initiation Protocol (SIP) proxies which process SIP signaling.
- SIP is an application-layer control protocol for creating, modifying, and terminating sessions with one or more participants.
- SIP proxies in the IMS network are called Call State Control Functions (CSCF) and the main features of the CSCF are to perform session control functions, service control functions and address translation functions.
- CSCF Call State Control Functions
- P-CSCF Proxy-CSCF
- I-CSCF Interrogating-CSCF
- S-CSCF Serving-CSCF
- the P-CSCF (not shown) is the first contact point in the IMS network.
- a P-CSCF is allocated to the UE.
- the same P-CSCF remains allocated to the UE during the lifetime of the registration, and all signaling between the UE and the IMS network traverses the P-CSCF.
- the I-CSCF (not shown) is located at the edge of the administrative (operator) domain, in signaling path between the P-CSCF and the S-CSCF.
- the I-CSCF routes received requests to a correct destination, typically to an S-CSCF.
- the S-CSCF implements the session control in the IMS network and acts as SIP registrar. All SIP signaling initiated by or destined to a certain UE traverses the S-CSCF assigned to serve the UE.
- a Home Subscriber Server (HSS) or User Mobility Server (UMS) stores all the user related subscription data, such as location information, security information and user profile information defining the services that the user is subscribed to.
- Subscription data is created into the HSS when an end user obtains an IMS subscription from an IMS service provider.
- the subscription data is associated with an IMS private user identity (IMPI) of the user.
- the HSS also maintains information about the S-CSCF allocated to the user.
- the I-CSCF may contact the HSS in order to find out the address of the allocated S- CSCF based on the IMS public user identity (IMPU) and IMS private user identity (IMPI) of the user sending the registration request.
- IMPU IMS public user identity
- IMPI IMS private user identity
- AS Application Servers
- ISC IMS Service Control
- an S-CSCF For establishing a session between an inviting UE and an invited UE, an S-CSCF forwards SIP requests towards the invited UE, possible after first giving the session control to an AS for executing a service and after the AS has given the session control back to the S-CSCF. Instead of the invited UE, the request could be terminated to an AS, for example to a voice mail server.
- Fig. 2 shows a structure of Filter Criteria that is basically a data structure including user specific service information from which an S-CSCF is able determine when an AS is to be contacted for providing a service to the user.
- User profiles are stored, in the HSS, per Private User Identity
- each user profile may comprise several service profiles associated with a Public User Identity (IMPU) .
- Filter Criteria are included in the service profile of the user profile downloaded from the HSS to the S-CSCF during the IMS registration procedure.
- Filter Criteria include a priority field. If the service profile comprises more than one Filter Criteria, the S- CSCF assesses Filter Criteria according to the priority of each Filter Criteria (highest priority is taken first) .
- a Trigger Point comprises one or more service trigger points which define the exact conditions of which have to be fulfilled in order to start a service and a certain AS is to be contacted. Examples of service trigger points are the presence of a specific SIP method (INVITE, OPTIONS, SUBSCRIBE,..), partial or full match on the content of any SIP header or SDP line, presence or absence of any SIP header, and content of Request-URI .
- Filter criteria further include the address of an AS (SIP URI) to be contacted if a service is to be started based on fulfilled conditions of one of the service point triggers.
- a Default Handling parameter of Filter Criteria defines the action to be taken if the AS to be contacted is not available, i.e. cannot be reached. The possible actions in this case are abort or continue the processing of the SIP request.
- Filter Criteria could include service information, which is transparent service related information that an S-CSCF may forward to an AS when contacting the AS .
- an S-CSCF is not able to contact an AS which is defined in the Filter Criteria to provide the service in question. Possible reasons for unavailability of the AS are, for example, some very fatal problem in the AS or an error in ISC interface configuration. The S-CSCF must then proceed according to Default Handling instructions in the Filter Criteria. However, even if the S- CSCF is able to contact the AS, further problems may occur relating to service execution in the AS. For example, the AS is not necessarily able to provide the service based on the information received from S-CSCF or an AS internal error may occur during the service execution.
- the AS responds to the S-CSCF with a SIP response code indicating that an error has occurred and possible more detailed information about the nature or type of the error.
- the above mentioned Default Handling parameter neither is examined nor used in these cases, since the AS was actually contacted successfully and the problem occurred only later, during the service execution in the AS .
- a service control interface e.g. the IMS service control interface (ISC).
- ISC IMS service control interface
- control device for providing communication control for users in a communications network
- the control device comprising: controlling means for controlling communication requests of the users; and evaluating means for evaluating response messages received from applications, wherein if a response message received from an application for a communication request is evaluated as an error message by the evaluating means, the controlling means is configured to continue control of the communication request based on service- specific data.
- service-specific data associated with a user
- the service-specific data including communication request handling instructions for response messages received from applications providing services; initiating a service for the user based on a request received from the user; receiving, in response to the initiating step, an error response from the service; and determining whether to continue processing the request received from the user based on the instructions given for the error response in the service-specific data.
- a serving device for executing services for users of a communications network comprising:
- determining means for determining whether a request received from a control device providing communication control for the users in the communications network can be handled by the serving device; transmitting means for transmitting a response message for the request to the control device, the response message indicating to the control device a determination result by the determining means; and adding means for adding information to the response message transmitted by the transmitting means if the determining means determines that the request cannot be handled by the serving device, wherein the information is to be used by the control device in deciding on communication request control .
- a data providing device comprising:
- At least one database storing user-specific data, the user-specific data comprising service-specific data; receiving means for receiving a request for retrieving service-specific data associated with a user, from a control device providing communication control for the user in a communications network; and transmitting means for transmitting the service-specific data to the control device upon the request, the service-specific data comprising, for at least one application, instructions for performing communication request control in correspondence with response messages transmitted from the at least one application to the control device.
- control system comprising:
- control device for providing communication control for users in a communications network; and a data providing device
- control device comprises controlling means for controlling communication requests of the users, evaluating means for evaluating response messages received from applications, and retrieving means for issuing a request for retrieving service-specific data associated with a user from the data providing device
- data providing device comprises at least one database storing user-specific data, the user-specific data comprising service-specific data, receiving means for receiving the request for retrieving the service- specific data associated with the user from the control device, and transmitting means for transmitting the service-specific data to the control device upon the request, wherein if a response message received from an application for a communication request is evaluated as an error message by the evaluating means, the controlling means is configured to continue control of the communication request based on the service-specific data received from the data providing device.
- control device for providing communication control for users in a communications network; and a serving device for executing services for the users, wherein the serving device comprises determining means for determining whether a request received from the control device can be handled by the serving device, and transmitting means for transmitting a response message for the request to the control device, the response message indicating to the control device a determination result by the determining means, and wherein the control device comprises controlling means for controlling communication requests of the users, and evaluating means for evaluating response messages received from the serving device, wherein if the response message received from the serving device for a communication request is evaluated as an error message by the evaluating means, the controlling means is configured to continue control of the communication request on the basis of service-specific data.
- the present invention can also be implemented as computer program product.
- an S-CSCF behavior in error situations where an error response is received from an AS can be improved.
- Fig. 1 shows a basic architecture of an Internet Protocol (IP) Multimedia Subsystem (IMS) to which the present invention is applicable.
- IP Internet Protocol
- IMS Internet Multimedia Subsystem
- Fig. 2 shows a structure of Filter Criteria according to the prior art.
- FIG. 3 shows a schematic block diagram illustrating an embodiment of a structure of a control device, a serving device and a data providing device according to the invention.
- FIG. 4 shows a flow chart illustrating a method of providing communication control for users in a communications network according to an embodiment of the invention.
- FIG. 5 shows a schematic block diagram illustrating signaling in an IMS network according to an embodiment of the invention .
- Fig. 6 shows a structure of Filter Criteria according to a first implementation example of the invention.
- Fig. 7 shows a structure of Filter Criteria according to a second implementation example of the invention.
- FIG. 3 shows a schematic block diagram illustrating an embodiment of a structure of a control device 100, a data providing device 200 and a serving device 300 according to the invention .
- the control device 100 provides communication control for users in a communications network.
- the control device 100 may comprise an S-CSCF (Serving Call State Control Function) in an IMS (Internet protocol Multimedia Subsystem) network.
- the control device comprises a controlling block 11 for controlling/handling communication requests of users and an evaluating block 12 for evaluating response messages received from applications which may run services for users of the communications network.
- the control device 100 may further comprise a retrieving block 13 for issuing a request for retrieving service-specific data associated with a user from the data providing device 200.
- a communication request may be a request for establishing a session or a request for sending a message .
- the data providing device 200 may comprise a Home Subscriber Server (HSS) or User Mobility Server (UMS) and comprises at least one database 21 storing user-specific data, such as a user profile, comprising service-specific data.
- the data providing device 200 further comprises a receiving block 22 for receiving the request for retrieving the service- specific data associated with the user from the control device 100, and a transmitting block 23 for transmitting the service- specific data to the control device 100 upon the request.
- the serving device 300 executes services for the users of the communications network and may comprise an Application Server (AS) running an application.
- the serving device comprises a determining block 31 for determining whether a request received from the control device 100 can be handled by the serving device 300, and a transmitting block 32 for transmitting a response message for the request to the control device 100, the response message indicating to the control device 100 a determination result by the determining block 31.
- the serving device 300 may further comprise an adding block 33 for adding information to the response message transmitted by the transmitting block 32 in case the determining block 31 determines that the request cannot be handled by the serving device 300, wherein the information is to be used by the control device in deciding on communication request control.
- the controlling block 11 continues control of the communication request on the basis of service-specific data.
- This data may have been retrieved from the data providing device 200 by the retrieving block 13 of the control device 100 or may have been provided to the control device 100 directly from an operator of the control device 100.
- the evaluating block 12 of the control device 11 may further evaluate any information added to the response message received from the application or serving device 300, the controlling block 11 deciding on continuing control of the communication request using the information added to the response message.
- the structures of the devices are not limited to those shown in Fig. 3.
- Blocks of a device may be combined to implement the functionality of the combined blocks in one 'super-block', or the functionality of a block may be further separated into sub-blocks .
- the blocks of each device may be implemented as application specific integrated circuits or by digital signal processor (s) .
- the devices shown in Fig. 3 are described to an extent necessary for understanding the present invention, and may additionally comprise conventional blocks and functions necessary for acting e.g. as S-CSCF, HSS and AS.
- Fig. 4 shows a flow chart illustrating a method of providing communication control for users in a communications network according to an embodiment of the invention.
- a service-specific data associated with a user are retrieved, the service-specific data including communication request handling instructions for response messages received from applications providing services.
- a service for the user is initiated.
- an error response from the service in step S44 it is decided on continuing (i.e. it is determined whether to continue) processing the request received from the user based on the instructions given for the error response in the service-specific data.
- control device 100 the functions of the control device 100 are implemented in an S-CSCF (Serving Call State Control Function) 51
- the functions of the data providing device 200 are implemented in an HSS (Home Subscriber Server) /UMS (User Mobility Server) 52
- the functions of the serving device 300 are implemented in an AS (Application Server) 53.
- S-CSCF Server Call State Control Function
- HSS Home Subscriber Server
- UMS User Mobility Server
- AS Application Server
- the S-CSCF 51 Upon registration of a user the S-CSCF 51 fetches initial Filter Criteria (iFC) via Cx interface from the HSS/UMS storing all the user related subscription data, such as location information, security information and user profile information defining the services that the user is subscribed to.
- the iFC are service-specific data associated with the user.
- the iFC further include communication request handling instructions for response messages received from applications providing services.
- the communication request handling instructions comprise response code specific default handling parameters.
- the S-CSCF 51 Upon receiving a request from the registered user, after having evaluated the iFC, the S-CSCF 51 initiates a service request to the AS 53 via ISC interface. In case the AS 53 is reachable but the application fails, the AS 53 responds with an error message, e.g. with a 4xx, 5xx or 6xx class response .
- SIP Responses include a 3-digit Status- Code and a Reason-Phrase.
- the Status-Code is intended for use by automata, whereas the Reason-Phrase is intended for the end user giving a short textual description of the Status-Code.
- SIP Responses are categorized into six classes based on the first digit of the Status-Code:
- Client Error the request contains bad syntax or cannot be fulfilled at this server
- the S-CSCF 51 When the S-CSCF 51 receives the error message from the AS 53, it decides on how to continue processing the request based on the instructions given for the error message in the iFC. For example, the S-CSCF 51 may further handle the request based on the response code specific default handling parameters, where some response codes can be configured as 'continue', meaning that the S-CSCF 51 should try to further process the request received from the user, and some other response codes can be configured as 'abandon', meaning that the S-CSCF 51 should continue the response handling.
- the S-CSCF 51 may check and process also additional information added to the error message, e.g. the content of the Reason-Phrase of a SIP response. The S-CSCF 51 may then base the decision on continuing processing the request also on this additional information. Also instructions may be given for the additional information in the iFC.
- Fig. 6 shows a structure of Filter Criteria according to a first implementation example of the invention.
- a further field 'Reason code handling' is provided for the default handling of specific responses from an application server running an application providing service (s).
- the response code specific default handling parameters include an instruction 'continue' for the response code '413', while for other response codes the S-CSCF is instructed to not continue handling the user request, i.e. to abandon processing of the user request, or proceed according to indicated response code.
- Fig. 7 shows a structure of Filter Criteria according to a second implementation example of the invention.
- the reason code handling is added to the 'Default handling' field.
- a general default handling parameter is set to 'abandon', while only when the response code is '413' processing of the user request is to be continued, i.e. the S- CSCF should try to process the request further despite/regardless of the error indicated by the AS 53.
- the S-CSCF 51 receives a request from a registered user causing the S-CSCF 51, based on an evaluation of the iFC retrieved from the HSS/UMS 52, to contact an application server, e.g. the AS 53, for the service of an Instant Message (IM) to GSM Short Message conversion.
- an application server e.g. the AS 53
- IM Instant Message
- GSM Short Message conversion e.g. the AS 53
- the AS 53 is not able to carry out this conversion e.g. because the instant message is too long, it responds with an error message '413 "Entity too long"'.
- the S-CSCF 51 looks up the response code specific default handling parameters in the iFC and, according to Fig.
- the S-CSCF 51 retrieves from the iFC that for a response message '413' processing of the user request is to be continued.
- the S-CSCF 51 continues handling the request as verifying the lower priority triggers in the iFC.
- the Instant Message handling can be continued without conversion possibility, and the S-CSCF 51 may try to deliver the instant message to the recipient by other means.
- the response code specific default handling parameters for relevant response codes are preferably set to 'abandon' (i.e. are preferably set to continue response handling) since otherwise the request would be processed further free-of-charge .
- control device behavior in error situations where an error response is received from an application is improved.
- control of the communication request can be continued on the basis of service- specific data.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Computer Security & Cryptography (AREA)
- Health & Medical Sciences (AREA)
- Cardiology (AREA)
- General Health & Medical Sciences (AREA)
- General Business, Economics & Management (AREA)
- Business, Economics & Management (AREA)
- Telephonic Communication Services (AREA)
- Mobile Radio Communication Systems (AREA)
- Computer And Data Communications (AREA)
- Silicon Compounds (AREA)
- Debugging And Monitoring (AREA)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP06765812A EP1897343B1 (de) | 2005-06-29 | 2006-06-21 | Dienstfehlerhandhabung in einem kommunikationsnetz |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP05014194 | 2005-06-29 | ||
US11/229,606 US7684323B2 (en) | 2005-06-29 | 2005-09-20 | Service error handling in a communications network |
PCT/IB2006/052011 WO2007000688A1 (en) | 2005-06-29 | 2006-06-21 | Service error handling in a communications network |
EP06765812A EP1897343B1 (de) | 2005-06-29 | 2006-06-21 | Dienstfehlerhandhabung in einem kommunikationsnetz |
Publications (2)
Publication Number | Publication Date |
---|---|
EP1897343A1 true EP1897343A1 (de) | 2008-03-12 |
EP1897343B1 EP1897343B1 (de) | 2010-06-09 |
Family
ID=37591041
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP06765812A Not-in-force EP1897343B1 (de) | 2005-06-29 | 2006-06-21 | Dienstfehlerhandhabung in einem kommunikationsnetz |
Country Status (5)
Country | Link |
---|---|
US (1) | US7684323B2 (de) |
EP (1) | EP1897343B1 (de) |
AT (1) | ATE471026T1 (de) |
DE (1) | DE602006014828D1 (de) |
WO (1) | WO2007000688A1 (de) |
Families Citing this family (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP5224689B2 (ja) * | 2004-11-26 | 2013-07-03 | 富士通株式会社 | ネットワーク・サービス制御方法 |
ATE463119T1 (de) * | 2006-08-23 | 2010-04-15 | Ericsson Telefon Ab L M | Verfahren zum registrieren einer nicht-ims- benutzereinrichtung in einer ims-domäne |
CN101690126B (zh) * | 2007-06-26 | 2013-12-18 | 艾利森电话股份有限公司 | 用于影响应用服务器向用户设备提供的服务的调用的方法和设备 |
CN101690076B (zh) * | 2007-07-10 | 2014-02-26 | 艾利森电话股份有限公司 | 使用ims来发现运营商提供的网络服务的方法 |
US20090024870A1 (en) * | 2007-07-20 | 2009-01-22 | Telefonaktiebolaget Lm Ericsson | System and method for managing application server responses in ip multimedia subsystem |
CN101127722A (zh) * | 2007-09-17 | 2008-02-20 | 中兴通讯股份有限公司 | 核心网元重启/故障恢复后的处理方法 |
JP4985435B2 (ja) * | 2008-01-30 | 2012-07-25 | 日本電気株式会社 | 監視分析装置、方法、及び、プログラム |
US9094411B2 (en) * | 2008-04-16 | 2015-07-28 | Alcatel Lucent | Mechanism to resume filter criteria at a specific point |
US8079810B2 (en) * | 2008-09-16 | 2011-12-20 | Siemens Energy, Inc. | Turbine airfoil cooling system with divergent film cooling hole |
US8239705B2 (en) | 2009-06-30 | 2012-08-07 | At&T Intellectual Property I, L.P. | Method and apparatus for managing communication services for user endpoint devices |
US20120144013A1 (en) * | 2010-12-01 | 2012-06-07 | Cisco Technology, Inc. | Discovery of on-path services for media flows |
CN103095484B (zh) | 2011-11-01 | 2019-01-08 | 中兴通讯股份有限公司 | 一种as异常的处理方法及系统 |
EP2817935A1 (de) * | 2012-02-24 | 2014-12-31 | Telefonaktiebolaget L M Ericsson (publ) | Verfahren und anwendung zur steuerung von anwendungsserveraufrufen in einem ims |
WO2014086433A1 (en) * | 2012-12-07 | 2014-06-12 | Telefonaktiebolaget L M Ericsson (Publ) | Default initial filter criteria |
DE102013203435A1 (de) * | 2013-02-28 | 2014-08-28 | Siemens Aktiengesellschaft | Verfahren zur Überwachung einer ereignisgesteuerten Funktion und Überwachungsvorrichtung zur Ausführung einer ereignisgesteuerten Funktion |
US10171515B2 (en) | 2016-04-20 | 2019-01-01 | International Business Machines Corporation | Notifying response sender of malformed session initiation protocol (SIP) response messages |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7849190B2 (en) * | 2001-02-23 | 2010-12-07 | Nokia Siemens Networks Oy | Internet protocol based service architecture |
US6652169B2 (en) | 2002-02-20 | 2003-11-25 | Hewlett-Packard Development Company, L.P. | Method and system for printer suggested upgrades to correct errors |
US20050177630A1 (en) * | 2003-12-19 | 2005-08-11 | Jolfaei Masoud A. | Service analysis |
-
2005
- 2005-09-20 US US11/229,606 patent/US7684323B2/en not_active Expired - Fee Related
-
2006
- 2006-06-21 EP EP06765812A patent/EP1897343B1/de not_active Not-in-force
- 2006-06-21 WO PCT/IB2006/052011 patent/WO2007000688A1/en not_active Application Discontinuation
- 2006-06-21 AT AT06765812T patent/ATE471026T1/de not_active IP Right Cessation
- 2006-06-21 DE DE602006014828T patent/DE602006014828D1/de active Active
Non-Patent Citations (1)
Title |
---|
See references of WO2007000688A1 * |
Also Published As
Publication number | Publication date |
---|---|
ATE471026T1 (de) | 2010-06-15 |
US20070005712A1 (en) | 2007-01-04 |
DE602006014828D1 (de) | 2010-07-22 |
EP1897343B1 (de) | 2010-06-09 |
WO2007000688A1 (en) | 2007-01-04 |
US7684323B2 (en) | 2010-03-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7684323B2 (en) | Service error handling in a communications network | |
US11082459B2 (en) | System and method for determining trust for SIP messages | |
US8059633B2 (en) | Call forwarding in an IP multimedia subsystem (IMS) | |
US8666402B2 (en) | Method for triggering user registration in IP multimedia subsystem | |
US9706019B2 (en) | Method, system, and network element for service processing after data of network element is invalid or network element fails | |
EP2055070B1 (de) | Verfahren zum registrieren einer nicht-ims-benutzereinrichtung in einer ims-domäne | |
EP2224664A1 (de) | Verfahren und System zum Steuern der Anrufannahme in IMS | |
US20150282242A1 (en) | Methods and apparatus for processing an ims session | |
EP1875714A2 (de) | Sitzungseinleitung von anwendungsservern in einem ip-multimedia-subsystem | |
US9578068B2 (en) | Methods and apparatus for processing an IMS session | |
EP2057821A1 (de) | Dienstidentifikationsoptimierung | |
AU2011359021A1 (en) | Methods and apparatuses for handling public identities in an internet protocol multimedia subsystem network | |
EP2566127A1 (de) | Verfahren und system zum ersetzen von ersatzparametern |
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: 20071128 |
|
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 |
|
DAX | Request for extension of the european patent (deleted) | ||
DAX | Request for extension of the european patent (deleted) | ||
17Q | First examination report despatched |
Effective date: 20090109 |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: NOKIA CORPORATION |
|
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: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REF | Corresponds to: |
Ref document number: 602006014828 Country of ref document: DE Date of ref document: 20100722 Kind code of ref document: P |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: VDEP Effective date: 20100609 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20100609 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: 20100609 |
|
LTIE | Lt: invalidation of european patent or patent extension |
Effective date: 20100609 |
|
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: 20100609 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: 20100609 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: 20100609 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: 20100609 |
|
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: 20100609 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: 20100910 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: 20100609 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20100609 Ref country code: MC Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20100630 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: 20100609 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20100609 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: 20100609 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: 20100609 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: 20101009 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: 20101011 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: 20100609 |
|
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: 20100609 |
|
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 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20100609 Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20100630 Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20100621 Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20100630 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: ST Effective date: 20110228 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602006014828 Country of ref document: DE Effective date: 20110309 |
|
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: 20100809 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20110615 Year of fee payment: 6 |
|
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 NON-PAYMENT OF DUE FEES Effective date: 20100621 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 Effective date: 20101210 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: 20100609 |
|
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: 20100609 |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20120621 |
|
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: 20120621 |
|
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: 20100909 |
|
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: 20100920 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R081 Ref document number: 602006014828 Country of ref document: DE Owner name: NOKIA TECHNOLOGIES OY, FI Free format text: FORMER OWNER: NOKIA CORP., 02610 ESPOO, FI |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20160614 Year of fee payment: 11 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R119 Ref document number: 602006014828 Country of ref document: DE |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20180103 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R081 Ref document number: 602006014828 Country of ref document: DE Owner name: WSOU INVESTMENTS, LLC, LOS ANGELES, US Free format text: FORMER OWNER: NOKIA TECHNOLOGIES OY, ESPOO, FI |