CN100426744C - Processing method for exception in course of P-CSCF and UE log-on - Google Patents
Processing method for exception in course of P-CSCF and UE log-on Download PDFInfo
- Publication number
- CN100426744C CN100426744C CNB2005101206021A CN200510120602A CN100426744C CN 100426744 C CN100426744 C CN 100426744C CN B2005101206021 A CNB2005101206021 A CN B2005101206021A CN 200510120602 A CN200510120602 A CN 200510120602A CN 100426744 C CN100426744 C CN 100426744C
- Authority
- CN
- China
- Prior art keywords
- cscf
- message
- network
- user
- registration
- 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.)
- Expired - Fee Related
Links
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The present invention relates to a processing method for abnormality in the registration process of P-CSCF and UE. When UE or P-CSCF receives the logout notification of a network, user data can be deleted after S-CSCF sending a logout notification message of the network is the same as S-CSCF registered by a current user; when the S-CSCF is different from the S-CSCF registered by the current user, a subscriber message is sent to the original S-CSCF to cancel subscription in order to cancel the subscription relation with the original S-CSCF, and then, the subscriber message is sent to new S-CSCF to establish the subscription relation with the new S-CSCF; the original S-CSCF deletes the relevant user data after the message is received. Therefore, the abnormality caused by the reselection of the S-CSCF due to repeated registration is avoided.
Description
Technical field
The present invention relates to the data communication field, specifically, relate to a kind of P-CSCF and UE and handle the unusual implementation method of registration process.
Background technology
IMS (IP Multimedia System) just is based on Session Initiation Protocol and (a kind ofly creates two sides or in many ways, revise, an independent sessions territory of CSCF (Call session Control Function conversation control function entity) the control application layer protocol of termination session), 3GPP (3G standard tissue) complete definition the interface of IMS, networking and operation flow.
Registration: IMS user must at first register if carry out session.The process of registration is exactly that the position of oneself is registered on network.
Network-initiated deregistration: owing to subscription data change, arrearage, registration timeout or other managerial reasons, network side can send Notify message (a kind of sip message) according to local policy and notify UE (subscriber equipment) and P-CSCF (Proxy-Call Session Control Function, agent conversation control function entity) that user data is nullified.According to Session Initiation Protocol, the user must send Subscriber (a kind of sip message) earlier and remove to subscribe to the login state of oneself, could after changing, receive login state the Notify message that server sends, so after succeeding in registration, UE and P-CSCF must send Subscriber message earlier to S-CSCF (Serving-Call Session Control Function, serving session control function entity, be the core controlled entity of IMS), like this could be after login state be changed, receive the Notify message deletion user data of network-initiated deregistration, guarantee the consistency of whole network data.
As network side and insert network element P-CSCF between the side as first access point of user, obtain user's routing iinformation by registration, above being routed to correct S-CSCF, the user goes.
The Service-Route header field is a sip message, and the inside carries the address of S-CSCF.200 message that succeeded in registration by indication in the address of S-CSCF are taken back to user and P-CSCF, and user and P-CSCF have just obtained the address information of S-CSCF like this; The user is sending invite message, and the S-CSCF address that will obtain from the registration the inside be added Route header field (this header field is used to refer to route sip message) to, on the S-CSCF in the time of so just can be with the registration of invite message route; When arriving P-CSCF, P-CSCF can check whether the Route header field that carries in the Invite message that the user sends is correct, if incorrect P-CSCF has two kinds of strategies to adopt, the firstth, refuse this user, the secondth, user's Route header field is revised as correct address.
Contact header field: being mainly used to is explanation user's address information, and calling both sides is known the other side's identity by the Contact address.
The technical scheme of prior art:
3GPP the inside regulation UE and P-CSCF receive that the processing of logout message of registration and network side is as follows:
Register flow path: P-CSCF is after receiving the 200ok message of registration, if also preserve user's Service-Route (registering in the past) among the P-CSCF, then the new Service-Route that carries with 200ok message the inside covers original value.The same P-CSCF of the processing procedure of UE.
Network-initiated deregistration: after receiving 200 message that succeed in registration, UE and P-CSCF will send the login state of Subscriber message to S-CSCF booking reader.In case user's login state changes like this, network side just can come logging off users by Notift message.UE and P-CSCF are after receiving the logout message Notify of network side, stipulate according to agreement, can not compare with the Service-Route that itself preserves the Contact address in the Notify message of receiving, thereby judge whether the S-CSCF that sends logout message NOTIFY is exactly the S-CSCF of active user's registration, but select directly user data to be deleted.
Prior art has following shortcoming:
Since may there be following abnormal conditions in the registration process, as shown in Figure 1:
Step 1-7:UE sends the REGISTER login request message to the network equipment.I-CSCF (inquiry session controlled function entity) selects S-CSCF (S-CSCF1) according to local policy, and Register message is sent to above server S-CSCF (S-CSCF1); S-CSCF (S-CSCF1) sends 200 message to subscription authentication success, issues the user inside own address is added in the Service-Route header field.P-CSCF and UE after receiving 200 message preserve Service-Route, note the address of S-CSCF (S-CSCF1).(middle 401 message of omitting S-CSCF1 to " authentication challenge " of UE transmission, and UE sends second the Register message of " authentication is responded " to S-CSCF1)
Step 8-9:P-CSCF sends subscribe message subscriber to S-CSCF (S-CSCF1) and subscribes to this user's login state, and S-CSCF (S-CSCF1) will subscribe to duration and send back to P-CSCF by 200 message.(process that I-CSCF selects S-CSCF has been omitted in the centre)
Step 10-11:UE sends subscribe message subscriber to S-CSCF (S-CSCF1) and subscribes to this user's login state, and S-CSCF1 will subscribe to duration and send back to UE by 200 message.
Step 12-18:UE sends follow-up REGISTER login request message to the network equipment.Because unusual (for example HSS (home subscriber server) is restarted, and the ServerName that preserves has originally been lost) takes place in the network; I-CSCF selects S-CSCF2 according to local policy, and Register message is sent to above server S-CSCF2; S-CSCF2 is to subscription authentication success, sends 200 message and issues the user inside own address is added in the Service-Route header field; P-CSCF and UE will cover old Service-Route preservation with new Service-Route after receiving 200 message, note the address of S-CSCF2, and the S-CSCF1 of original record is override.(middle 401 message of omitting S-CSCF2 to " authentication challenge " of UE transmission, and UE sends second the Register message of " authentication is responded " to S-CSCF2)
Step 19-20:(both in no particular order) S-CSCF1 of original user's registration is because overtime or other reasons, Notify message informing P-CSCF and UE deregistration user that network-initiated deregistration takes place; After UE and P-CSCF receive Notify message, according to existing protocol, can not judge whether the S-CSCF that sends network-initiated deregistration is the S-CSCF of current registration, but directly user data be nullified, cause unusual (for example ongoing session may unprovokedly be broken).
Summary of the invention
Described in view of this, unusual problem takes place in the S-CSCF that the objective of the invention is to solve because of a registration after repeatedly registration causes the S-CSCF of previous registration when nullifying.P-CSCF provided by the invention handles the unusual method of registration process, comprising:
Agent conversation control function entity P-CSCF is when receiving network-initiated deregistration notice Notify message, judge whether the serving session control function entity S-CSCF that sends described network-initiated deregistration notice Notify message is consistent with the S-CSCF of active user's registration, when both are consistent, delete described active user's user data, when both are inconsistent, do not delete described active user's user data.
Judge wherein whether consistent method comprises for both: after P-CSCF receives response message, check earlier whether the Service-Route that is preserved of user data the inside is consistent with the Service-Route that response message takes back.
This method also comprises:
The S-CSCF of the original registration of the serving session control function entity S-CSCF of the more current registration of P-CSCF and user when inconsistent, send Subscriber message to original S-CSCF and cancels subscriptions, and removes the subscribing relationship with original S-CSCF.
This method further comprises:
P-CSCF sets up subscribing relationship to new S-CSCF transmission subscriber message and new S-CSCF after the subscribing relationship of releasing and original S-CSCF, S-CSCF originally deletes relevant user data.
UE registration process abnormity processing method provided by the invention comprises:
User equipment (UE) is when receiving network-initiated deregistration notice Notify message, judge whether the S-CSCF that sends network-initiated deregistration notice Notify message is consistent with the S-CSCF of active user's registration, when both are consistent, delete described active user's user data, when both are inconsistent, do not delete described active user's user data.
Judge wherein whether consistent method comprises for both: after UE receives response message, check earlier whether the Service-Route that is preserved in the user data is consistent with the Service-Route that response message takes back.
This method also comprises:
UE checks the Service-Route that is preserved of user data the inside and the Service-Route that response message takes back earlier after receiving response message, preserve user data when both are identical.
This method further comprises:
The S-CSCF of the original registration of the serving session control function entity S-CSCF of the more current registration of UE and user when inconsistent, send Subscriber message to original S-CSCF and cancels subscriptions, and removes the subscribing relationship with original S-CSCF.
This method also comprises:
UE set up subscribing relationship to new S-CSCF transmission subscriber message and new S-CSCF, and original S-CSCF deletes relevant user data after receiving this message after the subscribing relationship of releasing and original S-CSCF.
Utilize P-CSCF provided by the invention and UE to handle the unusual implementation method of registration process, by at UE and P-CSCF when receiving the Notify of network-initiated deregistration notice, must judge when the S-CSCF that sends network-initiated deregistration notice Notify message is consistent with the S-CSCF of active user's registration, just delete user data, so just can avoid the S-CSCF that occurs because of a registration after repeatedly registration causes the S-CSCF of previous registration when nullifying to take place unusual.
Description of drawings
Fig. 1 is the flow chart of prior art scheme;
Fig. 2 is a flow chart of the present invention.
Embodiment
Core of the present invention be at UE and P-CSCF when receiving the Notift of network-initiated deregistration notice, can not be directly with user log off, must judge whether the S-CSCF that sends network-initiated deregistration notice Notify message is the S-CSCF that the active user registers, have only when both are consistent, could delete user data.If find that the S-CSCF of transmission Notify message and the S-CSCF that the active user registers are inconsistent, then do not nullify this user, must return 200 to the S-CSCF that sends Notify message, guarantee that this S-CSCF can nullify the user data of its preservation normally.UE and P-CSCF are when receiving 200 message of registration, if S-CSCF and the upward last S-CSCF that registers of user that discovery is handled in the current registration Register message are inconsistent, then forward once the S-CSCF of registration send subscriber (Expires header field value is 0) and cancel subscriptions, set up subscribing relationship with new S-CSCF simultaneously.
After P-CSCF receives 200 response messages, directly user data is not deleted, but whether the Service-Route that the Service-Route that is preserved that need to check the user data the inside and 200 message are taken back is consistent.If find that the S-CSCF of current registration is identical with the S-CSCF of the original registration of user, directly deletion gets final product; If it is inconsistent, sending Subscriber (Expires header field value is 0) to original S-CSCF (S-CSCF1) earlier cancels subscriptions, remove subscribing relationship with original S-CSCF (S-CSCF1), setting up subscribing relationship to new S-CSCF (S-CSCF2) transmission subscriber and new S-CSCF (S-CSCF2) then, and S-CSCF1 deletes relevant user data after receiving the message that cancels subscriptions.
If when removing subscribing relationship with old S-CSCF (S-CSCF1), do not receive 200 message that old S-CSCF (S-CSCF1) is definite, perhaps this S-CSCF (S-CSCF1) does not support to cancel subscriptions, and has no relations yet, and registers users as merit in the same old way.When the notice of cancellation of the follow-up network side of receiving, the Serice-Route that Contact address in the inspection notify message and this user preserve in registration process at present, if find that the S-CSCF of current transmission network-initiated deregistration notice Notify is consistent with the S-CSCF of the current registration of user, then, user data is nullified according to the normal process of agreement regulation; Otherwise return 200 message and give the S-CSCF (S-CSCF1) that sends Notify message, but P-CSCF does not delete the user data of preservation.So just can prevent that old S-CSCF is user log off.
Also adopt the processing method the same for UE equally with P-CSCF, at first send the SCBSCRIBER message (Expires header field value is 0) cancel subscriptions and old S-CSCF (S-CSCF1) with the subscribing relationship cancellation, set up new subscribing relationship with new S-CSCF (S-CSCF2) then.During for the Notify message of the network-initiated deregistration of receiving, whether the Service-Route that preserves in the time of must judging the Contact address with registration is consistent, if find that the S-CSCF of current transmission network-initiated deregistration notice Notify is consistent with the S-CSCF of the current registration of user, then, user data is nullified according to the normal process of agreement regulation; Otherwise return 200 message and give the S-CSCF (S-CSCF1) that sends Notify message, but do not delete user data.So just can prevent that old S-CSCF (S-CSCF1) is user log off.
Its handling process is as shown in Figure 2: suppose that the user has registered on S-CSCF1, the user initiates registration once more, and network takes place to have registered a user to above the S-CSCF2 unusually to have gone.(having omitted " authentication is responded "--second REGISTER request that network returns to network " authentication challenge " and the terminal of terminal down by 401 bands here)
Step 1-2: the user sends the Register login request message, sends on the network element I-CSCF by network element P-CSCF.
Step 3-4: because network takes place unusually, I-CSCF sends to S-CSCF (S-CSCF2) with Register message.
Step 5-6: omit second Register message of " authentication challenge " 401 message and " authentication is responded ", S-CSCF (S-CSCF2) successfully returns 200 message to network authentication.
The Service-Route (comprising S-CSCF2) that carries in Service-Route (comprising S-CSCF1) that preserve step 7-8:P-CSCF discovery user data the inside and 200 message is inconsistent, then send on subscriber message (Expires header field value the is 0) S-CSCF (S-CSCF1) until old and cancel subscriptions, after S-CSCF1 receives this message, with the user data deletion, and return 200 and give P-CSCF.
Step 9-10:P-CSCF sends subscriber message and new S-CSCF (S-CSCF2) sets up subscribing relationship to new S-CSCF (S-CSCF2).(annotating: set up the subscriber message of subscribing to and remove the subscriber message of subscribing to and to send simultaneously, the middle process of omitting I-CSCF selection S-CSCF).
Step 11: give UE with 200 message forward pass.
Step 12-15: with step 7-10.With old S-CSCF (S-CSCF1) subscribing relationship is removed, set up new subscribing relationship with new S-CSCF (S-CSCF2) simultaneously.
Step 16-17: after the user registration success, if P-CSCF receives the Notify message of network-initiated deregistration, the Service-Route that preserves in the time of must judging the contact address of carrying in this message whether with registration is consistent.If find that the S-CSCF of the S-CSCF of current transmission network-initiated deregistration notice Notify and the current registration of user is inconsistent, then think the network-initiated deregistration message that old S-CSCF sends, do not delete user data, return 200 message to the S-CSCF (S-CSCF1) that sends Notify message simultaneously. guarantee that flow process is correct, S-CSCF (S-CSCF1) can the old user data of its preservation is normal be nullified.
Step 18-19: when subscriber equipment is received the Notify of network-initiated deregistration, the same P-CSCF of its processing procedure.If the Service-Route that the contact address of carrying in the Notify message and when registration preserve is consistent, normal process then, otherwise return 200 message to the S-CSCF that sends Notify message, but do not delete user data.
The above; only for the preferable embodiment of the present invention, but protection scope of the present invention is not limited thereto, and anyly is familiar with those skilled in the art in the technical scope that the present invention discloses; the variation that can expect easily or replacement all should be encompassed within protection scope of the present invention.Therefore, protection scope of the present invention should be as the criterion with the protection range of claim.
Claims (8)
1, a kind of P-CSCF handles the unusual method of registration process, it is characterized in that, agent conversation control function entity P-CSCF is when receiving network-initiated deregistration notice Notify message, judge whether the serving session control function entity S-CSCF that sends described network-initiated deregistration notice Notify message is consistent with the S-CSCF of active user's registration, when both are consistent, delete described active user's user data, when both are inconsistent, do not delete described active user's user data.
2, method according to claim 1, it is characterized in that, whether consistent method comprises for the S-CSCF that judge to send described network-initiated deregistration notice Notify message and the S-CSCF of active user's registration: after P-CSCF receives that network-initiated deregistration is notified Notify message, check whether the Service-Route that preserves in described active user's the user data is consistent with the Contact address in the Notify message.
3, method according to claim 1 is characterized in that, when both were inconsistent, this method further comprised, P-CSCF sends Subscriber message to original S-CSCF and cancels subscriptions, and removes the subscribing relationship with described original S-CSCF.
4, processing method according to claim 3 is characterized in that, when both were inconsistent, this method further comprised: P-CSCF sets up subscribing relationship to new S-CSCF transmission subscriber message and new S-CSCF.
5, a kind of UE handles the unusual method of registration process, it is characterized in that, user equipment (UE) is when receiving network-initiated deregistration notice Notify message, judge whether the S-CSCF that sends network-initiated deregistration notice Notify message is consistent with the S-CSCF of active user's registration, when both are consistent, delete described active user's user data, when both are inconsistent, do not delete described active user's user data.
6, method according to claim 5, it is characterized in that, whether consistent method comprises for the S-CSCF that judge to send network-initiated deregistration notice Notify message and the S-CSCF of active user's registration: after UE receives that network-initiated deregistration is notified Notify message, check whether the Service-Route that preserves in described active user's the user data is consistent with the Contact address in the Notify message.
7, method according to claim 6 is characterized in that, when both were inconsistent, this method comprised that further UE sends Subscriber message to original S-CSCF, removes the subscribing relationship with described original S-CSCF.
8, method according to claim 7 is characterized in that, when both were inconsistent, this method further comprised: UE is setting up subscribing relationship to new S-CSCF transmission subscriber message and new S-CSCF.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005101206021A CN100426744C (en) | 2005-12-08 | 2005-12-08 | Processing method for exception in course of P-CSCF and UE log-on |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005101206021A CN100426744C (en) | 2005-12-08 | 2005-12-08 | Processing method for exception in course of P-CSCF and UE log-on |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1870522A CN1870522A (en) | 2006-11-29 |
| CN100426744C true CN100426744C (en) | 2008-10-15 |
Family
ID=37444079
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2005101206021A Expired - Fee Related CN100426744C (en) | 2005-12-08 | 2005-12-08 | Processing method for exception in course of P-CSCF and UE log-on |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100426744C (en) |
Families Citing this family (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101212351B (en) * | 2006-12-30 | 2011-05-25 | 中兴通讯股份有限公司 | User service tracking method for IMS network |
| CN101277525B (en) * | 2007-03-31 | 2012-01-25 | 华为技术有限公司 | Method and system as well as apparatus for proxy call conversation control entity to execute administrative operation |
| CN101132407B (en) * | 2007-08-13 | 2013-11-06 | 中兴通讯股份有限公司 | Method for processing exception caused by re-selection service call conversation control function |
| CN101127769B (en) * | 2007-08-20 | 2012-04-04 | 华为技术有限公司 | Method, system, terminal and server for user registration based on session originated protocol |
| CN101106573B (en) * | 2007-09-03 | 2011-06-22 | 中兴通讯股份有限公司 | Method for securing whole network data consistency |
| CN101132556B (en) * | 2007-09-24 | 2011-05-25 | 中兴通讯股份有限公司 | Registration method used for IP multimedia subsystem |
| CN101132645B (en) * | 2007-09-27 | 2012-09-05 | 中兴通讯股份有限公司 | Method for changing control function of processing proxy call conversation by IP multimedia subsystem |
| CN101141691B (en) * | 2007-10-11 | 2011-06-22 | 中兴通讯股份有限公司 | Method and system for P-CSCF to identify forbidden calling subscriber |
| CN101198166B (en) * | 2007-10-19 | 2011-06-22 | 中兴通讯股份有限公司 | Processing method when P-CSCF actively deletes user data |
| CN102035800B (en) * | 2009-09-25 | 2014-03-19 | 中兴通讯股份有限公司 | Third party registration failure processing method and device used for IMS (IP Multimedia Subsystem) |
| CN111260304B (en) * | 2019-11-26 | 2024-03-08 | 上海赛连信息科技有限公司 | Trial account management and issuing method and device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20040057858A (en) * | 2002-12-24 | 2004-07-02 | 한국전자통신연구원 | system for network initiated deregistration of user agent in Session Initiation Protocol and method thereof |
| WO2005025130A1 (en) * | 2003-09-03 | 2005-03-17 | Siemens Aktiengesellschaft | Notification method and communication system |
| WO2005036299A2 (en) * | 2003-10-13 | 2005-04-21 | Nokia Corporation | System and method for releasing sessions at network entities associated with the sessions |
| US6888828B1 (en) * | 2001-10-02 | 2005-05-03 | Nokia Corporation | System and method for providing at least one service obtained from a service network for a user in a packet switched communication network |
-
2005
- 2005-12-08 CN CNB2005101206021A patent/CN100426744C/en not_active Expired - Fee Related
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6888828B1 (en) * | 2001-10-02 | 2005-05-03 | Nokia Corporation | System and method for providing at least one service obtained from a service network for a user in a packet switched communication network |
| KR20040057858A (en) * | 2002-12-24 | 2004-07-02 | 한국전자통신연구원 | system for network initiated deregistration of user agent in Session Initiation Protocol and method thereof |
| WO2005025130A1 (en) * | 2003-09-03 | 2005-03-17 | Siemens Aktiengesellschaft | Notification method and communication system |
| WO2005036299A2 (en) * | 2003-10-13 | 2005-04-21 | Nokia Corporation | System and method for releasing sessions at network entities associated with the sessions |
Non-Patent Citations (4)
| Title |
|---|
| "SIP会话协议在第三代移动网络中关键问题研究". 徐晓宇，张惠民.数据通信，第2期. 2004 |
| "UMTS中IP多媒体子系统体系结构". 徐晓宇，张惠民.现代电信科技，第5期. 2004 |
| "SIP会话协议在第三代移动网络中关键问题研究". 徐晓宇，张惠民.数据通信，第2期. 2004 * |
| "UMTS中IP多媒体子系统体系结构". 徐晓宇，张惠民.现代电信科技，第5期. 2004 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1870522A (en) | 2006-11-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100426744C (en) | Processing method for exception in course of P-CSCF and UE log-on | |
| US9258179B2 (en) | Failure recovery in an IP multimedia subsystem network | |
| EP2198587B1 (en) | Failure recovery in an ip multimedia subsystem network | |
| US8576833B2 (en) | Fault tolerant voice over Internet protocol (VoIP) systems and methods to operate the same | |
| EP1895803B1 (en) | A method for processing the register abnormality during the user register procedure | |
| EP2140648B1 (en) | System and method for indicating circuit switched access at ims registration | |
| EP2381637B1 (en) | Registration backup data processing method, apparatus and system | |
| EP2055070B1 (en) | Method for registering in an ims domain a non-ims user device | |
| EP1884067B1 (en) | Method for requesting an unregistered UE to perform registration in the IMS | |
| EP1959632B1 (en) | Method, system and apparatus for using IMS communication service identifier | |
| US8532091B2 (en) | Method and apparatus for providing IMS services to circuit-switched controlled terminals | |
| KR20080068806A (en) | Provision of ims services via circuit-switched access | |
| EP2224664A1 (en) | Method and system for controlling call admission in IMS | |
| EP2795865B1 (en) | Session establishment in an ip multimedia subsystem network | |
| CN100550884C (en) | Based in the business procedure of retry mechanism to Session Initiation Protocol processing of request method | |
| CN101132407B (en) | Method for processing exception caused by re-selection service call conversation control function | |
| US20140254584A1 (en) | Notification of too many "no answer" of forwarded to number | |
| CN101207548A (en) | Processing method and entity of multi terminal sharing public identify | |
| CN100466811C (en) | Method for calling user terminal of IP multimedia subsystem | |
| EP1924054A1 (en) | Telecommunication system and method | |
| EP2566127B1 (en) | Method and system for replacing replace parameter |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| ASS | Succession or assignment of patent right |
Owner name: HUAWEI DIGIT TECHNOLOGY CO., LTD. Free format text: FORMER OWNER: HUAWEI TECHNOLOGY CO LTD Effective date: 20100909 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| COR | Change of bibliographic data |
Free format text: CORRECT: ADDRESS; FROM: 518129 BANTIAN HEADQUARTER BUILDING OF HUAWEI, LONGGANG DISTRICT, SHENZHEN CITY, GUANGDONG PROVINCE TO: 100085 NO.3, XINXI ROAD, SHANGDI, HAIDIAN DISTRICT, BEIJING |
|
| TR01 | Transfer of patent right |
Effective date of registration: 20100909 Address after: 100085 Beijing, Haidian District on the road, No. 3 Patentee after: Huawei Digit Technology Co., Ltd. Address before: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen Patentee before: Huawei Technologies Co., Ltd. |
|
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20081015 Termination date: 20151208 |
|
| EXPY | Termination of patent right or utility model |