CN1805448A - Mobile ip registration process for an always-on device - Google Patents

Mobile ip registration process for an always-on device Download PDF

Info

Publication number
CN1805448A
CN1805448A CN200610005828.1A CN200610005828A CN1805448A CN 1805448 A CN1805448 A CN 1805448A CN 200610005828 A CN200610005828 A CN 200610005828A CN 1805448 A CN1805448 A CN 1805448A
Authority
CN
China
Prior art keywords
error
registration
mip
network
mobile device
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN200610005828.1A
Other languages
Chinese (zh)
Other versions
CN1805448B (en
Inventor
M·卡勒杜尔·依斯拉姆
金真
萨依德·R·查乌瑞
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
BlackBerry Ltd
Original Assignee
Research in Motion Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Research in Motion Ltd filed Critical Research in Motion Ltd
Publication of CN1805448A publication Critical patent/CN1805448A/en
Application granted granted Critical
Publication of CN1805448B publication Critical patent/CN1805448B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W60/00Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/02Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04Registration at HLR or HSS [Home Subscriber Server]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W80/00Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04Network layer protocols, e.g. mobile IP [Internet Protocol]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W80/00Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04Network layer protocols, e.g. mobile IP [Internet Protocol]
    • H04W80/045Network layer protocols, e.g. mobile IP [Internet Protocol] involving different protocol versions, e.g. MIPv4 and MIPv6

Abstract

A system and method for an automatic retry method during initial registration and re-registration of a mobile device on a mobile Internet Protocol (MIP) network is provided. The mobile device is adapted to categorise a registration response (RRP) code and accordingly determine a course of action. By reacting intelligently to the RRP code category, the mobile device is able to maintain a point to point protocol (PPP) connectivity and achieve ''always-on'' status.

Description

Mobile IP registration process method at always online equipment
Technical field
Internuncial the providing of IP (Internet Protocol) to wireless device is provided the application, more specifically, relates to wireless device is registered on MIP (mobile IP) network.
Background technology
MIP (mobile IP, Mobile IP) is the agreement that is proposed by IETF (internet engineering task group) at first, and is described in file " RFC 2002-IP Mobility Support ".In the MIP network, HA (home agent, home agent) distributes to static home IP address each related mobile device usually.When mobile device was roamed in the MIP network, it was registered to FA (strange land agency, foreign agent), FA provide COA (Care-of Address, care-of-address).By enrollment process, the COA of mobile device is notified to HA.FA keeps the binding of home IP address to COA in being called as the special time length of registering the duration.Between HA and mobile device, set up the tunnel, make HA send grouping (packets) to mobile device by FA; Therefore, mobile device can reach by its home IP address.As long as mobile device was set up new registration procedure in the past in the registration duration, just can keep PPP (peer-peer protocol, point to point protocol) connectivity.
In SIP (simple IP, Simple IP) network, dynamically distribute relevant IP address, geographical position for mobile device by visit PDSN (packet data serving node, Packet Data Serving Nodes).When mobile device was roamed, it may be assigned with the relevant IP address of new geography in the duration that mobile device is not known.MIP compares with SIP (simple IP) lot of advantages is provided, as utilize the relevant home IP address of its non-geography realized with mobile device between communicate by letter.The needs of having eliminated the current geographical annex point of knowing mobile device have greatly increased roaming capacity, and make different application servers to reach mobile device by its known home IP address, and annex point to MIP network current with it is irrelevant.Equally, MIP has realized that the multi-user with different user ID/ password is provided with etc.
The mobile device that is configured to " only for mobile IP " may run into the multiple registration problem in the network, is not always the case during at homing position with in roaming.If these situations of incorrect processing then may cause the internuncial interruption of data, cause user " always online " mobile device relatively poor experience to occur.On the other hand, mobile device may cause the congested of unwarranted MIP network insertion, the battery life that reduces mobile device and MIP network to the powerful re-try attempt of MIP network registration.
Article " Diameter Mobile Ipv4Application " people such as Pat R.Calhoun, Internet Engineering Task Force, 20 volumes, the diameter that discloses the charging information of the mobile IPv 4 service that allows diameter server authentication, mandate and collection to offer mobile node in 2004 8 months is used.Combine with the cross-cutting ability of basic agreement, this uses the service of mobile node reception from the strange land service supplier that allow.Strange land and home agent will use diameter record keeping message to transmit to the diameter server and use message.
Article " IP Mobility Support for Ipv4 " at Ed.C.Perkins, Internet Engineering Task Force discloses in 2002 8 months and has allowed in the internet the transparent enhancing agreement that is routed to mobile node of IP datagram (datagrams).Always identify each node, and annex point to internet current with it is irrelevant with its home address.Away from its homing position the time, mobile node also is associated with Care-of Address, and Care-of Address provides and its current information relevant to the annex point of internet.This agreement provides to home agent transmitting register address.It is the datagram of destination that home agent sends with the mobile node by the tunnel of going to Care-of Address.After arriving the tunnel end, each datagram is passed to mobile node.
U.S. Pat 6,735,202 disclose the mobile management technology that is used in based in the multimedia mobile network of Internet Protocol.In the mobile management scheme of this invention, defined several only mobile management control messages, be used in communication system, at mobile subscriber station and network node, the multiple mobile management function of execution.These message can comprise: (i) location update message (LUM, Location Update Message); (ii) location confirmation message (LCM, Location Confirm Message); (iii) position enquiring message (LQM, Location Query Message); (iv) message (LRM, Location ReplyMessage) is replied in the position; (v) registration message (RM, Registration Message); (vi) message (Registration Reply Message) is replied in registration.With one or more being used in the IP-based network in these message, to carry out as mobile management functions such as mobile management in location management, mobile access and the calling.
The international open WO 2004/049664 of patent document discloses terminal that data are provided and the circuit that is used to upgrade portable terminal.To the initiation by network give information subsequently (subsequentprovisioning message) receive, this message request portable terminal initiates to upgrade the session that data are provided of portable terminal, and whether definite portable terminal is utilizing current registration Internet Protocol (IP) session to carry out foreground data applications.Whether utilizing current registration IP session to carry out determining of foreground data applications according to portable terminal, initiating the IP session selectively, so that the data that provide of portable terminal to be provided.
Summary of the invention
According to a wide in range scheme, the application provides the method in a kind of wireless device (105), comprising: attempt (200,201) automatically and set up the wireless protocols session, described wireless protocols uses statically-addressed to operate; At each error category in a plurality of error categories, when failing to set up the wireless protocols session, automatically perform at least one corresponding error classification specific step (204,205,206) owing to the mistake in this error category.
In certain embodiments, described wireless protocols is MIP (mobile Internet Protocol).
In certain embodiments, described method comprises: a) initialization MIP (mobile Internet Protocol) registration (200); B) send MIP registration request (201); Wherein at least one error category, described at least one corresponding error classification specific step (204,205,206) comprises returns step a) automatically; And at least one error category, described at least one corresponding error classification specific step (204,205,206) comprises returns step b) automatically.
In certain embodiments, described method comprises: at least one error category, return step a) at some conditions, and return step b) at other conditions (417,515,505).
In certain embodiments, at least one error category, described at least one corresponding error classification specific step (204,205,206) is included in the first rollback time (408,415,506,518) and returns step a) afterwards automatically; And at least one error category, described at least one corresponding error classification specific step (204,205,206) is included in the second rollback time (406,506) and returns step b) afterwards automatically.
In certain embodiments, described a plurality of error category comprises no register response (301), loses timing error (302), wrong (303) and temporary transient network error (304) is provided.
In certain embodiments, described method also comprises: the definition at least two group RRP codes, every group of RRP code definition the error category in described a plurality of error categories; The RRP code that reception is attempted in response to failed registration, and utilize RRP code (203) to determine error category.
In certain embodiments, at MIP registration duration past tense, and when wireless device moves to new MIP network, carry out initialization MIP registration.
In certain embodiments, when wireless device powers up, and when wireless device switches to new user and is provided with, carry out initialization MIP registration.
In certain embodiments, described method also comprises: at least two users of definition are provided with (703) on wireless device, and one of them is validated user setting (profile) in the given moment; Wherein at least one error category, at described at least two users in (702) each is set, differently define described at least one corresponding error classification specific step.
In certain embodiments, each user's setting is that NAI (network access identifier, networkaccess identifier) is provided with.
In certain embodiments, described method also comprises: safeguard the retry history that each user is provided with, described retry history comprises not allowing the sign of the network of registration; And,, carry out described at least one corresponding error classification specific step as the function of described retry history at least one error category.
In certain embodiments, at no register response, described at least one corresponding error classification specific step comprises the registration request that resends; At losing timing error, described at least one corresponding error classification specific step (414,514) comprising: if a) current challenge the unknown, lose or out-of-date, the request challenge resends the registration request then; Perhaps b) if there is registration sign mismatch, then adjusts timestamp, resend the registration request then; At temporary transient network error, described at least one corresponding error classification specific step (415,515) comprising: if a) have MIP session formerly, sending duration is zero registration request; B) discharge the resource be used to attempt to the network registration wireless device, then attempts registration wireless device again; And at mistake is provided, described at least one corresponding error classification specific step (416,516) comprising: if a) have MIP session formerly, sending duration is zero registration request; B) discharge the resource be used to attempt to the network registration wireless device; C) network is added in the tabulation of the network that does not allow the grouped data access, wait for the network that does not find in this tabulation of acquisition then, then the method for retry registration wireless device.
In certain embodiments, define each error category by corresponding RRP code-group: no register response, lose timing error, provide wrong and temporary transient network error.
In another embodiment, provide a kind of wireless device that is suitable for realizing one of said method.
In another embodiment, provide a kind of computer-readable medium, stored computer executable instructions on it, be used on wireless device, carrying out, thereby realized one of said method.
Description of drawings
Now, with reference to the accompanying drawings, preferred embodiment is described, wherein:
Fig. 1 is the schematic diagram of example MIP (mobile IP) network;
Fig. 2 is the embodiment according to the application, the flow chart of registering the method for mobile device on the MIP network;
Fig. 3 be according to the application embodiment, a plurality of flow charts of example error category specific actions are provided;
Fig. 4 be according to the application embodiment, on the MIP network flow chart of the method for initial registration mobile device;
Fig. 5 be according to the application embodiment, on the MIP network, set up new registration procedure the flow chart of the method for mobile device;
Fig. 6 A, 6B, 6C be according to the application embodiment, example RRP (registration reply) is provided other chart of code word; And
Fig. 7 is the block diagram of example mobile device.
Embodiment
Now, with reference to Fig. 1, show the schematic diagram of example MIP (mobile IP) network 100.MIP network 100 has HA (home agent) 101 that links to each other with home network 102 and the FA that links to each other with strange land network 104 (strange land agency) 103.Home agent 101 links to each other with strange land agency 103 by one or more networks 106.Although not shown in the drawings, there is a plurality of strange lands network 104 usually, each strange land network 104 has related FA 103 (not shown).Mobile device 105 is plotted near the strange land network 104, to represent its visit strange land network 104.Usually there are a plurality of mobile device (not shown).
Be in operation, mobile device 105 uses two IP addresses: home IP address and COA (Care-of Address).MIP session foundation relates to agent discovery, utilizes the tunnel of COA between FA 103 registrations and HA 101 and FA 103 to set up.In case provided and managed by HA 101, home IP address is normally static.COA is safeguarded by FA 103, and expression is to the annex point of strange land network 104.When mobile device 105 was roamed between different strange land networks 104, COA dynamically changed.FA 103 is notified to home agent 101 with COA, thereby can pass through the tunnel, utilizes its home IP address, arrives mobile device 105.
As the part of agent discovery process, FA 103 sends ICMP (Internet Control Message Protocol, Internet Control Message Protocol) AAM (agent advertisement message, agent advertisement message) to mobile device 105.AAM has the MIP agent advertisement extension, and also can comprise the FA challenge extension that is used to authenticate.A plurality of characteristic sets (for example, the reverse tunnel of supporting by FA 103) that the MIP agent advertisement extension is drawn together one or more COA, registration duration and supported by FA 103.After mobile device 105 received the information relevant with FA 103 abilities, it sent MIP RRQM (register request message, registration request message) to FA 103.RRQM is RRQ (registration request, registration request), and it comprises the IP address of home IP address, HA 101, the COA and a plurality of parameters relevant with authentication of being asked.Usually during initially providing, RRQM also can comprise the indication of the IP address of still unallocated home IP address and HA.After initial authentication, FA 103 is transmitted to HA 101 by network 106 with this information.In case mobile device 105 is by success identity, HA 101 sends RRPM (enrollment response message, registration response message) by FA 103 to mobile device 105, and whether the indication registration is successful.If the registration request is not accepted in FA 103 or HA 101 decisions, then indicate reason by RRP (registration is replied, the registration reply) code that is included among the RRPM.
In certain embodiments, CDMA (code division multiple access, Code-Division MultipleAccess) technology is used as the wireless network that links to each other with MIP network 100.But it also is possible adopting other technologies, and within the application's scope.
Automatic retry method
Now, turn to Fig. 2, show the embodiment according to the application, the flow chart of on MIP network 100, registering the method for mobile device 105.Mobile device 105 is carried out initialization in step 200, prepares to register to MIP network 100.Next, mobile device 105 is attempted registering to MIP network 100 in step 201.Usually come to determine successful registration in some way.If be registered in step 202 success, then this method finishes.But, also may register and unsuccessful answer message that can be by receiving the unsuccessful registration of indication or do not receive any answer message at all and indicate.If it is unsuccessful to be registered in step 202, then this method is classified in step 203 pair mistake.Do not reply message and receive and represent that the unsuccessful answer message of registering is the example at the error category of unsuccessful registration.
Usually, a plurality of error categories are possible.Fig. 2 shows N classification by step 204,205 and 206 expressions.In in step 204,205 and 206 each, carry out the action that is exclusively used in this error category.Preferably, automatically perform these actions, and need not any input from the user.After finishing these actions, this method continues.The detail how method continues is at using.For example, at some error categories, this method can continue by turning back to the initialized A of expression execution.At other error categories, this method can newly be registered the B that attempts need not to reinitialize and continues by turning back to expression.More generally, described method can continue A at some conditions, and continues B at other conditions.In certain embodiments, at least one error category, this method continues by returning A, and at least one other error category, this method continues by returning B.
In certain embodiments, before returning B, realized for the first rollback time, realized for the second rollback time that before returning A the second rollback time was longer than for the first rollback time.In specific example, an error category of definition this method is no matter for what MIP registration to attempt, without any response.The method continues B, realizes for the first rollback time between each MIP registration is attempted.If at this specific error category, experienced pre-configured number of failed attempts, then this method continues A at second rollback after the time.In another specific example, an error category of this method relates to the timing error that loses by the error code indication that receives.When this mistake took place, this method was waiting for that second rollback returns A after the time.But under given conditions, this method is returned B at first rollback after the time.
Error category specific actions
Now, turn to Fig. 3, with according to the application's embodiment, a plurality of block diagram form of example error category specific actions are provided, show another complete retry method.In operation, mobile device 105 sends RRQM, so that register to MIP network 100.If mobile device 105 receives the successful RRPM of indication registration, then mobile device 105 will be registered in the registration duration.In step 301,, then carry out action if mobile device 105 does not receive any response.
Step 302,303 and 304 other example error category specific actions of expression.In step 302,, carry out action when receiving indication when losing the RRPM of timing error.In step 303, when receiving the response of the temporary transient network error of indication, carry out action.In step 304,, carry out action when receiving indication when wrong response is provided.In one embodiment, realize the error category specific actions of Overall Steps 301,302,303 and 304.In another embodiment, at least one in the error category specific actions of performing step 301 and the step 302,303 and 304.
After a while, by means of Fig. 4 and Fig. 5, provide the details of these example error category specific actions.
The user is provided with (User Profiles)
In certain embodiments, each mobile device 105 supports a plurality of users to be provided with.The example that the user is provided with is NAI (network access identifier), and each NAI is provided with and comprises user ID, password and shared secret.Mobile device 105 can switch between several NAI are provided with, but preferably, at given time, has only a NAI to be provided with effectively.
In certain embodiments, be provided with, safeguard retry history at each NAI.For example, retry history comprises the tabulation of the network that does not allow to set up the MIP session.For example, can not set up the MIP session if having the mobile device 105 that effective NAI is provided with " x ", then mobile device 105 will write down network and not allow NAI setting " x " to set up the MIP session in this tabulation.If provide specific NAI to be provided with again, then wiped its whole associated retry history.Again the example that provides comprises that clear and definite user initiates to provide trial or network to initiate to provide trial, as IOTA (aerial internet, Internet over the air).
In certain embodiments, the retry method of being carried out by mobile device 105 is that effective NAI is provided with and/or with this NAI the function of the retry history that is associated is set.Can be provided with at each, dispose different retry methods.Then, when receiving given RRP code, performed retry method is at received RRP code and effective setting and/or retry history.
Automatic retry method at initial registration
Now, turn to Fig. 4, show embodiment, the flow chart of the method for initial registration mobile device 105 on MIP network 100 according to the application.Carry out initial registration, so that set up PPP session at mobile device 105.In order to keep " always online " state, preferably, mobile device 105 triggers initial registration automatically, for example, and when it powers up or switches to another NAI and is provided with.When initiation MIP session was set up, described method began in step 401.In step 402,, FA 103 abilities are notified to mobile device 105 by receiving AAM from FA 103.Utilize this information, mobile device 105 is asked registration in step 403 by sending RRQM to FA 103.In step 404, mobile device 105 attempts receiving the RRPM from FA 103.If do not receive RRPM, then mobile device 105 will be overtime by determining whether to arrive maximum RRQM, determine whether it should resend RRQM.If still the maximum RRQM of no show is overtime, then mobile device 105 will resend RRQM after time delay.In step 406, mobile device 105 set RRQM retry back-off timers, and waited for that at mobile device 105 it is expired before step 403 resends RRQM.But if it is overtime to have reached maximum RRQM in step 405, then mobile device 105 is in step 407 set failure code, and proceeds to step 408.In step 408, mobile device 105 prepares to start anew retry MIP initial registration after time delay.Mobile device 105 is cancelled the PPP stack with the LCP termination messages, so that discharge resource, and set MIP retry back-off timer, and wait for that MIP retry back-off timer is expired.In case MIP retry back-off timer is expired, then, attempt the MIP initial registration again by being looped back to step 401.
If mobile device 105 receives RRPM in step 404, then whether the mobile device 105 RRP code determining to be included among the RRPM in step 409 represents the success of MIP initial registration.If successfully set up the MIP session.Then described method finishes in step 410, and mobile device 105 was registered in the duration given by the registration duration.The 105 storage registration duration of mobile device, be used for triggering and set up new registration procedure.If the MIP initial registration is success not, then mobile device 105 is carried out from step 411 action of starting process according to receiving the RRP code.
Lose stationary problem if mobile device 105 is determined to exist according to the RRP code in step 411, then lose stationary problem in step 414 addressing.Mobile device 105 loses coincidence counter by determine whether to exceed maximum in step 417, determines whether to have experienced the too much stationary problem that loses.Do not lose coincidence counter if exceed maximum yet, then mobile device 105 will resend RRQM in step 403.Otherwise mobile device 105 prepares to start anew retry initial registration after time delay.In step 415, mobile device 105 is cancelled the PPP stack with the LCP termination messages, set MIP retry back-off timer, and wait for that MIP retry back-off timer is expired.In case MIP retry back-off timer is expired, then, attempt the MIP initial registration again by being looped back to step 401.
If there is no lose stationary problem, then mobile device 105 determines in step 412 whether the RRP code represents temporary transient network error.If there is temporary transient network error, then mobile device 105 prepares to start anew retry initial registration in the step of having discussed 415 after time delay.
If there is no temporary transient network error, then mobile device 105 determines in step 413 whether the RRP code represents to provide mistake.Provide mistake if exist, then mobile device 105 prepares to start anew retry initial registration after time delay.In step 416, mobile device 105 is cancelled the PPP stack with the LCP termination messages, and record does not allow the network that inserts in tabulation, and waits for the network that does not find in the tabulation up to obtaining.In case completing steps 416 then by being looped back to step 401, is attempted the MIP initial registration again.
In certain embodiments, at being different from the error category set that in step 411,412 and 413, realizes, analyze the RRP code.Error category can be revised or increase to this method.More generally, retry method is operated as the function of the RRP code that receives.Preferably, automatically perform retry method, and need not input from the user.Should be appreciated that Fig. 4 is a specific embodiment, and multiple other embodiment are possible.After a while, will the detail of preferred error categories be discussed by means of Fig. 6.
At the automatic retry method of setting up new registration procedure
Now, turn to Fig. 5, show embodiment, on MIP network 100, set up new registration procedure the flow chart of the method for mobile device 105 according to the application.In this case, mobile device 105 has existing PPP session, and the home IP address of being distributed is (x.y.z.w).Mobile device 105 is from step 500, in the registration duration expired before, set up new registration procedure its home IP address (x.y.z.w) automatically.In step 503, mobile device 105 is by sending RRQM, and its home IP address (x.y.z.w) is set up new registration procedure in request.In typical scene, receive the RRP code in step 504, and set up new registration procedure successfully, and, mobile device 105 is set up new registration procedure another registration duration in step 510 at step 509 indication MIP.
Step 501 to 507 among Fig. 5 and step 509 to 513 are equal to step 401 to 407 and step 409 to 413 in fact.Therefore, will the details of these steps be discussed no longer.Other steps relate to the retry method of mobile device 105 under the situation that does not receive the successful MIP of the indication RRP code of setting up new registration procedure.Preferably, the retry method of mobile device 105 is different with initial registration at setting up new registration procedure.
If mobile device 105 has experienced maximum RRQM when waiting for RRPM overtime, then prepare after time delay, to set up new registration procedure from step 501 retry.If when entering step 508, the MIP session exists, and then in step 508, mobile device 105 sending durations are zero RRQ code, so that stop the MIP session.Then, mobile device 105 is cancelled the PPP stack with the LCP termination messages, to discharge resource, its home IP address is reset to 0.0.0.0, set MIP retry back-off timer, and wait for that MIP retry back-off timer is expired.In case MIP retry back-off timer is expired, then, attempts MIP again and set up new registration procedure by being looped back to step 501.After completing steps 501 and 502, mobile device 105 will send in step 503 and comprise the RRQM of home IP address 0.0.0.0 that resets, thereby make HA 101 learn that mobile device 105 lost its home IP address.
If the RRP code that receives loses stationary problem in step 511 indication, then handle and lose stationary problem in step 514.Lose stationary problem in case solved, then mobile device 105 resends RRQM by being looped back to step 503, so that retry home IP address (x.y.z.w) is set up new registration procedure.
If the RRP code that receives is at the temporary transient network error of step 512 indication, then mobile device 105 determines whether and should set up new registration procedure from step 501 or 503 beginning retries.If mobile device 105 determines to exceed yet the registration duration in step 515, then will resend RRQM in step 503 by after setting up new registration procedure the time delay that the rollback timer provides.But if exceeded the registration duration, then mobile device 105 is prepared to set up new registration procedure at step 501 retry in step 518.Action in mobile device 105 execution in step 518 is equal to the action in the step 508 in fact.Owing to the details of step 508 had been discussed, the details of step 518 no longer had been discussed here.After step 518,, attempt MIP again and set up new registration procedure by being looped back to step 501.
If the RRP code that receives indication provides mistake, then mobile device 105 is prepared to set up new registration procedure at step 501 retry in step 516.If there is the MIP session when entering step 516, then mobile device 105 sending durations are zero RRQ code, so that stop the MIP session.Then, mobile device 105 is cancelled the PPP stack with the LCP termination messages, and discharging resource, record does not allow the network that inserts in tabulation, and waits for the network that does not find in the tabulation up to obtaining.Next, by being looped back to step 501, attempting MIP again and set up new registration procedure.
In certain embodiments, at being different from the error category set that in step 511,512 and 513, realizes, analyze the RRP code.Error category can be revised or increase to this method.More generally, retry method is operated as the function of the RRP code that receives.Preferably, automatically perform retry method, and need not input from the user.Should be appreciated that Fig. 5 is a specific embodiment, and multiple other embodiment are possible.After a while, will the detail of preferred error categories be discussed by means of Fig. 6 A, 6B, 6C.
Error category
Now, turn to Fig. 6 A, 6B, 6C, show embodiment, the chart of example error category is provided according to the application.Preferably, according to the RRP code, each mistake is divided three classes: temporarily lose stationary problem, temporary transient network error and problem is provided.In the method for Fig. 3 and Fig. 4, can see classification according to the RRP code of these classifications.If the method for Fig. 2 is classified to mistake according to the RRP code in step 203, can comprise also that then expression does not receive the additional category of RRP code.
Each classification of Fig. 6 A, 6B, 6C comprises at least one RRP code, and each all has relevant description and source.IANA (the Internet assignment numbers authority) provides up-to-date RRP code in following network address: Http:// www.iana.org/assignments/ Mobileip-numbers
Should be appreciated that Fig. 6 is used to classify the very concrete preferred embodiment of RRP code, and other embodiment are possible.In addition, IANA develops the tabulation of RRP code, and it is of course possible to the RRP code is made amendment, added or removes.Therefore, should be appreciated that the different embodiment of classification RRP code are possible, especially along with the development of IANA to the RRP code listing.
Mobile device
Now, turn to Fig. 7, show the block diagram of example mobile device 105.Mobile device 105 has with processor 701 and at least one NAI 703 that link to each other, as to be used to realize multiple automatic MIP retry method 702 function is set.
In operation, MIP retry method 702 utilizes processor 701 and NAI to be provided with 703 automatically, so that realize any means as described herein.Preferably, MIP retry method 702 comprises computer-readable medium automatically, stores computer executable instructions on it, is used to indicate mobile device 105 to realize any means as described herein.In another embodiment, MIP retry method 702 comprises any appropriate combination of hardware, software or firmware automatically, is used to realize any means as described herein.
Embodiment as described herein concentrates on the automatic retry method that is used for registration mobile device 105 on MIP network 100.More generally, other embodiment are possible, and relate to the automatic retry method that is used on other networks registration mobile device 105, and for example, described network has and utilizes non-geographical relevant addressed to handle the wireless protocols of ambulant addressing.In this network, initial address can be geographical relevant, is for example distributed by home agent, but when mobile device 105 moves to new network, under possible situation, keeps identical address.
By above instruction, the application's multiple modification and variant all are possible.Therefore, should be understood that, within the scope of the appended claims, can with specifically described the application that differently realizes here.

