WO2006053502A1 - Procede pour assurer la conformite d'information entre les noeuds de reseau - Google Patents
Procede pour assurer la conformite d'information entre les noeuds de reseau Download PDFInfo
- Publication number
- WO2006053502A1 WO2006053502A1 PCT/CN2005/001952 CN2005001952W WO2006053502A1 WO 2006053502 A1 WO2006053502 A1 WO 2006053502A1 CN 2005001952 W CN2005001952 W CN 2005001952W WO 2006053502 A1 WO2006053502 A1 WO 2006053502A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- user
- control function
- session control
- call session
- function entity
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/30—Network data restoration; Network data reliability; Network data fault tolerance
Definitions
- the present invention relates to mobile communication technologies, and in particular, to a method for ensuring information consistency between network nodes after a service call session control function entity fails to restart in an IP Multimedia Subsystem (IMS).
- IMS IP Multimedia Subsystem
- the IMS network is a network subsystem that implements IP multimedia communication control introduced on the packet bearer network by the 3rd Generation Mobile Communications Standardization Partnership Project (3GPP).
- the IMS network can provide a variety of access technologies, shield user access methods based on personalized user data, control the openness of business capabilities, and provide IP multimedia communication experience.
- the IMS network uses a packet domain (PS) or other IP access network as its bearer channel for upper layer control signaling and media transmission.
- PS packet domain
- HSS Home Subscriber Server
- CSCF Call Session Control Function
- MRF Media Gateway Control Function
- HSS Ownership Signing User Server
- a home network can have one or more HSSs, depending on the number of mobile subscription users, the capacity of network devices, and the specific networking conditions.
- the CSCF entity can be divided into three logical entities: Service CSCF (S-CSCF, Serving CSCF), Proxy CSCF (P-CSCF, Proxy CSCF), and Query CSCF (I-CSCF, Interrogating CSCF).
- S-CSCF Service CSCF
- P-CSCF Proxy CSCF
- I-CSCF Interrogating CSCF
- the S-CSCF entity is the service switching center of the IMS, performs session control, maintains the session state, and is responsible for management. User information, generating charging information, etc.
- P-CSCF entity is an access point for users to access IMS, complete user registration, responsible for service quality of service (QoS) control and security management
- I-CSCF entity is responsible for IMS domain Interworking, managing the allocation of S-CSCF, hiding network topology and configuration, generating billing data, etc.
- the process is: When the S-CSCF entity is completely broken, the registration update mechanism in the existing IMS network can be registered in one After receiving the re-registration message of the S-CSCF entity after the end of the period, the S-CSCF device is informed that the S-CSCF device is broken, so that the current session is released; or, within one registration period, it is sent to the S- by any one.
- the CSCF entity's message does not receive a response from the S-CSCF entity and learns that the S-CSCF device is broken, thereby releasing the current session.
- the message sent by other nodes will be processed as the first message received from the node, or the message sent by the other node may not be identified and discarded, or the S-CSCF entity follows the default manner. Processing and so on, which leads to a series of errors in the user's billing, security and service implementation, so that the IMS network can not meet the reliability requirements of the carrier-class network, and reduce the user's satisfaction with the IMS network. Summary of the invention
- the main object of the present invention is to provide a method for ensuring information consistency between network nodes, so as to ensure information consistency between network nodes after a temporary failure restart of the S-CSCF entity.
- a method for ensuring information consistency between network nodes includes the following steps:
- the routing information of the user acquired by the service call session control function entity is saved;
- the service call session control function entity acquires the routing information of the user and the profile information of the user;
- the service call session control function entity notifies the service control platform to perform a service control process related to the user logout according to the obtained profile information of the user, and notifies the user to perform the logout process according to the obtained route information.
- step A the serving call session control function entity acquires routing information of the user from a registration request sent by the user.
- step A the step of saving the routing information of the user acquired by the serving call session control function entity includes: the serving call session control function entity transmitting the obtained routing information of the user to the home subscription subscriber server, the home subscription subscriber server Save the routing information of the user;
- step B the step of the service call session control function entity acquiring the routing information of the user and the profile information of the user includes:
- the service call session control function entity sends its own identity and restart information to the home subscription user server;
- the home subscriber network server determines whether there is information about the user including the service call session control function entity identifier in the self, and if yes, the saved user's routing information The information and the profile information of the user are sent to the service call session control function entity.
- step A the step of the service call session control function entity transmitting the acquired routing information of the user to the home subscription user server includes: the service call session control function entity in the user registration process or after the user registration is completed The obtained routing information of the user is sent to the home subscription subscriber server.
- the method further includes: adding a cell to the existing Cx-Put message; in step A, the step of the serving call session control function entity transmitting the routing information of the user to the home subscription subscriber server comprises: the service call The session control function entity carries the routing information of the user on the added cell in the Cx-Put message and sends it to the home subscriber server.
- step A the step of the service call session control function entity transmitting the routing information of the user to the home subscriber network server includes: the service call session control function entity carrying the routing information of the user in a newly defined message To the home subscriber network.
- step A the step of saving the routing information of the user acquired by the serving call session control function entity includes: the serving call session control function entity saving the acquired routing information of the user in its own non-volatile memory. ;
- step B the step of the service call session control function entity acquiring the routing information of the user includes: the service call session control function entity acquiring routing information of the user from its non-volatile memory.
- the step A further includes: the service call session control function entity acquiring the profile information of the user from the home subscription server during the user registration process, and saving the acquired profile information of the user in the user registration process Non-volatile memory;
- step B the step of the service call session control function entity acquiring the profile information of the user includes: the service call session control function entity from its own non-volatile storage Get the user's profile information.
- step B the step of the service call session control function entity acquiring the profile information of the user includes: the service call session control function entity sending its own identity and restart information to the home subscription user server; the home subscription user server determines itself Whether there is information including the user of the service call session control function entity identifier, and if so, the user's profile information is sent to the service call session control function entity.
- the method further includes: adding a cell to an existing server allocation notification SAR message;
- the step of the service call session control function entity transmitting the identity identification and restart information to the home subscription subscriber server includes: the service call session control function entity carrying its own identity and restart information in the Cx-Notify message. The element is sent to the home subscriber server.
- the step of the service call session control function entity sending the identity identification and the restart information to the home subscription subscriber server includes: the service call session control function entity carrying its own identity and restart information in a newly defined message and sending the message to the home message Sign up for a user server.
- the method further includes: when the service call session control function entity interacts with each home subscription user server during the user registration process, the address information of the home subscription user server of the interaction information is saved in the service call session control function entity itself. Volatile memory;
- the serving call session control function entity performs the step of transmitting according to the address information of the home subscription subscriber server stored in its own non-volatile memory.
- the method further includes: saving address information of all home subscriber network servers in a non-volatile memory of the serving call session control function entity;
- the service call session control function entity is based on all saved in its own non-volatile memory
- the step of transmitting is performed by the address information of the home subscriber network.
- the user information includes an identifier of the user
- the step B further includes: the home subscription subscriber server sending the cancellation reason to the service call session control function entity;
- the step C further includes: the serving call session control function entity transmitting a logout reason to the user.
- step C the step of the service call session control function entity notifying the user to perform the logout includes: the service call session control function entity notifying the corresponding proxy call session control function entity to perform a logout process according to the acquired routing information; The call session control function entity notifies the user to perform the logout process, and deletes the relevant registration information of the user saved in itself.
- the step C further includes: the serving call session control function entity sending an indication of whether to re-register to the user, and the user decides whether to re-initiate registration to the network side according to the received indication of whether to re-register. process.
- the step C further includes: the serving call session control function entity notifying the application server related to the user to perform processing related to the user's logout according to the obtained routing information of the user.
- the S-CSCF entity separately notifies the user and the service control platform to perform the logout process according to the obtained user routing information and the user description file, thereby ensuring the consistency of information on each network node in the IMS network, thereby avoiding A series of problems caused by the S-CSCF entity restart, which greatly improves the reliability and security of the IMS network operation.
- FIG. 1 is a flow chart of an embodiment for implementing the present invention.
- FIG. 2 is an embodiment of the present invention in which an S-CSCF entity acquires a user from an HSS Flowchart of routing information and user profile information.
- FIG. 3 is a flow diagram of the present invention when the S-CSCF entity obtains routing information for the user from itself. Mode for carrying out the invention
- the S-CSCF entity is a service switching center of the IMS network, performs session control, maintains session state, and is responsible for managing user information and generating charging information. Therefore, when the S-CSCF entity temporarily restarts, it must notify the node that the network side interacts with the S-CSCF entity to take corresponding measures to ensure session consistency. Otherwise, it will lead to session state and billing. a series of mistakes. Aiming at this feature, the present invention proposes a method for ensuring information consistency between network nodes. The core idea is: after the S-CSCF entity obtains the routing information of the user, the route of the user acquired by the S-CSCF entity is saved.
- the S-CSCF entity acquires the routing information of the user and the profile information of the user when the S-CSCF entity restarts; the S-CSCF entity notifies the service control platform to perform the operation according to the obtained profile information of the user.
- the user cancels the related business control process, and notifies the user to perform the logout process according to the obtained routing information.
- FIG. 1 is a flow chart of an embodiment for implementing the present invention. Referring to Figure 1, in order to ensure the consistency of information between network nodes after the S-CSCF entity fails, the process of the present invention is:
- Step 101 After the S-CSCF entity obtains the routing information of the user, the routing information of the user acquired by the S-CSCF entity is saved.
- the S-CSCF entity acquires the routing information of the user from the registration request sent by the user in the process of the user registering with the network side. For example, the S-CSCF entity is registered from the user.
- the routing information of the user is obtained in the information fields of the Request-URI header, the Route header, the Contact header, the From header, the To header, and the Via header in the request.
- the process of saving the routing information of the user acquired by the S-CSCF entity may be: The S-CSCF entity saves the acquired routing information of the user in the non-volatile memory of the table itself. And, if the S-CSCF entity saves the acquired routing information of the user in its own non-volatile memory, the step may further include: the S-CSCF entity passes the HSS during the user registration process. The interaction process acquires the profile information of the user from the HSS, and saves the acquired profile information of the user in its own non-volatile memory.
- the process of saving the routing information of the user acquired by the S-CSCF entity may be: the S-CSCF entity sends the obtained routing information of the user to the HSS, and the HSS saves the S-CSCF entity. Get the routing information of the user.
- the S-CSCF entity may send the routing information of the user to the HSS after the user obtains the routing information of the user in the process of registering the user with the network side, or may route the user after the user completes the registration to the network side. Information is sent to the HSS.
- the implementation process of the S-CSCF entity sending the routing information of the user to the HSS may be: adding an SAR to the existing server allocation request SAR sent by the S-CSCF entity to the HSS, for example, adding a cell to the Cx-Put message.
- the S-CSCF entity carries the routing information of the user in the added cell in the Cx-Put message and sends it to the HSS; or the S-CSCF entity carries the routing information of the user in a new definition.
- the Cx interface message is sent to the HSS.
- Step 102 When the S-CSCF entity restarts after the fault occurs, the S-CSCF entity acquires the routing information of the user and the profile information of the user.
- Step 201 The S-CSCF entity sends its own identity and restart information to the HSS.
- the S-CSCF entity sends the self-identification and restart information to the HSS to notify the HSS that the S-CSCF entity has a restart event.
- the notification process may be: pre-allocation of the existing server to the HSS by the S-CSCF entity.
- the Cx-Notify message is added with a cell, so in this step, the S-CSCF entity carries the identity and restart information on the added cell in the Cx-Notify message and sends it to the HSS; or, S- The CSCF entity carries its own identity and restart information in a newly defined Cx interface message and sends it to
- the S-CSCF entity may store the address information of the HSS of the interactive information in the non-volatile memory of the S-CSCF entity itself when the information is exchanged with each HSS during the user registration process.
- the S-CSCF entity performs the sending process according to the address information of the HSS saved in the non-volatile memory, that is, the routing information of the user, The self-identification and the restart information are sent to the corresponding HSS; or, the address information of all the HSSs is stored in the non-volatile memory of the S-CSCF entity in advance, so that in the sending process corresponding to the above step 101 and the step 201, S The CSCF entity performs the transmission process according to the address information of all HSSs stored in its own non-volatile memory, that is, the user's routing information, self-identification and restart information are sent to all HSSs.
- the address information of the HSS is stored in the non-volatile memory of the S-CSCF entity, so that the S-CSCF entity can still obtain the address information of the HSS after the S-CSCF entity fails to restart, without being faulty. Restart and lose the address information of the HSS.
- Step 202 The HSS that receives the S-CSCF entity identifier and the restart information determines whether there is information about the user including the S-CSCF entity identifier in the self. If yes, step 203 is performed. Otherwise, the HSS returns to the S-CSCF entity. Failed to respond, ending the current process.
- Step 203 The HSS saves the routing information saved in itself and the description file of the user. The information is carried in the response message and sent to the S-CSCF entity.
- step 101 the S-CSCF entity stores the user's routing information and the user's profile information in its own non-volatile memory, then in this step, the S-CSCF entity is from its own non- The user's routing information and the user's profile information are obtained in the volatile memory.
- step 101 the S-CSCF entity only saves the user's routing information in its own non-volatile memory, and does not acquire and save the user's profile information
- the S-CSCF entity is Acquiring the routing information of the user from the non-volatile memory of the user, and the S-CSCF entity acquires the profile information of the user from the HSS, where the S-CSCF entity obtains the profile information of the user from the HSS.
- the process is the same as the process shown in Figure 2 above. In this case, the process of the corresponding step 203 is that the HSS only carries the profile information of the user saved in itself in the response message and sends it to the S-CSCF entity.
- Step 103 The S-CSCF entity notifies the service control platform to perform a service control process related to the user logout according to the filtering rule in the obtained user profile information.
- the S-CSCF entity may further notify the AS associated with the user to cancel the connection established with the user according to the received routing information.
- Step 104 The S-CSCF entity notifies the corresponding P-CSCF entity to perform the logout process according to the obtained routing information.
- Step 105 The P-CSCF entity notifies the user to perform the logout process, and deletes the related registration information of the user saved in itself.
- each network node in the network including the user, the P-CSCF entity, and the service control platform, performs a logout process for the user, thereby ensuring each network node.
- the consistency of information is the reason for the user to perform a logout process for the user.
- the P-CSCF entity may return a response message to the S-CSCF entity without waiting for the response message from the user.
- the S-CSCF entity After receiving the response message, the S-CSCF entity returns a response message to the HSS, and the HSS updates the user in the response. Registration information.
- the HSS that receives the S-CSCF entity identifier and the restart information determines the user information including the S-CSCF entity identifier in the user, and after the user information exists in the user information, the HSS may further The user's identity and logout reason are sent to the S-CSCF entity.
- the HSS can send the user's identity and logout reason in the registration termination request (Cx-Deregister) message to the S-CSCF entity.
- the S-CSCF entity further sends the logout reason to the P-CSCF entity
- the P-CSCF entity further sends the logout reason to the user.
- the S-CSCF entity may further send an indication of whether to re-register to the P-CSCF entity, and in step 105, the P-CSCF entity notifies the user.
- an indication of whether to re-register may be further sent to the user, so that the user may decide whether to re-initiate the registration process to the network side according to the received indication of whether to re-register.
- step 103 and step 104 to step 105 are only two steps that are distinguished for convenience of description. In a specific service implementation, there is no fixed execution sequence between step 103 and step 104 to step 105.
- the S-CSCF entity decides to initiate the logout process according to the restart event, and invokes the corresponding service logic, for example, notifying the related application server to perform and cancel the related operations;
- the S-CSCF entity sends a logout message Deregister to the P-CSCF entity; 3.
- the P-CSCF entity sends a logout notification UE Inform to the user UE, and notifies the UE if there is a reason for the logout;
- the P-CSCF entity returns a logout response message OK 200 to the S-CSCF entity;
- the UE can return a response message
- the UE returns a logout response message OK 200 to the P-CSCF entity, but since the UE may not be able to reply to the OK 200 message in some cases, the P-CSCF entity may be in the logout notification timing.
- the device After the device expires, it returns to the response message OK 200 in step 4, and does not need to wait for the response message returned by the UE; therefore, step 4 and step 5 can be performed in parallel;
- the S-CSCF entity sends an update message Cx-Put to the HSS to update the related registration information in the HSS;
- the HSS confirms the update process and returns an update response message Cx-Put resp to the S-CSCF entity.
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200410097243.8 | 2004-11-18 | ||
CNB2004100972438A CN100388864C (zh) | 2004-11-18 | 2004-11-18 | 一种呼叫会话控制功能模块重启后保证信息一致的方法 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2006053502A1 true WO2006053502A1 (fr) | 2006-05-26 |
Family
ID=36406836
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2005/001952 WO2006053502A1 (fr) | 2004-11-18 | 2005-11-18 | Procede pour assurer la conformite d'information entre les noeuds de reseau |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN100388864C (fr) |
WO (1) | WO2006053502A1 (fr) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR101212190B1 (ko) | 2008-06-20 | 2012-12-13 | 차이나 아카데미 오브 텔레커뮤니케이션즈 테크놀로지 | Pdn 연결의 릴리스를 실현하는 방법, 장치 및 그 시스템 |
CN103188714A (zh) * | 2011-12-29 | 2013-07-03 | 中兴通讯股份有限公司 | 实时数据采集方法、系统和采集网元 |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE102006026929B4 (de) * | 2006-06-09 | 2008-03-06 | Siemens Ag | Verfahren zur mehrfachen Registrierung eines multimodalen Kommunikationsendgerätes |
CN101090416B (zh) * | 2006-09-29 | 2012-02-29 | 中兴通讯股份有限公司 | 基本业务补充业务实现系统及方法 |
CN101170553B (zh) | 2006-10-24 | 2011-07-20 | 华为技术有限公司 | 实现互联网协议多媒体子系统容灾的方法和装置 |
CN101072326B (zh) * | 2007-06-20 | 2011-12-21 | 华为技术有限公司 | 访问非归属签约iptv业务提供者业务的方法、系统和设备 |
CN101123480B (zh) * | 2007-09-06 | 2010-06-09 | 中兴通讯股份有限公司 | 一种实现归属用户服务器数据一致性的方法 |
CN101127722A (zh) * | 2007-09-17 | 2008-02-20 | 中兴通讯股份有限公司 | 核心网元重启/故障恢复后的处理方法 |
US9026675B2 (en) * | 2008-10-31 | 2015-05-05 | Telefonaktiebolaget L M Ericsson (Publ) | IMS restoration procedures for multiple contacts |
CN101599921B (zh) * | 2009-06-18 | 2014-12-17 | 腾讯科技(深圳)有限公司 | 一种企业即时通信系统及其文件传输方法 |
CN102075545B (zh) * | 2011-02-18 | 2014-05-07 | 杭州华三通信技术有限公司 | 一种客户端注册指示方法、注册方法及其设备 |
US9049562B2 (en) * | 2011-08-10 | 2015-06-02 | Telefonaktiebolaget Lm Ericsson (Publ) | HSS fault recovery for non-3GPP access |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2002032084A2 (fr) * | 2000-10-09 | 2002-04-18 | Nokia Corporation | Desenregistrement d'adresse sur reseau multimedia internet |
WO2002073859A2 (fr) * | 2001-03-12 | 2002-09-19 | Nokia Corporation | Techniques de recuperation dans les reseaux mobiles |
KR20030055417A (ko) * | 2001-12-26 | 2003-07-04 | 삼성전자주식회사 | Ip 멀티미디어 서비스 가입자의 이동성 관리를 위한가입자 데이터 관리 장치 및 방법 |
-
2004
- 2004-11-18 CN CNB2004100972438A patent/CN100388864C/zh not_active Expired - Fee Related
-
2005
- 2005-11-18 WO PCT/CN2005/001952 patent/WO2006053502A1/fr active Application Filing
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2002032084A2 (fr) * | 2000-10-09 | 2002-04-18 | Nokia Corporation | Desenregistrement d'adresse sur reseau multimedia internet |
WO2002073859A2 (fr) * | 2001-03-12 | 2002-09-19 | Nokia Corporation | Techniques de recuperation dans les reseaux mobiles |
KR20030055417A (ko) * | 2001-12-26 | 2003-07-04 | 삼성전자주식회사 | Ip 멀티미디어 서비스 가입자의 이동성 관리를 위한가입자 데이터 관리 장치 및 방법 |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR101212190B1 (ko) | 2008-06-20 | 2012-12-13 | 차이나 아카데미 오브 텔레커뮤니케이션즈 테크놀로지 | Pdn 연결의 릴리스를 실현하는 방법, 장치 및 그 시스템 |
CN103188714A (zh) * | 2011-12-29 | 2013-07-03 | 中兴通讯股份有限公司 | 实时数据采集方法、系统和采集网元 |
Also Published As
Publication number | Publication date |
---|---|
CN100388864C (zh) | 2008-05-14 |
CN1780482A (zh) | 2006-05-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2006053502A1 (fr) | Procede pour assurer la conformite d'information entre les noeuds de reseau | |
US11638230B2 (en) | Method, apparatus and system for processing registration backup data | |
US8069365B2 (en) | Method and device for realizing IP multimedia subsystem disaster tolerance | |
US8571548B2 (en) | Method and system for changing a subscription | |
US8036659B2 (en) | Method for requesting an unregistered UE to perform registration in the IMS | |
US9185141B2 (en) | Managing roaming agreements between IMS networks | |
US8687557B2 (en) | Managing user registrations of roaming IMS users | |
US8935374B2 (en) | Method, system, and device for realizing registration mechanism of IP multimedia subsystem | |
WO2006102830A1 (fr) | Procede destine a un terminal d’identification de commande de routage d’interaction de capacite pendant que ims et cs sont co-instantanes | |
CN101299859B (zh) | 个域网管理方法、服务器及系统 | |
JP2009544200A (ja) | ネットワークにアクセスする方法、システムおよびデバイス | |
WO2017036227A1 (fr) | Procédé et dispositif réalisant une restauration de service appelé par un terminal | |
WO2009036629A1 (fr) | Procédé de traitement après redémarrage ou récupération sur sinistre d'un élément de réseau central | |
US20120177194A1 (en) | Method for connecting call | |
KR100703426B1 (ko) | 아이피 기반 멀티미디어 서브시스템에서 가입자 정보유실시 발신 및 착신 호를 가능하게 하는 방법 및 장치 | |
CN101052054B (zh) | 保持ps域和ims域ip地址注销一致性的方法 | |
EP1873980A1 (fr) | Procédé et système pour la modification d'un abonnement | |
WO2007090348A1 (fr) | Procédé, appareil et système de vérification de la validité pour système uri d'agent utilisateur globalement routable | |
WO2007041957A1 (fr) | Méthode et système de vérification de la cohérence de nom de fonctions de contrôle d’état d’appel de service | |
CN101132407B (zh) | 一种对重选服务呼叫会话控制功能导致的异常的处理方法 | |
WO2021213243A1 (fr) | Procédé d'enregistrement de service associé, dispositif associé et support de stockage lisible par ordinateur | |
CN101635963A (zh) | 多注册的方法、多注册情况下去注册的方法及相应装置 | |
KR101075614B1 (ko) | 아이피 기반 멀티미디어 서브시스템에서 가입자 정보유실시 착신호를 가능하게 하는 방법 | |
JP2010525623A (ja) | 通信ネットワークにおいて使用する方法、および、装置 | |
CN100536484C (zh) | 一种ip地址注销方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KM KN KP KR KZ LC LK LR LS LT LU LV LY MA MD MG MK MN MW MX MZ NA NG NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU LV MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 05808319 Country of ref document: EP Kind code of ref document: A1 |