CN1607842A - Method for synchronizing data between authentication server and home location register - Google Patents
Method for synchronizing data between authentication server and home location register Download PDFInfo
- Publication number
- CN1607842A CN1607842A CN 200310101110 CN200310101110A CN1607842A CN 1607842 A CN1607842 A CN 1607842A CN 200310101110 CN200310101110 CN 200310101110 CN 200310101110 A CN200310101110 A CN 200310101110A CN 1607842 A CN1607842 A CN 1607842A
- Authority
- CN
- China
- Prior art keywords
- certificate server
- data
- position register
- attaching position
- user
- 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
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
This invention discloses a data synchronizing method for a certification server and an attribution position register, which can synchronize the user signed data of the attribution position register and certification server without increasing new cards or influencing original service. The synchronous method includes: A judging if the time kept for user signed data on the certification server exceeds the threshold, if so, said user signed data is re-fetched from the attribution position register, B judging if the re-fetched data is successful, if so, then the time of the successful fetching is refreshed.
Description
Technical field
The present invention relates to the mobile communication system method of data synchronization, particularly the method for data synchronization of certificate server and attaching position register in WLAN (wireless local area network) and the mobile communication system fusion system.
Background technology
WLAN (wireless local area network) (Wireless Local Area Network, be called for short " WLAN ") is to utilize the radio frequency technology of (Radio Frequency is called for short " RF "), replaces traditional cable and the LAN that constitutes.The message transmission rate of WLAN can reach 11Mbps (802.11b) now, and flank speed can reach 54Mbps (802.11a), and transmission range can be more than 20km.It is that a kind of of wired network connecting mode replenished and expansion, makes online computer have mobility, can solve quickly and easily and use wired mode to be difficult for the network-in-dialing problem that realizes.WLAN has become the focus of data communication field development.
Wlan product mainly comprises two parts: wireless network card and WAP (wireless access point) (Access Point is called for short " AP ").Fundamental mode is: wireless network card is installed in notebook computer, desktop computer, personal digital assistant (Personal Digital Assistant, be called for short " PDA ") etc. on the terminal, be connected by wireless mode with AP, then to be connected with spider lines on wired mode, realization is connected with other networks (for example internet) AP.
Along with the rise and the development of WLAN technology, the intercommunication of WLAN and various wireless mobile communication networks is just becoming the emphasis of current research.These wireless mobile communication networks comprise: global system for mobile communications (Global System for mobile Communication, abbreviation " GSM "), code division multiple access (CodeDivision Multiple Access, abbreviation " CDMA ") system, Wideband Code Division Multiple Access (WCDMA) (WidebandCode Division Multiple Access, abbreviation " WCDMA ") system, TD SDMA (Time Division Synchronous CodeDivision Multiple Access SCDMA is called for short " TD-SCDMA ") system, CDMA2000 system etc.At third generation partner program (3rdGeneration Partnership Project, abbreviation " 3GPP ") in the standardization body, subscriber equipment (UserEquipment, be called for short " UE ") can link to each other with internet (Internet), Intranet (Intranet) by the access network of WLAN, can also connect via the network of WLAN access network and 3G (Third Generation) Moblie (The Third Generation is called for short " 3G ") system.
Fig. 1 shows WLAN and 3G merges system assumption diagram.UE10 is linked into WLAN Access Network 30 by wireless mode.WLAN Access Network 30 is connected with Internet/Intranet20 on the one hand, on the other hand with the 3G system in certificate server 60 and gateway GPRS supporting node (GGSN) (GPRS Gateway Support Node is called for short " GGSN ") 70 connect.The full name of certificate server 60 is authentication, mandate and record keeping server (Authentication, Authorization andAccounting Server are called for short " AAA Server ").Certificate server 60 also with the 3G system in GGSN70, home signature user server (Home Subscriber Server, be called for short " HSS ") 40, attaching position register (Home Location Register, be called for short " HLR ") 50, charging gateway (Charging Gateway, be called for short " CG ")/Charging Gateway Functionality (Charging GatewayFunctionality, be called for short " CGF ") 80, Online Charging System (Online Charging System is called for short " OCS ") 90 is connected.
3GPP has stipulated the interaction schemes of WLAN and 3G system.In WLAN and 3GPP system mutual, if UE10 is GSM user, then certificate server 60 is mutual with HLR50, adopts with the similar authentication mechanism of GSM and finishes authentication to UE; If UE10 is a 3G subscription, certificate server 60 is mutual with HSS40, and employing and the similar authentication mechanism of 3G are finished the authentication to UE.
Below in conjunction with Fig. 2 the access process that WLAN and 3G merge in the prior art is described.
In step 110, UE sets up bottom with the WLAN Access Network and is connected.Connect and generally to be undertaken by 802.1X agreement (for example 802.11b agreement etc.), authenticate at this moment, UE10 can not visit Internet/Intranet20, can only be mutual with certificate server 60, authenticate.
Then enter step 120, UE10 initiates authentication request and authenticates alternately with certificate server 60.It is mutual to have multiple messages between UE10 and the certificate server 60, provides international mobile station identity number (International Mobile Station Identify is called for short " IMSI ") etc. as UE10.This moment, certificate server 60 can be judged the local the authentication information whether pairing user of this UE10 be arranged, if having then directly authenticate and enter step 150, otherwise entered step 130.
In step 130, certificate server obtains user authentication information and preserves from HSS/HLR45.HSS/HLR45 is meant the meaning of HSS40 or HLR50.Specifically, to 3G subscription, certificate server 60 obtains user's authentication information from HSS40.To GSM user, certificate server 60 obtains user's authentication information from HLR50.
Then enter step 140, certificate server obtains user contracting data and is kept at this locality from HSS/HLR45.To 3G subscription, certificate server 60 obtains user contracting data from HSS40.To GSM user, certificate server 60 obtains user contracting data from HLR50.After this enter step 150.
In step 150,60 couples of UE10 of certificate server authenticate.If authentication is passed through, then enter step 160, otherwise refuse the access request of this UE10.
In step 160, certificate server 60 notice WLAN Access Networks 30 authentication successs.
Then enter step 170, WLAN Access Network 30 notice UE10 authentication successs.
Then enter step 180, certificate server 60 is to HSS40 registration location information.This step is only effective to 3G subscription.
Further detailed content about WLAN and 3G fusion, can reference literature 3GPP TS23.234 V1.9.0, " 3GPP system to Wireless Local Area Network (WLAN) Interworking, System Description ", Chinese can be translated into " the collaborative work of third generation partner program system and wireless lan (wlan), system description ", with document GSM 09.02V7.0.0, " Mobile Application Part (MAP) specification ", Chinese can be translated into " MAP (MAP) specification ".
For WLAN and 3G emerging system and related procedure thereof, the very important point is to keep user contracting data and the user contracting data among the HSS/HLR45 on the certificate server 60 synchronous.This is because in flow process shown in Figure 2, and certificate server 60 at first uses local user contracting data to authenticate, if local not this user's user contracting data just obtains from HSS/HLR45.If the user contracting data on certificate server 60 and the HSS/HLR45 can not keep may causing the mistake that authenticates synchronously.For example, the user contracting data on the HSS/HLR45 is revised, and has enlarged some users' access rights, but the user contracting data on the certificate server 60 still is original, does not do to upgrade synchronously, causes this user can't enjoy new authority thus.
If UE10 is a 3G subscription, no problem synchronously about user contracting data between certificate server 60 and the HSS40.Because in verification process, certificate server 60 obtains user contracting data and preserves (being step 140) by " SubscriberProfile Request " (user contracting data request) message request from HSS40, behind authentication success, certificate server 60 is initiated " WLANRegistration " (WLAN (wireless local area network) registration) flow process and is registered to HSS40, in this flow processing, HSS40 preserves the address of this certificate server 60 in this user's information.In subsequent process, if change has taken place in user's subscription data, or the deletion subscription data, HSS40 is notification authentication server 60 in time, keeps data sync, so that certificate server 60 is correspondingly processed.
If but UE10 is GSM user, between certificate server 60 and the HLR50 between can't realize at present synchronously about user contracting data.Between certificate server 60 and the HLR50 flow process as shown in Figure 3, this flow process is to utilize ripe Signaling System Number 7 protocol signaling to realize, doing like this is that HLR50 for fear of to existing network makes amendment.
In step 210, certificate server 60 obtains user's subscription data by " MAP_RESTORE_DATA " (MAP restore data) message request from HLR50, has user's IMSI in the parameter of this message.
Enter step 220 subsequently, HLR50 has user's IMSI and subscription data to certificate server 60 feedback " MAP_INSERT_SUBSCRIBER_DATA " (MAP insertion subscription data) message in the parameter of this message.HLR50 just provides user's subscription data simply, do not do other processing, and behind authentication success, be not similar to yet " WLAN Registration " flow process in case certificate server 60 to HLR50 registration, thereby the address of in HLR50, not preserving certificate server 60.
From above flow process as can be seen, in verification process, if do not have user's subscription data in the certificate server 60, then obtain user contracting data and preserve from HLR50, at this moment, certificate server 60 is consistent with user contracting data among the HLR50.But owing to do not have the address of user place certificate server 60 among the HLR50, when user contracting data changes among the HLR50, can't notification authentication server 60, promptly can't keep data sync, therefore, there is following shortcoming in the prior art scheme:
1, if changed user's subscription data in HLR50, as stop user's WLAN business, HLR50 can't deal with by notification authentication server 60.If the user has inserted WLAN success, unless the user initiatively roll off the production line, otherwise, just can enjoy the WLAN business always.
2, if user contracting data has been deleted in user's cancellation in HLR50, HLR50 can't deal with by notification authentication server 60.If the user has inserted WLAN success, unless the user initiatively roll off the production line, otherwise, just can enjoy the WLAN business always.
In order to address the above problem, a kind of improvement project is arranged at present, certificate server 60 is by initiating to have " MAP_UPDATE_LOCATION " (MAP renewal position) flow process of IMSI parameter, replace " MAP_RESTORE_DATA " flow process in the agreement, from HLR50, obtain user contracting data.In this flow process, VLR of certificate server 60 simulations initiates " MAP_UPDATE_LOCATION " request to HLR50.HLR50 can send " MAP_CANCEL_LOCATION " request message to the VLR at this original place of user earlier when handling this request, notify this VLR deletion user profile, and then register new VLR address (being actually the address of certificate server 60).Because HLR50 can register the address of certificate server 60, change has taken place in user contracting data in HLR50, HLR50 meeting proactive notification certificate server 60, thus make the user contracting data in the certificate server 60 to keep synchronously with HLR50, and when data change, handle accordingly.
In actual applications, there is following problem in such scheme: must issue the other neocaine of user, otherwise can not enjoy the professional and original user business of WLAN simultaneously.
Cause a main cause of this situation to be, because HLR50 can notify the VLR deletion user profile at the original place of user, so can influence the original user business.So,, have to take to send out again in addition the way of a neocaine for the user enjoys the WLAN business.
Summary of the invention
The technical problem to be solved in the present invention provides a kind of certificate server and attaching position register method of data synchronization, making is not increasing neocaine or is influencing under the prerequisite of original business, and the user contracting data of attaching position register and certificate server also can be synchronous.
In order to solve the problems of the technologies described above, the invention provides a kind of certificate server and attaching position register method of data synchronization, comprise following steps:
A judges whether the holding time of the user contracting data on the described certificate server surpassed thresholding, if then obtain described user contracting data again from described attaching position register;
B judges whether obtaining of described user contracting data be successful, if then upgrade the time of successfully obtaining described user contracting data from described attaching position register.
Wherein, also comprise following steps:
After the described certificate server of C successfully obtains described user contracting data from described attaching position register, judge the situation that described user contracting data changes, and carry out respective handling.
When initiating authentication request by subscriber equipment, the user also comprises following steps:
D judges the user contracting data whether described user is arranged in the described certificate server, if then directly use the described user contracting data in the described certificate server to authenticate, otherwise described certificate server obtains described user's user contracting data to described attaching position register.
Certificate server described in the described step D obtains step from described user's user contracting data to described attaching position register also comprises following substep:
The described certificate server of D1 obtains described user contracting data to described attaching position register;
D2 judges whether obtaining of described user contracting data be successful, if then authenticate with the described user contracting data that newly obtains, and preserves from the time that described attaching position register successfully obtains described user contracting data.
In described steps A, when the holding time of the user contracting data on the described certificate server does not surpass thresholding, obtain the user contracting data on the described certificate server of next bar, and reenter steps A.
In the described steps A, the step of obtaining described user contracting data from described attaching position register again comprises following substep:
The described certificate server of A1 sends the MAP recovered data message to described attaching position register;
The described attaching position register of A2 inserts subscription data message to described certificate server feedback MAP.
In the described steps A, the step of obtaining described user contracting data from described attaching position register again also comprises following substep:;
The described certificate server of A3 is replied MAP to described attaching position register and is inserted the user contracting data response message;
The described attaching position register of A4 is replied MAP restore data response message to described certificate server.
In the described steps A 1, comprise user's international mobile station identity number in the parameter of described MAP recovered data message.
In the described steps A 2, comprise user's international mobile station identity number and described user contracting data in the parameter of described MAP insertion subscription data message.
By relatively can finding, technical scheme difference with the prior art of the present invention is, local user's subscription data that certificate server regularly surpasses thresholding to the holding time carries out active and refreshes.
Difference on this technical scheme has brought comparatively significantly beneficial effect, is not promptly increasing neocaine or is influencing under the prerequisite of original business, can keep the synchronous of user contracting data among certificate server and the HLR in the given time.Because be initiatively to refresh, do not need to simulate VLR, do not need to delete among original VLR and set up new registration procedure after the user profile, therefore can not influence original business, do not need to increase neocaine.In case, therefore can keep the synchronous of user contracting data among certificate server and the HLR in the given time after the time that certificate server is preserved surpasses thresholding again because user contracting data just refreshes.This programme does not need to change HLR in the existing network in addition, and it is comparatively convenient to implement.
Description of drawings
Fig. 1 is that WLAN and 3G merge system assumption diagram;
Fig. 2 is the access process figure that WLAN and 3G merge in the prior art;
Fig. 3 is the flow chart that certificate server obtains the GSM user contracting data in the prior art from HLR;
Fig. 4 is the flow chart that certificate server according to an embodiment of the invention authenticates UE;
Fig. 5 is the flow chart of certificate server according to an embodiment of the invention and HLR method of data synchronization.
Embodiment
For making the purpose, technical solutions and advantages of the present invention clearer, the present invention is described in further detail below in conjunction with accompanying drawing.
The flow process that certificate server authenticates UE as shown in Figure 4, in step 310, UE initiates authentication request.
After this enter step 320, certificate server is judged the local subscription data whether this user is arranged, if then enter step 330, otherwise enters step 340.Remain with part or all of user's subscription data on the certificate server, these user contracting datas generally are that this user obtained and remained from HLR when inserting in the past.These user contracting datas can be deleted from certificate server on certain opportunity, but concrete deletion may have nothing in common with each other the generally strategy decision of being formulated by operator opportunity.Therefore when the user initiates authentication request, there is bigger chance to use the user contracting data of certificate server this locality.
In step 330, certificate server authenticates with local user contracting data, after this process ends.Because there is user contracting data this locality, therefore preferential use local user subscription data authenticates, and can raise the efficiency like this.
In step 340, after this certificate server enters step 350 to the user contracting data that HLR obtains this user.Preserved all users' user contracting data among the HLR, therefore when certificate server is found the local user contracting data that does not have needs the user of new access (for example for), send " MAP_RESTORE_DATA " message that has this user ISMI parameter to HLR, request sends this user's user contracting data, HLR replys " MAP_INSERT_SUBSCRIBER_DATA " message, has this user's IMSI and subscription data in the parameter of this message.
In step 350, certificate server judges whether obtaining of user contracting data be successful, if enter step 360, otherwise process ends, the authentication request of refusal UE.That judges user contracting data obtains whether successful method is exactly to check " MAP_INSERT_SUBSCRIBER_DATA " message of whether having received at the appointed time from HLR, and contains this user IMSI and effective user contracting data in the parameter of this message.
In step 360, certificate server authenticates with the user contracting data that obtains, and preserves the time of successfully obtaining these data.After this this flow process finishes.Why the time of successfully obtaining user contracting data be to preserve, certificate server and HLR data sync flow services are.
The identifying procedure of certificate server when UE initiates authentication request has been described above, certificate server and HLR data sync flow process has been described below in conjunction with Fig. 5.
In step 410, certificate server judges that the holding time of the local user contracting data of preserving whether above thresholding, if then enter step 420, otherwise enters step 430.Can know from step 360, certificate server all can be preserved acquisition time later on successfully obtaining each bar user contracting data, therefore if holding time that the acquisition time of more current system time and each bar user contracting data just can be known these data whether above thresholding.In a preferred embodiment of the present invention, adopt the mode of automatic regular polling that each bar user contracting data is checked.If data may be more, can also adopt following method: the user contracting data of checking predetermined quantity in the each overtime back of periodicity timer, and the position of keep to check finishing, next time periodically behind the timer expiry, check this inspection of position that finishes since the last time.
In step 420, certificate server sends " MAP_RESTORE_DATA " message to HLR, after this enters step 440.The IMSI that has the user in the parameter of this message, request HLR sends this user's user contracting data.
In step 430, certificate server is got next user contracting data, after this enters step 410.Because it is overtime that the holding time of active user's subscription data does not have, therefore get next user contracting data and check.
In step 440, HLR sends " MAP_INSERT_SUBSCRIBER_DATA " message to certificate server, after this enters step 450.After HLR receives " MAP_RESTORE_DATA " message, in local data base, find out corresponding user contracting data according to the IMSI in this message, then this IMSI and user contracting data are sent to certificate server as parameter by " MAP_INSERT_SUBSCRIBER_DATA " message.
In step 450, certificate server is replied " MAP_INSERT_SUBSCRIBER_DATA_ACK " (MAP inserts the user contracting data response) message to HLR, after this enters step 460.The purpose that sends this message is that certificate server informs that HLR has successfully received " MAP_INSERT_SUBSCRIBER_DATA " message.Otherwise,, can retransmit " MAP_INSERT_SUBSCRIBER_DATA " message if HLR can not receive " MAP_INSERT_SUBSCRIBER_DATA_ACK " message for a long time.
In step 460, HLR replys " MAP_RESTORE_DATA_ACK " (response of MAP restore data) message to certificate server, after this enters step 470.This message mainly is the response to " MAP_RESTORE_DATA " message in the step 420, and HLR informs that the work that certificate server " MAP_RESTORE_DATA " message requires finishes.
In step 470, whether user contracting data is obtained in the certificate server judgement successful, if then enter step 480, otherwise enters step 430.
In step 480, certificate server upgraded from the time that HLR successfully obtains user contracting data, after this entered step 490.The purpose of doing this step is in order to guarantee that the renewal of user contracting data can normally be carried out next time.
In step 490, certificate server is judged the situation that user contracting data changes, and carries out respective handling, after this enters step 430.If variation has taken place user contracting data, certificate server need be adjusted at once.For example deleted some users' user contracting data among the HLR, whether just on line will check this user so, if then need to force this user offline at once.
Though by reference some preferred embodiment of the present invention, the present invention is illustrated and describes, but those of ordinary skill in the art should be understood that, can do various changes to it in the form and details, and the spirit and scope of the present invention that do not depart from appended claims and limited.
Claims (9)
1. certificate server and attaching position register method of data synchronization is characterized in that, comprise following steps:
A judges whether the holding time of the user contracting data on the described certificate server surpassed thresholding, if then obtain described user contracting data again from described attaching position register;
B judges whether obtaining of described user contracting data be successful, if then upgrade the time of successfully obtaining described user contracting data from described attaching position register.
2. certificate server according to claim 1 and attaching position register method of data synchronization is characterized in that, also comprise following steps:
After the described certificate server of C successfully obtains described user contracting data from described attaching position register, judge the situation that described user contracting data changes, and handle.
3. certificate server according to claim 1 and attaching position register method of data synchronization is characterized in that, also comprise following steps when the user initiates authentication request by subscriber equipment:
D judges the user contracting data whether described user is arranged in the described certificate server, if then directly use the described user contracting data in the described certificate server to authenticate, otherwise described certificate server obtains described user's user contracting data to described attaching position register.
4. certificate server according to claim 3 and attaching position register method of data synchronization, it is characterized in that certificate server described in the described step D obtains step from described user's user contracting data to described attaching position register also comprises following substep:
The described certificate server of D1 obtains described user contracting data to described attaching position register;
D2 judges whether obtaining of described user contracting data be successful, if then authenticate with the described user contracting data that newly obtains, and preserves from the time that described attaching position register successfully obtains described user contracting data.
5. certificate server according to claim 1 and attaching position register method of data synchronization, it is characterized in that, in described steps A, when the holding time of the user contracting data on the described certificate server does not surpass thresholding, obtain the user contracting data on the described certificate server of next bar, and reenter steps A.
6. certificate server according to claim 1 and attaching position register method of data synchronization is characterized in that, in the described steps A, the step of obtaining described user contracting data from described attaching position register again comprises following substep:
The described certificate server of A1 sends the MAP recovered data message to described attaching position register;
The described attaching position register of A2 inserts subscription data message to described certificate server feedback MAP.
7. certificate server according to claim 6 and attaching position register method of data synchronization is characterized in that, in the described steps A, the step of obtaining described user contracting data from described attaching position register again also comprises following substep:
The described certificate server of A3 is replied MAP to described attaching position register and is inserted the user contracting data response message;
The described attaching position register of A4 is replied MAP restore data response message to described certificate server.
8. certificate server according to claim 6 and attaching position register method of data synchronization is characterized in that, in the described steps A 1, comprise user's international mobile station identity number in the parameter of described MAP recovered data message.
9. certificate server according to claim 6 and attaching position register method of data synchronization, it is characterized in that, in the described steps A 2, comprise user's international mobile station identity number and described user contracting data in the parameter of described MAP insertion subscription data message.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2003101011109A CN1324909C (en) | 2003-10-15 | 2003-10-15 | Method for synchronizing data between authentication server and home location register |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2003101011109A CN1324909C (en) | 2003-10-15 | 2003-10-15 | Method for synchronizing data between authentication server and home location register |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1607842A true CN1607842A (en) | 2005-04-20 |
| CN1324909C CN1324909C (en) | 2007-07-04 |
Family
ID=34756112
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2003101011109A Expired - Fee Related CN1324909C (en) | 2003-10-15 | 2003-10-15 | Method for synchronizing data between authentication server and home location register |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1324909C (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2007140699A1 (en) * | 2006-06-06 | 2007-12-13 | Huawei Technologies Co., Ltd. | A method and apparatus for updating subscriber signed data |
| CN101232634B (en) * | 2007-01-24 | 2011-10-26 | 华为技术有限公司 | Data synchronization method, system and device |
| CN105101197A (en) * | 2014-05-07 | 2015-11-25 | 中兴通讯股份有限公司 | User contract-signing information response and request method and device |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1188339B1 (en) * | 1999-06-24 | 2004-11-24 | Hewlett-Packard Development Company, L.P. | Method and system for providing telecommunication services across networks that use different protocols |
| DE60023155T2 (en) * | 2000-11-24 | 2006-07-06 | Telefonaktiebolaget Lm Ericsson (Publ) | Fraud detection procedure for mobile telecommunication networks |
-
2003
- 2003-10-15 CN CNB2003101011109A patent/CN1324909C/en not_active Expired - Fee Related
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2007140699A1 (en) * | 2006-06-06 | 2007-12-13 | Huawei Technologies Co., Ltd. | A method and apparatus for updating subscriber signed data |
| CN101232634B (en) * | 2007-01-24 | 2011-10-26 | 华为技术有限公司 | Data synchronization method, system and device |
| CN105101197A (en) * | 2014-05-07 | 2015-11-25 | 中兴通讯股份有限公司 | User contract-signing information response and request method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1324909C (en) | 2007-07-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10313869B2 (en) | Communication supporting method and apparatus using non-access stratum protocol in mobile telecommunication system | |
| JP4991969B2 (en) | Method and apparatus for updating access point name subscription configuration | |
| US9065641B2 (en) | Method and device for updating a key | |
| TW200945865A (en) | Method for handling the equipment identity requests and communication apparatus utilizing the same | |
| EP1733520A1 (en) | Method, apparatus and communications network for managing electronic mail services | |
| CN1689369A (en) | Method and system for establishing a connection via an access network | |
| CN1649435A (en) | Method for realizing roaming user to visit network inner service | |
| CN1835436A (en) | General power authentication frame and method of realizing power auttientication | |
| CN101043328A (en) | Cipher key updating method of universal leading frame | |
| CN1645793A (en) | Cut-in identification realizing method for wireless local network | |
| CN1567894A (en) | Method of route inquiry under condition of wireless local area network and mobile network intercommunication | |
| CN1795656A (en) | Secure traffic redirection in a mobile communication system | |
| CN1848823A (en) | System and method for intercommunicating with mobile network short message based on IP switch-in network | |
| CN1324909C (en) | Method for synchronizing data between authentication server and home location register | |
| JP2005528008A (en) | System and method for using CDMA mobile with GSM core infrastructure | |
| CN100346668C (en) | Updating protocal method of secret keys | |
| JP4984020B2 (en) | Communication system, node, authentication server, communication method and program thereof | |
| CN1642076A (en) | Method for obtaiing user identification by packet data gate for wireless LAN | |
| CN1802817A (en) | Method and network for WLAN session control | |
| CN1656748A (en) | Synchronization of an emulated device over a local link | |
| CN101064919A (en) | Method for authentication of CDMA user roaming to GSM network | |
| CN101835150B (en) | Method, device and system for updating shared enciphered data | |
| CN1829193A (en) | Route area updating method between SGSNs | |
| CN101998380B (en) | Method for transmitting mobile directory number (MDN) | |
| CN1617522A (en) | Method for sending a ata of user mark after renewing |
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 | ||
| C17 | Cessation of patent right | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20070704 Termination date: 20131015 |