Claims (16)

1, a kind ofly automatically attempt setting up the method for wireless protocols session in wireless device, described wireless protocols uses statically-addressed to operate, and described method comprises:
At each error category in a plurality of error categories, when failing to set up the wireless protocols session, automatically perform at least one corresponding error classification specific step owing to the mistake in this error category.
2, method according to claim 1 is characterized in that described wireless protocols is mobile Internet Protocol (MIP).
3, method according to claim 2 is characterized in that comprising:
A) initialization mobile Internet Protocol (MIP) registration; And
B) send MIP registration request;
Wherein at least one error category, described at least one corresponding error classification specific step comprises returns step a) automatically; And
At at least one error category, described at least one corresponding error classification specific step comprises returns step b) automatically.
4, method according to claim 3 is characterized in that comprising:
At at least one error category, return step a) at some conditions, and return step b) at other conditions.
According to claim 3 or 4 described methods, it is characterized in that 5, described at least one corresponding error classification specific step is returned step a) after being included in for the first rollback time automatically at least one error category; And wherein
At at least one error category, described at least one corresponding error classification specific step is returned step b) after being included in for the second rollback time automatically.
6,, it is characterized in that described a plurality of error category comprises no register response, loses timing error, wrong and temporary transient network error is provided according to any described method among the claim 1 to 5.
7, according to any described method among the claim 3 to 6, it is characterized in that also comprising:
The definition at least two group RRP codes, every group of RRP code definition the error category in described a plurality of error categories;
The RRP code that reception is attempted in response to failed registration, and utilize the RRP code to determine error category.
8,, it is characterized in that at MIP registration duration past tense, and when wireless device moves to new MIP network, carry out initialization MIP registration according to any described method among the claim 3 to 7.
9, according to any described method among the claim 3 to 7, it is characterized in that when wireless device powers up, and when wireless device switches to new user and is provided with, carry out initialization MIP registration.
10, according to any described method among the claim 1 to 9, it is characterized in that also comprising:
At least two users of definition are provided with on wireless device, and one of them is the validated user setting in the given moment;
Wherein at least one error category, each in being provided with at described at least two users differently defines described at least one corresponding error classification specific step.
11, method according to claim 10 is characterized in that it is network access identifier (NAI) setting that each user is provided with.
12, according to any described method among the claim 1 to 11, it is characterized in that also comprising:
Safeguard the retry history that each user is provided with, described retry history comprises not allowing the sign of the network of registration; And
At at least one error category,, carry out described at least one corresponding error classification specific step as the function of described retry history.
13, according to any described method among claim 6 or the claim 7 to 12, when being subordinated to claim 6, it is characterized in that:
At no register response, described at least one corresponding error classification specific step comprises the registration request that resends;
At losing timing error, described at least one corresponding error classification specific step comprises:
If a) current challenge the unknown, lose or out-of-date, the request challenge resends the registration request then; Perhaps
B) if there is registration sign mismatch, then adjust timestamp, resend the registration request then;
At temporary transient network error, described at least one corresponding error classification specific step comprises:
If a) have MIP session formerly, sending duration is zero registration request;
B) discharge the resource be used to attempt to the network registration wireless device, then attempts registration wireless device again; And
At mistake is provided, described at least one corresponding error classification specific step comprises:
If a) have MIP session formerly, sending duration is zero registration request;
B) discharge the resource be used to attempt to the network registration wireless device;
C) network is added in the tabulation of the network that does not allow the grouped data access, wait for the network that does not find in this tabulation of acquisition then, then the method for retry registration wireless device.
14, method according to claim 6 is characterized in that defining each error category by corresponding RRP code-group: no register response, lose timing error, provide wrong and temporary transient network error.
15, a kind of wireless device is characterized in that described equipment is suitable for realizing according to the described method of one of claim 1 to 14.
16, a kind of computer-readable medium stores computer executable instructions on it, be used for carrying out on wireless device, thereby realize according to any described method among the claim 1 to 14.
CN200610005828.1A 2005-01-10 2006-01-10 Mobile ip registration process for an always-on device Active CN1805448B (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
EP05100099A EP1679851B1 (en) 2005-01-10 2005-01-10 Mobile IP registration process for an always-on device
EP05100099.0 2005-01-10

Publications (2)

Publication Number Publication Date
CN1805448A true CN1805448A (en) 2006-07-19
CN1805448B CN1805448B (en) 2012-05-30

Family

ID=34938498

Family Applications (1)

Application Number Title Priority Date Filing Date
CN200610005828.1A Active CN1805448B (en) 2005-01-10 2006-01-10 Mobile ip registration process for an always-on device

Country Status (7)

Country Link
EP (1) EP1679851B1 (en)
CN (1) CN1805448B (en)
AT (1) ATE360323T1 (en)
DE (1) DE602005000928T2 (en)
ES (1) ES2285635T3 (en)
HK (1) HK1091068A1 (en)
SG (1) SG124354A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112968802A (en) * 2021-02-25 2021-06-15 紫光云技术有限公司 Universal method for managing IP state and relation of elastic public network

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8125954B2 (en) * 2007-05-04 2012-02-28 Futurewei Technologies, Inc. System for FA relocation with context transfer in wireless networks
WO2010051835A1 (en) * 2008-11-04 2010-05-14 Nokia Corporation An apparatus

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6160804A (en) * 1998-11-13 2000-12-12 Lucent Technologies Inc. Mobility management for a multimedia mobile network
US7734698B2 (en) * 2002-11-26 2010-06-08 Sony Ericsson Mobile Communications Ab Methods, systems and computer program products for non-intrusive subsequent provisioning of a mobile terminal

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112968802A (en) * 2021-02-25 2021-06-15 紫光云技术有限公司 Universal method for managing IP state and relation of elastic public network
CN112968802B (en) * 2021-02-25 2023-04-18 紫光云技术有限公司 Universal method for managing IP state and relation of elastic public network

Also Published As

Publication number Publication date
ES2285635T3 (en) 2007-11-16
CN1805448B (en) 2012-05-30
HK1091068A1 (en) 2007-01-05
ATE360323T1 (en) 2007-05-15
DE602005000928T2 (en) 2008-01-17
SG124354A1 (en) 2006-08-30
DE602005000928D1 (en) 2007-05-31
EP1679851A1 (en) 2006-07-12
EP1679851B1 (en) 2007-04-18

Similar Documents

Publication Publication Date Title
US7646753B2 (en) Mobile IP registration process for always-on device
CN1320843C (en) Method and apparatus for handoff of wireless packet data service connection
CN101345998B (en) Access network switch method, anchor point management equipment, mobile access equipment
CN1283126C (en) Methods and apparatus for mobile IP home agent clustering
CN1720757A (en) Method and apparatus for packet data service discovery
CN1679297A (en) Apparatus, method, system and software product supporting transition between network communication protocols
US20030067923A1 (en) Method for providing packet data service in a wireless communication system
US8224327B2 (en) Method and system for handoff of mobile node in mobile communication system supporting proxy mobile internet protocol
CN1675945A (en) Method and system of transferring session speed and state information between access and home networks
CN1774906A (en) Methods and apparatus for securing proxy mobile IP
CN1384648A (en) System and method for permitting IP mobile node to operate without seam in mobile IP network
CN1711792A (en) Method and apparatus for handoff of a wireless packet data services connection
CN1761359A (en) Mobile communication control method and communication control system
CN1902877A (en) Apparatus and method of controlling unsolicited traffic destined to a wireless communication device
CN1788520A (en) Link latency determination for mobile IP re-registration
CN103597863A (en) Methods and apparatus for determining address of a machine type communication device in a wireless network
EP1779629A1 (en) System and method for establishing dynamic home agent addresses and home addresses using the mobile ipv6 protocol
CN1736081A (en) Early determination of network support for mobile IP
CN102685712A (en) Mapping server in identity position separating network and implementation method thereof
EP1749391A1 (en) Method and apparatus for obtaining server information in a wireless network
CN1759587A (en) Telecommunications
CN1778090A (en) Methods and apparatuses for optimizing resource management in CDMA2000 wireless IP networks
CN101080891A (en) Method and apparatus to facilitate provision of an IPv6 prefix
CN1805448B (en) Mobile ip registration process for an always-on device
CN1902971A (en) Dynamic selection of a packet data serving node

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